I am having a problem accessing my personal assistant server. Everytime I dial the PA number, I get fast busy. I've configured everything according to the admin guide but when I look at the CTI routepoint in the cm admin screen, the status says "not found" & there is no IP address listed. I've checked that the CTI route point is associated with the PAuser. Any suggestions ?
what does the server status on the PA server show, I'm guessing down?
Check the Jtapi and Skinny config on the PA server to make sure this is correct. PA likes to resolve names so edit your LMhosts file on the PA server and add the names of the CM and Unity servers so you can ping them by name and just use names in PA config rather than IP addresses.
There is a bug in call manager to do with matching exact number e. 7001 instead of 700x, which means PA users can't call each other. I know this doesn't relate to your problem but it's worth watching out for.
Make sure you use wild card translation patterns such as 700X rather than individual numbers, also 700X Cti Route points, PA server is case sensitive when you enter the Route points in Server config.
Concentrate on making sure the JTAPI user and password config is correct on bothe the CM and PA servers as this is the most likely cause of your problem.
(who has had a bad experience with PA and TAC, and learned from it)
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...