Guest

Cisco Unified Intelligent Contact Management Enterprise

When Does JTAPI Need to Be Cycled in an IPCC Environment?

Cisco - When Does JTAPI Need to Be Cycled in an IPCC Environment?

Document ID: 19344

Updated: May 26, 2005

   Print

Introduction

This document answers some common questions about when you need to cycle the Java Telephony Application Programming Interface (JTAPI) process on a Cisco CallManager Peripheral Gateway (PG) after certain CallManager configuration changes.

Q. When do you need to cycle the JTAPI process on the Cisco CallManager PG?

A. When the JTAPI gateway process on the PG connects to Cisco CallManager, the process logs into the CallManager as a user. The typical login is PGuser. This user has control of certain devices based on user device associations. The answer to this question depends on the version of Cisco CallManager that you run in your environment:

  • Cisco CallManager version 3.1.x and later—JTAPI clients for these versions of Cisco CallManager see these changed device associations. JTAPI polls every 30 seconds for new and changed device associations.

  • Cisco CallManager version 3.0.x and earlier—JTAPI clients for this version of Cisco CallManager do not see these changed device associations. JTAPI polls every 30 seconds, only for new device associations. You need to cycle the JTAPI process on the PG in the case of changed device associations. In a simplexed PG environment, the cycle of the PG process is enough. In a duplexed environment, the exit_opc command is the best way to cycle JTAPI. Refer to the document Using the OPCTest Command Line Utility.

Q. When you make changes to the Dialed Number (DN) of an existing phone in the Cisco IP Contact Center (IPCC) environment, do you need to cycle the JTAPI process on the Cisco CallManager PG in order to see the changes?

A. When the JTAPI gateway process on the PG connects to Cisco CallManager, the process logs into the CallManager as a user. The typical login is PGuser. This user has control of certain devices based on user device associations. The answer to this question depends on the version of Cisco CallManager that you run in your environment:

  • Cisco CallManager version 3.1.x and later—JTAPI clients for these versions of Cisco CallManager see these changed device associations. JTAPI polls every 30 seconds for new and changed device associations.

  • Cisco CallManager version 3.0.x and earlier—JTAPI clients for this version of Cisco CallManager do not see these changed device associations. JTAPI polls every 30 seconds, only for new device associations. You need to cycle the JTAPI process on the PG in the case of changed device associations. In a simplexed PG environment, the cycle of the PG process is enough. In a duplexed environment, the exit_opc command is the best way to cycle JTAPI. Refer to the document Using the OPCTest Command Line Utility.

Related Information

Updated: May 26, 2005
Document ID: 19344