01-28-2015 08:12 AM
Hi
I'm trying to use the new addLine/removeLine tags in updatePhone in CUCM 10.5.1. It appears though as if CUCM wasn't yet in a place where this can be handled - here's what I get
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>No line is mentioned in removeLines tag</faultstring><detail><axlError><axlcode>5003</axlcode><axlmessage>No line is mentioned in removeLines tag</axlmessage><request>updatePhone</request></axlError></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
That seems to indicate that it only supports full lines in the removeLines tag.
Here's the full request
<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:updatePhone sequence="1">
<name>UPCHABLA</name>
<description>Updated phone SGRO</description>
<vendorConfig>
<videoCapability>0</videoCapability>
<desktopClient>
<ciscoSupportField>configurationfile=jabber-config201_72.xml</ciscoSupportField>
</desktopClient>
</vendorConfig>
<preemption>Disabled</preemption>
<removeLines>
<lineIdentifier>
<directoryNumber>7306</directoryNumber>
<routePartitionName>p_phones</routePartitionName>
</lineIdentifier>
</removeLines>
<addLines>
<lineIdentifier>
<directoryNumber>7307</directoryNumber>
<routePartitionName>p_gateways</routePartitionName>
</lineIdentifier>
</addLines>
<phoneTemplateName uuid="{8E1A10FA-A52C-4435-A4EC-540D266C8C37}">Standard Client Services Framework</phoneTemplateName>
<userLocale>English United States</userLocale>
<singleButtonBarge>Default</singleButtonBarge>
<joinAcrossLines>Off</joinAcrossLines>
<callInfoPrivacyStatus>Default</callInfoPrivacyStatus>
<ignorePresentationIndicators>false</ignorePresentationIndicators>
<dndOption>Ringer Off</dndOption>
<dndRingSetting>Beep Only</dndRingSetting>
<dndStatus>true</dndStatus>
<alwaysUsePrimeLine>Default</alwaysUsePrimeLine>
<alwaysUsePrimeLineForVoiceMessage>Default</alwaysUsePrimeLineForVoiceMessage>
<callingSearchSpaceName uuid="{DBBD54BA-AFDC-F929-67BF-AEA95C281A39}">CSS_intern</callingSearchSpaceName>
<devicePoolName uuid="{FDF26FD2-4196-9292-20F8-B92ACF6DDB3D}">DP_Bern</devicePoolName>
<commonPhoneConfigName uuid="{AC243D17-98B4-4118-8FEB-5FF2E1B781AC}">Standard Common Phone Profile</commonPhoneConfigName>
<networkLocation>Use System Default</networkLocation>
<locationName uuid="{607255BE-4FC6-17AF-3058-F5649148AFD0}">KLoten</locationName>
<useTrustedRelayPoint>Default</useTrustedRelayPoint>
<retryVideoCallAsAudio>true</retryVideoCallAsAudio>
<securityProfileName uuid="{C6085E14-A32C-4C5E-A3D1-8DAF60D81594}">Cisco Unified Client Services Framework - Standard SIP Non-Secure Profile</securityProfileName>
<sipProfileName uuid="{FCBC7581-4D8D-48F3-917E-00B09FB39213}">Standard SIP Profile</sipProfileName>
<cgpnTransformationCssName uuid="{DBBD54BA-AFDC-F929-67BF-AEA95C281A39}">CSS_intern</cgpnTransformationCssName>
<useDevicePoolCgpnTransformationCss>true</useDevicePoolCgpnTransformationCss>
<sendGeoLocation>false</sendGeoLocation>
<ringSettingIdleBlfAudibleAlert>Default</ringSettingIdleBlfAudibleAlert>
<ringSettingBusyBlfAudibleAlert>Default</ringSettingBusyBlfAudibleAlert>
<networkLocale>United States</networkLocale>
<enableExtensionMobility>false</enableExtensionMobility>
<builtInBridgeStatus>Default</builtInBridgeStatus>
<hlogStatus>On</hlogStatus>
<ownerUserName>testuser</ownerUserName>
<packetCaptureMode>None</packetCaptureMode>
<packetCaptureDuration>0</packetCaptureDuration>
<hotlineDevice>false</hotlineDevice>
<allowCtiControlFlag>true</allowCtiControlFlag>
<presenceGroupName uuid="{AD243D17-98B4-4118-8FEB-5FF2E1B781AC}">Standard Presence group</presenceGroupName>
<unattendedPort>false</unattendedPort>
<requireDtmfReception>false</requireDtmfReception>
<rfc2833Disabled>false</rfc2833Disabled>
<certificateOperation>No Pending Operation</certificateOperation>
<deviceMobilityMode>Default</deviceMobilityMode>
<remoteDevice>false</remoteDevice>
<isActive>true</isActive>
<isDualMode>false</isDualMode>
<phoneSuite>Default</phoneSuite>
<phoneServiceDisplay>Default</phoneServiceDisplay>
<isProtected>false</isProtected>
<mtpRequired>false</mtpRequired>
<mtpPreferedCodec>711ulaw</mtpPreferedCodec>
<outboundCallRollover>No Rollover</outboundCallRollover>
<deviceTrustMode>Not Trusted</deviceTrustMode>
<requireOffPremiseLocation>false</requireOffPremiseLocation>
<useDevicePoolCgpnIngressDN>true</useDevicePoolCgpnIngressDN>
<enableCallRoutingToRdWhenNoneIsActive>false</enableCallRoutingToRdWhenNoneIsActive>
</ns:updatePhone>
</soapenv:Body>
</soapenv:Envelope>
I'll now check if it works if I specify the line with a minimal set of information
@edit: of course, addLines are also affected. I get the same error except for the tag name when I send this:
<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:updatePhone sequence="1">
<name>UPCHABLA</name>
<description>Updated phone SGRO</description>
<vendorConfig>
<videoCapability>0</videoCapability>
<desktopClient>
<ciscoSupportField>configurationfile=jabber-config201_72.xml</ciscoSupportField>
</desktopClient>
</vendorConfig>
<preemption>Disabled</preemption>
<removeLines>
<line>
<index>0</index>
<dirn>
<pattern>7306</pattern>
<routePartitionName>p_phones</routePartitionName>
</dirn>
<associatedEndusers/>
</line>
</removeLines>
<addLines>
<lineIdentifier>
<directoryNumber>7307</directoryNumber>
<routePartitionName>p_gateways</routePartitionName>
</lineIdentifier>
</addLines>
<phoneTemplateName uuid="{8E1A10FA-A52C-4435-A4EC-540D266C8C37}">Standard Client Services Framework</phoneTemplateName>
<userLocale>English United States</userLocale>
<singleButtonBarge>Default</singleButtonBarge>
<joinAcrossLines>Off</joinAcrossLines>
<callInfoPrivacyStatus>Default</callInfoPrivacyStatus>
<ignorePresentationIndicators>false</ignorePresentationIndicators>
<dndOption>Ringer Off</dndOption>
<dndRingSetting>Beep Only</dndRingSetting>
<dndStatus>true</dndStatus>
<alwaysUsePrimeLine>Default</alwaysUsePrimeLine>
<alwaysUsePrimeLineForVoiceMessage>Default</alwaysUsePrimeLineForVoiceMessage>
<callingSearchSpaceName uuid="{DBBD54BA-AFDC-F929-67BF-AEA95C281A39}">CSS_intern</callingSearchSpaceName>
<devicePoolName uuid="{FDF26FD2-4196-9292-20F8-B92ACF6DDB3D}">DP_Bern</devicePoolName>
<commonPhoneConfigName uuid="{AC243D17-98B4-4118-8FEB-5FF2E1B781AC}">Standard Common Phone Profile</commonPhoneConfigName>
<networkLocation>Use System Default</networkLocation>
<locationName uuid="{607255BE-4FC6-17AF-3058-F5649148AFD0}">KLoten</locationName>
<useTrustedRelayPoint>Default</useTrustedRelayPoint>
<retryVideoCallAsAudio>true</retryVideoCallAsAudio>
<securityProfileName uuid="{C6085E14-A32C-4C5E-A3D1-8DAF60D81594}">Cisco Unified Client Services Framework - Standard SIP Non-Secure Profile</securityProfileName>
<sipProfileName uuid="{FCBC7581-4D8D-48F3-917E-00B09FB39213}">Standard SIP Profile</sipProfileName>
<cgpnTransformationCssName uuid="{DBBD54BA-AFDC-F929-67BF-AEA95C281A39}">CSS_intern</cgpnTransformationCssName>
<useDevicePoolCgpnTransformationCss>true</useDevicePoolCgpnTransformationCss>
<sendGeoLocation>false</sendGeoLocation>
<ringSettingIdleBlfAudibleAlert>Default</ringSettingIdleBlfAudibleAlert>
<ringSettingBusyBlfAudibleAlert>Default</ringSettingBusyBlfAudibleAlert>
<networkLocale>United States</networkLocale>
<enableExtensionMobility>false</enableExtensionMobility>
<builtInBridgeStatus>Default</builtInBridgeStatus>
<hlogStatus>On</hlogStatus>
<ownerUserName>testuser</ownerUserName>
<packetCaptureMode>None</packetCaptureMode>
<packetCaptureDuration>0</packetCaptureDuration>
<hotlineDevice>false</hotlineDevice>
<allowCtiControlFlag>true</allowCtiControlFlag>
<presenceGroupName uuid="{AD243D17-98B4-4118-8FEB-5FF2E1B781AC}">Standard Presence group</presenceGroupName>
<unattendedPort>false</unattendedPort>
<requireDtmfReception>false</requireDtmfReception>
<rfc2833Disabled>false</rfc2833Disabled>
<certificateOperation>No Pending Operation</certificateOperation>
<deviceMobilityMode>Default</deviceMobilityMode>
<remoteDevice>false</remoteDevice>
<isActive>true</isActive>
<isDualMode>false</isDualMode>
<phoneSuite>Default</phoneSuite>
<phoneServiceDisplay>Default</phoneServiceDisplay>
<isProtected>false</isProtected>
<mtpRequired>false</mtpRequired>
<mtpPreferedCodec>711ulaw</mtpPreferedCodec>
<outboundCallRollover>No Rollover</outboundCallRollover>
<deviceTrustMode>Not Trusted</deviceTrustMode>
<requireOffPremiseLocation>false</requireOffPremiseLocation>
<useDevicePoolCgpnIngressDN>true</useDevicePoolCgpnIngressDN>
<enableCallRoutingToRdWhenNoneIsActive>false</enableCallRoutingToRdWhenNoneIsActive>
</ns:updatePhone>
</soapenv:Body>
</soapenv:Envelope>
02-03-2015 04:24 PM
Stephan,
I got similar results when I tested this as well and it appears to be a bug. I will submit this up as a defect.
Thank you,
Jock
02-09-2015 10:19 AM
Could you post the bug id so that I can track this?
Thanks
02-11-2015 11:10 AM
Stephan the bug ID is CSCus89666
02-13-2015 08:28 AM
Stephan,
The remove lines problem is related to another bug CSCuq54437 , which has a fix for it now. The engineers are looking into the other problem with addLines.
I will let you know if they come up with anything else.
Thank You,
Jock
02-17-2015 03:05 PM
Stephan,
An update from the DE on the AXL updatePhone... the lineIdentifier tag should not be used with the addLines or removeLines tags, they should only be used under the lines tag. The DE said they will update the WSDL to reflect the proper use of lineIdentifier.
Thank You,
Jock
02-18-2015 12:22 AM
hat's a rather weird design choice though. I mean.. you can use lineIdentifiers on addPhone, thus adding lines without all the things around it... so why not on update (after all.. if cucm can add all the stuff that's in a <line> tag if you just use lineIdentifier for addPhone, it should be able to do so for updatePhone).
And even more so for removing lines.. a line is uniquely identified by a lineIdentifier, so the most efficient way to remove a line would effectivly be an updatePhone with a lineIdentifier in a removeLines.
02-19-2015 09:48 AM
Yeah I would agree with you to that end. I could send that up as a add feature request for them to put that functionality into the addLine and removeLine sections?
Let me know your thoughts on that.
06-09-2017 06:16 AM
I never answered but of course the answer is yes. Any step that makes things easier is appreciated.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: