05-05-2021 02:35 AM
Hello,
We develop a Chrome extension to add Cisco Telephony features to a web-based application.
For that we use the Cisco Jabber SDK Web (with the installation of the Cisco web communicator Chrome extensions and the SDK Browser Add-on)
We are many users using it in different companies and organizations, but we are actually facing a problem with one of our customers.
We use the MRA feature to connect the softphone to our UCM infrastructure through Expressway infrastructure.
The user can't connect to the UCM with our extension.
When we see on the Jabber Add-on logs, we can see this error code: "Get ServiceEvent Code. ServiceId: 1000 Code: 1002 Code Str: ServiceDiscoveryAuthenticationFailure"
And if we look deeper on this logs or on network traces, we see that the during the ServiceDiscovery authentication process, the workstation is trying to connect to a wrong domain (in our case we need to connect to "mycompany.com", it's the domain we indicate in our extension, and the Jabber sdk is tryning to connect to "wrongcompany.com")
It seems that this "wrongcompany.com" is an old domain that was using before on this workstation to connect to another UCM domain. And there was Jabber for windows installed on this workstation before too.
How can we solve that ? We try to uninstall everything, delete all the logs and cache linked to Jabber (\AppData\Roaming\Cisco\Unified Communications\ , \AppData\Local\Cisco\Unified Communications\ , C:\ProgramData\Cisco Systems\Cisco Jabber )
Is it a way on the Jabber SDK to force to connect ta a specific domain (put a parameter on the Service Discovery process) ?
Thanks in advance for your help
Regards,
Baptiste
05-11-2021 12:45 PM
Hello @baptiste.croizer,
I'm not an expert with Jabber, but I'd like to offer three resources which may be of help to you:
Hope this helps!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide