Troubleshoot VOIP Phone that receives calls but wont make them.

Jorge4757

Distinguished
Feb 4, 2014
5
0
18,510
Hello everyone I am currently employed as tech support and where I work I encounter this "weird" issue (hopefully there is a specific reason for this), basically its a VOIP Phone that connects trough a VPN tunnel using the internet from lets call it, Office-B to Office-A to the PBX server stored locally.

*I will provide a diagram to make it as clear as possible.
5E2F9588B.png


So I have this IP Phone connected to a 24 hub / really old 10/100 unmanaged switch inside an external warehouse, this switch is connected via Point-to-Point wireless antennas to a switch in the main office to get internet / LAN access; then it goes to the sonic wall appliance and that is connected the ISPs routers in this case AT&T, from there it goes to the VPN tunnel using the internet, in the other end of the tunnel there is a very similar structure but the phone its supposed to reach to the PBX on OFFICE-A which it does but it can only receive calls but it wont make calls, it kinda looks like it goes trough it rings once and choppy and then it says network disconnected.

Network Diagram


The VOIP phone I am using is a SNOM 300 and I tried to connect the same phone on OFFICE-B directly to the Switch and it will do the same I mentioned above, then I tried to setup the phone on OFFICE-A and it would work just fine, it doesn't matter whether or not its using 10.10.1.x or 172.20.20.x, the phone would work on OFFICE-A just fine.

Could you help me troubleshooting this issue or where can I start looking up?

Please also let me know if you need more information to begin with or tell me where should I post this so it gets more exposure since I really dont know if its right to put it here in the networking tab.


I intended to use wireshark in order to see at what point the packet stops or something similar, but I dont know how to set that up like what cables goes where, it might be an issue considering how much equipment its being used here.
 
Solution
Many times there are issues passing VoIP though firewalls. In SIP calls the ports that the end devices use are negotiated inside the sip data messages themselves. The phones normally are registered with some form of central call director and these session are TCP. The call setup between the end stations is all done via this session. This part normally works fine via a firewall since it is TCP on well known ports to a well known central call director.

What happens after everything is negotiated the ends stations attempt to send UDP data traffic directly between each other on what appears to outsiders as random UDP ports. The firewall needs a very special feature that can spy on the SIP messages and dynamically open these UDP...
Many times there are issues passing VoIP though firewalls. In SIP calls the ports that the end devices use are negotiated inside the sip data messages themselves. The phones normally are registered with some form of central call director and these session are TCP. The call setup between the end stations is all done via this session. This part normally works fine via a firewall since it is TCP on well known ports to a well known central call director.

What happens after everything is negotiated the ends stations attempt to send UDP data traffic directly between each other on what appears to outsiders as random UDP ports. The firewall needs a very special feature that can spy on the SIP messages and dynamically open these UDP ports. If you have encrypted SIP traffic this feature will not work. It is also this feature that allows these calls to go though a NAT dynamically, the firewall modifies the SIP messages on the fly...sorta a authorized man in the middle attack.

Check to be sure these option are correct. Not all firewall support this.....and if you are using H323 rather than SIP the list of supported firewalls is very small.
 
Solution