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

Re: [reSIProcate] Find SIP server - RFC 3263


Dmytro,

X-ten is using NAPTR/SRV/AAAA/A records to find it.  The fact that the
name is sip.testdomain.com is purely arbitrary.

You didn't specify the OS but if you have access to a unix/linux system
do 'dig any testdomain.com' and see what the SRV and NAPTR records are.

3263 refrences 2782 which expects '_' in front of _sip._udp SRV but
there is an older definition (that it doesn't appear resip supports)
that doesn't have the '_' (RFC2052) that dates back almost 10 years
now.  If your DNS doesn't have the _ that may be the difference.  I
recently got bit on Cisco refering to this as a v1 and v2 that I wasn't
expecting.

Jay

Dmytro Bogovych wrote:

> On Fri, 13 Jan 2006 03:35:38 +0200, Alan Hawrylyshen
> <alan@xxxxxxxxxxxx>  wrote:
>
>> I do not understand your question. At present, reSIProcate will use
>> the  rules described in RFC 3263 to locate the correct SIP server to
>> send the  request to, using the full compliment of NAPTR, SRV, AAAA
>> and A record  lookups (and message processing).
>>
>> What is it that you are looking for, specifically?
>
>
> Smth like this:
> MasterProfile user;
> user.setRealm("testdomain.com");
>
> the real SIP registrar/proxy for this domain (testdomain.com)
> is sip.testdomain.com. It is written in DNS records - X-ten lite
> finds  them ok.
>
> What is the easiest way to implement such functionality?
>
>