ā12-15-2022 11:19 AM - edited ā12-15-2022 11:22 AM
Hi,
When inbound call came from Sip trunk and the extension 201 answer the call and try transfer to another extension never works.
Could you help me?
Follow show run attached.
Detail , i dont know why but aparently when user press button transfer and digit the destination extension to transfer, the phone make two calls, for example the external inbound call came from SIP trunk, extension 201 answer this call and when press the transfer button and 207, occurs two calls , one to extension 2 , e another to extension 207.
Follow debug output:
Received:
INVITE sip:1199999994@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK544894f6
From: <sip:201@192.168.22.21>;tag=204c9eb24ea40cd85646ca34-088a3979
To: <sip:1199999994@192.168.22.10>;tag=98AAA8E4-105F
Call-ID: F9D75D83-763B11ED-87DAFC01-A571E559@192.168.22.10
Max-Forwards: 70
Session-ID: 4372a82e00105000a000204c9eb24ea4;remote=2e06eb62c05b578abd0e21d787c4019b
Date: Thu, 08 Dec 2022 14:32:35 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CP7861/14.1.1
Contact: <sip:BE8C-1652@192.168.22.21:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP204C9EB24EA4"
Accept: application/sdp
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "Thais" <sip:201@192.168.22.10>;party=called;id-type=subscriber;privacy=off;screen=yes
Call-Info: <urn:x-cisco-remotecc:hold>; reason= transfer; protect= true; noholdreversion
Supported: replaces,join,sdp-anat,norefersub,resource-priority,ex
VoIP-#tended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Recv-Info: conference
Recv-Info: x-cisco-conference
Content-Length: 340
Content-Type: application/sdp
Content-Disposition: session;handling=optional
v=0
o=Cisco-SIPUA 17690 1 IN IP4 192.168.22.21
s=SIP Call
t=0 0
m=audio 18536 RTP/AVP 8 0 116 18 101
c=IN IP4 192.168.22.21
b=TIAS:64000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:116 iLBC/8000
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly
Dec 8 14:32:36.490: //344762/F9D5890B87D4/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK544894f6
From: <sip:201@192.168.22.21>;tag=204c9eb24ea40cd85646ca34-088a3979
To: <sip:1199999994@192.168.22.10>;tag=98AAA8E4-105F
Date: Thu, 08 Dec 2022 14:32:36 GMT
Call-ID: F9D75D83-763B11ED-87DAFC01-A571E559@192.168.22.10
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.6.3.M9
Session-ID: 2e06eb62c05b578abd0e21d787c4019b;remote=4372a82e00105000a000204c9eb24ea4
Content-Length: 0
Dec 8 14:32:36.490: //344761/F9D5890B87D4/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:1199999994@186.224.204.132:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74B917A9
From: <sip:55112699999@200.170.192.130>;tag=98AAA934-204D
To: <sip:1199999994@186.224.204.132>;tag=as02b56d8b
Date: Thu, 08 Dec 2022 14:32:36 GMT
Call-ID: 4f07f18c5205de995758da802cff9ccd@186.224.204.132:5060
Supported: timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 4191521035-1983582701-2278882305-2775704921
User-Agent: Cisco-SIPGateway/IOS-15.6.3.M9
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1670509956
Contact: <sip:55112699999@192.168.2
VoIP-#2.10:5060>
Expires: 180
Allow-Events: telephone-event
Session-ID: 4372a82e00105000a000204c9eb24ea4;remote=2e06eb62c05b578abd0e21d787c4019b
Content-Type: application/sdp
Content-Length: 286
v=0
o=CiscoSystemsSIP-GW-UserAgent 9949 8395 IN IP4 192.168.22.10
s=SIP Call
c=IN IP4 192.168.22.10
t=0 0
m=audio 27692 RTP/AVP 8 101 19
c=IN IP4 192.168.22.10
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
a=sendonly
Dec 8 14:32:36.494: //344761/F9D5890B87D4/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74B917A9;received=200.170.192.130;rport=56624
From: <sip:55112699999@200.170.192.130>;tag=98AAA934-204D
To: <sip:1199999994@186.224.204.132>;tag=as02b56d8b
Call-ID: 4f07f18c5205de995758da802cff9ccd@186.224.204.132:5060
CSeq: 101 INVITE
Server: BR-SAO-CO1-SVV-SBC-01
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
Contact: <sip:1199999994@186.224.204.132:5060>
Content-Length: 0
Dec 8 14:32:37.370: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:2@192.168.22.10;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK53dc5f23
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
Max-Forwards: 70
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=00000000000000000000000000000000
Date: Thu, 08 Dec 2022 14:32:36 GMT
CSeq: 101 INVITE
User-Agent: Cisco-CP7861/14.1.1
Contact: <sip:BE8C-1652@192.168.22.21:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP204C9EB24EA4"
Expires: 180
Accept: application/sdp
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "Thais" <sip:201@192.168.22.10>;party=calling;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Recv-Info: conference
Recv-Info: x-cisco-conference
Content-Length: 351
Content-Type: application/sdp
Content-Disposition: session;handling=optional
v=0
o=Cisco-SIPUA 12818 0 IN IP4 192.168.22.21
s=SIP Call
b=AS:4064
t=0 0
m=audio 30228 RTP/AVP 8 0 116 18 101
c=IN IP4 192.168.22.21
b=TIAS:64000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:116 iLBC/8000
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
Dec 8 14:32:37.378: //344766/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK53dc5f23
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>
Date: Thu, 08 Dec 2022 14:32:37 GMT
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.6.3.M9
Session-ID: 00000000000000000000000000000000;remote=7f8e24e900105000a000204c9eb24ea4
Content-Length: 0
Dec 8 14:32:37.422: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
NOTIFY sip:2@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK5a161118
To: <sip:2@192.168.22.10>;tag=98AACB84-E14
From: <sip:201@192.168.22.21>;tag=204c9eb24ea40cda3f7dcb02-3f5cc705
Call-ID: FF1FEBE6-763B11ED-87E0FC01-A571E559@192.168.22.10
Session-ID: 5bf2a1ab00105000a000204c9eb24ea4;remote=00000000000000000000000000000000
Date: Thu, 08 Dec 2022 14:32:36 GMT
CSeq: 1000 NOTIFY
Event: kpml
Subscription-State: active; expires=7200
Max-Forwards: 70
Contact: <sip:BE8C-1652@192.168.22.21:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP204C9EB24EA4"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE
Content-Length: 0
Dec
VoIP-#8 14:32:37.502: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
NOTIFY sip:2@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK2e502d51
To: <sip:2@192.168.22.10>;tag=98AACB84-E14
From: <sip:201@192.168.22.21>;tag=204c9eb24ea40cda3f7dcb02-3f5cc705
Call-ID: FF1FEBE6-763B11ED-87E0FC01-A571E559@192.168.22.10
Session-ID: 5bf2a1ab00105000a000204c9eb24ea4;remote=00000000000000000000000000000000
Date: Thu, 08 Dec 2022 14:32:36 GMT
CSeq: 1001 NOTIFY
Event: kpml
Subscription-State: active; expires=7200
Max-Forwards: 70
Contact: <sip:BE8C-1652@192.168.22.21:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP204C9EB24EA4"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE
Content-Length: 205
Content-Type: application/kpml-response+xml
Content-Disposition: session;handling=required
<?xml version="1.0" encoding="UTF-8"?>
<kpml-response xmlns="urn:ietf:params:xml:ns:kpml-response" version="1.0" code="200" text="OK" suppressed="false" forced_flush="false" digits="3" tag="Backspace OK"/>
Dec 8 14:32:37.698: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
NOTIFY sip:2@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK0cfece8a
To: <sip:2@192.168.22.10>;tag=98AACB84-E14
From: <sip:201@192.168.22.21>;tag=204c9eb24ea40cda3f7dcb02-3f5cc705
Call-ID: FF1FEBE6-763B11ED-87E0FC01-A571E559@192.168.22.10
Session-ID: 5bf2a1ab00105000a000204c9eb24ea4;remote=00000000000000000000000000000000
Date: Thu, 08 Dec 2022 14:32:37 GMT
CSeq: 1002 NOTIFY
Event: kpml
Subscription-State: active; expires=7200
Max-Forwards: 70
Contact: <sip:BE8C-1652@192.168.22.21:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP204C9EB24EA4"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE
Content-Length: 205
Content-Type: application/kpml-response+xml
Content-Disposition: session;handling=required
<?xml version="1.0" encoding="UTF-8"?>
<kpml-response xmlns="urn:ietf:params:xml:ns:kpml-response" version="1.0" code="200" text="OK" suppressed="false" forced_flush="false" digits="7" tag="Backspace OK"/>
Dec 8 14:32:37.710: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:237@192.168.22.18:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74BC19C3
From: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
To: <sip:237@192.168.22.18>
Date: Thu, 08 Dec 2022 14:32:37 GMT
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 4280201981-1983582701-2279341057-2775704921
User-Agent: Cisco-SIPGateway/IOS-15.6.3.M9
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1670509957
Contact: <sip:201@192.168.22.10:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 273
v=0
o=CiscoSystemsSIP-GW-UserAgent 1593 285 IN IP4 192.168.22.10
s=SIP Call
c=IN IP4 192.168.22.10
t=0 0
m=audio 27694 RTP/AVP 8 101 19
c=IN IP4 192.168.22.10
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
Dec 8 14:32:37.722: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
NOTIFY sip:2@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK44cf59db
To: <sip:2@192.168.22.10>;tag=98AACB84-E14
From: <sip:201@192.168.22.21>;tag=204c9eb24ea40cda3f7dcb02-3f5cc705
Call-ID: FF1FEBE6-763B11ED-87E0FC01-A571E559@192.168.22.10
Session-ID: 5bf2a1ab00105000a000204c9eb24ea4;remote=00000000000000000000000000000000
Date: Thu, 08 Dec 2022 14:32:37 GMT
CSeq: 1003 NOTIFY
Event: kpml
Subscription-State: terminated; reason=timeout
Max-Forwards: 70
Contact: <sip:BE8C-1652@192.168.22.21:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP204C9EB24EA4"
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE
Content-Length: 218
Content-Type: application/kpml-response+xml
Content-Disposition: session;handling=required
<?xml version="1.0" encoding="UTF-8"?>
<kpml-response xmlns="urn:ietf:params:xml:ns:kpml-response" version="1.0" code="487" text="Subscription Exp" suppressed="false" forced_flush="false" digits="" tag="Backspace OK"/>
Dec 8 14:32:37.742: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.22.10:5060;received=192.168.22.10;branch=z9hG4bK74BC19C3
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
From: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
To: <sip:237@192.168.22.18>
CSeq: 101 INVITE
Content-Length: 0
Dec 8 14:32:37.978: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.22.10:5060;received=192.168.22.10;branch=z9hG4bK74BC19C3
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
From: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
To: <sip:237@192.168.22.18>;tag=Qo-nIJSdS.lU8LqvDe439pL-Ldn8fYFR
CSeq: 101 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Contact: <sip:BF50-877@192.168.22.18:5060>
Supported: replaces,join,sdp-anat,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-monrec,X-cisco-config,X-cisco-sis-5.0.0,X-cisco-xsi-7.0.1
Allow-Events: kpml,dialog
Remote-Party-ID: "Regina"<sip:237@192.168.22.10:5060>;privacy=off;screen=yes
Content-Length: 0
Dec 8 14:32:37.978: //344766/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK53dc5f23
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
Date: Thu, 08 Dec 2022 14:32:37 GMT
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:BF50-877@192.168.22.10:5060>
Server: Cisco-SIPGateway/IOS-15.6.3.M9
Session-ID: 7da678d28e69527daa91b04e5f71523f;remote=7f8e24e900105000a000204c9eb24ea4
Content-Length: 0
Dec 8 14:32:39.234: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
REGISTER sip:192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.44:5060;rport;branch=z9hG4bKPj3K8k4XSvcjRcXaHmDJL8FEODY4L-Gmx1
Max-Forwards: 70
From: "Guarita" <sip:239@192.168.22.10>;tag=ebl46nZ8bZ9nOc4OR5if6n6oQwiiuhPE
To: "Guarita" <sip:239@192.168.22.10>
Call-ID: GflYwPcuwY8zYKTSP8XjrQmm.oY1VKtb
CSeq: 67061 REGISTER
User-Agent: Cisco-CP3905/9.4.1
Contact: <sip:BF5C-22B8@192.168.22.44:5060>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-381c1aba3ebd>";+u.sip!devicename.ccm.cisco.com="SEP381C1ABA3EBD";+u.sip!model.ccm.cisco.com="592"
Expires: 3600
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0
Dec 8 14:32:39.234: //344768/003B20E587E3/SIP/Msg/ccsipDisplayMsg:
Sent:
VoIP-#SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.22.44:5060;rport;branch=z9hG4bKPj3K8k4XSvcjRcXaHmDJL8FEODY4L-Gmx1
From: "Guarita" <sip:239@192.168.22.10>;tag=ebl46nZ8bZ9nOc4OR5if6n6oQwiiuhPE
To: "Guarita" <sip:239@192.168.22.10>;tag=98AAD2C4-56F
Date: Thu, 08 Dec 2022 14:32:39 GMT
Call-ID: GflYwPcuwY8zYKTSP8XjrQmm.oY1VKtb
Server: Cisco-SIPGateway/IOS-15.6.3.M9
CSeq: 67061 REGISTER
Contact: <sip:239@192.168.22.44:5060>;expires=600
Expires: 600
Content-Length: 0
VoIP-#
VoIP-#
VoIP-#
VoIP-#
VoIP-#
VoIP-#
VoIP-#
VoIP-#
VoIP-#
Dec 8 14:32:45.298: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.22.10:5060;received=192.168.22.10;branch=z9hG4bK74BC19C3
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
From: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
To: <sip:237@192.168.22.18>;tag=Qo-nIJSdS.lU8LqvDe439pL-Ldn8fYFR
CSeq: 101 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Contact: <sip:BF50-877@192.168.22.18:5060>
Supported: replaces,join,sdp-anat,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-monrec,X-cisco-config,X-cisco-sis-5.0.0,X-cisco-xsi-7.0.1
Allow-Events: kpml,dialog
Remote-Party-ID: "Regina"<sip:237@192.168.22.10:5060>;privacy=off;screen=yes
Content-Type: application/sdp
Content-Length: 222
v=0
o=- 2210352256 2210352257 IN IP4 192.168.22.18
s=FOXPHONE
t=0 0
a=X-nat:0
m=audio 16386 RTP/AVP 8 101
c=IN IP4 192.168.22.18
a=rtpmap:8 PCMA/8000
a=sendrecv
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
Dec 8 14:32:45.302: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:BF50-877@192.168.22.18:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74BD471
From: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
To: <sip:237@192.168.22.18>;tag=Qo-nIJSdS.lU8LqvDe439pL-Ldn8fYFR
Date: Thu, 08 Dec 2022 14:32:37 GMT
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=7da678d28e69527daa91b04e5f71523f
Content-Length: 0
Dec 8 14:32:45.306: //344766/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK53dc5f23
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
Date: Thu, 08 Dec 2022 14:32:37 GMT
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:237@192.168.22.10:5060>
Supported: replaces
Server: Cisco-SIPGateway/IOS-15.6.3.M9
Session-ID: 7da678d28e69527daa91b04e5f71523f;remote=7f8e24e900105000a000204c9eb24ea4
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 250
v=0
o=CiscoSystemsSIP-GW-UserAgent 4090 4134 IN IP4 192.168.22.10
s=SIP Call
c=IN IP4 192.168.22.10
t=0 0
m=audio 27696 RTP/AVP 8 101
c=IN IP4 192.168.22.10
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Dec 8 14:32:45.354: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
VoIP-#ACK sip:237@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK0fd7e099
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
Max-Forwards: 70
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=7da678d28e69527daa91b04e5f71523f
Date: Thu, 08 Dec 2022 14:32:44 GMT
CSeq: 101 ACK
User-Agent: Cisco-CP7861/14.1.1
Remote-Party-ID: "Thais" <sip:201@192.168.22.10>;party=calling;id-type=subscriber;privacy=off;screen=yes
Content-Length: 0
Recv-Info: conference
Recv-Info: x-cisco-conference
VoIP-#
Dec 8 14:32:48.410: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:237@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK28523fd6
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
Max-Forwards: 70
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=7da678d28e69527daa91b04e5f71523f
Date: Thu, 08 Dec 2022 14:32:47 GMT
CSeq: 102 INVITE
User-Agent: Cisco-CP7861/14.1.1
Contact: <sip:BE8C-1652@192.168.22.21:5060;transport=udp>;+u.sip!devicename.ccm.cisco.com="SEP204C9EB24EA4"
Accept: application/sdp
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE,SUBSCRIBE,INFO
Remote-Party-ID: "Thais" <sip:201@192.168.22.10>;party=calling;id-type=subscriber;privacy=off;screen=yes
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1
Allow-Events: kpml,dialog
Recv-Info: conference
Recv-Info: x-cisco-conference
Content-Length: 351
Content-Type: application/sdp
Content-Disposition: session;handling=optional
v=0
o=Cisco-SIPUA 12818 1 IN IP4 192.168.22.21
s=SIP Call
b=AS:4064
t=0 0
m=audio 30228 RTP/AVP 8 0 116 18 101
c=IN IP4 192.168.22.21
b=TIAS:64000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:116 iLBC/8000
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly
Dec 8 14:32:48.414: //344766/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK28523fd6
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
Date: Thu, 08 Dec 2022 14:32:48 GMT
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
CSeq: 102 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.6.3.M9
Session-ID: 7da678d28e69527daa91b04e5f71523f;remote=7f8e24e900105000a000204c9eb24ea4
Content-Length: 0
Dec 8 14:32:48.414: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:BF50-877@192.168.22.18:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74BE63E
From: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
To: <sip:237@192.168.22.18>;tag=Qo-nIJSdS.lU8LqvDe439pL-Ldn8fYFR
Date: Thu, 08 Dec 2022 14:32:48 GMT
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
Cisco-Guid: 4280201981-1983582701-2279341057-2775704921
User-Agent: Cisco-SIPGateway/IOS-15.6.3.M9
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1670509968
Contact: <sip:201@192.168.22.10:5060>
Expires: 180
Allow-Events: telephone-event
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=7da678d28e69527daa91b04e5f71523f
Content-Type: application/sdp
Content-Length: 285
v=0
o=CiscoSystemsSIP-GW-UserAgent 1593 286 IN IP4 192.168.22.10
s=SIP Call
c=IN IP4 192.168.22.10
t=0 0
m=audio 27694 RTP/AVP 8 101 19
c=IN IP4 192.168.22.10
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000
a=ptime:20
a=sendonly
Dec 8 14:32:48.570: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.22.10:5060;received=192.168.22.10;branch=z9hG4bK74BE63E
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
From: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
To: <sip:237@192.168.22.18>;tag=Qo-nIJSdS.lU8LqvDe439pL-Ldn8fYFR
CSeq: 102 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Allow-Events: kpml,dialog
Contact: <sip:BF50-877@192.168.22.18:5060>
Content-Type: application/sdp
Content-Length: 222
v=0
o=- 2210352256 2210352258 IN IP4 192.168.22.18
s=FOXPHONE
t=0 0
a=X-nat:0
m=audio 16386 RTP/AVP 8 101
c=IN IP4 192.168.22.18
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=recvonly
Dec 8 14:32:48.578: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:BF50-877@192.168.22.18:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74BF6DA
From: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
To: <sip:237@192.168.22.18>;tag=Qo-nIJSdS.lU8LqvDe439pL-Ldn8fYFR
Date: Thu, 08 Dec 2022 14:32:48 GMT
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=7da678d28e69527daa91b04e5f71523f
Content-Length: 0
Dec 8 14:32:48.578: //344766/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK28523fd6
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
Date: Thu, 08 Dec 2022 14:32:48 GMT
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
CSeq: 102 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:237@192.168.22.10:5060>
Supported: replaces
Server: Cisco-SIPGateway/IOS-15.6.3.M9
Session-ID: 7da678d28e69527daa91b04e5f71523f;remote=7f8e24e900105000a000204c9eb24ea4
Supported: timer
Content-Type: application/sdp
Content-Length: 262
v=0
o=CiscoSystemsSIP-GW-UserAgent 4090 4135 IN IP4 192.168.22.10
s=SIP Call
c=IN IP4 192.168.22.10
t=0 0
m=audio 27696 RTP/AVP 8 101
c=IN IP4 192.168.22.10
a=recvonly
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
Dec 8 14:32:48.582: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
VoIP-#ACK sip:237@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.21:5060;branch=z9hG4bK193a1a67
From: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
To: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
Max-Forwards: 70
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=7da678d28e69527daa91b04e5f71523f
Date: Thu, 08 Dec 2022 14:32:47 GMT
CSeq: 102 ACK
User-Agent: Cisco-CP7861/14.1.1
Remote-Party-ID: "Thais" <sip:201@192.168.22.10>;party=calling;id-type=subscriber;privacy=off;screen=yes
Content-Length: 0
Recv-Info: conference
Recv-Info: x-cisco-conference
VoIP-#
Dec 8 14:32:53.330: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:201@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.18:5060;rport;branch=z9hG4bKPjRnyLQp-QrrXDckK8rDENQxCQsrVCDMQ5
Max-Forwards: 70
From: <sip:237@192.168.22.18>;tag=Qo-nIJSdS.lU8LqvDe439pL-Ldn8fYFR
To: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
CSeq: 4543 BYE
User-Agent: Cisco-CP3905/9.4.1
RTP-RxStat: Dur=7,Pkt=0,Oct=0,LatePkt=0,LostPkt=0,AvgJit=0,VQMetrics="MLQK=0.0000;MLQKav=0.0000;MLQKmn=0.0000;MLQKmx=0.0000;MLQKvr=0.95;CCR=0.0000;ICR=0.0000;ICRmx=0.0000;CS=0;SCS=0"
RTP-TxStat: Dur=7,Pkt=0,Oct=0
Content-Length: 0
Dec 8 14:32:53.334: //344766/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:BE8C-1652@192.168.22.21:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74C012AE
From: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
To: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
Date: Thu, 08 Dec 2022 14:32:48 GMT
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
User-Agent: Cisco-SIPGateway/IOS-15.6.3.M9
Max-Forwards: 70
Timestamp: 1670509973
CSeq: 101 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=121,OS=17412,PR=133,OR=20167,PL=0,JI=0,LA=0,DU=8
Session-ID: 7da678d28e69527daa91b04e5f71523f;remote=7f8e24e900105000a000204c9eb24ea4
Content-Length: 0
Dec 8 14:32:53.334: //344767/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.22.18:5060;rport;branch=z9hG4bKPjRnyLQp-QrrXDckK8rDENQxCQsrVCDMQ5
From: <sip:237@192.168.22.18>;tag=Qo-nIJSdS.lU8LqvDe439pL-Ldn8fYFR
To: "Thais" <sip:201@192.168.22.10>;tag=98AACCCC-1664
Date: Thu, 08 Dec 2022 14:32:53 GMT
Call-ID: FF51F7D9-763B11ED-87E2FC01-A571E559@192.168.22.10
Server: Cisco-SIPGateway/IOS-15.6.3.M9
CSeq: 4543 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=133,OS=20167,PR=121,OR=17412,PL=0,JI=0,LA=0,DU=8
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=7da678d28e69527daa91b04e5f71523f
Content-Length: 0
VoIP-#
Dec 8 14:32:53.358: //344766/FF1EB2FD87DB/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74C012AE
From: <sip:2@192.168.22.10>;tag=98AACDDC-15EE
To: "Thais" <sip:201@192.168.22.10>;tag=204c9eb24ea40cd9779d0377-17b59e3b
Call-ID: 204c9eb2-4ea402c5-3f5477ce-241ceec9@192.168.22.21
Session-ID: 7f8e24e900105000a000204c9eb24ea4;remote=7da678d28e69527daa91b04e5f71523f
Date: Thu, 08 Dec 2022 14:32:52 GMT
CSeq: 101 BYE
Server: Cisco-CP7861/14.1.1
Content-Length: 0
VoIP-#
Dec 8 14:33:08.494: //344761/F9D5890B87D4/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:1199999994@186.224.204.132:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.22.10:5060;branch=z9hG4bK74C1549
From: <sip:55112699999@200.170.192.130>;tag=98AAA934-204D
To: <sip:1199999994@186.224.204.132>;tag=as02b56d8b
Date: Thu, 08 Dec 2022 14:32:36 GMT
Call-ID: 4f07f18c5205de995758da802cff9ccd@186.224.204.132:5060
User-Agent: Cisco-SIPGateway/IOS-15.6.3.M9
Max-Forwards: 70
Timestamp: 1670509988
CSeq: 102 BYE
Reason: Q.850;cause=86
P-RTP-Stat: PS=202,OS=26914,PR=297,OR=47520,PL=0,JI=0,LA=0,DU=38
Session-ID: 4372a82e00105000a000204c9eb24ea4;remote=2e06eb62c05b578abd0e21d787c4019b
Content-Length: 0
Dec 8 14:33:08.494: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:55112699999@192.168.22.10:5060 SIP/2.0
Via: SIP/2.0/UDP 186.224.204.132:5060;branch=z9hG4bK5b064d1c;rport
Max-Forwards: 70
From: <sip:1199999994@186.224.204.132>;tag=as02b56d8b
To: <sip:55112699999@200.170.192.130>;tag=98AAA934-204D
Call-ID: 4f07f18c5205de995758da802cff9ccd@186.224.204.132:5060
CSeq: 103 BYE
User-Agent: BR-SAO-CO1-SVV-SBC-01
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0
Dec 8 14:33:08.498: //344761/F9D5890B87D4/SIP/Msg/ccsipDisplayMsg:
Sent:
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