Scenario Carrier ===> Kamailio ===> Ext on domainINVITE ===> ====> 200 OK <== <=== Repeated because carrier pcap shows private 192.168 IP in Contact header. cfg has WITH_NAT setup. I assumed that all I need to do. What more is required to get Kamilio IP and port in 200K to Carrier? K
On Fri, May 04, 2018 at 04:51:48PM +0000, KamDev Essa wrote:
What more is required to get Kamilio IP and port in 200K to Carrier?
That's not what you want to do, and it would not result in working behaviour. The Contact URIs need to be of the respective user agents for in-dialog requests to be routed correctly.
What you really need are the server-side NAT traversal folk traditions of the nathelper module. Examples of its use abound, including in the stock Kamailio config.
WITH_NAT automatically loads nathelper. Its in the stock cfg. #!ifdef WITH_NATloadmodule "nathelper.so" Does the stock cfg have to be tweaked any further to get this to work? KD On Friday, May 4, 2018, 12:55:36 PM EDT, Alex Balashov abalashov@evaristesys.com wrote:
On Fri, May 04, 2018 at 04:51:48PM +0000, KamDev Essa wrote:
What more is required to get Kamilio IP and port in 200K to Carrier?
That's not what you want to do, and it would not result in working behaviour. The Contact URIs need to be of the respective user agents for in-dialog requests to be routed correctly.
What you really need are the server-side NAT traversal folk traditions of the nathelper module. Examples of its use abound, including in the stock Kamailio config.
-
Alex Balashov -
KamDev Essa