Mitel 3300 SIP Trunk Looses Registration

[ralph]

I had an issue the AM with a customer where they loose their SIP trunk registration.

I get this log:
SIP trunk Broadvox2 Account <blanked> Registrar <IP Address Blanked> failed to register due to possible incorrect username and/or password.

To resolve, all I do is go into the SIP Peer Profile and make any change, save it and change it back.
(I changed the interconnect restriction)
This forces the trunk to re-register.

My questions are these:
1 - What would cause it to loose registration.
2 - Why wouldn't it simply retry to register on it's own without me having to reset the SIP Peer Profile.

Ralph

[brantn]

1.) I would venture to say that Broadvox made some change on their SBC or 2 some other device is trying to use the account info those are the only times I have seen a registration issue outside of network/hardware issues.

2.) It does try again depending on heartbeat time set by the provider and controller depending on when it is set to reregister 60 minutes or so on. By editing the form you are simply forcing the reregister.

[ralph]

2.) It does try again depending on heartbeat time set by the provider and controller depending on when it is set to reregister 60 minutes or so on. By editing the form you are simply forcing the reregister.

The trunks went down ~4:00 am.   I brought it up at 10:00AM.
I can't check the profile from where I'm at but it would appear it didn't try to re-register any time until I got to it.
Should I see a log of the retry?

Ralph

[brantn]

Yes you should see a reregister log I believe sounds like it is set for an extreme period of time at the vendor probably to minimize extra network traffic on their end. You should also see it by doing a sip capture.

[ralph]

Here's where I'm at with this:
My SIP trunks are still loosing it's registration.
I have alarm emails turned on so the net effect is a get an Critical Alarm followed 1 second later by a clear.

I suppose I could live with that except every once in a while I get a log that says
"SIP trunk <carrier> Account <account> Registrar xxx.xxx.xxx.xxx failed to register due to incorrect username and/or password."

From there I have to make a modification to the SIP peer and then change it back.  This forces the registration again.

Has anyone seen anything like this before?   I'm struggling to figure out if I have a Mitel, firewall or carrier issue.

Working on getting a capture now from both the carrier and one on the Mitel.

Ralph