SIP mysterious faiure

[meeko]

We've had SIP trunks operating on a pair of 3300s and two Audicodes SBCs. Within an hour of each other, the trunks on each controller went down and even after a reboot failed to re-register. The SBCs are complaining the Mitel isn't accepting a connection on UDP 5060, which is the configured SIP protocol and port. SIP maintenance commands don't return any output at all. SIP licenses are still allocated.

It's as if the SIP capability has been completely removed from the two controllers, and yet the configuration wasn't altered. Has anyone experienced this before?

[zac1234]

Have you tried running a capture on the 3300 using the SIP TCPDUMP maintenance command?  I would start there and use the SIP filter in Wireshark.  If you're not familiar with the SIP TCPDUMP commands then take a quick read in the help system (Maintenance -> Commands -> SIP).  Basically, you have to enter SIP TCPDUMP ON then generate some traffic.  Then stop it by entering SIP TCPDUMP OFF.  It saves the file in the /vmail folder.  I use WinSCP to retrieve the file or if you're at MiVB 9.0 then it can be retrieved from server-manager.  Once testing is complete, Mitel strongly recommends clearing the captures by using the SIP TCPDUMP CLEAR command.