This article describes the steps necessary to configure the SBC Edge so that a call may be placed from a SIP phone through the SBC Edge to an ISDN endpoint as depicted by the following call flow:
Topology |
---|
On this page: |
---|
Add two entries to the new Transformation Table configured as follows:
Transformation Table Configuration
Input Field Type | Input field Value | Output Field Type | Output Field Value | Match Type | Description |
---|---|---|---|---|---|
Called Address Number | .*6(\d{3})$ | Called Address/Number | 6/1 | Mandatory | LyncSetup: Full Number |
Calling Address Number | (.*) | Calling Address/Number | \1 | Mandatory | LyncSetup: Full Number |
Add an entry to the new Call Routing Table and configure with the values below; keep the fields not listed as the default values.
Call Routing Table Configuration
Field | Value |
---|---|
Number/Name Translation Table | Select appropriate Translation Table (i.e., Calls to ISDN phones) |
Destination Signaling Group | Select appropriate Signaling Group (i.e., ISDN:Lync Setup) |
Add a new SIP Signaling Group and configure it with the values below; keep the fields not listed as the default values.
Call Routing Table Configuration
Field | Value |
---|---|
SIP Mode | Local Registrar |
Registrar | SIP Phones |
Configure the port with the values listed below; keep the keep the fields not listed as the default values.
Call Routing Table Configuration
Field | Value |
---|---|
Port Alias | Specifies an alias for the port (i.e., T1 to Meridian) |
Description | Specifies the description (i.e., T1 to Meridian) |
Configure the new ISDN Signaling Group with the values listed below; keep the fields not listed as the default values.
Call Routing Table Configuration
Field | Value |
---|---|
Description | Description of Signaling Group |
Switch Variant | QSIG |
Tone Table | Default Tone Table |
Call Routing Table | Select appropriate Call Routing Table |
When the endpoint registers, the registration request arrives to the SBC Edge through the SIP signaling group, the SBC Edge responds to the REGISTRATION request with a 200 OK – a successful SIP endpoint registration occurs.
Using the Log Exchange utility, you can quickly verify the relevant SIP messaging:
Verify SIP Messaging