cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
244
Views
0
Helpful
4
Replies
Highlighted
Beginner

CUCM sends SIP BYE when call is placed on HOLD

I have read a lot of places that when a call is placed on HOLD, a SIP reINVITE is sent to UAS but in my case, a BYE event is sent. Below is such a BYE EVENT. This is received when the call is placed on HOLD.

Via: SIP/2.0/TCP 192.168.1.48:5060;branch=z9hG4bK3ff319b4c8;rport=45837
From: <sip:2702@192.168.1.48;x-nearend;x-refci=22278999;x-nearendclusterid=BR-Cluster2;x-nearenddevice=sikander2;x-nearendaddr=2702;x-farendrefci=22278998;x-farendclusterid=BR-Cluster2;x-farenddevice=sikander1;x-farendaddr=2701>;tag=1687~00d3be95-408b-41c6-90cf-01ef66258892-22279003
To: <sip:88888@192.168.1.124>;tag=7a132c30
Date: Mon, 20 Jul 2020 12:40:41 GMT
Call-ID: 373f7000-f15190c9-198-3001a8c0@192.168.1.48
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
P-Asserted-Identity: <sip:2702@192.168.1.48>
CSeq: 102 BYE
Session-ID: 00000000000000000000000000000000;remote=e09eaac54aa612f7f1b180eeebab1687
Content-Length: 0

Any leads?

4 REPLIES 4
Highlighted
Contributor

@sikanderhayat Single SIP message will not help to trace the issue.

from the message i guess you have 2 extensions 2701 and 2702 on two different CUCM cluster.

Can you tell the route pattern 88888@192.168.1.124 pattern routing to?

 

Please describe the call flow and components involved so as forum members can understand your architecture and help you to solve the issue.

*** Please rate helpful post. Please mark as answer if it solves your problem/query.
regards, Ritesh Desai
Highlighted

@Ritesh Desai 

The route pattern 88888@192.168.1.124 is pointing to my recorder app configured in SIP trunk.
Both my extensions (2701 and 2702) are on the same CUCM cluster. 2702 recording is enabled and an agent is logged with that extension on Finesse (UCCX). I am making a call from 2701 to 2702. Agents answered and I get SIP Events for both legs of the call. When Agent places the calls on HOLD, I get BYE SIP Events from both legs (Example shared above). Shouldn't the SIP Client send reINVITE instead of BYE?

Highlighted

@sikanderhayat What kind of call recording solution you have interated UCCX with? Verint, Calabrio, NICE?

*** Please rate helpful post. Please mark as answer if it solves your problem/query.
regards, Ritesh Desai
Highlighted
Beginner

Moreover, when the call is ended by Agent of Finesse(2702, recording enabled), the BYE event has got Reason header and when ended by 2701 (recording disabled), there is no reason header in SIP BYE event. Below are examples;

 

When ended by agent,

Via: SIP/2.0/TCP 192.168.1.48:5060;branch=z9hG4bK3db43e83a6c;rport=39302
From: <sip:2702@192.168.1.48;x-farend;x-refci=22278955;x-nearendclusterid=BR-Cluster2;x-nearenddevice=sikander2;x-nearendaddr=2702;x-farendrefci=22278954;x-farendclusterid=BR-Cluster2;x-farenddevice=sikander1;x-farendaddr=2701>;tag=1661~00d3be95-408b-41c6-90cf-01ef66258892-22278978
To: <sip:88888@192.168.1.124>;tag=f678968f
Date: Mon, 20 Jul 2020 12:08:44 GMT
Call-ID: c0a07380-f151894c-184-3001a8c0@192.168.1.48
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
P-Asserted-Identity: <sip:2702@192.168.1.48>
CSeq: 102 BYE
Reason: Q.850;cause=16
Session-ID: 00000000000000000000000000000000;remote=e09eaac54aa612f7f1b180eeebab1661
Content-Length: 0

And when ended by far-end (2701)

Via: SIP/2.0/TCP 192.168.1.48:5060;branch=z9hG4bK3e27a480e86;rport=39302
From: <sip:2702@192.168.1.48;x-farend;x-refci=22278980;x-nearendclusterid=BR-Cluster2;x-nearenddevice=sikander2;x-nearendaddr=2702;x-farendrefci=22278979;x-farendclusterid=BR-Cluster2;x-farenddevice=sikander1;x-farendaddr=2701>;tag=1666~00d3be95-408b-41c6-90cf-01ef66258892-22278987
To: <sip:88888@192.168.1.124>;tag=209282f
Date: Mon, 20 Jul 2020 12:11:02 GMT
Call-ID: 12e19480-f15189d6-187-3001a8c0@192.168.1.48
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
P-Asserted-Identity: <sip:2702@192.168.1.48>
CSeq: 102 BYE
Session-ID: 00000000000000000000000000000000;remote=e09eaac54aa612f7f1b180eeebab1666
Content-Length: 0
Content for Community-Ad