Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Are there any known problems with IVR/ICD when it is a co-resident with Cisco CallManager Attendant Console?

0
10 Posted

Are there any known problems with IVR/ICD when it is a co-resident with Cisco CallManager Attendant Console?

0
10

A. Cisco CallManager Attendant Console and Interactive Voice Response (IVR)/Interactive Call Distribution (ICD) both use Remote Method Invocation (RMI) for communication. The default RMI communication port is 1099. If Cisco CallManager Attendant Console starts up before IVR/ICD, it binds to port 1099 first. However, if Cisco CallManager 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. Cisco CallManager Attendant Console works fine in either situation. However, IVR/ICD runs into problems if the 1099 port is already taken when it starts up. This error appears in the IVR/ICD logs: java.rmi.server.ExportException: 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.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123