updateUser -> primaryExtension and associatedGroups not working

Version 1
    This document was generated from CDN thread

    Created by: Michael Schmidt on 10-05-2012 08:40:01 AM
    Hi,
     
    I just want to use the AXL function "updateUser" with this commands at our CUCM 8.6.2
     
    The "associatedDevices" command is working but
     
    - primaryExtension and also
    - associatedGroups
     
    are not working.
     
    Can anybody help me about this?
     
        <userid>citest</userid>
        <associatedDevices>
            <device>SEP0023EB51FED5</device>
        </associatedDevices>
        <primaryExtension>
            <pattern>1916664</pattern>
        </primaryExtension>
        <associatedGroups>
            <userGroup>
                <name>Standard CCM End Users</name>
            </userGroup>
        </associatedGroups>
     
    I also tried "primaryExtension" with "1916664 in Everyone" as I have to select this in the web gui of the end user. But this is also not working.
     
        <userid>citest</userid>
        <associatedDevices>
            <device>SEP0023EB51FED5</device>
        </associatedDevices>
        <primaryExtension>
            <pattern>1916664 in Everyone</pattern>
        </primaryExtension>
        <associatedGroups>
            <userGroup>
                <name>Standard CCM End Users</name>
            </userGroup>
        </associatedGroups>
     
    BR
    Michael

    Subject: Phone Service URI?
    Replied by: Wes Schochet on 14-05-2012 04:28:57 PM
    Is there a Phone Service URI that will clear out the ITL file on a phone?   I would like to automate this PITB process!

    Confidentiality Statement:
    This email/fax, including attachments, may include confidential
    and/or proprietary information and may be used only by the
    person or entity to which it is addressed. If the reader of
    this email/fax is not the intended recipient or his or her
    agent, the reader is hereby notified that any dissemination,
    distribution or copying of this email/fax is prohibited. If you
    have received this email/fax in error, please notify the sender
    by replying to this message and deleting this email or
    destroying this facsimile immediately.

    Subject: RE: updateUser -> primaryExtension and associatedGroups not working
    Replied by: Michael Schmidt on 14-05-2012 02:53:09 PM
    Hi,

    can anybody help at this?

    BR
    Michael

    Subject: RE: updateUser -> primaryExtension and associatedGroups not working
    Replied by: David Staudt on 15-06-2012 05:54:59 PM
    <associatedGroups> and <primaryExtension> seem to be working ok on my test 8.5(1) system using the following request:
     

    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/8.5">
      <soapenv:Header/>
      <soapenv:Body>
        <ns:updateUser sequence="1">
          <userid>cupuser1</userid>
          <pin>12345</pin>
          <associatedGroups>
            <userGroup>
              <name>Standard CCM End Users</name>
            </userGroup>
            <userGroup>
              <name>Standard CCM Super Users</name>
            </userGroup>
            <userGroup>
              <name>Standard CAR Admin Users</name>
            </userGroup>
          </associatedGroups>
          <primaryExtension>
            <pattern>1000</pattern>
            <routePartitionName>testPartition</routePartitionName>
          </primaryExtension>
        </ns:updateUser>
      </soapenv:Body>
    </soapenv:Envelope>


    Make sure the userGroup names are valid, down to spacing and case.


    Note that you can specify an extension either like:


    <primaryExtension uuid="{A4089E20-1A17-BEDF-CDDF-F2E5BE3A0648}"/>


    or like:



          <primaryExtension>
            <pattern>1000</pattern>
            <routePartitionName>testPartition</routePartitionName>
          </primaryExtension>
     
    but in the latter form you must provide both the pattern and routePartitionName.
     
    Also the primary extension must be a DN that exists on one of the devices associated to the user.