I've seen this problem too. What I've noticed is that after about 11
minutes the service tries to register again. It might be as simple
as just reducing the timeout before it retries.
Thanks,
Tim Ingalls
Shared Communications, Inc.
801-618-2102 Office
On 11/25/2011 07:46 AM, Philippe Laurent wrote:
Voted.
On Fri, Nov 25, 2011 at 9:42 AM, Tony
Graziano <[email protected]>
wrote:
On Fri, Nov 25, 2011 at 7:45 AM,
Joegen Baclor <[email protected]>
wrote:
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.
