I am trying to set up a 4 port Auto Attendant on a Call Manager system I have running. The Call Manager version is 3.1(3c) and the Application Manager version is 1.2a. I have managed to get the application engine running, but the JTAPI subsystem never gets past INITIALIZING. I have seen several messages with the JTAPI susbsystem in the PARTIAL_SERVICE mode. I have re-installed the JTAPI client from the publisher and still get the same thing. This is a co-resident install with the Application Manager running on the subscriber. Has anyone seen this before?
1) Uninstall the JTAPI client and reinstall from CM. I tried upgrading the JTAPI client once and it didn't work until I uninstalled and reinstalled from the control panel.
2) Verify your entire App admin config makes no references to PC names. Change all the PC names to IP addresses of the server. ( I believe the Engine config and the directory config make references to the server name/IP) I know the JTAPI looks for CM's IP address....
3) Verify all LDAP users created for AA have matching passwords in CM and the JTAPI config under Appadmin. All make sure that all the appropriate devices are associated and the user has "enable CTI application use" selected.
From my experience 97% of the time it is a misconfigured cti route point or cti port. As stated earlier check your resources setup in APP admin cti ports and cti route point are correct. And make sure the user has cti enabled and no primary extension.
Also check under jtapi configuration that CTI port groups are correct i.e sequential port numbers that you set-up in CM
Have a look at your trace file you might find the error in the url below.
Do you by any chance have the attendant console installed on the publisher as well?
if so have a look at this.
Q. Are there any known problems with IVR/ICD when it is a co-resident with Attendant Console?
A. Cisco CallManager Attendant Console and IVR/ICD both use RMI for communication. The default RMI communication port is 1099. If Attendant Console starts up before IVR/ICD, it binds to port 1099 first. However, if Attendant Console starts up after ICD/IVR is up and the port 1099 is already taken, it looks for the first available port after 1099. Attendant Console will work fine in either situation. However, IVR/ICD will run into problems if 1099 port is already taken when it starts up. You will see the following error in the IVR/ICD logs:
Port already in use: 1099.
There are two possible options to correct this problem:
Ensure that Cisco Telephony Call Dispatcher service starts after IVR/ICD.
Change the default RMI port in the IVR/ICD configuration.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...