Skip to content

Instantly share code, notes, and snippets.

@ctaloi
Created May 19, 2016 15:11
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ctaloi/23ce7ca69846593c150708a57700b168 to your computer and use it in GitHub Desktop.
Save ctaloi/23ce7ca69846593c150708a57700b168 to your computer and use it in GitHub Desktop.
WCS Routes Guide

WCS Routes - Internal Documentation /rev 002 2015-12-11 16:36:12


WCS Routes

Terms

ICR (Intelligent Call Router)
Customer facing application designed to facilitate advanced call flows, reporting and monitoring. The ICR application architecture is a custom application built on top of the hardened WCS network.

  • ICR Components
    • Customer facing web portal (web servers)
    • Backend SIP application servers
    • Backend DB application servers
    • Sonus SIP trunking for telephony connectivity

Translation A translation occurs when one telephone number (toll free or 1+) is converted to another. This could be a toll free number translated to a "ring to DID" or a standard domestic number translated to another domestic number.

Trunkgroup
A trunkgroup is an endpoint or the connection to a peer. Customers and carriers connect to our telephony network using a trunkgroup. The connection medium can be a physical TDM trunk or a virtual SIP connection. Using the ICR we are able to route calls to customer trunkgroup using the DTG parameter tagged on a SIP call.

Gateway
Physical telephony element to which a trunkgroup is bound.

Route Label Collection of provisioned routes.

Route A route or "routing label route" is the combination of a gateway and trunkgroup and the selected path a call takes to reach it's destination.

Trunkgroup Routing A customer with WCS trunking (SIP or TDM) may have one or many trunkgroups; each trunkgroup has a unique trunkgroup ID. This ID is specific to the customer account and is provided by WCS Engineering at the point of inception. The trunkgroup ID is the binding point between the ICR call processing node and the Sonus trunkgroup. The trunkgroup ID is necessary when the WCS operator provisions the customer account in the ICR.

trunkgroup routing call flow

Translation Routing
Translation based routing does not require a physical or virtual connection to the customer. The WCS operator will provision numbers for the WCS customer to configure using the ICR.

translations

Provisioning

Internal CMS Process

XXX [INSERT INTERNAL CMS PROCESS]

ICR Process

Accounts on the WCS ICR can use trunkgroup based routing, translation based routing, or a combination of both.

The following screencasts and screenshots show the necessary steps to provision a customer on the ICR.
The following data is necessary prior to account creation:

  • Customer name
  • Customer email
  • Customer company name
  • Customer number(s)
  • Customer contact number
  • If the account is a trunking account, the trunkgroup ID
  • Numbers to load for the customer

Adding customer, trunkgroups and numbers consists of populating forms with acquisition data above.

Adding a customer

Adding a trunkgroup

Adding numbers

Numbers can be loaded one at a time

Or as a bulk upload where the upload file contains one ten digit telephone number per line.

Screenshots


adding customer


new trunkgroup


new single number


bulk upload


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment