Presence API - Validation constraint violation in getPolledPresence in Version 14.0

[r.kloth]

We installed the new version of the Cisco Unified CM IM and Presence Server (System version: 14.0.1.10000-16) 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=http://schemas.xmlsoap.org/soap/envelope/ xmlns:urn="urn:cisco:cup:presence:soap">

    <soapenv:Header>

        <urn:session-key>551e376c-13b-44f32be3-312c-7</urn:session-key>

    </soapenv:Header>

    <soapenv:Body>

        <urn:getPolledPresence>

            <urn:contactsList>

                <urn:contact contactURI=alina.solo@test.abc.com />

            </urn:contactsList>

            <urn:presenceType>RICH_PRESENCE</urn:presenceType>

        </urn:getPolledPresence>

    </soapenv:Body>

</soapenv:Envelope>

And this is the response received:

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

<SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/ xmlns:SOAP-ENC=http://schemas.xmlsoap.org/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:Body>

        <SOAP-ENV:Fault>

            <faultcode>SOAP-ENV:Client</faultcode>

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

        </SOAP-ENV:Fault>

    </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

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?

Thanks.

[Tobias Heeb]

I have the same problem.

Did you solve it somehow?

Many Thanks

[r.kloth]

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.

[r.kloth]

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.

[r.kloth]

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

[Tobias Heeb]

That's good news!

I will test it in my lab too.

Did you also test the subscribed presence?

[r.kloth]

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.

[Urs Wuest]

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.

[r.kloth]

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