McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 329

↗ View in doc context
page
329
source
cucm/v15/feature-config-guide/feature-config-guide.md
chunk_id
cucm::v15::feature-config-guide::feature-config-guide::279

Interaction Feature Web Dialer supports CMCs and FACs in the following ways: • A user can enter the destination number in the dial text box of the WD HTML page or SOAP request, and then manually enter the CMC or FAC on the phone. • A user can enter the destination number followed by the FAC or CMC in the dial text box of the WD HTML page or SOAP request. For example, if the destination number is 5555, the FAC is 111, and the CMC is 222, a user can make a call by dialing 5555111# (FAC), 5555222# (CMC), or 5555111222# (CMC and FAC). Note • WebDialer does not handle any validation for the destination number. The phone handles the required validation. • If a user does not provide a code or provides the wrong code, the call will fail. • If a user makes a call from the WebApp with a DN that contains special characters, the call goes successfully after stripping the special characters. The same rules do not work in SOAP UI. Client Matter Codes and Forced Authorization Codes WebDialer Restrictions Restrictions Feature Cisco WebDialer supports phones that run Skinny Client Control Protocol (SCCP) and Session Initiation Protocol (SIP) that Cisco Computer Telephony Integration (CTI) supports. Note Few older phone models do not support Cisco Web Dialer that run SIP. Phones WebDialer Troubleshooting Authentication Error Problem Cisco WebDialer displays the following message: Authentication failed, please try again. Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 287 Placing Calls WebDialer Restrictions