Hi. 1. NAPTR question - RFC 3263 eludes to using NAPTR resolution for an entire domain, for example, in order to find the ingress proxy for callee sip:[EMAIL PROTECTED], one needs to invoke the algo in RFC 2915 on the host/domain portion of the sip uri, i.e. example.com.
Is there a way to go down to granularity of user search? E.g. for [EMAIL PROTECTED] I want to go via specific ingress server (in the domain example.com) or perhaps even look this user in a diff domain...? 2. ENUM question - Say I am a VoIP operator (example.com) serving all the 1000 users of +1-978-123-xxxx, but one. The user +1-978-123-6789 is to be served by the VoIP operator (diffop.com). How would I design my ENUM DB to reflect that? Where would my ENUM DB (name server) be located on the E164.arpa tree? (Will it be "located" both at 3.2.1.8.7.9.1.e164.arpa and at .9.8.7.6.3.2.1.8.7.9.1.e164.arpa or only at 3.2.1.8.7.9.1.e164.arpa with specific ENUM/NAPTR record for the user 6789?) Thx -uri _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
