04-01-2014 06:09 PM
Dear Team,
I am using the axl interface method of 'updateline" to update the info of call manager in order to configure the "call forward" function on the phone,I can be configured successfully on call manager 8.6 and 9.1.1, but when I configure this on call manager 9.1.2.10000, I get the error of "The specified Directory Number was not found". I check the configuration of this phone directory number, I don't find any problems.
the following is the code I used :
"POST /axl/ HTTP/1.0\r\n";
"Host:" + Global.CCM_IP + ":8443\r\n";
"Authorization: Basic " + authorization + "\r\n";
"Accept: text/*\r\n";
"Content-type: text/xml\r\n";
"SOAPAction: \"CUCM:DB ver=8.0\"\r\n";
"Content-length: ";
"<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:ns=\"http://www.cisco.com/AXL/API/8.0\">";
" <soapenv:Header/>";
"<soapenv:Body>";
"<ns:updateLine sequence=\"?\">";
"<pattern>" + phoneNum + "</pattern>";
"<routePartitionName>" + pattern + "</routePartitionName>";
"<callForwardAll>";
"<destination>" + forwardNum + "</destination>";
"</callForwardAll>";
"</ns:updateLine>";
"</soapenv:Body>";
"</soapenv:Envelope>";
it is emergency for me,
04-03-2014 01:38 AM
Now, I get the successfully response from the CUCM, like the following:
HTTP/1.1 200 OK
Set-Cookie: JSESSIONIDSSO=343B0FC5ABF602EF5F7EA3CD2ABC4FF9; Path=/; Secure; HttpOnly
Set-Cookie: JSESSIONID=B6EBCC3FCD00275E3224C78BF7A4C00B; Path=/axl/; Secure; HttpOnly
Content-Type: text/xml;charset=UTF-8
Content-Length: 321
Date: Thu, 03 Apr 2014 07:48:57 GMT
Connection: close
Server:
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:updateLineResponse sequence="?" xmlns:ns="http://www.cisco.com/AXL/API/8.0"><return>{FD7B72A8-3334-DDE7-FF14-25DD3759FDFB}</return></ns:updateLineResponse></soapenv:Body></soapenv:Envelope>
but on cisco IP Phone of 9951, we can not see the call forward setup successfully.
04-09-2014 02:13 PM
Could you double check the API call?
Also, check on the CUCM UI to see if the destination has been updated after perform AXL.
Here is mine that works
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:axl="http://www.cisco.com/AXL/API/8.5">
<soapenv:Header/>
<soapenv:Body>
<axl:updateLine sequence="?">
<pattern>9971</pattern>
<callForwardAll>
<destination>9951</destination>
</callForwardAll>
</axl:updateLine>
</soapenv:Body>
</soapenv:Envelope>
Regards,
Howard
04-09-2014 06:12 PM
Thanks for your advice, the problem have been resolved.
06-15-2014 09:06 PM
Hi Chao guo,
I got same issue "directory number is not found". My CCM is 9.1.1 and using compatible AXL. I tried several different DN but nothing works. What's your solution to fix the problem? Thanks a lot for the help!
My XML is configured as below:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/9.1">
<soapenv:Header/>
<soapenv:Body>
<ns:updateLine sequence="?">
<!--You have a CHOICE of the next 2 items at this level-->
<pattern>31726</pattern>
<!--Optional:-->
<autoAnswer>Auto Answer with Speakerphone</autoAnswer>
<!--Optional:-->
</ns:updateLine>
</soapenv:Body>
</soapenv:Envelope>
Lou
06-18-2014 11:41 PM
Hi Lou,
you can using the Howard who provide the AXL Request Info. and also please check the info of "<pattern>" have add
in the CUCM-->Call Routing-->Directory Number; and then check the whether you should add the tag of "<routePartitionName>" in your request.
the following is my coding of updateline:
<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:ns=\"http://www.cisco.com/AXL/API/8.0\">
<soapenv:Header/>
<soapenv:Body>
<ns:updateLine sequence=\"?\">
<pattern>" + phoneNum + "</pattern>
<routePartitionName>" + pattern + "</routePartitionName>
<callForwardAll>
<destination>" + forwardNum + "</destination>
</callForwardAll>
</ns:updateLine>
</soapenv:Body>
</soapenv:Envelope>
06-19-2014 09:01 AM
Thanks a lot Chao Guo. I will try this out.
What's the pattern for in routePartitionName? Is it just the partition name for the extension number?
06-19-2014 06:49 PM
Hi Lou,
Then following is the code that I get the routePartitionName.
<soapenv:Envelope xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:ns=\"http://www.cisco.com/AXL/API/8.0\">
<soapenv:Header/>
<soapenv:Body>
<ns:listLine sequence=\"?\">
<searchCriteria><pattern>" + phoneNum + "</pattern></searchCriteria>
<returnedTags>
<routePartitionName/>
</returnedTags>
</ns:listLine>
</soapenv:Body>
</soapenv:Envelope>
06-25-2014 02:47 AM
你是中国的不?你们俩都是中国的不?对话不能用中文啊
06-25-2014 02:48 AM
Are you Chiners?Why you have to talk in english?
06-19-2014 12:45 PM
Chao Guo,
I tried yours but still no luck. The directory number is configured in CallManager like you mentioned above. From the example given by Cisco, I don't have to put routePartitionName there. It's pretty odd, This should be very basic function which should work. Scratching my head now.
Lou.
06-19-2015 12:19 PM
Howard,
I am new to this AXL forum and not totally sure where to start, but I have a request from a user to try to automate a query for the current call forward information for a specific line. Following your reply post, it appears that I could do this with some AXL code, but I'm also not sure if there's a way to dump the Call Forward destination to a file for an end user's retrieval. Any help would be greatly appreciated. We are currently running CUCM 9.1(2).
Thanks in advance for your reply.
Arras
06-19-2015 01:10 PM
Yes, you'd do it with the AXL getLine API.
How you dump it to a file depends on the language or product you use to run the AXL command. Saving the results to a file doesn't have anything to do with AXL. You can write a program in PHP or Java or Python or C# or some other language that gets the results and saves them to a file. Or you could use SoapUI (SoapUI - The Home of Functional Testing) and just copy and paste the results from the results window.
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