cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1263
Views
0
Helpful
1
Replies
Highlighted
Beginner

AddDeviceProfile Function Fails on CUCM 8.6.2a

What?
addDeviceProfile function call fails after CUCM upgrade from rel 7.1.5 to 8.6.2

Application:
Cisco Unified Communications Manager (CUCM)

Current Version:
Cisco Unified Communications Manager Release 8.6.2

Previous Version:
Cisco Unified Communications Manager Release 7.1.5

We've tried changing the Headers after the upgrade, but received similar error messages:

Header for 7.1
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <axl:addDeviceProfile
    xmlns:axl="http://www.cisco.com/AXL/1.0"
    xsi:schemaLocation="http://www.cisco.com/AXL/1.0 http://ccmserver/schema/axlsoap.xsd"
    sequence="1234">
   
Header for 8.5

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <axl:addDeviceProfile
    xmlns:axl="http://www.cisco.com/AXL/8.5"
    xsi:schemaLocation="http://www.cisco.com/AXL/API/8.5 http://ccmserver/schema/axlsoap.xsd"
    sequence="1234">

Extension Mobility Service's URL changed after upgrade and was changed, but still received same error message:
   
Extension Mobility URL for 7.1.5
  <url>http://ccmserver:8080/emapp/EMAppServlet?device=#DEVICENAME#</url>
 
Extension Mobility URL for 8.6.2
  <url>http://ccmserver:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#</url>
   
Request:

  <newProfile>
  <name>userid</name>
  <description>UsernameFirstLast</description>
  <product>Cisco 7960</product>
  <model>Cisco 7960</model>
  <class>Device Profile</class>
  <protocol>SCCP</protocol>
  <protocolSide>User</protocolSide>
  <mlppIndicationStatus>Off</mlppIndicationStatus>
  <preemption>Disabled</preemption>
  <lines>
    <line index='1'>
    <label>UsernameFirst - 1212</label>
    <display>UsernameFirstLast</display>
    <dirn>
      <pattern>2223331212</pattern>
      <usage>Device</usage>
      <routePartitionName>SITE_Partition</routePartitionName>
    </dirn>
    <ringSetting>Use System Default</ringSetting>
    <maxNumCalls>4</maxNumCalls>
    <busyTrigger>2</busyTrigger>
    <callInfoDisplay>
      <callerName>true</callerName>
      <dialedNumber>true</dialedNumber>
    </callInfoDisplay>
    </line>
  </lines>
  <services>
    <service>
    <telecasterServiceName>ExtMob</telecasterServiceName>
    <name>ExtMob</name>
    <url>http://ccmserver:8080/emapp/EMAppServlet?device=#DEVICENAME#&EMCC=#EMCC#</url>
    </service>
  </services>
  <softkeyTemplateName>Standard</softkeyTemplateName>
  </newProfile>

Answer: 
  2012-05-09 18:53:46,759 INFO  [http-8443-3] servletRouters.AXLFilter -
  <SOAP-ENV:Envelope
  SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
  xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Header/>
  <SOAP-ENV:Body>
    <SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode>
    <faultstring>Item not valid: The specified URL was not found</faultstring>
    <detail>
      <axl:Error xmlns:axl="http://www.cisco.com/AXL/API/1.0">
      <axl:code>5007</axl:code>
      <axl:message>Item not valid: The specified URL was not found</axl:message>
      <request>addDeviceProfile</request>
      </axl:Error>
    </detail>
    </SOAP-ENV:Fault>
  </SOAP-ENV:Body>
  </SOAP-ENV:Envelope>
 
Other error message:
  Failed to read schema document '/usr/local/thirdparty/jakarta-tomcat/webapps/axl/schema/6.1/SoapEnvelope.xsd',
  because
    1) could not find the document;
    2) the document could not be read;
    3) the root element of the document is not <xsd:schema>.5001schema_reference.
 
Can someone comment on what could be wrong and/or post a sucessful AddDeviceProfile Request Sample Code for us to try?

1 REPLY 1
Highlighted
Beginner

Hi,

I dont know how to solve it but I identified the root cause. You can't see it because your probably reading the xml from a browser or something that properly parse the xml and special character, but, if you look at the request in the axl logs you'll find that &EMCC is changed to &,EMCC probably by the XML serialiser of the AXL proxy Class

Content for Community-Ad