Showing results for 
Search instead for 
Did you mean: 

Presence API - Validation constraint violation in getPolledPresence in Version 14.0

We installed the new version of the Cisco Unified CM IM and Presence Server (System version: and ran into a problem with the call "getPolledPresence" which returns an error "Validation constraint violation: value range or content length violation in element 'urn:contact'". I could not find any problem with the call and in version 12.5 there was no problem with this call.


Here is the request we send:

soapenv:Envelope xmlns:soapenv= xmlns:urn="urn:cisco:cup:presence:soap">







                <urn:contact />







And this is the response received:

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV= xmlns:SOAP-ENC= xmlns:xsi= xmlns:xsd= xmlns:cup="urn:cisco:cup:presence:soap">




            <faultstring>Validation constraint violation: value range or content length violation in element 'urn:contact'</faultstring>





I downloaded the WSDL file from the server and could not find any problem!


Does someone have a similar problem or is this known as a problem in the version 14.0?




I have the same problem.

Did you solve it somehow?


Many Thanks

No, the issue is not resolved so far.

Cisco has filed a defect (CSCvz26720) but did not make a fix and has not outlined a time plan when it will be fixed

I'm still waiting the defect to be reolved.

Cisco noted in the Bug CSCvz26720 that it should be fixed in the Versions:

- CUP.014.000(001.11900.006)

- CUP.014.000(001.11000.179)


I haven't checked it so far. Maybe this will help you.

Cisco has now a fix for the problem and I could successfully test it with the version: CUP


That's good news!

I will test it in my lab too.

Did you also test the subscribed presence?

Not sure what exactly you mean.

We use:

  • registerEndPoint
  • subscribe
  • getPolledPresence
  • getSubscribedPresence

So we register to be notified for presence changes and this works fine.

We use the same functions and have still problems.

The application user login and end user login gives us always only 2 characters long session id's.

Do you experience the same issues?


We always get the 2 characters long session id's and the other functions work with these session id's.

But it's not very reliable.

Sometimes I could not login the end user or application user. Sometimes the presence state is always Unknown. Sometimes I get another presence state but it's not possible to change it. Sometimes I get an error message "Failed to set contacts presence status".


I'm just wondering, if others face the same issues.

The session id looks like a GUID (see response below) - same with the end user login.
I have never seen, that it is only 2 characters long.
Also the interface is very reliable and we have no problem with it.

xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="" xmlns:SOAP-ENC="" xmlns:cup="urn:cisco:cup:presence:soap" xmlns:xsd="" xmlns:xsi=""> <SOAP-ENV:Body> <cup:loginResponse> <cup:success> <cup:session-key>f2cfb131-da3ad142-6474a122-b819c36e</cup:session-key> </cup:success> </cup:loginResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
Recognize Your Peers
Content for Community-Ad