IPO Gamma SIP wierdness 1

[OldAndKnackered]

Two separate companies, both with IPO 500 V2, one on 8.1(67), the other on 9.0.4. Both have Gamma SIP in and working, for over 2 years in the case of the 8.1 system, and 5 months for the other. The one with the 8.1 system has a Draytek router, the 9.0 had a Barracuda firewall. Both systems go down due to power (one planned, the other not), over the weekend. The SIP won't come back on. The only way to get it back again, has been to bypass the firewall/router and give the system an external address and tie down what it can talk to in IP routes. The company with the Barracuda are a computer consultancy and know how to configure firewalls. Does anyone know if anything that could cause this?

Regards
Cat

 

[derfloh]

That's a bad workaround. Perhaps the firewalls were running on a configuration that has not been saved and has been lost during reboot.

 

[OldAndKnackered]

I know it's not ideal, but until it can be determined what the underlying issue is, I don't have much choice, as they need a working system.

 

[Pepp77]

Simple test for Gamma SIP is to run STUN and ensure you get a valid response as Gamma SIP trunks utilise the STUN for every phone call. I had a site where I couldnt get calls to work properly and couldnt see why, turned out I had an IP route sending STUN requests to the wrong LAN port (STUN was statically assigned and not set to run on startup so didnt show failures).

| ACSS SME |

 

[amriddle01]

I have seen this BTW, in my case I was able to prove the Draytek was not forwarding the packets as it should, there was no SIP Rx at all...it worked at first but then stopped, bypassing the Draytek for testing purposes proved Gamma were responding. I think IT swapped out the Draytek in the end. We have had to bypass/replace Drayteks on many occasions where SIP issues just keep occurring and they always go away instantly

 

[OldAndKnackered]

Happened again,

This time is an IPO 500 V1 on vers 9.0 with a sonicwall firewall. Everything was working upto some point last week when they had an issue with the line the SIP was using/firewall, after they rebooted it, it hasn't worked. If I manually set the external IP address, set the firewall type to Open Internet, and set the ports, incoming calls work, but cut off after about 30 seconds. If I run STUN, the lines show as out of service. Gamma are saying that "The VIA header on which the SIP authenticates has a private IP address W.X.Y.Z.so the call is 403 rejected". Any ideas appreciated.

 

[janni78]

You can't set firewall type to Open Internet as then it won't send the Public IP in the SIP header.
Trying setting it to Blocking Firewall and make sure you use the correct LAN interface on the SIP lines Transport tab.

"Trying is the first step to failure..." - Homer