< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] enum support in resip


On 9/6/05, Jason Fischl <jason@xxxxxxxxxxx> wrote:
> On 8/31/05, Jason Fischl <jason@xxxxxxxxxxx> wrote:
> > Hi Nils,
> >
> > Thanks for your feedback. See inline.
> >
> > On 8/31/05, Nils Ohlmeier <lists@xxxxxxxxxxxx> wrote:
> > > Hi Jason,
> > >
> > > this really sounds great to me. Just two short comments from my own
> > > experience:
> > > - I would consider support for multiple enum suffix domains. Several 
> > > private
> > > ENUM branches showed up, and no matter if you like this or not, it should 
> > > be
> > > possible to query more then one branch before giving up.
> >
> > This seems like a good idea. Perhaps this argues for having a set of
> > enum suffixes carried around in the SipMessage - these could be
> > populated from the default set in the SipStack if none were specified
> > explicitly. An alternative would be to allow a comma seperated list in
> > the enumSuffix parameter.
> >
> > > - maybe requiring a specific URI parameter for doing ENUM lookups would 
> > > be an
> > > alternative to comparing the domain suffix. Although I'm currently not 
> > > quite
> > > sure what is the better/cleaner solution.
> > >
> >
> > I think what you are suggesting is what I meant. For example, the
> > following examples would do an enum lookup in the e164.org suffix.
> >
> > tel:+14155551212;enumSuffix=e164.org
> > sip:+14155551212@xxxxxxxxxxx;user=phone;enumSuffix=e164.org
> >
> 
> What is it that determines that an enum lookup should be done on a
> target URI? For now, is it safe to assume that an enum lookup should
> be done if the first character of the user portion of the URI is '+'?
> 
> We could additionally only do enum lookups if user=phone or for tel
> uris. Opinions?
> 
If the target URI is sips but the enum lookup produces a sip URI what
should the application do? Should it continue to use sips or assume
that the enum lookup failed?