multiple pbx behind NAT firewall

314 views
Skip to first unread message

Doug Mattingly

unread,
Dec 9, 2013, 10:26:55 PM12/9/13
to 2600h...@googlegroups.com
I have currently set up a single legacy asterisk pbx to a cloud kazoo pbx connector.  The legacy pbx is behind a nat firewall with a range of signalling (5060-5067) and RTP(10000-20000) audio ports forwarded to it and it has some offsite phones.  I would like to connect a couple other pbx's to the cloud kazoo pbx connector for developmental purposes (including a local kazoo installation if possible).  The development pbx's will only have local phones attached - no offsite phones.  So I'm trying to determine what ports, if any need to be forwarded to them and if I need to use another public fixed IP address for each PBX.  Since you generally need to forward ports to servers but not to clients and since the development pbx's are acting as clients to the cloud kazoo and are not acting as servers to any offsite phones, my first thought is that I don't need to forward ports to them.  But then I know SIP acts a little different in this regard than most other applications.  Any thoughts are welcome.

Thanks,
Doug

Darren Schreiber

unread,
Dec 9, 2013, 10:45:22 PM12/9/13
to 2600h...@googlegroups.com
There is a general misconception in the world that somehow the remote server dictates what ports need to be open. This is not how it works.

The ports you use on your side are up to you. In Asterisk there should be a way to configure the local RTP and SIP ports. Those are the ports your side requests when receiving SIP and audio via RTP. You would forward whatever ports you opened on your side.

It really shouldn’t have anything to do with Kazoo. That said, Kazoo will try to fix NAT if the public IP and ports your PBX presents are wrong. So make sure you are presenting a proper public IP from your side so Kamailio does not try to fix them.


--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Doug Mattingly

unread,
Dec 16, 2013, 4:13:51 PM12/16/13
to 2600h...@googlegroups.com
Thanks Darren.  I now have 2 different asterisk boxes connected to a carrier but I still cannot get my local kazoo installation to register to a carrier.  For testing purposes, I'm trying to connect a locally installed kazoo to my cloud kazoo account using the cloud's pbx connector (is that even possible?).  I have used the private IP address throughout the kamailio/local.cfg file.  I set up acls in ecallmgr using the IP address of my cloud kazoo account.  Is there anything else I'm missing?

By the way, my goal here is to connect the locally installed kazoo to my current SIP provider and use it to route phone numbers to local pbx's as I slowly migrate completely off of the legacy pbx. When my current provider contract is expired, I intend to port the phone numbers to the cloud kazoo account.  Will the local kazoo installation route phone numbers from a non-kazoo carrier via the pbx connectors?

Thanks again for all the help.
Doug
Reply all
Reply to author
Forward
0 new messages