CUCM sends sip CANCEL with no Reason Header if call canceled.

etitovets · ‎10-30-2019

Hi community,

User makes external call but cancel the call getting no answer.
If the user cancel the call, CUCM v10.5 sends sip CANCEL to the telephony provider.
But this CANCEL does not contains Reason Header with cause code.

Here is example:

CANCEL sip:9220010@10.0.0.2:5060 SIP/2.0
Via: SIP/2.0/TCP 10.0.11.3:5060;branch=z9hG4bK4d3ad9735fc177
From: <sip:1044@10.0.11.3>;tag=88198552~905238d3-a581-4a17-bbae-6fb37b748e36-92054025
To: <sip:9220010@10.0.0.2>
Date: Tue, 29 Oct 2019 11:42:09 GMT
Call-ID: 22770400-db812591-2a2f61-d0c000a@10.0.11.3
User-Agent: Cisco-CUCM10.5
CSeq: 101 CANCEL
Max-Forwards: 70
Content-Length: 0

The service provider requires Reason: Q.850;cause=16;text="Normal call clearing", in case of cancel the call.

Is it possible to force CUCM to send sip CANCEL with Reason header in case of cancel the call?

Thanks,

Yort Mantup · ‎10-30-2019

I may be misunderstanding this but if you are making an external call I assume the call is using a SIP Gateway which is where the the Cancel Q850 Cause Code 16 would generate from. Is there an issue when the user is hanging up an external call attempt?

etitovets · ‎11-01-2019

Hello Yort,

Yes, the issue is when the user is hanging up an external call attempt.
CUBE is used as SIP gateway. But the CUBE is just translating the CANCEL which it receive from CUCM.

Of course I can configure CUBE to add the Reason sip-header via sip profile. But if CUCM will send CANCEL with Reason header in another call situation then CUBE will add the second Reason sip-header Q850 Cause Code 16. The CANCEL will consist two Reason headers in this case. Am I right?