Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 01:55 AM
Subject: RE: Ad hoc conference
Replied by: Mohan Potluri on 15-07-2010 05:44:36 PM
Redirect from a RP should work. Are you seeing any exceptions?
I don't see any issues with the solution.
This document was generated from CDN thread
Created by: Gionata Navarra on 15-07-2010 03:20:49 PM
Hi all, new question.
I'm implementing an "ad hoc" conference using JTapi and CUCM 7.0, but I've found some problems trying to realize concept of room.
To follow parlayx standard I can register a CTI RP (the requested room), invite each participant making a call one by one from RP, when answered redirect them to a CTI Port and at the end join every call with conference method.
Are there any other solutions less complex?
Anyway with this kind of solution still remains the problem of redirect method on CTI RP. It seems not working.
Thank you all.
Subject: RE: Ad hoc conference
Replied by: Gionata Navarra on 16-07-2010 10:25:58 AM
Redirect from a RP should work. Are you seeing any exceptions?
I don't see any issues with the solution.
Yes, I receive this exception:
"com.cisco.jtapi.PlatformExceptionImpl: CCNException not handled: com.cisco.cti.client.CCNException: redirect failure"
when I redirect from Route Point to Cti port.
I'm not able to attach jtapi.log file because even after call it's empty.
This is my jtapi.ini file, I don't know what's wrong to obtain log.
#Cisco Jtapi version 7.0(2.1000)-4 Release ini parameters
#Fri Jul 16 11:16:07 CEST 2010
INFORMATIONAL=0
DesiredServerHeartbeatInterval=30
TracePath=D:\Mylog
FileNameExtension=log
SyslogCollector=
TraceFileSize=1048576
AVVERTIMENTO=1
UseAlarmService=0
ProviderOpenRequestTimeout=200
JavaSocketConnectTimeout=15
JtapiPostConditionTimeout=15
ApplicationIgnoresFwdDestination=0
ApplicationPriority=2
SecurityTraceEnabled=1
AlarmServicePort=1444
RouteSelectTimeout=5000
ProviderRetryInterval=30
QueueStatsEnabled=0
FileNameBase=CiscoJtapi
JTAPI_DEBUGGING=0
PeriodicWakeupEnabled=0
CTI_DEBUGGING=0
JTAPINotificationPort=2789
Traces=WARNING;INFORMATIONAL;DEBUG
PeriodicWakeupInterval=50
AlarmServiceHostname=
QueueSizeThreshold=25
Debugging=JTAPI_DEBUGGING;JTAPIIMPL_DEBUGGING;CTI_DEBUGGING;CTIIMPL_DEBUGGING;PROTOCOL_DEBUGGING;MISC_DEBUGGING
PROTOCOL_DEBUGGING=0
UseSystemDotOut=0
MISC_DEBUGGING=0
UseSameDirectory=1
NumTraceFiles=10
UseSyslog=0
DEBUG=1
SecurityTraceLevel=2
UseTraceFile=1
WARNING=0
CMAssignedAppID=0
INFORMAZIONE=1
UseProgressAsDisconnectedDuringErrorEnabled=0
CtiManagers=xxx.xxx.xxx.xxx;;;;;;;;;
Directory=
LanguageTFTPServerIP=xxx.xxx.xxx.xxx
CTIIMPL_DEBUGGING=0
CtiRequestTimeout=30
SecurityProperty=jtapiUser,,jtapiUser,,3804,xxx.xxx.xxx.xxx,69,/C\:/java/lib/,false,false;
JTAPIIMPL_DEBUGGING=0
SyslogCollectorUDPPort=514
Any idea?
Subject: RE: Ad hoc conference
Replied by: Mohan Potluri on 19-07-2010 05:09:21 PM
Try this in jtapi.ini file and see if you can generate trace files:
INFORMATIONAL=1
DesiredServerHeartbeatInterval=30
TracePath=JTAPILOG
FileNameExtension=log
SyslogCollector=
TraceFileSize=1048576
UseAlarmService=0
ProviderOpenRequestTimeout=200
JavaSocketConnectTimeout=15
HuntListEnabled=1
JtapiPostConditionTimeout=15
ApplicationIgnoresFwdDestination=0
ApplicationPriority=2
SecurityTraceEnabled=1
AlarmServicePort=1444
RouteSelectTimeout=5000
ProviderRetryInterval=30
DropAnyPartyEnabled=1
QueueStatsEnabled=0
FileNameBase=CiscoJtapi
JTAPI_DEBUGGING=1
PeriodicWakeupEnabled=0
CTI_DEBUGGING=1
JTAPINotificationPort=2789
Traces=WARNING;INFORMATIONAL;DEBUG
PeriodicWakeupInterval=50
AlarmServiceHostname=
QueueSizeThreshold=25
Debugging=JTAPI_DEBUGGING;JTAPIIMPL_DEBUGGING;CTI_DEBUGGING;CTIIMPL_DEBUGGING;PROTOCOL_DEBUGGING;MISC_DEBUGGING
PROTOCOL_DEBUGGING=1
UseSystemDotOut=0
MISC_DEBUGGING=1
UseSameDirectory=1
NumTraceFiles=10
UseSyslog=0
DEBUG=1
SecurityTraceLevel=2
UseTraceFile=1
WARNING=1
CMAssignedAppID=0
UseProgressAsDisconnectedDuringErrorEnabled=0
CtiManagers=;;;;;;;;;
Directory=
LanguageTFTPServerIP=
ProviderOpenRetryAttempts=5
CTIIMPL_DEBUGGING=1
CtiRequestTimeout=30
JTAPIIMPL_DEBUGGING=1
SecurityProperty=jtapiUser,,jtapiUser,,3804,xxx.xxx.xxx.xxx,69,/C\:/java/lib/,false,false;
CtiRedirectRequestTimeout=120
SyslogCollectorUDPPort=514
Subject: RE: Ad hoc conference
Replied by: Gionata Navarra on 20-07-2010 02:43:05 PM
Try this in jtapi.ini file and see if you can generate trace files:
INFORMATIONAL=1
DesiredServerHeartbeatInterval=30
TracePath=JTAPILOG
FileNameExtension=log
SyslogCollector=
TraceFileSize=1048576
UseAlarmService=0
ProviderOpenRequestTimeout=200
JavaSocketConnectTimeout=15
HuntListEnabled=1
JtapiPostConditionTimeout=15
ApplicationIgnoresFwdDestination=0
ApplicationPriority=2
SecurityTraceEnabled=1
AlarmServicePort=1444
RouteSelectTimeout=5000
ProviderRetryInterval=30
DropAnyPartyEnabled=1
QueueStatsEnabled=0
FileNameBase=CiscoJtapi
JTAPI_DEBUGGING=1
PeriodicWakeupEnabled=0
CTI_DEBUGGING=1
JTAPINotificationPort=2789
Traces=WARNING;INFORMATIONAL;DEBUG
PeriodicWakeupInterval=50
AlarmServiceHostname=
QueueSizeThreshold=25
Debugging=JTAPI_DEBUGGING;JTAPIIMPL_DEBUGGING;CTI_DEBUGGING;CTIIMPL_DEBUGGING;PROTOCOL_DEBUGGING;MISC_DEBUGGING
PROTOCOL_DEBUGGING=1
UseSystemDotOut=0
MISC_DEBUGGING=1
UseSameDirectory=1
NumTraceFiles=10
UseSyslog=0
DEBUG=1
SecurityTraceLevel=2
UseTraceFile=1
WARNING=1
CMAssignedAppID=0
UseProgressAsDisconnectedDuringErrorEnabled=0
CtiManagers=;;;;;;;;;
Directory=
LanguageTFTPServerIP=
ProviderOpenRetryAttempts=5
CTIIMPL_DEBUGGING=1
CtiRequestTimeout=30
JTAPIIMPL_DEBUGGING=1
SecurityProperty=jtapiUser,,jtapiUser,,3804,xxx.xxx.xxx.xxx,69,/C\:/java/lib/,false,false;
CtiRedirectRequestTimeout=120
SyslogCollectorUDPPort=514
Ok now I'm able to attach jtapiLog.
In my scenario I've a Cti Route Point 5000, a registered number 401, and a CTI Port 3001.
5000 calls 401,
401 answers the call,
then I redirect connection [5000] and I obtain the exception:
"com.cisco.jtapi.PlatformExceptionImpl: CCNException not handled: com.cisco.cti.client.CCNException: redirect failure"
this is the code:
call.connect(provider.getAddress("5000").getTerminals()[0], provider.getAddress("5000"), "401");
Connection[] conns = call.getConnections();
CiscoConnection conn = (CiscoConnection) conns[0];
conn.redirect("3001");
Thanks
Subject: RE: Ad hoc conference
Replied by: Mohan Potluri on 20-07-2010 07:27:24 PM
My suspesion is that call search space (css) of RP doesn't have the partition of ctiports.
3001 is in All-Ip-Phone-PT
5000 is in International-PT.
There are in different partitions and 5000 can "reach" 3001 only if css of 5000 contains the paritions of ctiports. Can you check if css of RP has all the paritions of ctiports?
You may want to try out with default partitions to see if you run into this exception.
Subject: RE: Ad hoc conference
Replied by: Gionata Navarra on 21-07-2010 03:54:54 PM
My suspesion is that call search space (css) of RP doesn't have the partition of ctiports.
3001 is in All-Ip-Phone-PT
5000 is in International-PT.
There are in different partitions and 5000 can "reach" 3001 only if css of 5000 contains the paritions of ctiports. Can you check if css of RP has all the paritions of ctiports?
You may want to try out with default partitions to see if you run into this exception.
I've changed configuration following your suggestion but I catch the same exception.
Actual configuration:
RP 5000:
Incoming-CSS and Incoming-PT
Cti port 3000:
Incoming-CSS and Incoming-PT
In particular Incoming-CSS has Three partitions:
https://138.132.115.138:8443/ccmadmin/cssEdit.do?key=c6e3fdc8-13df-7f93-e237-46f13bfa076c
Incoming-PT, All-Ip-Phone-PT and Internationl-PT.
I attach jtapiLog file.
Thank you
Subject: RE: Ad hoc conference
Replied by: Mohan Potluri on 21-07-2010 05:41:48 PM
I am seeing the same "Timeout" error response from CUCM for redirect request. I need CUCM SDL and SDI logs to find out the root cause. You may want to enter a case with Cisco Developer Support team to get this escalated.
Subject: RE: Ad hoc conference
Replied by: Mohan Potluri on 22-07-2010 07:28:25 PM
SDL and SDI logs are created by default. These logs can be downloaded using RTMT (Real time monitoring tool). RTMT can be downloaded from plugins page of CUCM admin.
After installing RTMT, you can click on 'Trace centra'l and download the logs for CTIManager service and CallManager service from all nodes.
Subject: RE: Ad hoc conference
Replied by: Gionata Navarra on 22-07-2010 03:05:11 PM
I am seeing the same "Timeout" error response from CUCM for redirect request. I need CUCM SDL and SDI logs to find out the root cause. You may want to enter a case with Cisco Developer Support team to get this escalated.
where can I retrieve those logs?
They are enabled by default on cucm or must be configured?
Subject: RE: Ad hoc conference
Replied by: Gionata Navarra on 23-07-2010 01:10:51 PM
SDL and SDI logs are created by default. These logs can be downloaded using RTMT (Real time monitoring tool). RTMT can be downloaded from plugins page of CUCM admin.
After installing RTMT, you can click on 'Trace centra'l and download the logs for CTIManager service and CallManager service from all nodes.
I've been able to download only SDL log files, no traces of SDI log files.
I attach them and also JtapiLog file.
thank you
Subject: RE: Ad hoc conference
Replied by: Chikeobi Njaka on 10-08-2011 03:41:18 PM
SDL and SDI logs are created by default. These logs can be downloaded using RTMT (Real time monitoring tool). RTMT can be downloaded from plugins page of CUCM admin.
After installing RTMT, you can click on 'Trace centra'l and download the logs for CTIManager service and CallManager service from all nodes.
I've been able to download only SDL log files, no traces of SDI log files.
I attach them and also JtapiLog file.
thank you
Mohan,
Was there ever a response to this case? It is the exact same thing I am getting. I thought it might have been due to the fact that I did not have an observer on the address to which I was redirecting, but no. I put an observer and still there is a pause of about 5 seconds before the redirect errors out. I also tried to redirect to a hard phone (this time without an observer- Call and Address), think that the phone should ring. It also errored out.
Any help will be appreciated. My log (using the jtapi.ini about) is attached.
Subject: RE: Ad hoc conference
Replied by: Mohan Potluri on 10-08-2011 04:06:15 PM
When the call from Route Point CUCS_RP_02 is answered. CiscoMediaOpenLogicalChannelEv will be delivered to terminal observer. Application need to set the IP address, port number for this call using [url=../../../../com/cisco/jtapi/extensions/CiscoMediaTerminal.html#setRTPParams(com.cisco.jtapi.extensions.CiscoRTPHandle, com.cisco.jtapi.extensions.CiscoRTPParams)]setRTPParams method (in CiscoMediaTerminal interface) whenever this event is seen. If media is not setup call will be disconnected by CUCM. Feature requests (redirect, transfer) on this call will fail. IP address and port number needs to be set (using setRTPParams method) even when there is no real person to transmit the media.
Labels:
Getting Started
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:
Customers Also Viewed These Support Documents