NAPTR resolution

[Nikolay Kondratyev]

Hi,

We use pbxnsip version 3.0.1.3023 (Centos).

I have set up a trunk with outbound proxy "m600.lab.nstel.ru".

Pbxnsip does NAPTR lookup for "m600.lab.nstel.ru" and gets two records:

 

[8] 20081212172627: DNS: Add dns_naptr m600.lab.nstel.ru 20 10 s SIP+D2U - _sip._udp.m600.lab.nstel.

ru 25 15 s SIP+D2T - _sip._tcp.m600.lab.nstel.ru

 

My understanding of rfc 3263 and 2915 is that a client must select a transport acoording to the lowest 'order' field in the NAPTR record.

In my case it should be UDP, nevertheless pbxnsip uses tcp when sending calls to m600.lab.nstel.ru.

 

My opinion is that this behavoiur does not correspond to the standards.

Am i correct?

Please clarify...

 

Thanks in advance,

Nikolay.

[Vodia PBX]

We use pbxnsip version 3.0.1.3023 (Centos).

I have set up a trunk with outbound proxy "m600.lab.nstel.ru".

Pbxnsip does NAPTR lookup for "m600.lab.nstel.ru" and gets two records:

 

[8] 20081212172627: DNS: Add dns_naptr m600.lab.nstel.ru 20 10 s SIP+D2U - _sip._udp.m600.lab.nstel.

ru 25 15 s SIP+D2T - _sip._tcp.m600.lab.nstel.ru

 

My understanding of rfc 3263 and 2915 is that a client must select a transport acoording to the lowest 'order' field in the NAPTR record.

In my case it should be UDP, nevertheless pbxnsip uses tcp when sending calls to m600.lab.nstel.ru.

 

My opinion is that this behavoiur does not correspond to the standards.

 

Well... Today NAPTR is practically non-existant. The PBX should sort after the priority, not sure what'S wrong here... But IMHO the best way to deal with this is to avoid NAPTR at all. It is asking for trouble, and we don't want that!