05-21-2018 06:22 AM
Hi guys,
We have a BIB recording system, and it works fine without TLS supported.
But now we are facing a problem while supporting TLS.
We already setup certificate and SIP trunk with TLS and CUCM and recording have exchange SIP message successfully.
The question is:
After CUCM:INVITE, recorder:200, CUCM:ACK, CUCM send a BYE immediately.
Following is the follow for an example:
INVITE sip:7777@192.168.1.68:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK3399730b01b6
From: <sip:371@192.168.1.126;x-nearend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13197~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253128
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336a-7e01a8c0@192.168.1.126
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: Geolocation
Call-Info: <sip:192.168.1.126:5061>;method="NOTIFY;Event=telephone-event;Duration=500"
Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000
Cisco-Guid: 0868011136-0000065536-0000000029-2114037952
Session-Expires: 1800
P-Asserted-Identity: <sip:371@192.168.1.126>
Privacy: none
Remote-Party-ID: <sip:371@192.168.1.126>;party=calling;screen=yes;privacy=off
Contact: <sip:371@192.168.1.126:5061;transport=tls>;isFocus
Max-Forwards: 70
Content-Length: 0
INVITE sip:7777@192.168.1.68:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339a731ae306
From: <sip:372@192.168.1.126;x-nearend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13198~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253129
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336b-7e01a8c0@192.168.1.126
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: Geolocation
Call-Info: <sip:192.168.1.126:5061>;method="NOTIFY;Event=telephone-event;Duration=500"
Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000
Cisco-Guid: 0868011136-0000065536-0000000030-2114037952
Session-Expires: 1800
P-Asserted-Identity: <sip:372@192.168.1.126>
Privacy: none
Remote-Party-ID: <sip:372@192.168.1.126>;party=calling;screen=yes;privacy=off
Contact: <sip:372@192.168.1.126:5061;transport=tls>;isFocus
Max-Forwards: 70
Content-Length: 0
INVITE sip:7777@192.168.1.68:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339b6ba80edd
From: <sip:371@192.168.1.126;x-farend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13199~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253134
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336c-7e01a8c0@192.168.1.126
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: Geolocation
Call-Info: <sip:192.168.1.126:5061>;method="NOTIFY;Event=telephone-event;Duration=500"
Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000
Cisco-Guid: 0868011136-0000065536-0000000031-2114037952
Session-Expires: 1800
P-Asserted-Identity: <sip:371@192.168.1.126>
Privacy: none
Remote-Party-ID: <sip:371@192.168.1.126>;party=calling;screen=yes;privacy=off
Contact: <sip:371@192.168.1.126:5061;transport=tls>;isFocus
Max-Forwards: 70
Content-Length: 0
INVITE sip:7777@192.168.1.68:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339b6ba80edd
From: <sip:371@192.168.1.126;x-farend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13199~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253134
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336c-7e01a8c0@192.168.1.126
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: Geolocation
Call-Info: <sip:192.168.1.126:5061>;method="NOTIFY;Event=telephone-event;Duration=500"
Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000
Cisco-Guid: 0868011136-0000065536-0000000031-2114037952
Session-Expires: 1800
P-Asserted-Identity: <sip:371@192.168.1.126>
Privacy: none
Remote-Party-ID: <sip:371@192.168.1.126>;party=calling;screen=yes;privacy=off
Contact: <sip:371@192.168.1.126:5061;transport=tls>;isFocus
Max-Forwards: 70
Content-Length: 0
INVITE sip:7777@192.168.1.68:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339c177f9538
From: <sip:372@192.168.1.126;x-farend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13200~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253135
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336d-7e01a8c0@192.168.1.126
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: Geolocation
Call-Info: <sip:192.168.1.126:5061>;method="NOTIFY;Event=telephone-event;Duration=500"
Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000
Cisco-Guid: 0868011136-0000065536-0000000032-2114037952
Session-Expires: 1800
P-Asserted-Identity: <sip:372@192.168.1.126>
Privacy: none
Remote-Party-ID: <sip:372@192.168.1.126>;party=calling;screen=yes;privacy=off
Contact: <sip:372@192.168.1.126:5061;transport=tls>;isFocus
Max-Forwards: 70
Content-Length: 0
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK3399730b01b6
From: <sip:371@192.168.1.126;x-nearend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13197~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253128
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336a-7e01a8c0@192.168.1.126
CSeq: 101 INVITE
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK3399730b01b6
From: <sip:371@192.168.1.126;x-nearend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13197~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253128
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336a-7e01a8c0@192.168.1.126
CSeq: 101 INVITE
Contact: <sip:192.168.1.68:5061;transport=tls>
Allow: ACK, BYE, CANCEL, UPDATE
Content-Type: application/sdp
Content-Length: 215
v=0
o=- 30008 30008 IN IP4 192.168.1.68
s=crystal
c=IN IP4 192.168.1.68
b=CT:1000
t=0 0
m=audio 30008 RTP/AVP 0 8 9 18
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
ACK sip:192.168.1.68:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339d172cc592
From: <sip:371@192.168.1.126;x-nearend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13197~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253128
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336a-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Privacy: none
Content-Length: 0
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339a731ae306
From: <sip:372@192.168.1.126;x-nearend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13198~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253129
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336b-7e01a8c0@192.168.1.126
CSeq: 101 INVITE
Content-Length: 0
BYE sip:192.168.1.68:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339e262accb0
From: <sip:371@192.168.1.126;x-nearend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13197~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253128
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336a-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
Privacy: none
P-Asserted-Identity: <sip:371@192.168.1.126>
CSeq: 102 BYE
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339a731ae306
From: <sip:372@192.168.1.126;x-nearend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13198~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253129
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336b-7e01a8c0@192.168.1.126
CSeq: 101 INVITE
Contact: <sip:192.168.1.68:5061;transport=tls>
Allow: ACK, BYE, CANCEL, UPDATE
Content-Type: application/sdp
Content-Length: 215
v=0
o=- 30010 30010 IN IP4 192.168.1.68
s=crystal
c=IN IP4 192.168.1.68
b=CT:1000
t=0 0
m=audio 30010 RTP/AVP 0 8 9 18
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339b6ba80edd
From: <sip:371@192.168.1.126;x-farend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13199~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253134
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336c-7e01a8c0@192.168.1.126
CSeq: 101 INVITE
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339b6ba80edd
From: <sip:371@192.168.1.126;x-farend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13199~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253134
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336c-7e01a8c0@192.168.1.126
CSeq: 101 INVITE
Contact: <sip:192.168.1.68:5061;transport=tls>
Allow: ACK, BYE, CANCEL, UPDATE
Content-Type: application/sdp
Content-Length: 215
v=0
o=- 30012 30012 IN IP4 192.168.1.68
s=crystal
c=IN IP4 192.168.1.68
b=CT:1000
t=0 0
m=audio 30012 RTP/AVP 0 8 9 18
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
ACK sip:192.168.1.68:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339f48e009c1
From: <sip:372@192.168.1.126;x-nearend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13198~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253129
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336b-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Privacy: none
Content-Length: 0
BYE sip:192.168.1.68:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK33a03e661542
From: <sip:372@192.168.1.126;x-nearend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13198~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253129
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336b-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
Privacy: none
P-Asserted-Identity: <sip:372@192.168.1.126>
CSeq: 102 BYE
Content-Length: 0
CANCEL sip:7777@192.168.1.68:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339b6ba80edd
From: <sip:371@192.168.1.126;x-farend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13199~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253134
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336c-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
CSeq: 101 CANCEL
Max-Forwards: 70
Privacy: none
Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000
Reason: Q.850; cause=21
Content-Length: 0
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339c177f9538
From: <sip:372@192.168.1.126;x-farend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13200~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253135
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336d-7e01a8c0@192.168.1.126
CSeq: 101 INVITE
Content-Length: 0
ACK sip:192.168.1.68:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK33a131fddfa2
From: <sip:371@192.168.1.126;x-farend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13199~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253134
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336c-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Privacy: none
Content-Length: 0
BYE sip:192.168.1.68:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK33a2212c9fcf
From: <sip:371@192.168.1.126;x-farend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13199~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253134
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336c-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
Privacy: none
P-Asserted-Identity: <sip:371@192.168.1.126>
CSeq: 102 BYE
Reason: Q.850;cause=16
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339c177f9538
From: <sip:372@192.168.1.126;x-farend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13200~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253135
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336d-7e01a8c0@192.168.1.126
CSeq: 101 INVITE
Contact: <sip:192.168.1.68:5061;transport=tls>
Allow: ACK, BYE, CANCEL, UPDATE
Content-Type: application/sdp
Content-Length: 215
v=0
o=- 30014 30014 IN IP4 192.168.1.68
s=crystal
c=IN IP4 192.168.1.68
b=CT:1000
t=0 0
m=audio 30014 RTP/AVP 0 8 9 18
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=rtpmap:18 G729/8000
CANCEL sip:7777@192.168.1.68:5061 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339c177f9538
From: <sip:372@192.168.1.126;x-farend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13200~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253135
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336d-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
CSeq: 101 CANCEL
Max-Forwards: 70
Privacy: none
Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000
Reason: Q.850; cause=21
Content-Length: 0
ACK sip:192.168.1.68:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK33a3175e86da
From: <sip:372@192.168.1.126;x-farend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13200~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253135
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336d-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Privacy: none
Content-Length: 0
BYE sip:192.168.1.68:5061;transport=tls SIP/2.0
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK33a45ff2809c
From: <sip:372@192.168.1.126;x-farend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13200~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253135
To: <sip:7777@192.168.1.68>
Date: Mon, 21 May 2018 12:48:06 GMT
Call-ID: 33bccc80-b021c006-336d-7e01a8c0@192.168.1.126
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
Privacy: none
P-Asserted-Identity: <sip:372@192.168.1.126>
CSeq: 102 BYE
Reason: Q.850;cause=16
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK339e262accb0
From: <sip:371@192.168.1.126;x-nearend;x-refci=30253121;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP44D3CA590200;x-nearendaddr=371;x-farendrefci=30253120;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP24B65744E4E6;x-farendaddr=372>;tag=13197~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253128
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336a-7e01a8c0@192.168.1.126
CSeq: 102 BYE
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/TLS 192.168.1.126:5061;branch=z9hG4bK33a03e661542
From: <sip:372@192.168.1.126;x-nearend;x-refci=30253120;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP24B65744E4E6;x-nearendaddr=372;x-farendrefci=30253121;x-farendclusterid=StandAloneCluster;x-farenddevice=SEP44D3CA590200;x-farendaddr=371>;tag=13198~dc2b6003-f4e6-4e1f-95a9-5a7f08c90c7a-30253129
To: <sip:7777@192.168.1.68>
Call-ID: 33bccc80-b021c006-336b-7e01a8c0@192.168.1.126
CSeq: 102 BYE
Content-Length: 0
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide