I just had a case where an ITSP returned "500 Server Internal Error" to a REGISTER request from sipXbridge.
sipXbridge had been successfully re-registering with the ITSP every 5 minutes for the last several days, so I've no idea why the ITSP suddenly sent this return response. The problem is that sipXbridge did not raise an alarm about the condition, and more worryingly, from then appears to have made no further attempts to re-register with the ITSP until I manually restarted SIP Trunking 7 hours later, whereupon a successful registration was immediately made. There was not a single log sipxbridge.log entry after the 500 Server Internal Error was received from the ITSP 7 hours previously, although sipXbridge was shown as still "Running" in System->Servers->Services. Before I submit this as an issue in JIRA, can anyone confirm if this is the proper behaviour of sipXbridge, or have I found a bug? Using build 3.11.12-015038 2009-03-31T14:01:59 ecs-centos5 Thanks, J _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
