Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by shamesaaron

  1. On 1/20/2021 at 10:09 AM, Meat said:

    The below works in AWS.  I haven't worked much with Azure's networking environment, but I can't imagine (well, I can, it's Microsoft) that the DNAT / SNAT workings are too different.  Assign PUB IP to instance/interface, then just change the below configs in Kamailio and Freeswitch.  If you're using an all-in-one, then you'll just need one PUB.  I've got a clustered setup going with my Kama and FS instances separate. 

    On Freeswitch -  Remember FS trunks directly out of the cluster.  It does not route out back through Kamailio.  

    nano /etc/kazoo/freeswitch/sip_profiles/sipinterface_1.xml

    Set <param name="ext-rtp-ip" value="auto"/>   to    <param name="ext-rtp-ip" value="x.x.x.x."/>     (x.x.x.x is the external IP you have assigned to this instance)
    Set <param name="local-network-acl" value="localnet.auto"/>  to   <param name="local-network-acl" value="NOPE"/> # “NOPE” doesn't matter, just not localnet.auto

    On Kamailio

    nano /etc/kazoo/kamailio/local.cfg  

    Should be down at the bottom of the file.  The advertise flag essentially tells Kamailio what to change the IP to when it detects NAT.

    listen=UDP_SIP advertise x.x.x.x:5060 
    listen=TCP_SIP advertise x.x.x.x:5060

    (where x.x.x.x is your public IP address you assigned)

    I believe that's it.  Hopefully that'll help.


    Can confirm, applied these settings to a sandbox deployment without a bindable external IP and everything worked perfect.

  2. I don't think he is looking for alternatives to Azure.  He wants to know how to get Kazoo to work within Azure Cloud.

    The only issue I can think of is Kamailio not being able to bind to the external IP.  Does anyone have config examples of how to use Kamailio when it cannot bind to the external IP?  I know someone had got Kazoo working within Docker which would have required a similar type of config.

  • Create New...