Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Intel Customer Support will be observing the Martin Luther King holiday on Monday, Jan. 17, and will return on Tues. Jan. 18.
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646
1135 Discussions

SIP connectivity when MCU is behind a NAT

Vincent_R_1
Beginner
116 Views

Hi

I installed MCU v 3.3 on a new server which is behind a NAT.  MCU works great and i can connect multiple webRTC clients to it.  But i have issue with SIP.  It seems that the MCU conference is using the private IP of my MCU to register, so I guess this is probably the reason.

On my Kamailio server, the MCU conference is seen as Contact:: sip:conf-0x7fcf4c04d9b0@10.0.0.5:51993

Where can i change the internal MCU address (10.0.0.5) to its public address? 

Thanks a lot for the help.

-VR

0 Kudos
2 Replies
He_Z_Intel
Employee
116 Views

Normally Kamailio server listens to all NICs on your computer unless you configure it other way.

i would try something like this:

1. on kamailio, create an account for MCU with public IP: user name:" mcu@public.ip"

2. configure SIP connectivity username and server on the management portal

3. then i think it would work.

Vincent_R_1
Beginner
116 Views

Hi

I tried this - it did not work.  I also tried many other things on the Kamailio side, no success.

Note that my MCU and Kamailio servers are on different servers, different subnets, and that my MCU is behind multiple NATs.

So back to my question:  Is there any way i can make sure my MCU registered as mcu@public.ip instead of mcu@private.ip?

Thanks

-VR 

Reply