Anyone experienced SIP Trunks refusing to attempt a registration?
I have had several instances where after a few minutes of failed registrations the controller refuses to attempt to register again regardless of any changes to the SIP Peer for or Network Elements.
SIP REREGISTER PEER command indicates it was submitted, but packet capture confirms no registration attempt was output.
Likewise saving the SIP Peer form, disabling and enabling the Network Element, and BUSY FORCE/RTS all don't enable it to send out another registration attempt.
Only solution I have found is to reboot the controller, which in some instances I have had to do 5-6 times to try different things to get it working.
Seems like there is some sort of a failed attempt counter that needs to be reset?
Anyone come across this, or better yet have a solution?
I have had several instances where after a few minutes of failed registrations the controller refuses to attempt to register again regardless of any changes to the SIP Peer for or Network Elements.
SIP REREGISTER PEER command indicates it was submitted, but packet capture confirms no registration attempt was output.
Likewise saving the SIP Peer form, disabling and enabling the Network Element, and BUSY FORCE/RTS all don't enable it to send out another registration attempt.
Only solution I have found is to reboot the controller, which in some instances I have had to do 5-6 times to try different things to get it working.
Seems like there is some sort of a failed attempt counter that needs to be reset?
Anyone come across this, or better yet have a solution?
