Open a jira.
On 11/24/2011 08:50 PM, Tony Graziano wrote:
I have noticed whenever there is an issue with sipx notbeing able to
authenticate to a sip trunk provider, it gets tuck on "AUTHENTICATING"
and does not have a timeout or recycle mechnim to stop and try again
after xx seconds.
The end result is that when it is not authenticated and it fails, it
becomes necessary to restart trunking (which may require bringing down
already authenticated trunks).
I think there should be a watchdog timer when trunking is active to
restart the gateway if it does not authenticate after xx seconds (then
sleep for 10 and retry, etc.). This will help it to auto-recover in
the event there is an issue with the connection or the provider.
Any thoughts?
--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
<mailto:[email protected]>
Fax: 434.465.6833
Email: [email protected] <mailto:[email protected]>
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
<mailto:[email protected]>
Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
