SystemInfo API using different XMPP Domains

[eschippe]

The SystemInfo API provides different XMPP Domains when requesting the primary and the secondary node (but the primary and secondary are always in the same order).

Is it a problem in our configuration? Should the XMPP domains be the same or should I select my remote server based on the provided XMPP domain ?

[dekwan]

Hi,

The XMPP Domain will be different for the two nodes because it is typically the fqdn of the node. When you want to connect to the Finesse notification for node 1, you use that xmpp domain, if you want to use the Finesse notification for node 2, you use the xmpp domain of the secondary.

Thanx,

Denise

[eschippe]

Thanks for the update Denise.

Can I ask another question please?

Q: Is there a way to ‘unsubscribe’ the feeds after a Finesse API Client crash?

What about the XMPP subscriptions that were done manually?

I could not find the answer here: Subscription Management<https://developer.cisco.com/docs/finesse/#subscription-management>

Thanks in advance,

Ernst

[dekwan · Accepted solution]

Hi,

You only need to unsubscribe to subscriptions that were manual. You don't have to worry about the ones that were automatically done. You need to send the unsubscribe request for every manual subscription you made. Example:

<iq type='set'
   from='ChuckieNorrad@finesse-server.cisco.com'
   to='pubsub.finesse-server.cisco.com'
   id='unsub1'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub'>
  <unsubscribe
  node='/finesse/api/Team/TheA/Users'
  jid='userid@finesse-server.cisco.com'/>
  </pubsub>
</iq>

This was actually in the Subscription Management link you pasted, so I am not sure if I'm not answering your question correctly.

Thanx,

Denise

[eschippe]

Thanks for your response Denise. ☺