[asterisk-users] Asterisk 1.8.7.2 now sends rport always

[José Pablo Méndez Soto]

Hey,

I have been testing with Cisco phones and have been able to register them
with new firmware 9.2.1 (7911/7945/7970). All worked until I realized that
from version 1.8.7.2, the VIA header contains the rport parameter, which
breaks the phone registration process. Basically, the device can´t parse
the VIA header this way, and when it gets the 200 OK to the REGISTER
message containing the rport parameter, it refuses to process the
registration internally, although it doesn´t complaint about it and
Asterisk shows it as registered.

Asterisk 1.8.7.1  doesn´t behave this way and all works fine. The
documentation about the use of the nat= parameter in sip.conf states:

;        nat = no                ; Default. Use rport* if* the remote side
says to use it.

I understand that the other side must send an empty rport parameter to
report the far end it needs the rport field to be filled in as per the RFC.
The IP Phone is not sending the field at all, generating incongruity
between the documentation and the real behavior. The only reason I think
Asterisk would find the condition to be true, is due to a mismatch between
the source port and VIA header ip:port inside the REGISTER message.

Could this be the trigger of the 200 OK with rport (and, other SIP messages
as well)?
Can it be implemented a nat = never option in future releases?

I believe this is of utmost importance as many deployments are based on
Cisco phones nowdays.

Thanks.


 *José Pablo Méndez
*********
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20111218/9f6519da/attachment.htm>