...
- From the WebUI, access the Monitor tab.
- View the channels used for PSTN connection to the Emergency call route (for both Analog and Digital routes).
- If the channels show in Alerting state but the other side answered the call, the emergency call was not connected. See Step c.
- If the channels show in normal state, and the emergency call connected, no other configuration is required.
- Configure the SBC for Emergency Services.
Panel |
---|
|
| through | Image Modified |
|
Verify through Logs
Note |
---|
This example applies to Sonus 2000 system logs; the same process applies to obtaining Sonus 1000 system logs. |
- From the WebUI, access Logs. See Working with Logging.
- Ensure the log level is set to Trace (see Managing Subsystems Logging).
- For CAS: Set to CAS TRACE level.
- For ISDN: Set to ISDN TRACE level.
- View the logs. The connect message data (noted in the red lines below) should be present in the logs for 911 calls. These messages indicate the PSTN is sending the connect message to the SBC. If these lines are not present, you must configure the SBC for emergency services.
- Configure the SBC for Emergency Services.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Verify Connect Message through Logs - For SBC 2000 |
---|
| This example is a Trace Level System log, which applies to Sonus SBC 2000 with CAS E&M Signaling. Image Modified |
|
Configure the SBC for Emergency Services
...
- Access Settings> Telephone Mappings Table.
- Create and configure a Message Translation table (i.e., Alerting to Connect). See Creating and Modifying Entries to Message Translation Tables).
- Configure Message Type as Alerting/180 Ringing.
- Apply changes.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Configre Message Mapping for CAS Calls |
---|
| Image Modified |
|
For ISDN calls
- Access Settings> Telephone Mappings Table.
- Create and configure a Message Translation table (i.e. Proceeding to Connect). See Creating and Modifying Entries to Message Translation Tables.
- Configure Message Type as Proceeding (ISDN only).
- Apply changes.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Configure Message Mapping for ISDN Calls |
---|
| Image Added |
|
...
Step 2: Create Transformation Table
...
- Access Settings> Transformation.
- Create a call Transformation Table for 911 calls (i.e., LyncToT1-911). See Creating and Modifying Entries to Transformation Tables.
- Configure per parameters below.
- Apply changes.
...
|
Caption |
---|
0 | Figure |
---|
1 | Create Transformation Table for 911 Calls |
---|
| Image Modified |
|
For all Other Call Destinations
...
- Access Settings> Transformation.
- Create a call Transformation Table for all other call destinations except 911 (i.e., Lync to T1). See Creating and Modifying Entries to Transformation Tables).
- Configure per parameters below.
- Apply changes.
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Create Transformation Table for Other Call Destinations |
---|
| Image Modified |
|
Step 3: Add Transformation Table to the Call Route Table
...
- Access Settings > Call Routing Table.
- Create a Call Route for 911 calls (i.e., Emergency Calls)
- Select the Number/Name Transformation Table that includes 911 specifications (i.e, LyncToT1-911 calls).
- (For CAS only) Select the Message Translation table that includes Alerting/180 Ringing (i.e., Alerting To Connect).
- (For ISDN calls only) Select the Message Translation table that includes Proceeding (ISDN only) (i.e., Proceeding To Connect).
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Add Transformation to Call Route Table for 911 Calls |
---|
| Image Modified |
|
For all other IP calls
Add a Transformation table (LyncToT1) to the Routing table used for routing IP calls to the T1 carrier.
- Access Settings > Call Routing Table.
- Create a Call Route for all IP calls (not 911).
- Select the Number/Name Transformation Table created for all IP calls (i.e, LyncToT1 calls).
Panel |
---|
|
Caption |
---|
0 | Figure |
---|
1 | Add to Transformation for |
---|
|
| all other | Image Modified |
|