RE: PIN authentication

RE: using web dialer with windows authentication

2012-06-15T23:17:35Z

Yes, for example via the HTTP interface, you would use the makeCallProxy request, for the SOAP API, use makeCallSoap using the credentials of a webdialer proxy user: [url=http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/webdialer/1_0_3/wbdladm.html#wp1042731]http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/webdialer/1_0_3/wbdladm.html#wp1042731[/url]

RE: WebDialer Video Endpints supported

2012-01-21T00:24:35Z

WebDialer uses UCM CTI primitives to do its thing, so the supported list of devices for CTI should match: http://developer.cisco.com/web/jtapi/wikidocs/-/wiki/Main/Cisco+CTI+Supported+Device+Matrix As you mention, those devices do not appear to be supported

RE: PIN authentication

2010-04-28T21:39:04Z

Not sure why WebDialer does not accept the PIN, though I believe this is consistent with other UCM APIs - AXL, CTI, etc. Can't think of any UCM app or API that accepts PIN, other than Extension Mobility, where it was implemented due to limited input capability at the phone. One rationalization would be that the password is more secure than the PIN, and since Webdialer use case is on the PC, where the user has access to a keyboard, password was used. I have numerous applications on my desktop that have saved my AD password - for example IM client, email client, etc. - so I don't think it's unreasonable for an app to store it if it's properly encrypted. However security policies vary, and I do see where it could be helpful to have a security level above 'none' (use a global proxy user) and below 'best' (require AD password.)

RE: PIN authentication

2010-04-27T22:18:16Z

WebDialer allows to use a 'master' set of credentials to make calls 'on behalf of' end user phones. To do this, create a new UCM application user, with group 'Standard EM Authentication Proxy Rights', and use this user as the credentials in In this way your app can make calls on behalf of users without requiring any authentication from them, if you wish. If you still need to validate their UCM PIN, you can use the AXL SOAP API to do so, before making the request.

RE: Proxy User and Extension Mobility

2010-04-14T11:34:54Z

This is a known issue, some enhancements are needed for WebDialer to robustly support extension mobility users.

RE: WebDialer over HTTP : Pause dial modifier for phone extension

2010-03-18T23:17:29Z

AFAIK the destination is dialed 'en-bloc' and adding delay+post-dial digits wouldn't make any sense. You may want to look into performing the dialing via the IP Phone Services XML interface (see the latest guide for updates to the 'Dial' URI which supports pause/delay character.) For complete control of calls/dialing including post-dial digits/DTMF, see one of the CTI interfaces - TAPI/JTAPI.

RE: getProfileSoap - what's the point?

2010-03-02T01:09:04Z

What version of UCM are you testing with? Can you describe in a little detail the sequence of events/observations? The intention of getDeviceProfile would be to give you a list of possible originators for the Webdialer makecall - AFAIK this should be interacting with E/M, but I would like to try your scenario.

RE: What's wrong with this isClusterUserSoap message?

2010-02-26T01:08:15Z

Side note, I use soapUI a lot to test web services - that's where I got the raw HTTP request info. Other developers use Fiddler (freeware Windows) or Charles (trialware java) to debug raw HTTPS traffic - these tools are setup as 'man in the middle' proxies, useful when using opaque clients like .NET.

RE: What's wrong with this isClusterUserSoap message?

2010-02-26T01:04:17Z

The port is missing from the request URL: 8443, though I doubt that is it. Looking closer at your request, it looks like "urn:isClusterUserSoap" is added as a _SOAP_ header, not an _HTTP_ header (see my previous raw HTTP request.) Trying your version just now I also get a HTTP 500 response - so I think that's the culprit.

RE: What's wrong with this isClusterUserSoap message?

2010-02-25T22:33:37Z

Just checking - is the Webdialer service activated/running? Are you posting to the right URL? [b]https://10.88.131.133/webdialer/services/WebdialerSoapService70 or [/b] [b]https://10.88.131.133/webdialer/services/WebdialerSoapService[/b] HTTP headers good? [b]POST https://10.88.131.133/webdialer/services/WebdialerSoapService HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: text/xml;charset=UTF-8 SOAPAction: "" User-Agent: Jakarta Commons-HttpClient/3.1 Host: 10.88.131.133 Content-Length: 513 dstaudt [/b]

RE: Web Dialer URL

2010-02-08T22:16:24Z

That should be the correct URL (assuming you are using UCM 7.0 or higher). You might check that the Webdialer service is activated/running, though I believe the error you see is not due to that. Can you provide the actual XML of your request? Might use attachment as sometimes the forum

RE: Web Dialer Window Keeps Resizing

2009-11-12T00:10:24Z

Is the browser used one supported by the WebDialer feature? What OS/browser/version do you see the problem on? Have you tried other browsers?

RE: SOAP WSDL Device Name / ID

2009-10-21T18:41:07Z

Yes, that will work fine.

RE: SOAP WSDL Device Name / ID

2009-10-21T07:39:37Z

getProfileSoap should be the request you want to use. You can create a UCM Application User with 'Standard EM Authentication Proxy Rights' which can be used to query the profile of any UCM user. Note the following is using the wd70.wsdl at https:///webdialer/wsdl/wd70.wsdl Sample request: [b][/b] [b] [/b] [b] [/b] [b] [/b] [b] [/b] [b] webDialerProxyUser[/b] [b] password[/b] [b] [/b] [b] testUser[/b] [b] [/b] [b] [/b] [b][/b] and response: [b][/b] [b] [/b] [b] [/b] [b] [/b] [b] [/b] [b] [/b] [b] Success[/b] [b] [/b] [b] [/b] [b] [/b] [b] [/b] [b] [/b] [b] 0[/b] [b] [/b] [b] SEP00070EB9C4B4[/b] [b] [/b] [b] 1000 ; no partition[/b] [b] 2000 ; no partition[/b] [b] [/b] [b] [/b] [b] [/b] [b][/b]

RE: Error when using getProfileSoap

2009-09-24T04:16:17Z

I believe this issue has to do with the XML response generated by UCM (using Java Axis WSDL generated code), and the .NET WSDL generated code you are using - the .NET code is not able to handle the 'multiref' structures. This article has a detailed discussion: http://www.ibm.com/developerworks/webservices/library/ws-tip-j2eenet1/ Workaround would be to 'manually' use XML DOM to walk the XML response object.

RE: Re: How do I get WebDialer

2009-07-07T20:07:21Z

The CUAE Tech Center is here: http://developer.cisco.com/web/cuae/home. There is quite a bit of documentation and several samples available to get you started. Note this product requires a separate CUAE server to run the app on, though you can download the software and get started on a commodity PC for free. If that's too much complexity, you can also accomplish what you want here via TAPI (Windows) or JTAPI (Java) call control APIs.

RE: Re: How do I get WebDialer

2009-07-06T22:58:20Z

WebDialer uses UCM's CTI interface to effect the outdial, taking control of the calling device and initiating a call request. In your situation, it _may_ be possible in that: - CTI does support control of analog devices on VG248 gateways (not VG224s, though) - The analog device/port must be associated to your UCM user account in the standard fashion - The analog device must already be off-hook when the WebDialer request is made If, as I suspect, you just want 2 numbers connected, regardless of where/what they may be (for example they could be across a trunk,) then WebDialer is probably not going to suffice. You could implement something like that fairly easily via the CUAE, having it outdial each of the two phones, and then connecting them together.

RE: Web Dialer - Failed to open device/line

2009-07-06T22:46:27Z

When the WebDialer dialogs come up, which device are you selecting to make the call from? Make sure the extension mobility profile is the one selected.

RE: proxy user

2009-06-03T22:39:51Z

My understanding is that WebDialer can place a call for a phone based on: - Credentials supplied are those of the user associated to the phone - Credentials supplied have been given 'Standard EM Authentication Proxy Rights' The latter is able to use WebDialer to place calls for any phone - i.e. on-behalf-of/proxy http://www.ciscosystems.or.at/en/US/docs/voice_ip_comm/cucmbe/admin/6_0_1/ccmfeat/fswbdlr.html#wp1050037

RE: PIN authentication

2009-04-03T21:54:14Z

The SOAP make call request does require the user's password (and not pin) by design. Have you investigated the webdialer proxy user functionality? Using this you would be able to either make the call without user input via the proxy user, or validate the user pin via your app (using AXL doAuthenticateUser request) then place the call on their behalf using the proxy user.