Skip to main content

Outbound Whitelist

The Outbound Whitelist feature controls which outbound calls are permitted from your organization. This provides security by restricting calls to approved destinations only.

Overview​

Outbound Whitelist:

  • Restricts outbound calls to approved destinations
  • Routes calls through specific Cloudonix trunks
  • Defines allowed countries and area codes
  • Enforces least-privilege calling permissions
note

This feature is available to Owner role only.

warning

When the outbound whitelist is enabled, all outbound calls are rejected by default. Only destinations matching whitelist entries are allowed.

Prerequisites​

Before using Outbound Whitelist:

  1. Configure Cloudonix integration in Settings
  2. Ensure outbound trunks are available from Cloudonix

Creating a Whitelist Entry​

Step 1: Add New Entry​

  1. Navigate to Outbound Whitelist in the sidebar
  2. Click New Whitelist Entry

Step 2: Configure Entry​

Name

  • Enter a descriptive name (e.g., "US Domestic", "Emergency Numbers")

Country

  • Select the destination country from the dropdown
  • Shows country name with calling code (e.g., 🇺🇸 [+1] United States)

Additional Prefix (Optional)

  • Enter area code or prefix without country code
  • Example: 972 for Dallas, 212 for New York
  • Combined with country to create full prefix

Voice Trunk

  • Select the Cloudonix trunk for routing calls
  • Trunks are fetched from your Cloudonix configuration
  • Required for call routing

Step 3: Save​

Click Create to add the whitelist entry.

How It Works​

Call Flow​

  1. User attempts outbound call
  2. System strips country code from destination
  3. System checks if destination matches any whitelist entry
  4. If match found: Call proceeds using specified trunk
  5. If no match: Call is rejected

Matching Logic​

  • Country code is matched first
  • If additional prefix is configured, it must also match
  • Multiple entries can exist for the same country with different prefixes

Managing Whitelist Entries​

Viewing Entries​

The whitelist page shows:

  • Name - Entry identifier
  • Country - Destination country
  • Prefix - Additional prefix if configured
  • Trunk - Cloudonix trunk for routing
  • Status - Active or Inactive

Activating/Deactivating​

Toggle the status switch to enable or disable an entry without deleting it.

Editing​

  1. Find the entry in the list
  2. Click Edit
  3. Modify fields as needed
  4. Click Update

Deleting​

  1. Find the entry
  2. Click Delete
  3. Confirm deletion

Common Configurations​

Allow US Domestic Calls​

  • Country: United States (+1)
  • Prefix: (leave empty)
  • Trunk: Select US trunk

Allow Specific Area Code​

  • Country: United States (+1)
  • Prefix: 972 (Dallas area code)
  • Trunk: Select US trunk

Allow International Destination​

  • Country: United Kingdom (+44)
  • Prefix: (leave empty or specify area)
  • Trunk: Select international trunk

Troubleshooting​

Outbound Calls Rejected​

  • Verify a whitelist entry exists for the destination country
  • Check if additional prefix matches (if configured)
  • Ensure the entry is Active
  • Verify trunk is selected and available

No Trunks Available​

  • Check Cloudonix integration in Settings
  • Verify Cloudonix account has outbound trunks configured
  • Click Refresh to fetch latest trunks

Cannot Create Entry​

  • Verify you have Owner role (not PBX Admin)
  • Ensure Cloudonix is configured
  • Check that trunks are available

Calls Not Routing Correctly​

  • Verify correct trunk is selected
  • Check Cloudonix trunk configuration
  • Review call logs for routing errors

Best Practices​

Security​

  • Start with minimal whitelist and expand as needed
  • Use specific prefixes instead of broad country access
  • Regularly review whitelist entries

Organization​

  • Use descriptive names (e.g., "US-SF-Office" not "Entry1")
  • Group similar destinations together
  • Document business justification for each entry

Maintenance​

  • Review whitelist quarterly
  • Remove unused entries
  • Update trunks when Cloudonix configuration changes

Related Documentation: