Search the Community
Showing results for tags 'NAT'.
Hi, Here is our issue. Hopefully someone has some ideas as we are stuck right now: 1) Two main offices each with their own snomONE (4.5) and a bunch of remote offices connected via ipsec VPN and a bunch of floating sip phones connecting via public internet to either of the main PBXs 2) All calls between offices and phones work perfectly and have been like that for the last 5 years or so until we recently had to switch phone providers and had to create a new SIP trunk instead of the old analog trunk we were using. 3) For the SIP trunk to work, we have tried every single setting and configuration we can think of. The only way we manage to make sound travel in both directions (the PBXs are being a Meraki firewall with the correct ports opened and NAT) is to add to the snomONEs a IP Routing List entry like 18.104.22.168/255.255.255.0/192.168.0.7 0.0.0.0/0.0.0.0/22.214.171.124 With this entry, the new SIP trunk work perfectly BUT we loose connectivity of the remote phones. Moreover, the calls between extensions between the main offices only last less than 2 minutes before the call gets dropped. Any ideas? Thanks all for the help Nathan
Hi everyone, I'm trying to use Vodia PBX on one of my Ubuntu server hosted at OVH. Installation was ok, the trunk SIP given by OVH was ok too and I created two extensions for phones that I have at work. Everything was working for the best. But yesterday, my company wanted to add a firewall (Fireware XTM WatchGuard). So now I have a private IP address for my PBX and all traffic is going to the firewall which redirects everything, as you can imagine. I opened all the ports needed, I think at least. The biggest problem I have now is that there is no sound when I try to call someone. I tried to open RTP ports configured in the PBX, to see if it can be another hidden option but I got nothing. Do you have any solution I could try? After spending so much time on it, any idea will be really appreciated. Sorry for my english if you see something wrong. Cheers, David