Reference applications

RE: Could Not connect error while testing basicChatDemo.html

2013-05-17T12:09:55Z

1. If I am going to run my sample on xampp server, that is localhost, then what should be the 'domain' ? 2. I am using a localhost:7070 as the BOSH server as i used openfire. please help

RE: Could Not connect error while testing basicChatDemo.html

2013-05-16T16:10:02Z

Saagar, Are you setting up your own CUPS server? What version of CUPS are you using? The key to connect to your CUPS is to 1. Setup a correct domain: the domain that your CUPS server is with in. Ex: cisco.com 2. BOSH server address: http://:7335/httpbinding 3. Mske sure the CORS is been in consideration. Meaning All BOSH request needs to have the same protocol with the page original. Ex: http -> http, https -> https Hope this help Howard

Could Not connect error while testing basicChatDemo.html

2013-05-16T11:53:04Z

Hello, I deployed the complete package of the SDK provided for IM on my local apache server, but I get a an error: Could not connect: stream:error xmlns:stream="http://etherx.jabber.org/streams" service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-streams"/ /stream:error I also tried with changing httpBindingUrl to '/httpbinding' from 'cup02:7335/httpbinding' and i also tried changing all of them, i.e, domain to 'hpcl.co.in' and httpbinding to '10.15.0.10.8443/httpbinding' as provided my local enterprise server.. But i am getting the same problem. I need it for a project. Please help me out.

RE: JabberSDK with salesforce webcommunicator error in softphone.log

2013-05-06T23:26:27Z

Joshua - "Not User Authorized" means the web page's domain has not been authorized to use the Cisco Web Communicator plug-in. This is a new security feature in the 3.0 release. It is described here [url=http://developer.cisco.com/web/jabber-developer/feature-note-access-control-dialog]http://developer.cisco.com/web/jabber-developer/feature-note-access-control-dialog[/url]. Be sure you are using the 3.0 version of cwic.js. That should cause the security pop-up dialog to appear so you can authorize the domain. - Jim

JabberSDK with salesforce webcommunicator error in softphone.log

2013-05-06T19:45:34Z

Trying to implement the SDK with salesforce.com as described on cisco.com. I'm getting the following errors in my softphone.log file on my machine. Any ideas? 2013-05-06 13:37:07,378 INFO [0x0000056c] [cdm\src\win32\devicemonitorimpl.cpp(698)] [csf.cdm] [DoRegisterDeviceInterfaceToHwnd] - DoRegisterDeviceInterfaceToHwnd() 2013-05-06 13:37:07,378 INFO [0x0000056c] [\cdm\src\win32\devicemonitorimpl.cpp(70)] [csf.cdm] [cdm::DeviceMonitorImpl::startMessagePump] - startMessagePump() 2013-05-06 13:37:07,644 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI get_version called 2013-05-06 13:37:07,644 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI get_version returning 2013-05-06 13:37:07,644 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI get_connectionStatus called 2013-05-06 13:37:07,644 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - Not User Authorized 2013-05-06 13:37:07,644 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI get_connectionStatus returning 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI encryptCucmPassword called 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - Not User Authorized 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI encryptCucmPassword returning 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI set_TftpAddressList called 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - Not User Authorized 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI set_TftpAddressList returning 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI set_CtiAddressList called 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - Not User Authorized 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI set_CtiAddressList returning 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI set_CcmcipAddressList called 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - Not User Authorized 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI set_CcmcipAddressList returning 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI get_connectionStatus called 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - Not User Authorized 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI get_connectionStatus returning 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI connect called 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - Not User Authorized 2013-05-06 13:37:07,659 INFO [0x00001368] [callcontrol\CallControlWrapper.cpp(2386)] [webuc] [CallControlWrapper::logInfo] - CiscoWebCommunicatorAPI connect returning

RE: Basic Chat-demo sample is not working in firefox and IE.

2013-04-01T04:33:46Z

Howard, I am using Mozilla firefox 19.0.2. Regards, Karthik

RE: Basic Chat-demo sample is not working in firefox and IE.

2013-03-21T21:35:16Z

Hi Karthik, What version of Mozilla are you using? I didn't see the problem from my end. Howard

RE: Basic Chat-demo sample is not working in firefox and IE.

2013-03-21T06:28:23Z

Howard, After deploy the sample application into my webserver, it is working in IE. But In firefox, I am not to connect(login). Please help on this. Karthik

RE: Basic Chat-demo sample is not working in firefox and IE.

2013-03-20T14:23:28Z

That's correct... Howard

RE: Basic Chat-demo sample is not working in firefox and IE.

2013-03-20T13:18:31Z

Hi Howard, Previously I tried to run the url([b]C:\Users\xxx\Desktop\JabberChat\basic-chat-demo\basicChatDemo.html[/b]) in the IE browser [b].[/b] From my observations, I think that I have to deploy this sample in Local Server (IIS or apache server) and after that I have to run the url(http://localhost/basicChatDemo.html) in IE browser. Please correct us if I misunderstood. Karthik

RE: I am not able to log in with Sample in Firefox and IE. Chrome is workin

2013-03-19T20:09:11Z

Hi[b] [/b][color=#525252]Praveen,[/color][color=#525252] [/color] [color=#525252]For IE, you have to run the sample from web server to make sure [/color][color=#525252]all BOSH requests (original or "see-other-uri")[/color] [color=#525252]have the same protocol as the page origin.[/color] [color=#525252]In this case, the web server needs to be in "http". You should be able to get the page to work from the web server.[/color] [color=#525252]Hope this help[/color] [color=#525252]Howard[/color]

RE: Basic Chat-demo sample is not working in firefox and IE.

2013-03-19T20:06:15Z

Hi[b] [/b][color=#525252]karthik,[/color][color=#525252] [/color] [color=#525252]For IE, you have to run the sample from web server to make sure [/color][color=#525252]all BOSH requests (original or "see-other-uri")[/color] [color=#525252]have the same protocol as the page origin.[/color] [color=#525252]In this case, the web server needs to be in "http". You should be able to get the page to work once you run the sample from that web server.[/color] [color=#525252]Hope this help.[/color] [color=#525252]Howard[/color]

RE: Basic Chat-demo sample is not working in firefox and IE.

2013-03-19T16:51:30Z

Hi karthik, I think you are facing the same issue than Praveen mentioned on [url=http://developer.cisco.com/web/jabber-developer/jabber-voice-forum/-/message_boards/message/12864907]this post[/url]. I do not have access to the sandbox unfortunately, can you continue working with the SDK in Chrome while we are investigating the problem ? Thanks, Thomas

Basic Chat-demo sample is not working in firefox and IE.

2013-03-19T10:16:28Z

When I try to download and run the basic-chat-demo sample from the link [url=http://developer.cisco.com/web/jabber-developer/im-core-api-sample]http://developer.cisco.com/web/jabber-developer/im-core-api-sample[/url]. The provided sample is working in google chrome. But if the same sample tried in firefox then I got the following error "Could not connect:

". If the same sample tried in IE then I got the following error "[b]Access is denied.[/b]" Please help me on this.

RE: I am not able to log in with Sample in Firefox and IE. Chrome is workin

2013-03-11T13:29:24Z

Hi Thomas, I am trying to connect to sand box CUP and test(REf:http://developer.cisco.com/web/jabber-developer/testing/shared-sandbox). I get the following error when i use the sample "Cisco AJAX XMPP Library 8.6.1 Debug/doc/examples/sampleclient.html" in Firefox(v 20.0) Log 18:51:36:541 Note: Service discovery is disabled on the client. Log 18:51:36:545 Cross site is true. Log 18:51:36:548 Update _connectToNode = cup02 Log 18:51:36:555 Bosh URL is: http://cup02:7335/httpbinding Log 18:51:36:598 network timeout retry 1 Log 18:51:37:143 network timeout retry 2 Log 18:51:37:656 network timeout retry 3 Log 18:51:38:184 [Console] Stream closedwith error:Operation failed (

) Log 18:51:38:187 closed:

I get the following in IE 9. Log 18:54:15:790 Note: Service discovery is disabled on the client. Log 18:54:15:795 Cross site is true. Log 18:54:15:797 Update _connectToNode = cup02 Log 18:54:15:800 Bosh URL is: http://cup02:7335/httpbinding Works perfect in Chrome. Thanks, Praveen

RE: using csf node.js to make outbound call

2013-03-11T12:16:08Z

Hi Frank, Unfortunately the current Jabber SDK does not include any helper for click-to-call, I am not familiar with the TAPI/TSAPI details, is it complicated to use ? A node module for click-to-call would be very interesting I think. Thomas

RE: I am not able to log in with Sample in Firefox and IE. Chrome is workin

2013-03-11T11:56:22Z

Hi Praveen, Do you have more details about the actual error in Firefox and IE ? Does the browser console show anything wrong ? Is it a connection error ? What type of server (WebEx Connect or CUPS) are you using for testing ? Thanks, Thomas

I am not able to log in with Sample in Firefox and IE. Chrome is working.

2013-03-11T10:31:52Z

i followed the link http://developer.cisco.com/web/jabber-developer/im-core-api-sample Its working fine in Chrome(v25.0) alone, but not working in firefox(v 20.0) or ie(v 9.0). Could any one help me run my sample in firefox and IE?

RE: using csf node.js to make outbound call

2013-03-08T12:14:19Z

Hi Thomas, Thanks for the reponse. The requirement is to be able to establish a call between 2 endpoints based on different events, so I would incline to agree that it is like a 'click-to-call' type scenario. What I am trying to avoid is to write extensive code like TSAPI to make the call. Any help would be appreciated. Jabber has a lot of potential in code simplication and I was really hoping we can go that route. Frank

RE: using csf node.js to make outbound call

2013-03-08T11:13:06Z

Hi Frank, Do you want a "click-to-call"-like solution, where node.csf would send a request to CUCM to establish a call between 2 endpoints, or would you like the call to be controlled directly from the application which received the SMTP event ? As you said the cwic API is supported in browsers only, the current Jabber SDK does not provide any server-side call control API. Thomas