We have a SIP implementation that is working for the most part with no problems.
It has been in place for a while with no problems.
Recently we ported some local numbers to allow them to also use the SIP trunk, we have discovered that when calling a particular company local to us, with an especially long attendant message, the call disconnects after 30 seconds.
During the call and the company's openeing message, there are no prompts prior to the disconnect.
Calling from Cell does not exibit this problem.
Doing a "debug ccsip event" shows the following at termination, the BYE sip [email protected], is my extension and our CUBE router.
"Debug ccsip error" did not really show me anythigng that looked related.
083821: .Sep 7 15:12:30.012 EDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 220.127.116.11:5107;branch=z9hG4bK9itbu7200gcgsn0ps1i0sdmhjpk50.1
From: <sip:[email protected]>;tag=1369187014-1283886719404
To: <sip:[email protected]>;tag=AA5466D4-25BA
Call-ID: [email protected]
CSeq: 919489547 BYE
In order to troubleshoot the SIP call, is "event" the best tag to use?
With BYE message, is that my gateway terminating the message, or did it get received from the remote end?
Is there potentially a timeout happenign that would disconnect he SIP call with no input from the user?