cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
900
Views
0
Helpful
2
Replies

EndCall Failed

filipe.paredes
Level 1
Level 1

Hi all,


When i use the webdialer service to make a call with a certain user that is logged in on his phone, it works ok. But the EndCall (endCallSoap method) returns an error:


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

<!--
@namespace html url(http://www.w3.org/1999/xhtml); :root { font:small Verdana; font-weight: bold; padding: 2em; padding-left:4em; } * { display: block; padding-left: 2em; } html|style { display: none; } html|span, html|a { display: inline; padding: 0; font-weight: normal; text-decoration: none; } html|span.block { display: block; } *[html|hidden], span.block[html|hidden] { display: none; } .expand { display: block; } .expand:before { content: '+'; color: red; position: absolute; left: -1em; } .collapse { display: block; } .collapse:before { content: '-'; color: red; position: absolute; left:-1em; }
--><NBCallResponse xmlns="http://bcpcorp.net/webservices/webdialerservice/2008/08"xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><a><ResponseCode></a>1</ResponseCode><a><ResponseDescription></a>EndCall Failed</ResponseDescription></NBCallResponse>

I dont understand what the problem is, since the makeCall works fine.

Thanks

1 Accepted Solution

Accepted Solutions

bvanturn
Cisco Employee
Cisco Employee

That does not sound like a known issue. You should check the server side WebDialer logs, CTIManager logs and CallManager logs to understand better why this is failinging in this scenario.

View solution in original post

2 Replies 2

bvanturn
Cisco Employee
Cisco Employee

That does not sound like a known issue. You should check the server side WebDialer logs, CTIManager logs and CallManager logs to understand better why this is failinging in this scenario.

Unfortunately i can't access the logs of the CUCM where the WebDialer problem is happening. But i figured it out.

The problem were 2 mistakes of my part:

The 1st was that i tested the endcall for the wrong device and because no call was active in that device, the endcall returned that error.

The 2nd was that i tested it for 2 diferent clients were one was using the CUCM 7 and the other the CUCM 8. In the CUCM 7, request the endcall to a phone that has no active call, it replies sucess, but in the CUCM 8 it replies that error. I'm assuming that in CUCM 8 the behavior is different. But the endcall replies sucess if a call is active on the phone