04-06-2016 02:28 AM
Hi everybody,
i just noticed that addPhone requests on cucm 10.5 does not set securityProfileName at all.
Here's my soap request:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://www.cisco.com/AXL/API/10.5">
<SOAP-ENV:Body>
<ns1:addPhone>
<phone>
<name>SEP123456787357</name>
<product>Cisco 9951</product>
<class>Phone</class>
<protocol>SIP</protocol>
<protocolSide>User</protocolSide>
...
<securityProfileName>secp_unit_test_1</securityProfileName>
...
</phone>
</ns1:addPhone>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Similar request works with cucm 11 and 9, but does not work with cucm 10. Any idea?
Thanks for your help!
Regards, Michael
Solved! Go to Solution.
04-13-2016 01:07 AM
Found the error. My test used a certificate operation with keysize of 1024, so cucm ignored my security profile and selected a security profile with corresponding keysize. Don't know why this only works on cucm 10.5 and cucm 11.0 does not have that check...
04-08-2016 09:01 AM
Seems to work on my 10.5 test system, using a built-in security profile name:
<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:addPhone>
<phone>
<name>CSFLABUSER32</name>
<product>Cisco Unified Client Services Framework</product>
<model>Cisco Unified Client Services Framework</model>
<class>Phone</class>
<protocol>SIP</protocol>
<protocolSide>User</protocolSide>
<devicePoolName>Default</devicePoolName>
<securityProfileName>Cisco Unified Client Services Framework - Standard SIP Non-Secure Profile</securityProfileName>
<sipProfileName>Standard SIP Profile</sipProfileName>
<lines>
<line>
<index>1</index>
<dirn>
<pattern>1032</pattern>
<routePartitionName/>
</dirn>
</line>
</lines>
<ownerUserName>labuser1</ownerUserName>
</phone>
</ns:addPhone>
</soapenv:Body>
</soapenv:Envelope>
Can you confirm the security profile name is an exact match on your system? Could you try a built-in security profile? Maybe try renaming without the underscores..?
04-13-2016 01:07 AM
Found the error. My test used a certificate operation with keysize of 1024, so cucm ignored my security profile and selected a security profile with corresponding keysize. Don't know why this only works on cucm 10.5 and cucm 11.0 does not have that check...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide