Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Call delay on incoming CUCM 9.1.1

I am experiencing an issue with users experiencing a delay in the RTP stream on incoming calls. This is happening at a particular location and occurs with incoming site calls as well as incoming via the ITSP. This is a clustered infrastructure with Cisco UBEs. Site A answers ringing phone and says "Thanks for calling, this is Bob how can I help you?" and people on the other end are only hearing "I help you?" etc.

Site 1 ----- CUBE_A ----- ITSP

Site 2 ----- CUBE_A

Site 3 ----- CUBE_A

ETC ETC

It is not happening at all sites that share the CUBE's trunk to the ITSP so I dont think its an issue with the SIP profile or trunk. Also, since this happens between sites, I dont believe the trunk is the issue.

QOS is configured the same on all sites. This includes ones that have no issues.

I checked WAN links and everything seems good.

I checked the switch and everything seems good on ports as well as the trunk to the router.

We are running 6921 and 7942 phones.

Stumped.

Any ideas would be greatly appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions
New Member

Call delay on incoming CUCM 9.1.1

CSCue50773

upgrade

15 REPLIES

Call delay on incoming CUCM 9.1.1

Hi.

Please attach a debug ccsip messages during a delayed call.

Thanks

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

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

Call delay on incoming CUCM 9.1.1

Carlo,

Please see below. Thanks

540622: Nov  8 18:49:50.783: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:xxxxxxxxxx@xxx.xx.xx.xx SIP/2.0
Via: SIP/2.0/UDP 72.11.192.82:5060;branch=z9hG4bKq348mg304gnh1lgq90k0.1
From: <>xxxxxxxxxx@xx.xx.xxx.xx;user=phone>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.xx.xx>
Call-ID: BW1349507320811131982825720@xxx.xx.xx.xx
CSeq: 478560711 INVITE
Contact:
Supported: 100rel
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept: application/media_control+xml,application/sdp,multipart/mixed
Max-Forwards: 39
Content-Type: application/sdp
Content-Length: 197
Route:

v=0
o=- 2178467081 1 IN IP4 72.11.192.93
s=-
c=IN IP4 72.11.192.93
t=0 0
m=audio 49376 RTP/AVP 18 0 8 101
a=ptime:20
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15


540623: Nov  8 18:49:50.785: //3157575/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP xx.xx.xxx.xx:5060;branch=z9hG4bKq348mg304gnh1lgq90k0.1
From: <>xxxxxxxxxx@xx.xx.xxx.xx;user=phone>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.xx.xx>
Date: Fri, 08 Nov 2013 18:49:50 GMT
Call-ID: BW1349507320811131982825720@72.11.192.10
CSeq: 478560711 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Content-Length: 0


540624: Nov  8 18:49:50.785: //3157576/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:xxxxxxxxxx@xx.xx.25.100:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xx.54.50:5060;branch=z9hG4bK192FCD273
From: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
To:
Date: Fri, 08 Nov 2013 18:49:50 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@172.16.54.50
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 1643246522-1205670371-2425275781-4192054310
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M2
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1383936590
Contact: <8138188597>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 38
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 306

v=0
o=CiscoSystemsSIP-GW-UserAgent 1124 8737 IN IP4 xxx.xx.54.50
s=SIP Call
c=IN IP4 172.16.54.50
t=0 0
m=audio 27782 RTP/AVP 18 0 101 19
c=IN IP4 172.16.54.50
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:19 CN/8000


540625: Nov  8 18:49:51.151: //3157576/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP xxx.xx.54.50:5060;branch=z9hG4bK192FCD273
From: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
To:
Date: Fri, 08 Nov 2013 18:49:50 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@172.16.54.50
CSeq: 101 INVITE
Allow-Events: presence
Content-Length: 0


540630: Nov  8 18:49:51.578: //3157576/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP xxx.xx.54.50:5060;branch=z9hG4bK192FCD273
From: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
To: ;tag=991105~c5c64f56-4dee-4ada-bc88-2c1fc1fa65c2-106983788
Date: Fri, 08 Nov 2013 18:49:50 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@172.16.54.50
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: <8009950>
Remote-Party-ID: <8009950>;party=called;screen=yes;privacy=off
Contact:
Content-Length: 0


540631: Nov  8 18:49:51.578: //3157575/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP xx.xx.192.82:5060;branch=z9hG4bKq348mg304gnh1lgq90k0.1
From: <8138188597>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F22CCC-175B
Date: Fri, 08 Nov 2013 18:49:50 GMT
Call-ID: BW1349507320811131982825720@xx.xx.192.10
CSeq: 478560711 INVITE
Require: 100rel
RSeq: 7856
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <>xxxxxxxxxx@xxx.xx.54.50:5060>
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Content-Length: 0


540632: Nov  8 18:49:51.680: //3157576/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.54.50:5060;branch=z9hG4bK192FCD273
From: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
To: <>xxxxxxxxxx@xx.xx.xx.100>;tag=991105~c5c64f56-4dee-4ada-bc88-2c1fc1fa65c2-106983788
Date: Fri, 08 Nov 2013 18:49:50 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@172.16.54.50
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Allow-Events: presence
Supported: replaces
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Session-Expires:  1800;refresher=uas
Require:  timer
P-Asserted-Identity: "VoiceMail" <>8009950@xx.xx.xx.100>
Remote-Party-ID: "VoiceMail" <>8009950@xx.xx.xx.100>;party=called;screen=yes;privacy=off
Contact: <>xxxxxxxxxx@xx.xx.xx.100:5060>;isFocus
Content-Type: application/sdp
Content-Length: 237

v=0
o=CiscoSystemsCCM-SIP 991105 1 IN IP4 xx.xx.xx.100
s=SIP Call
c=IN IP4 xx.xx.xx.220
b=TIAS:64000
b=AS:64
t=0 0
m=audio 23398 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15


540633: Nov  8 18:49:51.680: //3157576/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:xxxxxxxxxx@xx.xx.xx.100:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xx.54.50:5060;branch=z9hG4bK192FCF19CE
From: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
To: <>xxxxxxxxxx@xx.xx.xx.100>;tag=991105~c5c64f56-4dee-4ada-bc88-2c1fc1fa65c2-106983788
Date: Fri, 08 Nov 2013 18:49:50 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@172.16.54.50
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


540634: Nov  8 18:49:51.730: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:xxxxxxxxxx@xxx.xx.54.50:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.xxx.xx:5060;branch=z9hG4bK9sd1cr2048h0sk04t0n1.1
From: <>xxxxxxxxxx@xx.xx.xxx.82;user=phone>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F22CCC-175B
Call-ID: BW1349507320811131982825720@72.11.192.10
CSeq: 478560712 PRACK
RAck: 7856 478560711 INVITE
Max-Forwards: 39
Content-Length: 0


540635: Nov  8 18:49:51.730: //3157575/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.192.82:5060;branch=z9hG4bK9sd1cr2048h0sk04t0n1.1
From: <>xxxxxxxxxx@xx.xx.192.82;user=phone>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F22CCC-175B
Date: Fri, 08 Nov 2013 18:49:51 GMT
Call-ID: BW1349507320811131982825720@xx.xx.192.10
Server: Cisco-SIPGateway/IOS-15.2.4.M2
CSeq: 478560712 PRACK
Content-Length: 0


540636: Nov  8 18:49:51.730: //3157575/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.192.82:5060;branch=z9hG4bKq348mg304gnh1lgq90k0.1
From: <>xxxxxxxxxx@xx.xx.192.82;user=phone>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F22CCC-175B
Date: Fri, 08 Nov 2013 18:49:51 GMT
Call-ID: BW1349507320811131982825720@xx.xx.192.10
CSeq: 478560711 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <>xxxxxxxxxx@xxx.xx.54.50:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

v=0
o=CiscoSystemsSIP-GW-UserAgent 3678 1750 IN IP4 xxx.xx.54.50
s=SIP Call
c=IN IP4 xxx.xx.54.50
t=0 0
m=audio 21634 RTP/AVP 0 101
c=IN IP4 xxx.xx.54.50
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20


540637: Nov  8 18:49:51.830: //3157575/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.192.82:5060;branch=z9hG4bKq348mg304gnh1lgq90k0.1
From: <>xxxxxxxxxx@xx.xx.192.82;user=phone>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx";tag=C7F22CCC-175B
Date: Fri, 08 Nov 2013 18:49:51 GMT
Call-ID: BW1349507320811131982825720@72.11.192.10
CSeq: 478560711 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <>xxxxxxxxxx@xxx.xx.54.50:5060>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.2.4.M2
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 247

v=0
o=CiscoSystemsSIP-GW-UserAgent 3678 1750 IN IP4 172.16.54.50
s=SIP Call
c=IN IP4 xx.xx.54.50
t=0 0
m=audio 21634 RTP/AVP 0 101
c=IN IP4 xxx.xx.54.50
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20


540638: Nov  8 18:49:51.890: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:xxxxxxxxxx@xxx.xx.54.50:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.192.82:5060;branch=z9hG4bKgcsr47206gd1capu06g1.1
From: <>xxxxxxxxxx@xx.xx.192.82;user=phone>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F22CCC-175B
Call-ID: BW1349507320811131982825720@xx.xx.192.10
CSeq: 478560711 ACK
Contact:
Max-Forwards: 39
Content-Length: 0


540639: Nov  8 18:49:51.898: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:xxxxxxxxxx@xxx.xx.54.50:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.192.82:5060;branch=z9hG4bKgcsr47206gd1capu06g1.1
From: <>xxxxxxxxxx@xx.xx.192.82;user=phone>;tag=650915513-1383936590732-
To: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F22CCC-175B
Call-ID: BW1349507320811131982825720@xx.xx.192.10
CSeq: 478560711 ACK
Contact:
Max-Forwards: 39
Content-Length: 0


540703: Nov  8 18:50:08.461: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
UPDATE sip:xxxxxxxxxx@xxx.xx.54.50:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.25.100:5060;branch=z9hG4bK13b33c51f9fd25
From: <>xxxxxxxxxx@xx.xx.25.100>;tag=991105~c5c64f56-4dee-4ada-bc88-2c1fc1fa65c2-106983788
To: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
Date: Fri, 08 Nov 2013 18:49:51 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@172.16.54.50
User-Agent: Cisco-CUCM9.1
Max-Forwards: 70
Supported: timer,resource-priority,replaces
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 UPDATE
Supported: X-cisco-srtp-fallback
Supported: Geolocation
P-Asserted-Identity: "Billy Bob" <>3389110@xx.xx.25.100>
Remote-Party-ID: "Billy Bob" <>3389110@xx.xx.25.100>;party=calling;screen=yes;privacy=off
Contact: <>xxxxxxxxxx@xx.xx.25.100:5060>
Content-Length: 0


540704: Nov  8 18:50:08.461: //3157576/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.25.100:5060;branch=z9hG4bK13b33c51f9fd25
From: <>xxxxxxxxxx@xx.xx.25.100>;tag=991105~c5c64f56-4dee-4ada-bc88-2c1fc1fa65c2-106983788
To: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
Date: Fri, 08 Nov 2013 18:50:08 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@172.16.54.50
Server: Cisco-SIPGateway/IOS-15.2.4.M2
CSeq: 101 UPDATE
Allow-Events: telephone-event
Contact: <>xxxxxxxxxx@xxx.xx.54.50:5060>
Supported: timer
Content-Length: 0


540748: Nov  8 18:50:16.265: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
BYE sip:xxxxxxxxxx@xxx.xx.54.50:5060 SIP/2.0
Via: SIP/2.0/UDP xx.xx.25.100:5060;branch=z9hG4bK13b3473348aa88
From: <>xxxxxxxxxx@xx.xx.25.100>;tag=991105~c5c64f56-4dee-4ada-bc88-2c1fc1fa65c2-106983788
To: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
Date: Fri, 08 Nov 2013 18:49:51 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@172.16.54.50
User-Agent: Cisco-CUCM9.1
Max-Forwards: 70
CSeq: 102 BYE
Reason: Q.850;cause=16
Content-Length: 0


540749: Nov  8 18:50:16.265: //3157575/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Sent:
BYE sip:xx.xx.192.82:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP xxx.xx.54.50:5060;branch=z9hG4bK192FE01378
From: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F22CCC-175B
To: <>xxxxxxxxxx@xx.xx.192.82;user=phone>;tag=650915513-1383936590732-
Date: Fri, 08 Nov 2013 18:49:51 GMT
Call-ID: BW1349507320811131982825720@xx.xx.192.10
User-Agent: Cisco-SIPGateway/IOS-15.2.4.M2
Max-Forwards: 70
Timestamp: 1383936616
CSeq: 101 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=1065,OS=170400,PR=1220,OR=194108,PL=0,JI=0,LA=0,DU=24
Content-Length: 0


540750: Nov  8 18:50:16.265: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/UDP xx.xx.25.100:5060;branch=z9hG4bK13b3473348aa88
From: <>xxxxxxxxxx@xx.xx.25.100>;tag=991105~c5c64f56-4dee-4ada-bc88-2c1fc1fa65c2-106983788
To: <>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F229B4-2319
Date: Fri, 08 Nov 2013 18:50:16 GMT
Call-ID: 61F241CE-47DD11E3-9094C585-F9DDAC26@xxx.xx.54.50
Server: Cisco-SIPGateway/IOS-15.2.4.M2
CSeq: 102 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=1220,OS=194108,PR=1065,OR=170400,PL=0,JI=0,LA=0,DU=24
Content-Length: 0


540751: Nov  8 18:50:16.337: //3157575/61F1F3BA908E/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.16.54.50:5060;branch=z9hG4bK192FE01378
From: "xxxxxxxxxx xxxxxxxxxx"<>xxxxxxxxxx@xxx.xx.54.50>;tag=C7F22CCC-175B
To: <>xxxxxxxxxx@xx.xx.192.82;user=phone>;tag=650915513-1383936590732-
Call-ID: BW1349507320811131982825720@xx.xx.192.10
Timestamp: 1383936616
CSeq: 101 BYE
Content-Length: 0

New Member

So I am also facing same

So I am also facing same issue .We only see the issue when you call to specific location so I believe its more about that GW rather than the CuCM.

CuCM version: 9.1.2

 GW Version 15.1

Any thought?

Cisco Employee

Re:Call delay on incoming CUCM 9.1.1

Hi,

When you say that site to site calls also face the same issue, what is the exact call flow in that case?

Example : ip phone 1 (site A) >> cucm >> ip phone 2 (site b)

Or

Ip phone 1 >> cucm >> sip >> cube >> sip >> cucm >> ip phone 2

Regards,

Jagpreet


Sent from Cisco Technical Support Android App

Call delay on incoming CUCM 9.1.1

Hi,

The call flow is as follows:

Site 1 -- Site Gateway -- MPLS Cloud -- CUBE 2 -- CUCM -- CUBE 1 or 2 -- MPLS Cloud -- Site Gateway -- Site 2

That is for signaling. The RTP stream for site to site calls goes as follows:

Site 1 -- Site 1 Gateway -- MPLS Cloud -- Site 2 Gateway -- Site 2 Phone

The flow for PSTN calls is as follows:

Site 1 -- Site 1 Gateway -- MPLS Cloud -- CUBE 1 -- ITSM

Call delay on incoming CUCM 9.1.1

I forgot to mention that these calls flow through the IVR with Unity Connection. The issue only seems to happen when calls are routed through UC.

Call delay on incoming CUCM 9.1.1

Any ideas?

New Member

Re:Call delay on incoming CUCM 9.1.1

Hi. Did you get a resolution to this as the symptoms match an issue a customer is having?


Sent from Cisco Technical Support Android App

Call delay on incoming CUCM 9.1.1

Richard,

The issue has been resolved. We were expierencing a Cisco bug related to queuing and upgrading to 9.1.2 or 9.2.1 solved it. I forgot the version we went to but it was speifically made to address this bug.

Thanks and good luck.

New Member

Call delay on incoming CUCM 9.1.1

whats the bug id

Call delay on incoming CUCM 9.1.1

New Member

Call delay on incoming CUCM 9.1.1

CSCue50773

upgrade

New Member

Call delay on incoming CUCM 9.1.1

issue has started re-occuring currently running CUCM 9.1.2 we have also upgrade Unity connection to the same version as well as use new OVA template and recreated all of our VM with 4 cpu. AS they origianlly only had two cpu cisco thought that could have been causing issue. Our issue seems to start off with a single site and continue to grow now to multiple sites reporting the same 3 to 5 sec delay issue. I am running out of ideas? Any one else got one.

New Member

Call delay on incoming CUCM 9.1.1

Hello Collaboration team

Please i have the same issue ,  i upgraded my box from CUCM 7.1 to 9.1 at the remote location the users start to complain about delay to resppond to the call about 3 sec ( the can her only how we can help ) ? can use the same procedure or my case difirent

Call delay on incoming CUCM 9.1.1

I would upgrade from 9.1

2385
Views
5
Helpful
15
Replies
CreatePlease login to create content