[cisco-voip] CCX 5.0 Issue

[Buchanan, James]

You may also wish to check and make sure the right script is being invoked, and also make sure that any referenced CSQs are in place.

James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | jbuchanan at presidio.com<mailto:jbuchanan at ctiusa.com>
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com<http://www.presidio.com/>
CCIE #25863, Voice


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Anthony Holloway
Sent: Thursday, February 10, 2011 1:38 PM
To: Cauthen, John A.
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCX 5.0 Issue

Could you run a data re-sync?  Go to Subsystems > Telephony and you'll find it on the lower left sidebar.

Just do a check and see if there are any discrepancies.

If you check in CUCM, I would imagine you would see the alerting name of the CTI port for DN 7806 is 7801.  This probably happens when you create the CTI port group and you specify a number instead of a name for the alerting field.

Anthony

On Thu, Feb 10, 2011 at 1:24 PM, Cauthen, John A. <John.Cauthen at agg.com<mailto:John.Cauthen at agg.com>> wrote:
We are having an issue with one of our Applications (auto attendant) in CCX 5.0 not being invoked when the DN associated to trigger configuration is dialed.  When the DN is dialed it goes to one of the assigned CTI Ports from the related Call Control Group, rings twice then plays the ‘I’m sorry…system problems’ prompt.  In the trigger configuration I changed the application association to another application that uses the same Call Control Group and the trigger worked fine when associated with the other application.

I also noticed that when I dial the DN my phone displays two CTI Ports from the Call Control Group:

i.e.          To 7801
                (7806)

Rings twice then changes the CTI Port number in ():

i.e.          To 7806

Then plays the ‘I’m sorry…system problems’ prompt.

We did reboot the server yesterday morning and noticed the issue last night…we had not had any problems before that.  I have tried refreshing everything (application, script, prompts, etc.), made sure the script was still loaded, and made sure the prompts are still in prompt management.  Double checked the trigger configuration as well.  I know I must be missing something because it’s still not working and of course this wasn’t the first time we have ever rebooted this server.

Any suggestions will be appreciated.

Thanks,
John


________________________________
Note:

This message and any attachments from the law firm Arnall Golden Gregory LLP may contain CONFIDENTIAL and legally protected information.  If you are not the addressee and an intended recipient, please do not read, copy, use or disclose this communication to others;  also, please notify the sender by replying to this message, and then delete it from your system.  Thank you.

________________________________

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110210/23e41e46/attachment.html>