This Best Practice describes how the Sonus SBC 1000/2000 handles incoming calls when the Server is down or unreachable. The Sonus SBC routes the calls according to general configuration guidelines. The information below includes expected behavior for call routing when there is a problem reaching the server (i.e, registration fails, wrong configuration, etc.).

This Best Practice assumes the following:

  • Incoming call is based on Federated IP/Signaling Group listen port/transport protocol.
  • Incoming call is one of the following: ISDN, SIP, or CAS.

Call Survivability when SIP Server is down - How calls are routed with PSTN Backup

A call route to the PSTN must be created in order for calls to be re-routed to the PSTN as a backup mechanism if the SIP Server is unavailable. See Managing SIP Server Tables and Managing Call Routing Tables.

When the SIP server (SIP Signaling Group) is down or unavailable, the call is routed to the PSTN as follows:

Basic Call Mode with Agent Type as "Back-to-Back User Agent" Configuration - How Incoming Calls are handled

Below are the components of a basic configuration

Scenario 1: Registration to server fails; Monitor using SIP Options for the corresponding SIP Server is incorrectly configured.

The Sonus SBC handles the calls as follows:

Scenario 2: Registration to server is not configured; Monitor using SIP Options for SIP Server fail

The Sonus SBC handles the calls as follows:

Scenario 3: Registration to server succeeds; Monitor using SIP options for SIP Server fail

When a very high registration expires (Global Time to Live TTL) interval is configured (configuration available through the Contact Registrant Table), ensure it is sent more frequently. For example, set the registration interval less than the time set for the Registration to expire.

The Sonus SBC handles the calls as follows: 

Scenario 4: Registration to server fails; Monitor using SIP Options for SIP Server are successful

The Sonus SBC handles the calls as follows:

Scenario 5: Both Registration and Monitor using SIP Options for SIP Server fail

The Sonus SBC handles the calls as follows:

Scenario 6: Receiving a 3xx/4xx/5xx/6xx response to Register with a Retry after header

The Sonus SBC handles the calls as follows:

Scenario 7: Receiving final 5xx/6xx (without Retry after header) failure responses to Register

The Sonus SBC handles the calls as follows:

Scenario 8: Receiving 3xx/4xx (without Retry after header) response to Register

The Sonus SBC handles the calls as follows:

Forward Register after Local Processing Mode - How Incoming Calls are handled in the Sonus SBC 1000/2000

Below are the components of a configuration that includes Forward Register after Local Processing Mode (configured through the SIP Signaling Group).

Scenario 1: Registration fails; Fwd Register Option not configured

The Sonus SBC handles the calls as follows:

Scenario 2: Fwd Register Option fails; Registration not configured

The Sonus SBC handles the calls as follows:

Scenario 3: Registration fails; Fwd Register Option succeeds

The Sonus SBC handles the calls as follows:

Scenario 4: Registration succeeds; Fwd Register Option fails

The Sonus SBC handles the calls as follows:

 

Troubleshoot Configuration for connection to a Server

To troubleshoot a server failure due to configuration, verify the current Registration and SIP Server Options configured on the Sonus SBC 1000/2000.

Verify Signaling Group

In the Signaling Group screen, the selections available in the SIP Server Table drop down list are derived from the entries configured in the SIP Server Table. This signaling group is used in the SIP Server Table and corresponds to the Server being contacted.

Verify the Signaling Group Server Table selected for this specific signaling group as follows: 

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Signaling Groups.
  3. Click on the desired SIP Signaling Group.
  4. In the SIP Channels and Routing portion, verify the SIP Server Table selected.
  5. Change or update as necessary. See Creating and Modifying SIP Signaling Groups.

 

Verify Registration/Monitor for SIP Options (for SIP Server)

Through the SIP Server Table, you choose the Contact Registrant table that will be used by a Signaling Group to register one or more contacts to a registrar. Contact Registrant Tables are used to manage contacts that are registered to a SIP server. When Monitor using SIP options is selected, an Options message is sent to the server with more detailed information, such as how often the Sonus SBC 1000/2000 queries the server with an Options message to determine the server's availability.

When a Server is unreachable and the problem is registration failing or SIP options not being successful, you can verify the configuration as follows:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to SIP > SIP Server Table.
  3. Select the desired SIP Server table that corresponds to the Server being contacted.
  4. Click the Contact Registrant Table drop down box. All available registration tables listed in the Contact Registrant Tables are displayed. 

    When a challenge (401/407) is issued by the server, the table selected from the Remote Authorization drop down list is used by a SIP Server Table.

  5. From the Monitor drop down list, select SIP options.
  6. Verify the configuration and adjust, if necessary. See Creating and Modifying Entries in SIP Server Tables.

 

Verify Configuration for Contact Registrant

The configuration configured in the Contact Registrant Tables is used to manage contacts that are registered to a SIP server. If registration to a Server is successful, but the Monitor using SIP Options fail, verify the following configuration.

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to SIP > Contact Registrant Table.
  3. Click the table that corresponds to the Server.
  4. Verify the configuration (i.e. Global Time to Live) and adjust, if necessary. See Creating and Modifying Entries in Contact Registrant Tables.

 

Verify Forward Register Option

If registration to a Server is successful, but the Forward Register option fails, verify the following configuration:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Signaling Groups.
  3. Click on the desired Signaling group that corresponds to the Server.
  4. From the SIP Mode drop down list, select Fwd Reg. after Local Processing.