6961 XSD Problem

Version 1

    Subject: RE: 6961 XSD Problem
    Replied by: David Staudt on 05-12-2011 12:56:46 PM
    Sounds like a potential defect.  You can provide a network packet capture (e.g. Wireshark) for the working and non-working scenarios?  Attach here is fine...

    Subject: RE: 6961 XSD Problem
    Replied by: HOLGER SIMON on 05-12-2011 06:31:12 PM
    Sounds like a potential defect.  You can provide a network packet capture (e.g. Wireshark) for the working and non-working scenarios?  Attach here is fine...


     
     
    Hello,
    i have attached the XML responses of the phoneservice server below, which the phone tries to process.
    For easier reading, if have extracted the xml.

    The NON working example causes a phone service crash/non responding.

    This request fails, because the phone cannot handle the value of the url tag, in our case the legnth of the correlationID seams to be the problem.
    The XSD says, URL tag can have a length up to 255, but that don't works on the 6961, it crashes if the length exceeds 171.
     
    Kind regard,
    Holger
     
    NON Working example:
    <CiscoIPPhoneInput xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <Prompt>Change PIN</Prompt>
    <URL>
    http://10.10.100.100:10000/phone_services/cp?device=SEPFFFFFFFFFFFF&action=edit&correlationId=7509998070404154841--2c2f6994.133d4988e7d.-6cab&lineUuid=FFFFFFFF-9246-463F-D07E-1234567890D
    </URL>
    <InputItem>
    <DisplayName>PIN (old)</DisplayName>
    <DefaultValue/>
    <QueryStringParam>old_pin</QueryStringParam>
    <InputFlags>NP</InputFlags>
    </InputItem>
    <InputItem>
    <DisplayName>PIN (new)</DisplayName>
    <DefaultValue/>
    <QueryStringParam>new_pin1</QueryStringParam>
    <InputFlags>NP</InputFlags>
    </InputItem>
    <InputItem>
    <DisplayName>PIN (new)</DisplayName>
    <DefaultValue/>
    <QueryStringParam>new_pin2</QueryStringParam>
    <InputFlags>NP</InputFlags>
    </InputItem>
    </CiscoIPPhoneInput>
     
     
    Working example:
    <CiscoIPPhoneInput xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <Prompt>PIN Ändern</Prompt>
    <URL>
    http:///10.10.100.100:7001/phone_services/cp?device=SEPE05FB9C4A713&action=edit&correlationId=7509998070404154841--2c2f6994
    </URL>
    <InputItem>
    <DisplayName>PIN (alt)</DisplayName>
    <DefaultValue/>
    <QueryStringParam>old_pin</QueryStringParam>
    <InputFlags>NP</InputFlags>
    </InputItem>
    <InputItem>
    <DisplayName>PIN (neu)</DisplayName>
    <DefaultValue/>
    <QueryStringParam>new_pin1</QueryStringParam>
    <InputFlags>NP</InputFlags>
    </InputItem>
    <InputItem>
    <DisplayName>PIN (Wiederholung)</DisplayName>
    <DefaultValue/>
    <QueryStringParam>new_pin2</QueryStringParam>
    <InputFlags>NP</InputFlags>
    </InputItem>
    </CiscoIPPhoneInput>
    This document was generated from CDN thread

    Created by: HOLGER SIMON on 05-12-2011 11:41:51 AM
    Hello,
     
    we are developing a simple phone service that should allow users to change their PINs (the XML of the service is attached). The service comprises of 3 input fields (old PIN, new PIN and new PIN confirmation). In order to correlate requests and responses require our backend system the line¿s UUID as well as special correlation id. They are added to the (callback) URL associated with the phone service as parameters.

    It works as expected on all phones except of CP-6961. On this type of phone, whenever the associated URL exceeds 171 characters, the backspace button on the phone stops to work. The length of associated URL is less than 171 characters then everything works fine. The backspace button is not generated by us but rather by the phone. So, we have no way to influence the behaviour of this button. Further, according to official developer guide and corresponding XSD, the URL can be 256 characters long, so, we don¿t violate the XSD.

    CUCM  Version: 8.5.1.13031
    Phoneload  Version 6961: 9.2.1 ES5

    Kind regards,
    Holger

    Subject: RE: 6961 XSD Problem
    Replied by: HOLGER SIMON on 28-12-2011 12:26:32 PM
    Hello Mr. Staudt,
    I have attached the captures.
    do you need more input from my side?

    Kind regards,
    Holger

    Subject: RE: 6961 XSD Problem
    Replied by: HOLGER SIMON on 06-01-2012 09:42:47 AM
    Hello Mr. Staudt,
    here I have attached the Files from the phones webserver.

    Kind regards,
    Holger

    Subject: RE: 6961 XSD Problem
    Replied by: David Staudt on 06-01-2012 03:53:21 PM
    Thanks the XML and code samples will be very helpful.
     
    Two items:
     
    - The phones do support cookies, so you should be able to put the correlation ID into the cookie and workaround the problem
    - The firmware load you are reporting is an older load, I would suggest trying with the latest load 9.2.2.6, just in case

    Subject: RE: 6961 XSD Problem
    Replied by: HOLGER SIMON on 09-01-2012 09:47:07 AM
    Hello,
    thanks for your answer!

    to your first point:
    the implementation of that is alreday finished and it is not easy for us to change that to cookies.
     
    to your second point:
    Today i have downloaded the 9.2.2.6 and tested with that, but the problem is the same with this. If the URL Parameter within the page exceeds 171 characters, the phone is unable to process that page.

    Kind regards,
    Holger

    Subject: RE: 6961 XSD Problem
    Replied by: David Staudt on 12-01-2012 11:24:09 AM
    The phone engineering team has confirmed this issue as a new defect, please use CSCtx32637 for tracking.  A fix will be provided in an upcoming firmware release TBD.