cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
781
Views
5
Helpful
1
Replies
George Paxson
Beginner

AXL SOAP API call forward all fails on CUCM 11.5

I have an existing Python script to change call forward all destination that was reliable on a prior CUCM version but is unreliable on CUCM 11.5. The number appears updated in the GUI but the calls fail as if the number is undefined. Toggling the call forward all to voicemail on and off restores the CTI route point function. I see no issue with script. The problem is 50/50 whether it works or not.

xmlTemplate = """<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:axl="http://www.cisco.com/AXL/API/11.5"><soapenv:Header/><soapenv:Body><axl:updateLine><pattern>%(dirn)s</pattern><callForwardAll><destination>%(dest)s</destination></callForwardAll></axl:updateLine></soapenv:Body></soapenv:Envelope>"""

1 REPLY 1
George Paxson
Beginner

I have determined that Python is malforming the XML with DOS format inputs.  The problem only appears in the XML output and not by comparing variables inputs.

The script functions enough to display the destination number in the GUI, but is not sane.

Direct command line input to the Python script does not cause the issue.

The forward list is created by other people if someone wants to know why a DOS text file is used for input.  We will convert the file to Unix before running the script.  We have also recently migrated to an E.164 dial plan introducing '\' to directory numbers which may contribute to the problem.

Confusing problem as the script did not outright fail with bad input.

Issue is resolved.

Content for Community-Ad

Spotlight Awards 2021