Re: [reSIProcate] enum question
Jason Fischl wrote:
As currently implemented, enum lookups are performed at the same place
in the transaction layer where other dns lookups (NAPTR, SRV, A, AAAA)
are done. This means that if I send a request to the stack targeted at
tel:+14155551212 that the dns resolver checks to see if the number can
be resolved using enum and if so it forwards the request to the sip
url that the number maps to. e.g. sip:directory-assistance@xxxxxxxxxxx
Currently, the Request-Line is left unmodified. The question is,
should the stack rewrite request-uri to be the sip url or should it
leave it as a tel url?
Hi Jason!
The request URI should be changed to the URI found in ENUM.
regards
Klaus
Consider the following example:
UA1: a@xxxxxxxxxxxx
Proxy1: example1.com
UA2: b@xxxxxxxxxxxx ---> tel:+14155551212
Proxy2 example2.com
If UA1 dials tel:+14155551212 the request gets routed to example2.com.
If UA1 (or Proxy1 on behalf of UA1) doesn't rewrite the request-uri to
be sip:b@xxxxxxxxxxxx then proxy2 will have to determine (perhaps
through an enum lookup of its own) that it is responsible for the
dialed number? This is more significant if proxy2 is really just an
edge proxy and doesn't have direct access to example2.com's location
service.
What do folks think?
Jason
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel