Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About mpotluri
08-18-2017
Stats
Member since
08-08-2008
248
Posts
91
Helpful
36
Solutions
07-23-2017
10:07 PM
(P1-rmcm66) 1001217/1 ConnDisconnectedEv 2030::5 [#55] Cause:100 CallCtlCause:0 CiscoCause:0 FeatReason:31 This event indicates that the connection is created to address 2030 of type 5 (MONITORING_TARGET). We should not be seeing this call physical phone. The same snippet of the log you at attached only shows the call at faisalqa1:2091 going to IDLE state. It doesn't cover the events when or the call to startMonitor API. If you are seeing the call which is used to issue startMonitor request on agents physical phone, this needs to be investigated further and you may need to raise a case with developer support team.
... View more
07-23-2017
08:51 PM
Richard, If you just want to know about the calls coming in or originated from this device, you can create a Cisco phone thats shares a line with Polycom phone, include the Cisco Phone in your TAPI application control list and collect the call data. You will not be able to do any features on the call answered at Polycom device.
... View more
07-20-2017
11:23 AM
Code looks ok. Can you attach or copy JTAPI logs from the time agent answered the call to the time after startMonitor API call?
... View more
07-20-2017
08:59 AM
You may want to look at Feature Configuration Guide for Cisco Unified Communications Manager, Release 10.5(2) - Silent Monitoring [Cisco Unifi… for details of Silent Monitoring feature. Monitor call should not be visible on agent phone. Is customer to agent call in connected state? How are you creating this call? As mentioned in my previous update, you should see 2 calls: call1 between agent and customer and call2 on supervisor.
... View more
07-19-2017
01:54 PM
In typical call center scenario the call is routed to an agent where it is answered. Now customer and agent are talking on say Call1. Supervisor now wants to monitor the call. She can listen to the conversation between customer and agent by initiating silentMonitor request on behalf of her phone. This is a separate call from supervisor phone - say call2. If you specify CiscoCall.PLAYTONE_BOTHLOCALANDREMOTE in call2.startMonitor request, agent will hear a monitor tone periodically till supervisor hangs up. You need to use PLAYTONE_NOLOCAL_OR_REMOTE if you don't want agent to know about it. The third parameter in call2.startMonitor should be terminal connection of agent from Call1. HTH
... View more
07-19-2017
11:54 AM
You will mostly likely see an exception if you do connect and startMonitor API calls back to back. After you call connect API, it takes a few seconds for the call to ring the destination, get answered and for media to setup. startMonitor will succeed only if call is answered and media is setup. You need to wait a second or 2 after you answer the aCall before calling startMonitor.
... View more
07-19-2017
10:54 AM
aCall is a call object created by provider.createCall() and it will not have any connections till you call connect() API on it. To get to the call on agent you need to use srcAdd.getConnections()[0].getTerminal Connections()[0] //if there is only one call on agent address Try this: aCall.startMonitor(provider.getTerminal("faisalqa1"), provider.getAddress("2091"), s rcAdd.getConnections()[0].getTerminal Connections()[0] , CiscoCall.SILENT_MONITOR,CiscoCall.PLAYTONE_BOTHLOCALANDREMOTE); Let us know the result.
... View more
07-19-2017
10:06 AM
Silent monitor is done for a call on agent phone from a supervisor phone. The third parameter in startMonitor is the terminal connection of the call on agent phone. You can monitor a call only if it is connected and media is setup. You need to find the call on the agent, make sure that the terminal connection of the agent is in TALKING state and then call startMonitor API. If you want to monitor an incoming call to agent, add code in your call observer to create a new thread when it receives TALKING state for the terminal connection of agent Terminal and call startMonitor in the new thread. HTH
... View more
07-05-2017
08:50 AM
Cisco JTAPI supports Cisco phones only. http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/10_5_2/CUCM_BK_J6E0E2F6_00_jtapi-developers-guide-1052… has a list of supported devices.
... View more
06-13-2017
03:05 PM
Each phone is represented by a Cisco Terminal object. You can enumerate all the terminals from Provider and use the API on all terminals. You need to go through the JTAPI 1.2 spec and Cisco JTAPI developer guide to get an understanding on JTAPI call model and its API.
... View more
06-13-2017
02:29 PM
byte[] sendData(byte[] terminalData) is the API to send XML message to the phone. This API is available on CiscoTerminal. You can put the following as a byte[] and use the above API. <CiscoIPPhoneText><Title></Title><Prompt></Prompt><Text>This is a test message through sendData</Text></CiscoIPPhoneText> JTAPI test tool available at Cisco JTAPI show cases this functionality as well. You can use this test app to get familiar with Cisco JTAPI API.
... View more
06-08-2017
09:50 AM
If you want to route the call to more than 1 party, you will probably need a Hunt Pilot configured with simultaneous ringing (broadcast) hunt list. In selectRoute() API you can use the hunt pilot DN. This can be easily done if the list of destinations is static. Conference will not ring the destinations at the same time. If the destination list is dynamic, you could use AXL interface to change the hunt list before routing the call to hunt pilot. This could be a little messy. If you want to ring all destinations without the Hunt List, you need a CTIPort for each destination. First route the call to to a CTIPort (port1) , answer the call there and make calls from each CTIPort to the destination list. After the call is answered by the destination you can a decide to redirect the call to port1 and do a direct transfer at port1. HTH
... View more
06-08-2017
09:34 AM
You may need to raise a case with Cisco Dev Support with relevant JTAPI logs to resolve this.
... View more
06-05-2017
10:16 AM
When applications give the userid/password in getProvider() API, Cisco JTAPI uses the userid/password to authenticate with CTIManager. There a couple of ways to get authenticated one of the which is giving the userid/password. Another method would be to provide token. You still need to find a way to get the SSO token, so that application can successfully authenticate. You can't avoid authentication.
... View more
06-05-2017
10:10 AM
There are 2 sample apps ( JTrace and makecall) that comes with Cisco JTAPI installation. After you install Cisco JTAPI you should see these 2 in apps in your installation folder. There is another Cisco JTAPI test tool which show cases the capability of Cisco JTAPI API and can be found at Cisco JTAPI.
... View more
07-23-2017
(P1-rmcm66) 1001217/1 ConnDisconnectedEv 2030::5 [#55] Cause:100
CallCtlCause:0 CiscoCause:0 FeatRea...
Created by
mpotluri
in Call Control
07-23-2017
07-23-2017
Richard, If you just want to know about the calls coming in or
originated from this device, you can ...
07-20-2017
Code looks ok. Can you attach or copy JTAPI logs from the time agent
answered the call to the time a...
07-20-2017
You may want to look at Feature Configuration Guide for Cisco Unified
Communications Manager, Releas...
07-19-2017
In typical call center scenario the call is routed to an agent where it
is answered. Now customer an...
07-19-2017
You will mostly likely see an exception if you do connect and
startMonitor API calls back to back.Af...
07-19-2017
aCall is a call object created by provider.createCall() and it will not
have any connections till yo...
07-19-2017
Silent monitor is done for a call on agent phone from a supervisor
phone. The third parameter in sta...
07-05-2017
Cisco JTAPI supports Cisco phones only.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtap...
06-13-2017
Each phone is represented by a Cisco Terminal object. You can enumerate
all the terminals from Provi...
06-13-2017
byte[] sendData(byte[] terminalData) is the API to send XML message to
the phone. This API is availa...
Created by
mpotluri
in Call Control
06-08-2017
06-08-2017
If you want to route the call to more than 1 party, you will probably
need a Hunt Pilot configured w...
06-08-2017
You may need to raise a case with Cisco Dev Support with relevant JTAPI
logs to resolve this.
Created by
mpotluri
in Call Control
06-05-2017
06-05-2017
When applications give the userid/password in getProvider() API, Cisco
JTAPI uses the userid/passwor...
Public Statistics
| Date Registered | 08-08-2008 09:33 AM |
| Date Last Visited | 08-18-2017 03:51 AM |
| Total Messages Posted | 248 |
| Total Helpful Votes Received | 91 |
Helpful Votes From
