cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
312
Views
0
Helpful
1
Replies
Enthusiast

presence state "unkown" for all users using CUP SOAP webservice after update CUP from version 9 to 10.5.2

After updating to version 10.5.2.20000-1 a 3rd party application can't get the presence state of the users using SOAP Presence Web Service.

I tested with SoapUI: Login as application user, login as presence enabled enduser, "getPolledPresence" request (BASIC_PRESENCE and RICH_PRESENCE), response with "unkown" presence state:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cup="urn:cisco:cup:presence:soap">

   <SOAP-ENV:Header/>

   <SOAP-ENV:Body>

      <cup:getPolledPresenceResponse>

         <cup:presenceResponse>

            <cup:presenceType>BASIC_PRESENCE</cup:presenceType>

            <cup:basicPresenceList>

               <cup:contact presenceStatus="UNKNOWN" contactURI="user1@sie.at"/>

               <cup:contact presenceStatus="UNKNOWN" contactURI="user2@sie.at"/>

               <cup:contact presenceStatus="UNKNOWN" contactURI="user3@sie.at"/>

            </cup:basicPresenceList>

            <richPresenceList xmlns="urn:cisco:cup:presence:soap"/>

         </cup:presenceResponse>

      </cup:getPolledPresenceResponse>

   </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Complete SOAP sequence is in soap-test.pdf

 

Thanks in advance,

Matthias

Everyone's tags (4)
1 REPLY 1
Highlighted
Enthusiast

Resolution:

Resolution:

In the Presence Engine logs we can see this error:

11:03:05.275 |system.pe.jabber 1416194 ERROR ClientEmComponent::onError() called Handshake error:
Possible causes could be wrong secret, duplicate or unexpected configuration id passed, or invalid protocol from connection entity.

The above error messages matched with the BUG # https://bst.cloudapps.cisco.com/bugsearch/bug/CSCup49349/

Workaround performed:

1.  Perform a full DRS backup of the cluster, if a restore is required for any reason.

2.  Login to  IM&P server using a remote support account (root)

3.  Update the xcpsecret value in the database on IM&P

4.  Restart the following services: 'Cisco XCP Config Manager' , 'Cisco XCP Router' , 'Cisco Presence Engine'

CreatePlease to create content