Voice gateway, activation and deployment

Preserve the no-PSTN boundary

Do not add carrier trunks, public telephone numbers or external outbound routes.

Audience: CRM administrators, staff callers, customer contacts, voice-platform engineers and website operatorsPermission: Root/voice-platform administratorModule v1.1.3
Exact navigationServer administration → supplied xConnect deployment runbook
Before you begin
  • Confirm the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What this guide covers

Do not add carrier trunks, public telephone numbers or external outbound routes. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Server administration → supplied xConnect deployment runbook.
  2. Locate the record, setting or action used to preserve the no-pstn boundary.
  3. Complete the displayed fields or controls exactly as described in this guide.
  4. Select the available save, submit, update, call, sign, upload or confirm action.
  5. Return to the related register, portal, dashboard or call panel and verify the recorded result.

Fields, choices and supported possibilities

Deployment actionDo not add carrier trunks, public telephone numbers or external outbound routes.

Code-backed validations and workflow rules

  • Use read-only audit first, module-owned paths, same-operation rollback and live verification.
  • Do not change unrelated voice services or enable PSTN.

Expected result and verification

  • The preserve the no-pstn boundary workflow completes without a validation, permission or availability error.
  • The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
  • Any client-visible or public result appears only where the code explicitly allows it.

Security, privacy and operational checks

  • Use a controlled test case, contact, extension or website origin before production rollout.
  • Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.