I'm having a problem where I've created a Pilot Point, it shows up in the web interface with the same settings as several others(different DN of course), but I get a fast busy when trying to dial it. Hunt group members are not busy. When I look in the real time monitoring at 'Devices:CTI' I see all of the working Pilot Points, but not my new ones. I thought maybe the database connection was broken, but clicking on the resource usage button and switching to 'Directory Servers' shows that the publisher and other server are connected fine.
Thank you for posting your fix to your own problem as it has fixed our little snafu as well. We didn't know that even if you were NOT going to use the Attendant Console with certain Pilot Point/Hunt Groups, that you STILL have to associate the user 'ac' to the pilot point devices.
Lesson learned yet again on the Net professionals Forum.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...