2nd call coming to the Hunt

fei he · ‎03-07-2017

Hi

We recently cross an issue where one way audio when answer from hunt queued calls and call flow as below:

ITSP ---sip---> CUBE(SP) --- sip--> CUCM --- sip---> ip phone

PSTN caller 1 call the hunt and answer by IP phone with 2 way audio. Then 2nd PSTN call coming into hunt which configured for Native queuing and 2nd call is queued as all hunt members are already on the call and PSTN caller 2 hear music on hold. IP phone disconnect PSTN caller 1 and PSTN caller 2 previous queued is ringing to IP Phone and PSTN caller 2 start hear ring back tone. IP Phone answer the call and one-way audio occurs where PSTN caller 2 can hear IP Phone but IP Phone cannot hear PSTN caller 2 (same call flow works perfectly fine when all calling and called party from internal ip phone).

Has anyone came cross similar issue and any suggestion?

Fei

Dennis Mink · ‎03-07-2017

Sound like either a: a routing issue (ping between phones and PSTN gateway).

or b, which is most likely, a signalling issue. when your caller called into the native queueing then the queue will send to your caller that RTP=inactive and it will only play out the music on hold. I am guessing that when a phone becomes available, there is no re-invite to signal that RTP is now 2ways.

can you trace the call and send us the SIP traces.

cheers

Please remember to rate useful posts, by clicking on the stars below.

fei he · ‎03-24-2017

2nd call coming to the Hunt and call is been queued (on hold), call flow shows Carriage send the original INVITE to the CUBE, CUBE replies and sends a 200OK/SDP for answer with media attribute sendonly.

00171775.002 |17:08:09.600 |AppInfo |SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.111.3.253 on port 51977 index 2571831 with 1033 bytes:[525958909,NET]
INVITE sip:+61262644589@10.111.2.5:5060 SIP/2.0
Via: SIP/2.0/TCP 10.111.3.253:5060;branch=z9hG4bK+089560f63f02643084aba99e578d54281+sip+1+ac27ca87
Supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join,x-nortel-sipvc,gin,com.nortelnetworks.im.encryption,tdialog
From: <sip:+61280854712@10.111.3.253:5060>;tag=10.111.3.253+1+188e73cd+54b8b409
To: <sip:+61262644589@10.111.2.5:5060>
CSeq: 3996 INVITE
Expires: 180
Content-Length: 190
Call-Info: <sip:10.111.3.253:5060>;method="NOTIFY;Event=telephone-event;Duration=2000"
Contact: <sip:10.111.3.253:5060;transport=tcp>
Content-Type: application/sdp
Call-ID: 0e6aafbd5f893e9aadc1978a16c0a3c5@10.111.3.253
Max-Forwards: 49
Allow: INVITE,BYE,CANCEL,ACK,REGISTER,SUBSCRIBE,NOTIFY,MESSAGE,INFO,REFER,OPTIONS,PUBLISH,PRACK
Accept: application/sdp, application/dtmf-relay
v=0
o=PVG 65156409607295 65156409607295 IN IP4 10.111.3.254
s=-
c=IN IP4 10.111.3.254
t=0 0
m=audio 27190 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

00172133.001 |17:08:09.788 |AppInfo |SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.111.3.253 on port 51977 index 2571831 [525958974,NET]
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.111.3.253:5060;branch=z9hG4bK+089560f63f02643084aba99e578d54281+sip+1+ac27ca87
From: <sip:+61280854712@10.111.3.253:5060>;tag=10.111.3.253+1+188e73cd+54b8b409
To: <sip:+61262644589@10.111.2.5:5060>;tag=1590641452~8f65986a-1de3-4cbe-a6b4-16bb52492403-43429771
Date: Tue, 07 Mar 2017 06:08:09 GMT
Call-ID: 0e6aafbd5f893e9aadc1978a16c0a3c5@10.111.3.253
CSeq: 3996 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: replaces
Server: Cisco-CUCM10.5
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=MIXED
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: <sip:+61262644589@10.111.2.5>
Remote-Party-ID: <sip:+61262644589@10.111.2.5>;party=called;screen=yes;privacy=off
Contact: <sip:+61262644589@10.111.2.5:5060;transport=tcp>
Content-Type: application/sdp
Content-Length: 225
v=0
o=CiscoSystemsCCM-SIP 1590641452 1 IN IP4 10.111.2.5
s=SIP Call
c=IN IP4 10.111.3.4
t=0 0
m=audio 4000 RTP/AVP 8 101
a=ptime:20
a=rtpmap:8 PCMA/8000
a=sendonly --------------> CUBE instruct EVOLVE this call been queued or on hold.
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Once the queued call is answered, there is a re-INVITE coming from the CUBE and the Carriage replies with 200OK/SDP recvonly which is causing the one way speech.

00185286.001 |17:08:21.728 |AppInfo |SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 10.111.3.253 on port 5060 index 2401885 [525962245,NET]
INVITE sip:10.111.3.253:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.111.2.5:5060;branch=z9hG4bK2bec81347f5a2cd
From: <sip:+61262644589@10.111.2.5:5060>;tag=1590641452~8f65986a-1de3-4cbe-a6b4-16bb52492403-43429771
To: <sip:+61280854712@10.111.3.253:5060>;tag=10.111.3.253+1+188e73cd+54b8b409
Date: Tue, 07 Mar 2017 06:08:21 GMT
Call-ID: 0e6aafbd5f893e9aadc1978a16c0a3c5@10.111.3.253
Supported: timer,resource-priority,replaces
User-Agent: Cisco-CUCM10.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 104 INVITE
Max-Forwards: 70
Expires: 180
Allow-Events: presence
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Min-SE: 1800
P-Asserted-Identity: <sip:+61262643770@10.111.2.5>
Remote-Party-ID: <sip:+61262643770@10.111.2.5>;party=calling;screen=yes;privacy=off
Contact: <sip:367e1c51-af86-2224-e512-936a09af226d@10.111.2.5:5060;transport=tcp>
Content-Type: application/sdp
Content-Length: 229
v=0
o=CiscoSystemsCCM-SIP 1590641452 4 IN IP4 10.111.2.5
s=SIP Call
c=IN IP4 10.136.156.120
b=TIAS:64000
b=AS:64
t=0 0
m=audio 18254 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

00185341.002 |17:08:21.774 |AppInfo |SIPTcp - wait_SdlReadRsp: Incoming SIP TCP message from 10.111.3.253 on port 5060 index 2401885 with 803 bytes:
[525962266,NET]
SIP/2.0 200 OK
Supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join,x-nortel-sipvc,gin,com.nortelnetworks.im.encryption
Call-ID: 0e6aafbd5f893e9aadc1978a16c0a3c5@10.111.3.253
CSeq: 104 INVITE
From: <sip:+61262644589@10.111.2.5:5060>;tag=1590641452~8f65986a-1de3-4cbe-a6b4-16bb52492403-43429771
To: <sip:+61280854712@10.111.3.253:5060>;tag=10.111.3.253+1+188e73cd+54b8b409
Via: SIP/2.0/TCP 10.111.2.5:5060;received=10.111.2.5;branch=z9hG4bK2bec81347f5a2cd
Content-Length: 224
Contact: <sip:10.111.3.253:5060;transport=tcp>
Content-Type: application/sdp
v=0
o=PVG 65156409607295 65156409607296 IN IP4 10.111.3.254
s=-
c=IN IP4 10.111.3.254
t=0 0
m=audio 27190 RTP/AVP 8 101
a=recvonly --------------> this cause one way speech
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

This issue is now resolved after we uncheck "Send send-receive SDP in mid-call INVITE" on SIP profile used by trunk.

Dennis Mink · ‎03-26-2017

By looking at the traces, the invite from the second call comes with no codec. The 200 OK comes with a codec and a send only. so when the 2nd call gets picked up, there is a codec towards PSTN (g711alaw), but no codec i.e. voice from PSTN.

I would reach out to your provider, and ask them why that Eoraly Offer SDP does not contain any codecs.

Please rate if this helps.

Please remember to rate useful posts, by clicking on the stars below.

christian.kiesel · ‎11-04-2019

Hello I have the same problems. I have try all options.

at the end the log files.

thanks!

enarev · ‎11-30-2023

Hello I have the same problem.

Carlo Poggiarelli · ‎11-30-2023

Hi,

Please post the output of a debug ccsip message while reproducing the issue.

Thanks

Regards

Carlo

Please rate all helpful posts "The more you help the more you learn"

enarev · ‎12-01-2023

Hi Carlo, thank you for reply.

there is no option for me to attach a file, every time i try i get following error messages:

The attachment's ccsip_messages.txt content type (text/plain) does not match its file extension and has been removed

Carlo Poggiarelli · ‎12-01-2023

Hi.

Try without underscore.

Let me know

Cheers

Carlo

Please rate all helpful posts "The more you help the more you learn"

enarev · ‎12-07-2023

Hi Carlo, i have tried it in all possible variations and unfortunately had no success with the upload. So now I'm using this method:

030233: Dec 1 10:52:03.920: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Received:
UPDATE sip:+491603680613@10.136.33.70:5060 SIP/2.0
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK13395f7fec074d
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:51:42 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
Supported: timer,resource-priority,replaces

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 103 UPDATE
Session-ID: 80d35b4551d6babd3c9256ba51655576;remote=82d2b9a14449591fbe42dfa1224e68c1
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=VIDEO_UNSPECIFIED
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uac
Min-SE: 1800
P-Asserted-Identity: <sip:004926379447999@10.136.33.60>
Contact: <sip:+4926379447911@10.136.33.60:5060>
Content-Length: 0


030234: Dec 1 10:52:03.921: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK13395f7fec074d
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550

To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:03 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
Server: Cisco-SIPGateway/IOS-16.12.4a
CSeq: 103 UPDATE
Allow-Events: telephone-event
Contact: <sip:+491603680613@10.136.33.70:5060>
Session-ID: 82d2b9a14449591fbe42dfa1224e68c1;remote=80d35b4551d6babd3c9256ba51655576
Require: timer
Session-Expires: 1800;refresher=uac
Supported: timer
Content-Length: 0


030235: Dec 1 10:52:03.924: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+491603680613@10.136.33.70:5060 SIP/2.0
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339604ed67ab
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400

Date: Fri, 01 Dec 2023 09:52:03 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
Supported: 100rel,timer,resource-priority,replaces
Cisco-Guid: 0279989442-2405831150-2528763291-0054196701
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 104 INVITE
Max-Forwards: 70
Expires: 180
Allow-Events: presence
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=VIDEO_UNSPECIFIED
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uac
Min-SE: 1800
Session-ID: 80d35b4551d6babd3c9256ba51655576;remote=82d2b9a14449591fbe42dfa1224e68c1
P-Asserted-Identity: <sip:004926379447999@10.136.33.60>
Contact: <sip:+4926379447911@10.136.33.60:5060>
Content-Length: 0




030236: Dec 1 10:52:03.925: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339604ed67ab
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:03 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
CSeq: 104 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-16.12.4a
Session-ID: 82d2b9a14449591fbe42dfa1224e68c1;remote=80d35b4551d6babd3c9256ba51655576
Content-Length: 0


030237: Dec 1 10:52:03.925: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK

Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339604ed67ab
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:03 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
CSeq: 104 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:+491603680613@10.136.33.70:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-16.12.4a
Session-ID: 82d2b9a14449591fbe42dfa1224e68c1;remote=00000000000000000000000000000000
Require: timer
Session-Expires: 1800;refresher=uac
Supported: timer
Content-Type: application/sdp
Content-Length: 246


v=0
o=CiscoSystemsSIP-GW-UserAgent 4073 5024 IN IP4 10.136.33.70
s=SIP Call
c=IN IP4 10.136.33.70
t=0 0
m=audio 9846 RTP/AVP 8 101
c=IN IP4 10.136.33.70
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

030238: Dec 1 10:52:03.939: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+491603680613@10.136.33.70:5060 SIP/2.0
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK13396140169c1e
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:03 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
User-Agent: Cisco-CUCM11.5

Max-Forwards: 70
CSeq: 104 ACK
Allow-Events: presence
Session-ID: 80d35b4551d6babd3c9256ba51655576;remote=82d2b9a14449591fbe42dfa1224e68c1
Content-Type: application/sdp
Content-Length: 180

v=0
o=CiscoSystemsCCM-SIP 1722336 3 IN IP4 10.136.33.60
s=SIP Call
c=IN IP4 10.11.20.60
t=0 0
m=audio 29958 RTP/AVP 8
a=X-cisco-media:umoh
a=ptime:20
a=rtpmap:8 PCMA/8000

030239: Dec 1 10:52:04.104: //2950713/330F19000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 100.88.38.226:5060;branch=z9hG4bK35CB8DB

From: <sip:004926379447910@versatel.sip>;tag=843B54DF-207C
To: <sip:004915142614398@versatel.sip>;tag=3jeupg6t-CC-16
Call-ID: 9ED0A9B-8F6611EE-96B6DD9B-33AF9DD@100.88.38.226
Timestamp: 1701424323
CSeq: 103 BYE
P-Access-Network-Info: IEEE-802.11;"ue-ip=100.88.38.226";"ue-port=5060";"location-info=100.88.38.226"
Content-Length: 0


030244: Dec 1 10:52:08.196: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+491603680613@10.136.33.70:5060 SIP/2.0
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339663c002011
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:08 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70

Supported: 100rel,timer,resource-priority,replaces
Cisco-Guid: 0279989442-2405831150-2528763291-0054196701
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 105 INVITE
Max-Forwards: 70
Expires: 180
Allow-Events: presence
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=VIDEO_UNSPECIFIED
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uac
Min-SE: 1800
Session-ID: 80d35b4551d6babd3c9256ba51655576;remote=82d2b9a14449591fbe42dfa1224e68c1
P-Asserted-Identity: <sip:004926379447999@10.136.33.60>
Contact: <sip:+4926379447911@10.136.33.60:5060>
Content-Length: 0


030245: Dec 1 10:52:08.198: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339663c002011
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:08 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
CSeq: 105 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-16.12.4a
Session-ID: 82d2b9a14449591fbe42dfa1224e68c1;remote=80d35b4551d6babd3c9256ba51655576
Content-Length: 0


030246: Dec 1 10:52:08.198: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339663c002011
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550

To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:08 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
CSeq: 105 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:+491603680613@10.136.33.70:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-16.12.4a
Session-ID: 82d2b9a14449591fbe42dfa1224e68c1;remote=00000000000000000000000000000000
Require: timer
Session-Expires: 1800;refresher=uac
Supported: timer
Content-Type: application/sdp
Content-Length: 246

v=0
o=CiscoSystemsSIP-GW-UserAgent 4073 5024 IN IP4 10.136.33.70
s=SIP Call

c=IN IP4 10.136.33.70
t=0 0
m=audio 9846 RTP/AVP 8 101
c=IN IP4 10.136.33.70
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

030247: Dec 1 10:52:08.363: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+491603680613@10.136.33.70:5060 SIP/2.0
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK133967243e3e01
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:08 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 105 ACK
Allow-Events: presence

Session-ID: 80d35b4551d6babd3c9256ba51655576;remote=82d2b9a14449591fbe42dfa1224e68c1
Content-Type: application/sdp
Content-Length: 247

v=0
o=CiscoSystemsCCM-SIP 1722336 4 IN IP4 10.136.33.60
s=SIP Call
c=IN IP4 10.49.20.161
b=TIAS:64000
b=CT:64
b=AS:64
t=0 0
m=audio 31216 RTP/AVP 8 101
a=ptime:20
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

030248: Dec 1 10:52:08.365: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Received:
UPDATE sip:+491603680613@10.136.33.70:5060 SIP/2.0

Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339687bf3381c
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:08 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
Supported: timer,resource-priority,replaces
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 106 UPDATE
Session-ID: 80d35b4551d6babd3c9256ba51655576;remote=82d2b9a14449591fbe42dfa1224e68c1
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=VIDEO_UNSPECIFIED
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires: 1800;refresher=uac
Min-SE: 1800
P-Asserted-Identity: "4710" <sip:004926379447999@10.136.33.60>
Contact: <sip:+4926379447911@10.136.33.60:5060>

Content-Length: 0


030249: Dec 1 10:52:08.367: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339687bf3381c
From: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
To: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
Date: Fri, 01 Dec 2023 09:52:08 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
Server: Cisco-SIPGateway/IOS-16.12.4a
CSeq: 106 UPDATE
Allow-Events: telephone-event
Contact: <sip:+491603680613@10.136.33.70:5060>
Session-ID: 82d2b9a14449591fbe42dfa1224e68c1;remote=80d35b4551d6babd3c9256ba51655576
Require: timer
Session-Expires: 1800;refresher=uac
Supported: timer
Content-Length: 0


030287: Dec 1 10:52:25.033: //2950716/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:004926379447911@100.88.38.226:5060 SIP/2.0
Via: SIP/2.0/UDP 100.88.36.38:5060;branch=z9hG4bK3imecm00307d067eodv0cd0000g10.1
Call-ID: fsz5ee6f6frfj6iuqrzzterpfqru3esg@ATS.esn001vas001.voice.huawei.versatel.mpls.13
From: <sip:01603680613@Versatel.de;user=phone>;tag=jgjrg5pp-CC-13

To: <sip:004926379447911@10.200.15.2;transport=udp;user=phone>;tag=843B813F-290
CSeq: 3 BYE
Max-Forwards: 59
Reason: SIP;cause=200;text="User Triggered"
P-Access-Network-Info: xDSL;"location-info=100.88.38.226"
Content-Length: 0


030288: Dec 1 10:52:25.035: //2950716/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 100.88.36.38:5060;branch=z9hG4bK3imecm00307d067eodv0cd0000g10.1
From: <sip:01603680613@Versatel.de;user=phone>;tag=jgjrg5pp-CC-13
To: <sip:004926379447911@10.200.15.2;transport=udp;user=phone>;tag=843B813F-290
Date: Fri, 01 Dec 2023 09:52:25 GMT
Call-ID: fsz5ee6f6frfj6iuqrzzterpfqru3esg@ATS.esn001vas001.voice.huawei.versatel.mpls.13
Server: Cisco-SIPGateway/IOS-16.12.4a
CSeq: 3 BYE
Reason: Q.850;cause=16
Session-ID: 80d35b4551d6babd3c9256ba51655576;remote=82d2b9a14449591fbe42dfa1224e68c1

Content-Length: 0


030289: Dec 1 10:52:25.035: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:+4926379447911@10.136.33.60:5060 SIP/2.0
Via: SIP/2.0/UDP 10.136.33.70:5060;branch=z9hG4bK35CB972327
From: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
To: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
Date: Fri, 01 Dec 2023 09:52:08 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
User-Agent: Cisco-SIPGateway/IOS-16.12.4a
Timestamp: 1701424345
CSeq: 103 BYE
Reason: SIP;cause=200;text="User Triggered"
P-Access-Network-Info: xDSL;"location-info=100.88.38.226"
Max-Forwards: 59
Session-ID: 82d2b9a14449591fbe42dfa1224e68c1;remote=80d35b4551d6babd3c9256ba51655576
Content-Length: 0




030290: Dec 1 10:52:25.038: //2950697/F6635C339696/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:+497618832400@10.136.33.70:5060 SIP/2.0
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339762d60c7cd
From: <sip:+4926379447911@10.136.33.60>;tag=1722306~0048b14b-05aa-49bd-8135-a09e0f721b42-51655534
To: <sip:+497618832400@10.136.33.70>;tag=843AD4D8-718
Date: Fri, 01 Dec 2023 09:51:02 GMT
Call-ID: F663F85B-8F6511EE-969CDD9B-33AF9DD@10.136.33.70
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 BYE
Reason: Q.850;cause=16
Session-ID: 541e11b8998c12e11c7687ba51655535;remote=d484bb2dfa3851cb8e2d7a7885ccb242
Content-Length: 0


030291: Dec 1 10:52:25.040: //2950696/F6635C339696/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:+497618832400@100.88.36.38:5060;user=phone;transport=udp SIP/2.0

Via: SIP/2.0/UDP 100.88.38.226:5060;branch=z9hG4bK35CB98482
From: <sip:004926379447911@10.200.15.2;transport=udp;user=phone>;tag=843AD4F1-1632
To: <sip:07618832400@Versatel.de;user=phone>;tag=d33i3j5p-CC-30
Date: Fri, 01 Dec 2023 09:51:02 GMT
Call-ID: z6t353f3srijqedidutf5esid6r5jjze@ATS.esn001vas001.voice.huawei.versatel.mpls.30
User-Agent: Cisco-SIPGateway/IOS-16.12.4a
Timestamp: 1701424345
CSeq: 101 BYE
Reason: Q.850;cause=16
Session-ID: 541e11b8998c12e11c7687ba51655535;remote=d484bb2dfa3851cb8e2d7a7885ccb242
Max-Forwards: 70
Content-Length: 0


030292: Dec 1 10:52:25.041: //2950697/F6635C339696/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.136.33.60:5060;branch=z9hG4bK1339762d60c7cd
From: <sip:+4926379447911@10.136.33.60>;tag=1722306~0048b14b-05aa-49bd-8135-a09e0f721b42-51655534

To: <sip:+497618832400@10.136.33.70>;tag=843AD4D8-718
Date: Fri, 01 Dec 2023 09:52:25 GMT
Call-ID: F663F85B-8F6511EE-969CDD9B-33AF9DD@10.136.33.70
Server: Cisco-SIPGateway/IOS-16.12.4a
CSeq: 101 BYE
Reason: Q.850;cause=16
Session-ID: d484bb2dfa3851cb8e2d7a7885ccb242;remote=541e11b8998c12e11c7687ba51655535
Content-Length: 0


030293: Dec 1 10:52:25.041: //2950717/10B04CC296B9/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.136.33.70:5060;branch=z9hG4bK35CB972327
From: <sip:+491603680613@10.136.33.70>;tag=843B8133-400
To: <sip:+4926379447911@10.136.33.60>;tag=1722336~0048b14b-05aa-49bd-8135-a09e0f721b42-51655550
Date: Fri, 01 Dec 2023 09:52:25 GMT
Call-ID: 10B09AD6-8F6611EE-96BFDD9B-33AF9DD@10.136.33.70
Server: Cisco-CUCM11.5
CSeq: 103 BYE

Content-Length: 0


030294: Dec 1 10:52:25.188: //2950696/F6635C339696/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 100.88.38.226:5060;branch=z9hG4bK35CB98482
From: <sip:004926379447911@10.200.15.2;transport=udp;user=phone>;tag=843AD4F1-1632
To: <sip:07618832400@Versatel.de;user=phone>;tag=d33i3j5p-CC-30
Call-ID: z6t353f3srijqedidutf5esid6r5jjze@ATS.esn001vas001.voice.huawei.versatel.mpls.30
Timestamp: 1701424345
CSeq: 101 BYE
P-Access-Network-Info: xDSL;"location-info=100.88.38.226"
Content-Length: 0


030295: Dec 1 10:52:25.694: //2950730/4DE18D800000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 100.88.38.226:5060;branch=z9hG4bK35CB94193

macnow · ‎09-22-2023

I also heve tshi problem

One way voice when answered from hunt queue

Hi Carlo, i have tried it in all possible variations and unfortunately had no success with the upload. So now I'm using this method: