Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Created by: Arvind Sharma on 11-01-2011 07:20:35 PM I have an application in which Phone A (7970) starts a "New Call" - Using JTAPI sendData - Dials the DN for Phone B. Phone B shows incoming call and SoftKey1 shows "Answer" Using the JTAPI sendData again, the Application sends "Key:Soft1" to Phone B. But the Phone B doesn't seems to be honoring that Key press. It doesn't Answer the incoming call. Env. Details: Provider Version: [8.0.2.40000-1] JTAPI Client Ver: Cisco Jtapi version 8.0(0.98000)-13 Release XML Data: <CiscoIPPhoneExecute><ExecuteItem Priority="0" URL="Key:Soft1"/></CiscoIPPhoneExecute> XML Response: <?xml version="1.0" encoding="utf-8"?> <CiscoIPPhoneResponse> <ResponseItem URL="Key:Soft1" Data="Success" Status="0" /> </CiscoIPPhoneResponse> The Application controls both Phone A/B with CallOBserver and TerminalObserver on both the Phones. BTW, if the Application sends *any* other SoftKey - that works. I even tried sending a incorrect SoftKey9 - that gave expected error. Any suggestions ? Thanks! Arvind
Subject: RE: Softkey - sendData issue Replied by: David Staudt on 11-01-2011 09:55:48 PM It's possible that the soft key set is not yet ready (transitioning) after the incoming call hits the phone, and your request is discarded. Can you try adding a short delay? It's also possible that answering a call via XSI key press is disabled for security reasons, since XSI is not a secure API. Think of 'silently' turning on a phone's speaker in a person's office without them knowing. I'm researching this - if so it needs to be documented. Certainly the most sure way of answering the call will be via JTAPI commands, i.e. call.answer().
Subject: RE: Softkey - sendData issue Replied by: Arvind Sharma on 11-01-2011 10:12:16 PM Tried with some delay - didn't help (the app was waiting for the Phone B to be in ALERTING state as well)... I can buy the reasoning behind it to be disabled via XSI interface. The reason for using the Softkey via XSI is to mimic the end-user actions of answering a call (by pressing the "Answer" Softkey) for one of the product I am working on. But what is interesting I found that the same key works if I send the XSI via HTTP - as against JTAPI in my current App. So when I have the same setup as I mentioned earlier - only this time using HTTP instead of JTAPI to send Data - then I can send Key:Soft1 - and that does work. Only thing is I don't want to mix and match JTAPI Application with one call using HTTP interface (not sure how well that will scale in future)..... I will wait for your research feedback. Thanks! Arvind
It's possible that the soft key set is not yet ready (transitioning) after the incoming call hits the phone, and your request is discarded. Can you try adding a short delay?
It's also possible that answering a call via XSI key press is disabled for security reasons, since XSI is not a secure API. Think of 'silently' turning on a phone's speaker in a person's office without them knowing. I'm researching this - if so it needs to be documented.
Certainly the most sure way of answering the call will be via JTAPI commands, i.e. call.answer().
Subject: RE: Softkey - sendData issue Replied by: Arvind Sharma on 11-01-2011 10:37:45 PM okay - I have to take the blame for this one 🙂 Turned out that there was some hidden control character/spaces in the XML string which I was sending to the phone. The one in the HTML cases was clean. After spending some more time on debugging the JTAPI version saw that error. What threw me off was the "sucess" response I kept getting even with the embedded invalid character. My apologies for taking any of your time on this issue ! Case clsosed 🙂 Thanks for your help. Arvind
Tried with some delay - didn't help (the app was waiting for the Phone B to be in ALERTING state as well)...
I can buy the reasoning behind it to be disabled via XSI interface.
The reason for using the Softkey via XSI is to mimic the end-user actions of answering a call (by pressing the "Answer" Softkey) for one of the product I am working on.
But what is interesting I found that the same key works if I send the XSI via HTTP - as against JTAPI in my current App.
So when I have the same setup as I mentioned earlier - only this time using HTTP instead of JTAPI to send Data - then I can send Key:Soft1 - and that does work.
Only thing is I don't want to mix and match JTAPI Application with one call using HTTP interface (not sure how well that will scale in future).....
I will wait for your research feedback.
Thanks!
Arvind
It's possible that the soft key set is not yet ready (transitioning) after the incoming call hits the phone, and your request is discarded. Can you try adding a short delay?
It's also possible that answering a call via XSI key press is disabled for security reasons, since XSI is not a secure API. Think of 'silently' turning on a phone's speaker in a person's office without them knowing. I'm researching this - if so it needs to be documented.
Certainly the most sure way of answering the call will be via JTAPI commands, i.e. call.answer().
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: