[cisco-voip] Native Call Queuing on UCM 12.5 with SIP Trunks

[Pawlowski, Adam]

We went from 15.4(3)M9 to 15.7(3)M4b

Noted also in this version that we previously allowed video/media to flow to the CUBE just in case we were ever to use it for routing media calls, and this version (15.7) drops calls from Jabber, etc when we place them on hold.

TAC said it was something to do with the number of options in the SDP changing and it being a protocol violation. The IEC error and Q code did sort of indicate this, but, as to why Cisco's systems don't want to play nice protocol wise with each other I don't know.



From: Ryan Huff <ryanhuff at outlook.com>
Sent: Monday, December 2, 2019 10:25 AM
To: Pawlowski, Adam <ajp26 at buffalo.edu>; cisco-voip at puck.nether.net
Subject: Re: Native Call Queuing on UCM 12.5 with SIP Trunks

Adam,

I've not encountered the streaming issue with a SIP trunk, just H.323.. interesting.

Out of curiosity, what code level in the ISR G2 did you go to when you encountered this? The behavior of simplex streaming is to send a null/fake IP address in the logic channel multimedia control message, which for anything required to check incoming RTP packets against the IP/port would fail (creating the silent MoH condition) which I was under the impression was only the G3 ISRs.

Thanks,

Ryan
________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> on behalf of Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>
Sent: Monday, December 2, 2019 8:50 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Native Call Queuing on UCM 12.5 with SIP Trunks


After an upgrade on our CUBE to a later IOS (ISR G2) we needed to have the duplex streaming parameter enabled for MOH/Ringback to work properly.



I believe there is a note about that being needed for the 4400 series gateways as well, but, I know we didn't have it before but needed it at some point to get media to be heard properly by the far end in a network hold kind of situation.



Adam







From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Mark H. Turpin
Sent: Monday, December 2, 2019 8:20 AM
To: Dana Tong <dana.tong at yellit.com.au<mailto:dana.tong at yellit.com.au>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Native Call Queuing on UCM 12.5 with SIP Trunks



Does the problem go away if you force an MTP?



Can you provide a debug ccsip messages of an external call?



Can you share your sanitized CUBE config?



Curious if your call/media is changing after the initial announcement and your ITSP doesn't care for the way you're attempting to change it.



________________________________

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> on behalf of Dana Tong <dana.tong at yellit.com.au<mailto:dana.tong at yellit.com.au>>
Sent: Monday, December 2, 2019 12:36 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] Native Call Queuing on UCM 12.5 with SIP Trunks



*** EXTERNAL EMAIL - DO NOT CLICK LINKS ***

Hi all,



This being back on the tools is doing my head in. I think I've been away too long.



So I have configured native call queuing on UCM 12.5.x

Internal calls queue fine. The initial announcement plays. Period announcements work and the MOH is fine in between.



External calls hear the initial announcement.

There is no MOH after the announcement and the external user has ring-back tone.

There is no periodic announcement.



Any thoughts on why internal is okay and external is not working? Is it relating to SIP supplementary services?



Cheers

Dana


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191202/a9d1b7a6/attachment.htm>