Jump to content

Meat

Members
  • Posts

    9
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Meat

  1. Hey Tommy,

    I would highly suggest you look at this post for help getting Kazoo working behind a NAT.  This discusses using Azure and AWS, all of which use NAT'ng.  Should get you all squared away... 

     

    And to directly add some guidance to your question there, if your signaling is working correctly then you've most likely got Kamailio setup correctly (still double check with link above).  Freeswitch is what handles your media in the Kazoo setup and it needs to be told as well that it's behind a NAT.  

  2. 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.

     

  3. Hello Community,

    I'm entirely sure this is the correct place for this post, but I didn't see anywhere else more appropriate. 

    I'm looking to source some development help to transition our current web and phone applications over to Kazoo from a proprietary system in use now which offers Vmail, PBX, and Live Ansering (ACD) services.  Everything is currently API driven now using an MVC (Cake) framework, so essentially we just need someone to possibly use the SDK that's already built https://github.com/2600hz/kazoo-php-sdk (update if necessary) and then go through the process of building the library into our system. Documentation already exists for the existing system, so it shouldn't be a difficult task for someone(s) familiar with Kazoo to come in and accomplish.  This is for a well established business of nearly 20 years and we have developers in house to assist but want to get this done ASAP.  

    I have already setup a working cluster with just an issue or two that I would like assistance in correcting.  An example being no audio on WebRTC calls but soft phones and your run of the mill sip phone work flawlessly.  I'm well versed in Asterisk and have a fairly good understand of Kamailio, just not yet there with Freeswitch. So some advise on layout, and some development on the above mentioned project is what I'm after.

    Can someone point me in the right direction here to source that? 

×
×
  • Create New...