[cisco-voip] CUE 8.0 with CUCM Issue

Mon Apr 18 10:26:29 EDT 2011

Thanks for the Assist today, certainly a good night's sleep helped me to solve this, I tried to deploy this as I would a Unity Connection or Unity in that my GW was in an inbound partition that only access a DID -PT where Translations pass it into Auto attendant or Extensions. This does not work with CUE, with CUE, the Inbound CSS on the GW must have direct access to the CUE Ports.

Jorge
From: Jason Aarons (AM) [mailto:jason.aarons at us.didata.com]
Sent: Sunday, April 17, 2011 11:14 PM
To: Ryan Schwab; Jorge L. Rodriguez Aguila; 'Cisco-Voip'
Subject: RE: [cisco-voip] CUE 8.0 with CUCM Issue

I have to agree that reloading CUE 8x has fixed more problems than I want to admit.  Usually it revolves around CTI registration failures.

>From a technical view reloading is the last thing I want to do, I'd rather debug and get a bug id, make the product better.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Schwab
Sent: Sunday, April 17, 2011 9:51 PM
To: 'Jorge L. Rodriguez Aguila'; 'Cisco-Voip'
Subject: Re: [cisco-voip] CUE 8.0 with CUCM Issue

As you've described, there should be no need for transcoding. I was also incorrect, if the CUE did need a transcoder, the CTI ports would engage one (as per it's MRGL).

http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_configuration_example09186a0080289ef0.shtml#intro

Take a look here, not sure if it will add any value though. My experience with CUE integrating with CUCM (version 7.0) has been it takes a few reloads on initial configuration to get everything going 100%. I know it's just shooting in the dark, but it may be worth a reload of the CUE module and also a reset on the IPIPGW in CUCM.

Good luck!

From: Jorge L. Rodriguez Aguila [mailto:jorge.rodriguez at netxar.com]
Sent: April-17-11 7:32 PM
To: Ryan Schwab; 'Cisco-Voip'
Subject: RE: [cisco-voip] CUE 8.0 with CUCM Issue

IP2IP GW is on same region and Device Pool as VM CTI Ports, So is Transcoder and They are part of the MRG and MRGL  associated with the Device Pool

From: Ryan Schwab [mailto:schwaby81 at shaw.ca]
Sent: Sunday, April 17, 2011 9:24 PM
To: Jorge L. Rodriguez Aguila; 'Cisco-Voip'
Subject: RE: [cisco-voip] CUE 8.0 with CUCM Issue

Jorge,

This does sound like a transcoding issue. The device that does not support a codec would need to request a transcoder resource. In this case, that's the CUE.

Your CUE is registered via CTI Ports to CUCM? Is the SIP/T1 gateway in a different region than the CTI Ports/Route point?

Where do you have your transcoding resources registered too? If remember correctly the way to do this is to register your transcoder resources in the same fashion you would if it was a CME.

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jorge L. Rodriguez Aguila
Sent: April-17-11 6:39 PM
To: Cisco-Voip (cisco-voip at puck.nether.net)
Subject: [cisco-voip] CUE 8.0 with CUCM Issue

I have integrated a CUE 8.0 with CUCM 8.0.3 and internally it works perfectly but when calls coming in from a T1 or a SIP trunk are transferred to CUE I get Busy tone on T1 and dropped call on the SIP trunk(IP2IP GW running SIP towards Provider and H323 towards Call Manager). I have verified that even though I am running G711u I have HW transcoding resources available. Any ideas on what Might be? This is my first CUE to Call Manager (non express) I don't seem to find what is wrong and some pointers into where to look are greatly appreciated.

Jorge Rodriguez

________________________________

Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110418/477c8098/attachment.html>