I have noticed this as well. I have seen a few configs like your DUNDi
setup, that use the fullcontact URI to directly contact a phone. I was
always puzzled how everyone was making this work with NAT.
I have not looked into it much yet, but I wonder if the new netfilter
SIP conntrack/NAT extension might help overcome this issue?
Regards,
David
On 12/3/06, JR Richardson <[EMAIL PROTECTED]> wrote:
Hi All,
Has anyone else noticed that when a sip phone sitting behind a nat
registers to asterisk using realtime database, the private IP of the
phone is put into the fullcontact field instead of the public contact
IP. The database has the correct public IP in the ipaddr field and
correct port number in the port field, which is actually what asterisk
uses to to contact the device.
This eliminates the ability to use the fullcontact URI to directly
contact the nat'ed phone. Works great for non-nat'ed devices.
Is this by purpose or an oversight the way Realtime pulls the correct
contact info in the sip registration header from the device?
Does anyone know how to correct this behavior? It is the same with
nat=yes or nat=no.
Thanks.
JR
--
JR Richardson
Engineering for the Masses
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
