Hi,
On Fri, 5 May 2006, Colin Whittaker wrote:
But I guess in your case the algorithm doesn't work. As your server has a
private IPv4 address, Sofia will enter "NAT-mode", but it doesn't notice
I think this is a common enterprise architecture. A local proxy/SBC also
behind the NAT/firewall for internal PBX functionality.
What exactly is "NAT-mode" ?
yes, definitely nothing wrong with the setup and the problem of
re-registrations needs to fixed.
As for the NAT mode, it's just an alternative code path in the
registration code that tries to decide how to perform the registration
(especially deciding whether to use sip-outbound and rport). See
documentation in libsofia-sip-ua/nua/nua_register.c:nua_stack_register()
to see the steps currently taken.
Of course, it is important that this logic will not break SIP-proxies/SBC
that try to do the same thing at the network end. Please let us know if
you have a case where the above mechanism causes problems..
--
under work: Sofia-SIP at http://sofia-sip.sf.net
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
