Appears to have been removed from IOS XE...   https://community.cisco.com/t5/routing/ip-dns-server-configuration-in-asr-1006/td-p/2141875   ... View more

I can understand this reasoning for phones.  The use case for phones is different - the xsd explicitly requires a uuid or a name. But this gets really confusing for singletons.  Here, I can send none, it's not validated in the schema but returns errors in some cases, and in others not.  So based on what you're saying, I now need to consider the scenario where ldapAuth was never configured, as only then will a get an error.  But you're also saying that it will return something (I haven't checked this) if there was a prior config, but it's disabled?  :/ If that's the expected behaviour distinguishing the two cases, then so be it.  Ultimately I want a reliable way to determine the UUID (if available) in all cases.  At least I understand it now... thanks! ... View more

That's being added by the soap library I'm using.  It's not resulting in an error in any other calls Not sure why you're going on about defining in the GUI.  I shouldn't have to define it in the UI for the get to work on a singleton call.  It should return the element, or return nothing.  It should not raise an exception.  That's why I demonstrated the inconsistency between the two Reqs. It works in the positive case.  It's the negative case where the bug is. ... View more

Hi, As I said: don't include the braces {} You need to specify the pkid values for each. you're incorrectly specifying userid and device name ... View more

Please remove the double quote. You need to replace everything that's in the braces with a valid pkid.  The braces are obviously not part of the sql statement. I'm not sure what ` sfareed_em` is, but please note that you need a user pkid there. ... View more

INSERT INTO enduserdevicemap     (fkenduser, fkdevice, tkuserassociation) VALUES     ('{eu_pkid}', '{d_pkid}', 1) In the AFNP paradigm, you could do this in a try/catch construct, and filter the error to ignore for duplicate inserts if you get them.  I think this is quicker than an AXL get/update trawling through an xml sequence. Assumes you have both PKIDs.  otherwise you'd need to get them first or with sql querying. ... View more

Hi, Looking at updatePhone in the schema, I see that this requires an XPhoneLine object. The schema for this is: <xsd:complexType name= "XPhoneLine" >   <xsd:sequence minOccurs= "0" >   <xsd:element maxOccurs= "1" minOccurs= "1" name= "index" type= "axlapi:XInteger" />   <xsd:element maxOccurs= "1" minOccurs= "0" name= "label" type= "axlapi:String50" />   <xsd:element maxOccurs= "1" minOccurs= "0" name= "display" type= "axlapi:String50" />   <xsd:element maxOccurs= "1" minOccurs= "1" name= "dirn" type= "axlapi:XDirn" >   <xsd:annotation>   <xsd:documentation> Only uuid attribute is returned in response </xsd:documentation>   </xsd:annotation>   </xsd:element>   <xsd:element default= "Ring" maxOccurs= "1" minOccurs= "0" name= "ringSetting" type= "axlapi:XRingSetting" />   <xsd:element default= "Use System Default" maxOccurs= "1" minOccurs= "0" name= "consecutiveRingSetting" nillable= "true" type= "axlapi:XRingSetting" >   <xsd:annotation>   <xsd:documentation> Consecutive Rings Setting. Replaces the consective ring setting on IPPhone. </xsd:documentation>   </xsd:annotation>   </xsd:element>   <xsd:element default= "Use System Default" maxOccurs= "1" minOccurs= "0" name= "ringSettingIdlePickupAlert" nillable= "true" type= "axlapi:XRingSetting" >   <xsd:annotation>   <xsd:documentation> Applicable only for IP Phones </xsd:documentation>   </xsd:annotation>   </xsd:element>   <xsd:element default= "Use System Default" maxOccurs= "1" minOccurs= "0" name= "ringSettingActivePickupAlert" nillable= "true" type= "axlapi:XRingSetting" >   <xsd:annotation>   <xsd:documentation> Applicable only for IP Phones </xsd:documentation>   </xsd:annotation>   </xsd:element>   <xsd:element maxOccurs= "1" minOccurs= "0" name= "displayAscii" type= "axlapi:String50" />   <xsd:element maxOccurs= "1" minOccurs= "0" name= "e164Mask" nillable= "true" type= "axlapi:String255" />   <xsd:element default= "Use System Policy" maxOccurs= "1" minOccurs= "0" name= "mwlPolicy" type= "axlapi:XMWLPolicy" />   <xsd:element default= "2" maxOccurs= "1" minOccurs= "0" name= "maxNumCalls" type= "axlapi:XInteger" />   <xsd:element default= "1" maxOccurs= "1" minOccurs= "0" name= "busyTrigger" type= "axlapi:XInteger" />   <xsd:element maxOccurs= "1" minOccurs= "0" name= "callInfoDisplay" >   <xsd:complexType>   <xsd:sequence minOccurs= "0" >   <xsd:element default= "true" maxOccurs= "1" minOccurs= "0" name= "callerName" type= "axlapi:boolean" />   <xsd:element default= "false" maxOccurs= "1" minOccurs= "0" name= "callerNumber" type= "axlapi:boolean" />   <xsd:element default= "false" maxOccurs= "1" minOccurs= "0" name= "redirectedNumber" type= "axlapi:boolean" />   <xsd:element default= "true" maxOccurs= "1" minOccurs= "0" name= "dialedNumber" type= "axlapi:boolean" />   </xsd:sequence>   </xsd:complexType>   </xsd:element>   <xsd:element maxOccurs= "1" minOccurs= "0" name= "recordingProfileName" nillable= "true" type= "axlapi:XFkType" />   <xsd:element maxOccurs= "1" minOccurs= "0" name= "monitoringCssName" nillable= "true" type= "axlapi:XFkType" />   <xsd:element default= "Call Recording Disabled" maxOccurs= "1" minOccurs= "0" name= "recordingFlag" type= "axlapi:XRecordingFlag" />   <xsd:element default= "Default" maxOccurs= "1" minOccurs= "0" name= "audibleMwi" type= "axlapi:XStatus" >   <xsd:annotation>   <xsd:documentation> Not applicable for gatewayEndpointAnalogAccess and CiscoCatalyst600024PortFXSGateway </xsd:documentation>   </xsd:annotation>   </xsd:element>   <xsd:element maxOccurs= "1" minOccurs= "0" name= "speedDial" nillable= "true" type= "xsd:string" />   <xsd:element default= "General" maxOccurs= "1" minOccurs= "0" name= "partitionUsage" type= "axlapi:XPartitionUsage" >   <xsd:annotation>   <xsd:documentation> This tag cannot be modified. It can only be specified in the add request. </xsd:documentation>   </xsd:annotation>   </xsd:element>   <xsd:element maxOccurs= "1" minOccurs= "0" name= "associatedEndusers" >   <xsd:complexType>   <xsd:sequence minOccurs= "0" >   <xsd:element maxOccurs= "unbounded" minOccurs= "0" name= "enduser" type= "axlapi:XEnduserMember" />   </xsd:sequence>   </xsd:complexType>   </xsd:element>   <xsd:element default= "true" maxOccurs= "1" minOccurs= "0" name= "missedCallLogging" type= "axlapi:boolean" />   <xsd:element default= "Gateway Preferred" maxOccurs= "1" minOccurs= "0" name= "recordingMediaSource" type= "axlapi:XPreferredMediaSource" />   </xsd:sequence>   <xsd:attribute name= "ctiid" type= "xsd:nonNegativeInteger" /> </xsd:complexType> It looks like you're missing this: <xsd:element maxOccurs= "1" minOccurs= "1" name= "dirn" type= "axlapi:XDirn" > Note the minOccurs="1" Please can you update your update request to include XDirn?  Its schema is the standard directory number info: <xsd:complexType name= "XDirn" >   <xsd:sequence minOccurs= "0" >   <xsd:element maxOccurs= "1" minOccurs= "1" name= "pattern" type= "xsd:string" />   <xsd:element maxOccurs= "1" minOccurs= "1" name= "routePartitionName" nillable= "true" type= "axlapi:XFkType" />   </xsd:sequence>   <xsd:attribute name= "uuid" type= "axlapi:XUUID" /> </xsd:complexType> If this works after you include this - it's an AXL defect for returning a 200 OK.  It's 99% a bug - doesn't follow the schema. ... View more

Think you're getting no response here because you're not showing any effort or any idea of what you really want.  For a start, what language are you looking to develop your script in?  Have you tried anything yourself?  Where are you stuck? ... View more

Not AXL - you're looking in the wrong place: https://developer.cisco.com/docs/sxml/#!control-center-services-api-reference soapGetServiceStatus soapGetStaticServiceList ... View more

Excellent, got you now. ... View more

Can you give an example of what you mean by this: some requests do provide <addXXX> and <removeXXX> lists where you can add/remove items instead of manipulating the full list. ... View more

Hi, I've had confirmation that they are supported for phones as well (am still confirming 3rd-party device support).  Can you please apply to the SIP Profile for the device, and do an SDL capture and share this?  I reckon we should be able to get this working, or at least do an analysis and check! ... View more

One more question - the way you're describing, this should be supported for 3rd party SIP devices as well? ... View more

Awesome!  Good to know, thank you for the confirmation. ... View more

Really?  I had read that normalization scripts were only supported for trunks. ... View more