Guest

Preview Tool

Cisco Bug: CSCta77690 - JTAPI not removing connections for redirecting parties at forward

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

6.1(3)

Description (partial)

Symptom:
In a Genesys T-server integration, there are 2 agents using T-server Agent Desktop, controlling their IP Phones. 

Agent A calls Agent B. Agent B's phone is ringing, but he has not answered the call yet.

The calling and called party see a connected event, while the call is actually not connected yet: the called phone is still ringing.

JTAPI shows this:

3314: Jul 15 13:33:37.624 GMT+000 %JTAPI-JTAPI-7-UNK:(P1-jtapi_genesys) 10062/1 CallCtlConnEstablishedEv 299109:genesys [#365] Cause:100 CallCtlCause:0 CiscoCause:0 CiscoFeatureReason:12

This should be CallCtlConnEstablishedEv 299109:genesys_agent

=> JTAPI is not sending a connected event for the DN of the agent, but for the callforwarding CTI Route Point.
JTAPI has the connected event for the call in an incorrect partition.

Conditions:
First found in CUCM 6.1.3-1000-13.
Also found in 6.1.4 main release.
Other 6.x versions can be affected as well.

CallFlow:
299105/genesys_agent --> CTI RP 299109/genesys CFA to Genesys Controlled CTI RP 299548/genesys --> 299109/genesys_agent
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.