Administration XML Developer Forums

Combination View Flat View Tree View
Threads [ Previous | Next ]
I tried to associate a user with a Phone Profile and a Primary Extension with an
updateUser Request and got an error message.
 
<ns:updateUser sequence="1">
          <userid>emuser</userid>
         <phoneProfiles> 
              <profileName>udp-xyz</profileName>
         </phoneProfiles>
         <primaryExtension>
              <pattern>123456</pattern>
              <routePartitionName>partition</routePartitionName>
         </primaryExtension>  
</ns:updateUser>
 
<axl:Error xmlns:axl="http://www.cisco.com/AXL/API/7.1">
    <axl:code>5003</axl:code>
     <axl:message>Primary Extension DN should be associated with the associated devices of the User</axl:message>
     <request>updateUser</request>
 </axl:Error>
 
But it works if I use an updateUser with an additional associatedDevices set to the
same value as the phoneProfiles.

<ns:updateUser sequence="1">
   <userid>emuser</userid>
   <associatedDevices>     
      <device>udp-xyz</device>
   </associatedDevices>
   <phoneProfiles>
      <profileName>udp-xyz</profileName>
   </phoneProfiles>
    <primaryExtension>
        <pattern>123456</pattern>
         <routePartitionName>partition</routePartitionName>
     </primaryExtension>
</ns:updateUser>
 
Is this operation correct/allowed?

RE: Primary Extension
Answer
10/5/11 12:00 PM as a reply to GUENTER TREPOHL.
I have run into the same issue. If I provide a Primary Extension in the addUser AXL the CUCM 8 I have responds with "Primary Extension DN should be associated with the associated device of the User", yet if I remove th primaryExtension tag the user is added fine. Surely this doesn't have to be a two step deal (i.e AddUser then UpdateUser?)
 
How can we associate a Primary Extension DN with a user's associated devices before the user exists?
Nice one cisco.
 
Aaron

Hi Graham,

I have had to do the add and then update for a while now, it would be good to have it accepted in the Add,
but it's not that a big of a deal to perform an update as well IMHO
(after almost 10 years of AXL programming I guess I just have accepted the flaws and work around them)

regards
Sascha