topic Re: Update action on user's primary extension through AXL not working in Management

Update action on user's primary extension through AXL not working

sagarn1 — Mon, 12 Oct 2015 19:02:43 GMT

We are trying to update user's primary extension by assigning a new primary extension with existing pattern/partition information in a .NET application via UpdateUserReq. It returns true (no errors/exceptions) but on CUCM primary extension remains blank. Any additional attributes that we need to set to achieve this? Thank you in advance for your help.

Re: Update action on user's primary extension through AXL not working

npetrele — Tue, 13 Oct 2015 14:27:59 GMT

Can you post a sample of the XML request(s) you're using?

Re: Update action on user's primary extension through AXL not working

sagarn1 — Tue, 13 Oct 2015 16:25:15 GMT

I am not using XML. I have compiled WSDL and using function "UpdateUserReq" exposed by it.

Re: Update action on user's primary extension through AXL not working

npetrele — Tue, 13 Oct 2015 17:25:23 GMT

So what are you using? Java or .NET? You're still sending XML, it's what the API does. Could you either post the code that prepares the data for the update, or you can use something like Fiddler to capture the XML, and then post the XML. I actually use Java itself to output the XML. Here's a sample of the kind of code I use:

//Create a String writer object which will be

//used to write jaxbElment XML to string

StringWriter writer = new StringWriter();

// create JAXBContext which will be used to update writer

JAXBContext context = JAXBContext.newInstance(XFkType.class);

// marshall or convert jaxbElement containing student to xml format

context.createMarshaller().marshal(jaxbObj, writer);

//print XML string representation of Student object

System.out.println( writer.toString() );

Re: Update action on user's primary extension through AXL not working

darksnowcat — Wed, 14 Oct 2015 05:55:28 GMT

Which AXL version and which CUCM version do you use?

Re: Update action on user's primary extension through AXL not working

npetrele — Wed, 14 Oct 2015 14:16:04 GMT

Sorry, I don't know why I missed the .NET in your original post.

It would help if you could show the XML that you're sending. Also, are you specifying the routePartitionName (yes, even if it is blank)?

Re: Update action on user's primary extension through AXL not working

sagarn1 — Wed, 14 Oct 2015 14:50:06 GMT

yes, we are setting routePartitionName in the update. I will grab the XML using Fiddler and share with you.

Re: Update action on user's primary extension through AXL not working

sagarn1 — Wed, 14 Oct 2015 15:35:00 GMT

here is XML that is going to the server:

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

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

<soap:Body>

<userid xmlns="">xyzyyzz</userid>

<device>CSFxyzxyz</device>

</associatedDevices>

<routePartitionName>PT_XXXYYY</routePartitionName>

</primaryExtension>

<name>Standard CCM End Users</name>

<userRole>Standard CCM End Users</userRole>

<userRole>Standard CCMUSER Administration</userRole>

</userRoles>

</userGroup>

<name>Standard CTI Enabled</name>

<userRole>Standard CTI Enabled</userRole>

</userRoles>

</userGroup>

<name>Standard CTI Allow Control of Phones supporting Connected Xfer and conf</name>

<userRole>Standard CTI Allow Control of Phones supporting Connected Xfer and conf</userRole>

</userRoles>

</userGroup>

<name>Standard CTI Allow Control of Phones supporting Rollover Mode</name>

<userRole>Standard CTI Allow Control of Phones supporting Rollover Mode</userRole>

</userRoles>

</userGroup>

</associatedGroups>

<profileName uuid="bd7190d8-73e2-7f53-be33-52170979ffb6">CSTTestDeviceProfile</profileName>

</phoneProfiles>

<presenceGroupName xmlns="">Standard Presence group</presenceGroupName>

<subscribeCallingSearchSpaceName xmlns="">CSS_XYZXYZ</subscribeCallingSearchSpaceName>

<enableEmcc xmlns="">false</enableEmcc>

<serviceProfile xmlns="" uuid="{A46437D0-2222-B226-F5AA-70F471CC733E}">UCSP_JABBER_XYZ</serviceProfile>

<userIdentity xmlns="">xyzyyzz@myorg.com</userIdentity>

</updateUser>

</soap:Body>

</soap:Envelope>

Re: Update action on user's primary extension through AXL not working

sagarn1 — Wed, 14 Oct 2015 15:36:26 GMT

10.5 AXL on 10.5 CUCM.

Re: Update action on user's primary extension through AXL not working

dstaudt — Wed, 14 Oct 2015 15:40:56 GMT

Just a thought (I can't test this at the moment), but I know that the Primary Line is validated to ensure it is present on one of the user's associated devices. If you are trying to update the user to add the device at the same time as setting the primary line, there might be a race condition where AXL attempts to do one before the other.

Maybe try making this a two-request process where you associate the device, and then do a subsequent updateUser to set the Primary Line..?

Re: Update action on user's primary extension through AXL not working

npetrele — Wed, 14 Oct 2015 15:48:26 GMT

I recommend that approach (two steps). There's also another way to bypass the restriction of the primary line having to be one of the user's associated devices before you set it as the primary extension. Use addExtensionInfo, instead, and set the sortOrder to 0, which assigns it to the primary extension.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/10.5">

<soapenv:Header/>

<soapenv:Body>

<ns:updateUser>

<userid>nicholas</userid>

</extension>

</addExtensionsInfo>

</ns:updateUser>

</soapenv:Body>

</soapenv:Envelope>

Re: Update action on user's primary extension through AXL not working

sagarn1 — Wed, 14 Oct 2015 15:49:44 GMT

User and device (with the line) are already associated. In this request, we are just trying to update primary extension. It returns true but changes nothing on the user.

Re: Update action on user's primary extension through AXL not working

dstaudt — Wed, 14 Oct 2015 15:56:02 GMT

In that case, you may want to not re-include the device association part of the request, as I suspect that will have the effect of AXL first removing all associated devices, and then re-adding the (same) device - possibly causing the race condition previously mentioned.

Re: Update action on user's primary extension through AXL not working

npetrele — Thu, 15 Oct 2015 16:24:50 GMT

Unfortunately, there are certain cases where it will return true even when the operation does not do what you expect.

As David said, I'd leave the associated devices tag/function out of the request. Or, as I suggested earlier, use the addExtensionsInfo with sortOrder=0 instead of primaryExtension.

Re: Update action on user's primary extension through AXL not working

sagarn1 — Thu, 15 Oct 2015 19:31:06 GMT

We tried the approach of not including device association again and just update primary extension - same result.

In .Net, we did not find any API for updating "extension info". We are now trying to do it using raw XML instead. I will post the results once we complete this change and test it.

Re: Update action on user's primary extension through AXL not working

sagarn1 — Fri, 16 Oct 2015 18:06:54 GMT

It worked with raw XML. Thank you.