In this section:

How Call Routing Works

In the SBC Edge Portfolio (SBC), all call routing occurs between Signaling Groups.

Signaling Groups are the logical representations of call-handling systems such as private branch extensions (PBX), Microsoft Lync 2010/2013 Servers, fax machines and analog phones.

In order to route any call to or from a call system connected to SBC, you must first configure a Signaling Group to represent that device or system. The following list illustrates the hierarchical relationships of the various Telephony routing components of a SBC call system:

Signaling Group — describes the source call and points to a routing definition known as a Call Route Table
  → Call Route Table — contains one or more Call Route Entries
         → Call Route Entries → points to the destination Signaling Group(s)

Each call routing entry describes how the call should be routed and also points to a Transformation Table which defines the conversion of names, numbers and other fields when routing a call.

Logic Path

The diagram below illustrates possible paths of a call from an external call from a ISDN PRI service line connected to the SBC system to an internal Lync 2010 server or analog phone or fax devices connected to a Tenor Analog device.


Logic Path


SBC Call Logic Steps

  1. An outside call comes through the ISDN PRI line connected to the SBC system and is routed to the ISDN Signaling Group.

  2. In order to route the call, the SBC ISDN Signaling Group system engages the Call Route Table attached to it.

  3. SBC processes the Call Route Table entries and their attached Transformation Table entries, looking for a match to the called number.
    1. SBC finds a match for a 4xxx local extension managed by a Lync 2010 Server.
    2. SBC finds a match for a x2001 or x2002 local extension analog device, managed by a Tenor Analog system.

  4. SBC routes the call to the appropriate Signaling Group and the receiving system processes the call.


Related topics: