This should work (without Jabber clients), and seems to in my 10.5 test environment:
(login app user to get app session ID)
Login labuser1
POST https://10.194.104.62:8083/presence-service/users/labuser1/sessions
Presence-Session-Key: 577c04a7-146-4941dfa2-2591-2
--------------------------
<?xml version="1.0" encoding="UTF-8"?>
<session>
<sessionKey>577c057f-17d-66c94166-7569-1</sessionKey>
</session>
Login labuser2
POST https://10.194.104.62:8083/presence-service/users/labuser2/sessions
Presence-Session-Key: 577c04a7-146-4941dfa2-2591-2
--------------------------
<?xml version="1.0" encoding="UTF-8"?>
<session>
<sessionKey>577c06fe-f1-7852b5e5-51fa-1</sessionKey>
</session>
Set presence of labuser1 (be sure to set Presence-Override to false)
PUT https://10.194.104.62:8083/presence-service/users/labuser1/presence/basic
Content-Type: application/xml
Presence-Session-Key: 577c057f-17d-66c94166-7569-1
Presence-Expiry: 86400
Presence-Override: false
<?xml version="1.0"?>
<presence>AVAILABLE</presence>
Get polled presence on behalf of labuser2 for contact labuser1
Presence-Session-Key: 577c06fe-f1-7852b5e5-51fa-1
---------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<presenceList type="basic">
<contact presenceStatus="AVAILABLE" contactURI="labuser1@ds-cups105.cisco.com"/>
</presenceList>
Comments
0 comments
Please sign in to leave a comment.