Setting Primary Device on CIPC

Version 1
    This document was generated from CDN thread

    Created by: MIKE WILCOX on 21-09-2011 07:28:51 PM
    Greetings!
     
    I have a bunch of CIPC that were created but did not have the Primary Device field set to the user's hard phone resulting in three DLUs being consumed instead of one DLU.
     
    I am sending an AXL request to set the <primaryDeviceName> attributed but am getting an error back about an unexpected end of file. Any insights?
     
    Thanks,
     
    Mike
     
    Here is the request:
     
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

             <SOAP-ENV:Body>
            <updatePhone>
            <name>PO696910044096</name>
    <primaryPhoneName>SEP00175A871B32</primaryPhoneName>
    </updatePhone>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>

    And here is the response:
     
    <SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header/>
    <SOAP-ENV:Body>
    <SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode>
    <faultstring>Premature end of file.</faultstring>
    <detail><axl:Error xmlns:axl="http://www.cisco.com/AXL/7.0"><axl:code>5001</axl:code>
    <axl:message>Premature end of file.</axl:message>
    <request/></axl:Error></detail>
    </SOAP-ENV:Fault></SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
     
     

    Subject: RE: New Message from MIKE WILCOX in Administration XML (AXL) - Administrati
    Replied by: Dennis Heim on 21-09-2011 07:33:02 PM
    That may be easier to do with raw sql.

    Dennis Heim
    Network Voice Engineer
    CDW  Advanced Technology Services
    10610 9th Place
    Bellevue, WA 98004

    317.569.4255 Single Number Reach
    317.569.4201 Fax
    dennis.heim@cdw.com<mailto:dennis.heim@cdw.com>
    cdw.com/content/solutions/unified-communications/<http://www.cdw.com/content/solutions/unified-communications/>

    From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    Sent: Wednesday, September 21, 2011 4:29 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from MIKE WILCOX in Administration XML (AXL) - Administration XML Questions: Setting Primary Device on CIPC

    MIKE WILCOX has created a new message in the forum "Administration XML Questions":

    --------------------------------------------------------------
    Greetings!

    I have a bunch of CIPC that were created but did not have the Primary Device field set to the user's hard phone resulting in three DLUs being consumed instead of one DLU.

    I am sending an AXL request to set the <primaryDeviceName> attributed but am getting an error back about an unexpected end of file. Any insights?

    Thanks,

    Mike

    Here is the request:

    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

             <SOAP-ENV:Body>
            <updatePhone>
            <name>PO696910044096</name>
    <primaryPhoneName>SEP00175A871B32</primaryPhoneName>
    </updatePhone>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>

    And here is the response:

    <SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header/>
    <SOAP-ENV:Body>
    <SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode>
    <faultstring>Premature end of file.</faultstring>
    <detail><axl:Error xmlns:axl="http://www.cisco.com/AXL/7.0"><axl:code>5001</axl:code>
    <axl:message>Premature end of file.</axl:message>
    <request/></axl:Error></detail>
    </SOAP-ENV:Fault></SOAP-ENV:Body>
    </SOAP-ENV:Envelope>


    --
    To respond to this post, please click the following link:

    <http://developer.cisco.com/web/axl/forums/-/message_boards/view_message/4523091>

    or simply reply to this email.