Mitel 5000 SIP Trunks lockup and require a system reboot ??

[Nathan]

Hi Everyone

i have multiple Mitel 5000s installed on SIP Trunks with different providers, intermittently they require a reboot as all inbound calls stop working

i can see the SIP is still connected/Registered with the provider a 200 OK
because the SIP is still registered when this happens the calls don't follow the failover destination setup by the SIP provider either 

i can take the service in and out of service this makes no difference to the inbound calls until i reboot the system then it works fine for a few weeks until it happens again

has anyone else experienced this ??

[sarond]

What type of firewall are you running?

We had an issue recently with a Sonciwall and Telstra IAD on NBN.
The Sonicwall UDP NAT Connection Timeout was only set to 30sec by default, so we could register and make calls after the registration but if the calls were idle for longer than the 30sec they would stop as the connection was closed.
Telstra were set to register every 180sec so we increased the UDP Connection time to 240sec and haven't had a problem.

You could try enabling keep-alive on the MiVO250 to keep the connection open by sending SIP OPTIONS to the peer.
System/Devices and Feature Codes/SIP Peers/SIP Trunk Groups/{SIP Trunk Group}/Configuration/Keep-Alive

[Nathan]

Thanks for the reply

i have Keep Alive set on for all the systems its in the default setting
Ping - YES
ping interval - 60sec
ping failure threshold - 1

most sites are running a Mikrotik router as the gateway with various internet connections - NBN - 4G - HFC etc

we are using commander as the primary SIP provider at present 

[b_hackbarth]

On the back of the chassis is an aux ethernet port that is bridged to the LAN port.  Connect up to this and run a wireshark capture, wait for the failure, then start at the bottom of the capture and start moving your way up for clues.

What software revision is the controller running?

[kmcanally]

Were you able to resolve this issue? And if so, what did you discover? We are facing a similar issue where the customer is unable to make or receive calls, despite the SIP logs showing TX/RX continuing to occur up to the point of the reboot. Once the reboot is performed the issue is fixed. It seems that whenever a network event occurs, latency, outage, etc.. the 5000 never recovers, and must be rebooted. Call Failure Threshold is set to 0. Keep Alive has been verified as enabled, Re-Registration attempts raised from default of 5 to 100. Currently running 6.2.5.80 sw.

[Tech Electronics]

kmcanally,

How long had the trunks been working fine before this issue started happening. You are not at the most current version of 6.2 either so you could try upgrading to 6.2 SP 2 PR6 [6.2.5.93] as there are a few SIP fixes between your version and the latest one.

If you are feeling adventurous you could go to the latest and greatest 6.3 as it has a few pages of fixes associated with it on various aspects of system operation.

Thanks,

TE

[NTEDave]

6.3 seems to be really good at recovering from network outages, recently we installed a 250 running Gamma SIP trunks in the UK.

We had a lot of trouble with the Broadband AND router during install and whenever the internet connection went off then back on the SIP trunks just re-connected and started working again.