Setting up outgoing calling permissions in Webex Calling

Do

Navigate to Management > Locations, select the location, and open Calling > Call Handling > Outgoing Call Permissions 31. Review the call types listed: Internal, Toll Free, National, International, Operator Assistance, Chargeable Directory Assistance, Special Services I and II, and Premium Services I and II 15. Note that Cisco Calling Plan is Cisco's bundled PSTN solution 40. During a Cisco Calling Plan trial, International and Premium Services I and II call types are blocked 41, and calls to X11 services other than 911 are unsupported 42.

Verify

Confirm that the Outgoing Call Permissions page is visible and lists the current action for each call type 31​15.

Do

Record the current action, the Allow transfer/forwards status, any active digit patterns, authorization codes, and auto-transfer numbers for the location 31​52. For any user or workspace you plan to evaluate, navigate to Management > Users (or Workspaces), select the entity, and open Calling > Call Handling > Outgoing Call Permissions to note whether it uses Location Settings or Custom Settings 46​47. To capture an audit baseline, open Management > Security > Audit on the Admin activities tab, filter by category and audit cluster, and export the recent activity to CSV (up to 20,000 events per report) 3​2.

Verify

Suggested check: verify you have documented every active action, transfer setting, code, and pattern across the location and individual entities.

Block restricted calls outright

Do

No auto-transfer numbers are required when restricted call types are set to Block 1.

Verify

Suggested check: verify that no unnecessary auto-transfer destinations are assigned on the page.

Require an authorization code

Do

No auto-transfer numbers are required when restricted call types require an authorization code 1.

Verify

Suggested check: verify that no unnecessary auto-transfer destinations are assigned on the page.

Auto-transfer calls to an assigned number

Do

WarmTransfer's reading of the sources is that auto-transfer numbers should be configured before a call type or digit pattern is set to Auto-transfer 51. On the location's Auto-transfer numbers page, enter transfer numbers 1, 2, and 3 (up to 3 numbers total) and click Save 53​54.

Verify

Confirm that the configured numbers appear in the Auto-transfer numbers list 54.

Rollback

On the Auto-transfer numbers page, click the X next to each number and confirm Delete 54.

Block restricted calls outright

Do

No authorization codes are required when restricted call types are set to Block 1.

Verify

Suggested check: verify that no unneeded authorization codes remain active on the location.

Require an authorization code

Do

WarmTransfer's reading of the sources is that authorization codes should be configured before any call type is set to Require Authorization Code 8. Under the location's Authorization Codes page, click Add code, enter a description and the code, and click Add 6. You can configure up to 1,000 codes per location 12. For bulk management, upload a CSV with at most 1,000 codes per file and an Action column set to ADD, REPLACE, or REMOVE 7.

Verify

Confirm that the added codes appear in the Authorization Codes list 6.

Rollback

Select individual codes and click Delete, or click Delete All to clear all location codes 6. Alternatively, upload a CSV with the Action column set to REMOVE 7.

Auto-transfer calls to an assigned number

Do

No authorization codes are required when restricted call types are set to Auto-transfer 1.

Verify

Suggested check: verify that no unneeded authorization codes remain active on the location.

Block restricted calls outright

Do

In the location's Outgoing Call Permissions page under Permissions by call type, set International, Premium Services I and II, and any other restricted types to Block 1. International calls are calls outside the country requiring an international calling code 30, while Premium Services calls provide information or entertainment for a fee charged directly to the caller 43. Set standard business calls such as Internal (calls within the company) and National (calls within the country) to Allow 29​32. Click Save 1.

Verify

Confirm that the page displays Block next to each restricted call type and Allow next to permitted types 1.

Rollback

Suggested rollback: change each modified call type back to its baseline setting recorded in Step 2 and save.

Require an authorization code

Do

In the location's Outgoing Call Permissions page under Permissions by call type, set International, Premium Services I and II, and any other restricted types to Require Authorization Code 1. International calls are calls outside the country requiring an international calling code 30, and Premium Services calls charge a caller fee for information or entertainment 43. Set Internal and National calls to Allow 29​32. Click Save 1.

Verify

Confirm that the page displays Require Authorization Code next to each restricted call type 1.

Rollback

Suggested rollback: change each modified call type back to its baseline setting recorded in Step 2 and save.

Auto-transfer calls to an assigned number

Do

In the location's Outgoing Call Permissions page under Permissions by call type, set International, Premium Services I and II, and any other restricted types to Auto-transfer to number 1, 2, or 3 1. International calls are calls outside the country requiring an international calling code 30, and Premium Services calls provide information or entertainment charged directly to the caller 43. Set Internal and National calls to Allow 29​32. Click Save 1.

Verify

Confirm that the page displays the assigned Auto-transfer slot next to each restricted call type 1.

Rollback

Suggested rollback: change each modified call type back to its baseline setting recorded in Step 2 and save.

Do

For each call type, configure the Allow transfer/forwards setting, which determines whether that specific outgoing call type may be transferred or forwarded 52. Note that Chargeable Directory Assistance covers directory assistance companies that charge for calls, and Special Services I and II cover carrier-specific special destination numbers 27​44. Save your changes 1.

Verify

Confirm that the transfer/forward toggle displays the expected state for each call type 52.

Rollback

Suggested rollback: restore the toggle states for each call type according to your baseline record.

Use call types only

Do

Permissions by digit pattern take precedence over permissions by call type 39. Review the Permissions by digit pattern section under the location's outgoing call permissions to confirm no conflicting digit patterns remain active from previous configurations 39.

Verify

Confirm that no unwanted patterns appear in the Permissions by digit pattern list 35.

Add digit patterns

Do

Under Permissions by digit pattern, click Add digit pattern 35. Enter a unique Name and a unique Pattern (up to 50 characters each), choose a Permission action, optionally select Allow transfers/forwards, and click Add 35. In pattern syntax, X matches 1 digit, ! matches 1 or more digits and must be the last character, [ ] with - defines a digit range, and + may appear only as the first character 38. You can configure up to 500 digit patterns per location, user, workspace, or virtual line 37. For bulk additions, upload a CSV containing at most 500 patterns per file, up to 25 pattern sets per row, with the Action set to ADD, REPLACE, or REMOVE 34. When a dialed number matches multiple patterns, Webex Calling selects the pattern with the fewest expansions, then applies wildcard precedence (exact digit, then range, then X, then !), then lexicographic order 36. Note that permissions by digit pattern take precedence over permissions by call type 39.

Verify

Confirm that each configured pattern appears in the list with its assigned permission 35.

Rollback

On the Permissions by digit pattern page, select an individual pattern and delete it, click Delete all, or upload a CSV file with the Action column set to REMOVE 35​34.

Apply location default to all entities

Do

Confirm that users and workspaces inherit the location settings by default 47. For any user or workspace, open Management > Users (or Workspaces), select the entity, and navigate to Calling > Call Handling > Outgoing Call Permissions 46. Ensure the setting is toggled to Location Settings 47.

Verify

Confirm that the entity's Outgoing Call Permissions screen shows Location Settings selected 47.

Rollback

Suggested rollback: if an entity previously required a custom profile, reapply Custom Settings and enter its baseline rules.

Apply custom settings to specific users, workspaces, or virtual lines

Do

To override permissions for a user or workspace, go to Management > Users (or Workspaces), select the target entity, and open Calling > Call Handling > Outgoing Call Permissions 46. For virtual lines, navigate to Services > Calling > Virtual Lines 49. Select Custom Settings, customize permissions by type, auto-transfer numbers, digit patterns, or authorization codes, and click Save 45​47. Each user, workspace, or virtual line supports up to 1,000 authorization codes and up to 500 digit patterns 11​37. Custom digit patterns for an entity are evaluated first, and location settings apply only if none match 26. For virtual lines using Cisco Calling Plan, ensure the Cisco Calling Plan setting is enabled so the line can make outgoing calls 50 (in bulk virtual line CSV uploads, set the Outgoing column to TRUE) 48.

Verify

Confirm that the entity's Outgoing Call Permissions page shows Custom Settings with the specific rules displayed 45​47.

Rollback

In the entity's Outgoing Call Permissions page, select Location Settings and save to return it to inheriting the location default 47.

Block restricted calls outright

Do

From a test phone or endpoint at the location, dial an outgoing destination belonging to a blocked call type (such as an international number) 30. Then place a control call to an allowed national destination 32.

Verify

Confirm that the call to the blocked destination fails and the control call connects 1. Cisco notes that a call type set to Block under outgoing calling permissions is a common cause of call failures 14.

Require an authorization code

Do

From a test endpoint at the location, dial an outgoing destination belonging to a restricted call type 30. When prompted, enter the authorization code followed by the # key 13.

Verify

Confirm that upon entering the valid code, you hear an announcement that the authorization code is accepted and the call rings 5. Suggested check: place a second call, enter an incorrect code, and verify that the call fails to connect.

Auto-transfer calls to an assigned number

Do

From a test endpoint at the location, dial an outgoing destination belonging to an auto-transfer restricted call type 30.

Verify

Confirm that the call redirects immediately to the configured auto-transfer destination number 1​53.

Do

To audit administrative updates, navigate to Management > Security > Audit on the Admin activities tab 3. Filter the log and export entries to CSV (up to 20,000 events per report) 2. Note that admin activity events are retained for 3 years in the India audit cluster and 1 year in other clusters, and search covers only the past year 4. In the Webex Calling Detailed Call History report, Pro Pack provides 400 days of history and Standard provides 89 days, with at most 31 days per report run 22. Each call leg generates originating and terminating rows linked by a Correlation ID 23​20. Report timestamps are in UTC and cannot be converted to other time zones in the report 24. For automated ingestion, the Detailed Call History API returns calls completed between 48 hours ago and 5 minutes ago 18.

Verify

Confirm that your test calls appear in the report under the Call type field, which reports values including SIP_NATIONAL, SIP_INTERNATIONAL, SIP_TOLLFREE, and SIP_PREMIUM 19. For international test calls, verify that the International country field reflects the dialed country 21.