cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
127
Views
0
Helpful
0
Replies
Highlighted

makeCallSoap return different response is CUCM Cluster

Hi,

Our customer's developer team has developed an application which request to Cisco WebDialer in order to trigger the phone to call out using makeCallSoap.

They found that when they request to Node 2 the response's format looks like:

<?xml version=\"1.0\" encoding=\"UTF-8\"?>

<soapenv:Envelope

       xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\"

       xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"

       xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">

       <soapenv:Body>

              <ns1:makeCallSoapResponse soapenv:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"

                     xmlns:ns1=\"urn:WD70\">

                     <return href=\"#id0\"/>

              </ns1:makeCallSoapResponse>

              <multiRef id=\"id0\" soapenc:root=\"0\" soapenv:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\" xsi:type=\"ns2:CallResponse\"

                     xmlns:soapenc=\"http://schemas.xmlsoap.org/soap/encoding/\"

                     xmlns:ns2=\"urn:WebdialerSoap\">

                     <responseCode href=\"#id1\"/>

                     <responseDescription xsi:type=\"xsd:string\">Success</responseDescription>

              </multiRef>

              <multiRef id=\"id1\" soapenc:root=\"0\" soapenv:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\" xsi:type=\"xsd:int\"

                     xmlns:soapenc=\"http://schemas.xmlsoap.org/soap/encoding/\">0

              </multiRef>

       </soapenv:Body>

</soapenv:Envelope>

One day, many months passed, the response's format was changed to:

<?xml version=\"1.0\" encoding=\"UTF-8\"?>

<soapenv:Envelope

        xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\"

        xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\"

        xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">

        <soapenv:Body>

                <ns1:makeCallSoapResponse soapenv:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\"

                       xmlns:ns1=\"urn:WD70\">

                       <return href=\"#id0\"/>

                </ns1:makeCallSoapResponse>

                <multiRef id=\"id0\" soapenc:root=\"0\" soapenv:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\" xsi:type=\"ns2:CallResponse\"

                        xmlns:soapenc=\"http://schemas.xmlsoap.org/soap/encoding/\"

                       xmlns:ns2=\"urn:WebdialerSoap\">

                       <responseCode xsi:type=\"xsd:int\">0</responseCode>

                       <responseDescription xsi:type=\"xsd:string\">Success</responseDescription>

                </multiRef>

        </soapenv:Body>

</soapenv:Envelope>

The different part is in the red color format. Then they test requesting to Node 1 and found that the response is in the first format which means the response format between Node1 and Node2 is different.

Our customer informed us they unable to capture the response if it was changed. And our customer has questions:

- Why the response's format has been changed?

- Why response's format between Node1 and Node2 is different?

Our implementation team told us there was no upgrade, configuration or reboot on CUCM.

Thanks,

Rasik

This widget could not be displayed.