When I make an outbound call from Asterisk softphone and remote the party ends the call instead of accepting it and the call is connecting from originating end and we did not get the bye/disconnect message from the router end. When outbound calls are initiated from Microsip and the call is connected and get the bye/cancel message is received from the Asterisk end. when we initiate a call from the router end (By Csim command) we got the bye/cancel/disconnect message from the other end when the remote party disconnects the call without accepting the calls. please find the call flow
Could you please confirm any Sip parameter needs to be set at the PABX end so that we can get bye/disconnect message when we cancel the calls instead of accepting it.
Cisco Gateway Logs.txt (2.9 KB) Asterisk Issabel PABX Log.txt (11.6 KB)
I have uploaded the logs along with comments in the logs as I have got Sip 400 bad request message at PABX logs when we disconnect the call please let us know what changes need to be done at the PABX end or the Router end.
*Apr 16 00:25:38.150: ISDN Se0/1/0:15 Q931: DISCONNECT pd = 8 callref = 0xD41C----------------------call disconnect message receivd from Cisco Router when remote party end the calls
Cause i = 0x80ED - Unknown cause value
The far side of the ISDN link on the other side of the Cisco rejected the call with no meaningful explanation. 400 does not seem to be the right error, but then it is Cisco an they can make the rules.
As the caller ID and called number are different lengths, but both of unknown format, I’d suspect that the caller ID wasn’t acceptable. I’m not sure why the other end of the ISDN sent Alerting, if they didn’t like the numbers, though.
400 is invalid request, as it says in the message, A disconnect from the far side, with an unknown reason doesn’t seem to be sufficient evidence that the request was invalid. If it was invalid I would not have expected the Cisco to try to start the ISDN leg of the call.
Bad Request is defined as:
21.4.1 400 Bad Request
The request could not be understood due to malformed syntax. The Reason-Phrase SHOULD identify the syntax problem in more detail, for example, “Missing Call-ID header field”.
and I would have interpreted that to mean that the Cisco could not understand the request.
The reason it quotes also isn’t helpful (although I suppose it covers getting a response code that it doesn’t understand , from the ISDN network):
Cause No. 111 - protocol error, unspecified [Q.850]
This cause is used to report a protocol error event only when no other cause in the protocol error class applies.
Unknown number format means that it is not in one of the standard ISDN formats, and typically means it is the form that a user would manually dial it.
One other point, if this should get into details of the Issabel dialplan and its GUI setting, this is not an appropriate forum, as there is little knowledge of its internals here. They have their own forum although all the postings seemed to be in Spanish.
I think the clearing cause on the far side of the Cisco is 109 (0x80ED & 0x7F, converted to decimal). None of the lists of Q.850 codes, that I checked, lists that, so I think the Cisco diagnosis that it is unknown is correct. You will have to ask whoever operates the far end of the ISDN what it means.
I would expect the caller ID and called number to be in the same format, but, again, you would need to ask the people at the other end of the ISDN. They may not like “unknown” format numbers at all. I don’t know if the Cisco will pass through international format , even if the SIP is configured to indicate that.