Created by: Leya Thiam on 24-12-2010 09:12:58 AM Hi evrybody, we have a genesys call center architecture with: genesys tserver for CUCM 8.0 working with a CUCM 4.2. when the supervisor try to initiate a silent monitoring this error occured:"This version of JTAPI doesn't support monitoring".do someone known what seem to be the problem? what version of CUCM will propably be able to solve this error? thank you for your help.
Subject: RE: Genesys silent monitoring with CUCM Replied by: Mohan Potluri on 26-12-2010 06:32:24 AM CUCM and JTAPI support for Silent Monitoring starts from CUCM 6.0.1 version.
Subject: RE: Genesys silent monitoring with CUCM Replied by: Jacky Reinbold on 14-01-2011 11:05:12 AM Hi Leya, I did experience a similar error by tryin to make a JTAPI connection from a Genesys T-Server to CUCM 8.0.3. @15:12:28.2871 Link [1,s0] start (link_start) link [1] 'link-tcp' start (tcp_start) connecting to 10.0.160.1:2789... contacted on socket [11] @15:12:28.2879 Link [1,s0] Changing state to 1 @15:12:28.2920 TEventInterface started in socket mode. @15:12:28.2920 Ccm T-Server init completed OK. 2011-01-05T15:12:28.292 Standard bgv204 TSCCM GCTI-00-05061 Initialization completed ... @15:12:58.2878 Link [1,s1] link start timer expired. Closing link. @15:12:58.2879 Link [1,s1] stop @15:12:58.2879 LinkReg [1, act=0] clearAll @15:12:58.2880 Link [1,s1] Changing state to 0 @15:12:58.2880 Erasing all linkIDs for CallId->LinkId[1] map. 2011-01-05T15:12:58.288 Standard bgv204 TSCCM GCTI-01-51116 JTAPI link '1' failure. @01/05/11 15:12:58.2881 [51116] JTAPI link '1' failure.@15:12:58.2882 CcmDevice::sendAddrOOSforLink for link:1 Could you find out the origin of the JTAPI link '1' failure in your case ???
Regards,
Jacky
Subject: Genesys with CUCM 8.0.3 Integration - JTAPI link '1' failure Replied by: Jacky Reinbold on 14-01-2011 11:36:02 AM Hi Guys, have tryed a basic Genesys T-Server Integration with CUCM 8.0.3 over JTAPI and obtain a JTAPI link '1' failure.
TCP 2789 should be correct.
Any idea of what could be the origin ?
Here is a customer trace from the Genesys Server.
@15:12:28.2871 Link [1,s0] start (link_start) link [1] 'link-tcp' start (tcp_start) connecting to 10.0.160.1:2789... contacted on socket [11] @15:12:28.2879 Link [1,s0] Changing state to 1 @15:12:28.2920 TEventInterface started in socket mode. @15:12:28.2920 Ccm T-Server init completed OK. 2011-01-05T15:12:28.292 Standard bgv204 TSCCM GCTI-00-05061 Initialization completed ... @15:12:58.2878 Link [1,s1] link start timer expired. Closing link. @15:12:58.2879 Link [1,s1] stop @15:12:58.2879 LinkReg [1, act=0] clearAll @15:12:58.2880 Link [1,s1] Changing state to 0 @15:12:58.2880 Erasing all linkIDs for CallId->LinkId[1] map. 2011-01-05T15:12:58.288 Standard bgv204 TSCCM GCTI-01-51116 JTAPI link '1' failure. @01/05/11 15:12:58.2881 [51116] JTAPI link '1' failure.@15:12:58.2882 CcmDevice::sendAddrOOSforLink for link:1
Thanks a lot for any reply, Jacky
Subject: RE: Genesys with CUCM 8.0.3 Integration - JTAPI link '1' failure Replied by: David Staudt on 14-01-2011 05:04:26 PM Won't be able to help with the Genesys logs - will need to query them. You should be able to enable the JTAPI logs, and perhaps see a more detailed error message. Since you mention ports, it's important to note that standard vs. secure JTAPI connections use different on UCM ports: normally the UCM user associated with JTAPI should _not_ have 'Standard CTI Secure Connection' (unless you're sure all steps to enable secure CTI connection are in place) as this will force UCM to reject connections coming in on the standard JTAPI port.
Subject: RE: Genesys with CUCM 8.0.3 Integration - JTAPI link '1' failure Replied by: Jacky Reinbold on 14-01-2011 06:04:26 PM
Won't be able to help with the Genesys logs - will need to query them. You should be able to enable the JTAPI logs, and perhaps see a more detailed error message.
Since you mention ports, it's important to note that standard vs. secure JTAPI connections use different on UCM ports: normally the UCM user associated with JTAPI should _not_ have 'Standard CTI Secure Connection' (unless you're sure all steps to enable secure CTI connection are in place) as this will force UCM to reject connections coming in on the standard JTAPI port.
Hi David, Ok, it's interesting what you told me, I will verify the application user rights. The used connection should be a standard not secured CTI connection. In the developper documentation and in a networkers breakout session BRKUCC-2323 I've found out that the connection TCP Port for third party JTAPI connections should be 2748 or 2789 for classic unsecure connections for CTI/JTAPI and 2749 (CTI) for secure connections . This documentation does not specify what default port have to be used for an external application (third party callcenter for example) to connect through a legacy JTAPI integration to the CUCM/cti manager. I suppose it should be TCP 2789, as it is the only JTAPI port available. 2748 and 2749 are CTI Ports I deduce my following question: what is the right tcp port to connect a third party callcenter application through JTAPI to a CTI manager/CUCM in a classical not secure architecture? tcp 2748 ? tcp 2789 ? both ? others ? The cisco solution partner ANDTEK which is also a JTAPI application developping vendor told me That 2748 is the right port, but I'm not really agree as I see the usage of this port more in the CTI/TAPI corner and not in the JTAPI corner. Thanks alot, Jacky
Subject: RE: Genesys with CUCM 8.0.3 Integration - JTAPI link '1' failure Replied by: David Staudt on 14-01-2011 08:41:54 PM I always remembered it as #ABC (hex), i.e. 2748 decimal.
Subject: RE: Genesys silent monitoring with CUCM Replied by: Evandro Nunes on 31-03-2011 03:55:39 PM Hi Jacky,
I'll need do an integration between Genesys and CUCM 8.0. Do you have any documents about this integration ?
I've already done integration between CUCM and UCCX (Cisco). Is the idea the same when integrating with Genesys ?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
