02-21-2022 02:12 AM
Hi,
I am facing an issue in XMPP library jabberwerx/CAXL. The issue is that sometimes (randomly, no particular scenario) my connection of XMPP is lost with cisco finesse. I observed the behavior of the finesse desktop client at the same time and it works fine without any issue.
The error I received from CAXL is:
<error><internal-server-error xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error>
This is not a one-time issue, I have encountered this multiple times. Generally, it happens at the time of login (where we first establish an XMPP connection).
Can you please guide me on this?
Thanks.
02-22-2022 12:00 PM
Hi,
Looking at the spec, it says that an internal-server-error is:
The server has experienced a misconfiguration or other internal error that prevents it from servicing the stream.
What version of Finesse are you using? Is this CCX or CCE? Also, are you using websocket or BOSH?
Just FYI, Strophe.js is the recommended JS XMPP library. You can find a Strophe with websocket example here: https://github.com/CiscoDevNet/finesse-sample-code/tree/master/NonGadgetSampleWithStropheAndWebsocket
Thanx,
Denise
02-22-2022 11:13 PM - edited 02-22-2022 11:33 PM
Hi Denise,
Thanks for taking the time out.
We are facing this issue for CCE 12.6 and CCX 12.5 at the moment and we are using bosh for XMPP connection with finesse.
I was just thinking that if the issue is somehow related to the server then shouldn't we face the same problem on the Cisco Finesse Desktop client as well?
02-23-2022 09:04 AM
Hi,
I was just thinking that if the issue is somehow related to the server then shouldn't we face the same problem on the Cisco Finesse Desktop client as well?
I agree. I was just trying to point out what the spec says, but I was also thinking maybe it is the way you are connecting. Is it possible for you to switch to Strophe.js? The Finesse team has always suggested using that library instead of CAXL which is no longer being updated.
If not, I would suggest turning on the OpenFire logs, trying to reproduce it (I know you said it is random), and looking at the logs. Remember turning on the OpenFire logs is a performance hit, so you probably don't want to do it for a long time if it is a production system.
Thanx,
Denise
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