Page History
...
This Best Practice describes how the Sonus SBC 1000/2000 handles
| Spacevars | ||
|---|---|---|
|
| Info |
|---|
This Best Practice assumes the following:
|
Call Survivability when SIP Server is down - How calls are routed with PSTN Backup (SIP Survivability)
| Info |
|---|
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. |
...
- Incoming call is allowed. Since the server is down, the Signaling Group's Server Status is set as Down. Instead of attempting to send calls to the server, the call proceeds to the next Destination Signaling Group (if configured based on the routing policy, which must include the PSTN). See Managing Signaling Groups.
- Based on routing configuration, incoming calls are made without any post dial delay to the configured SIP or ISDN trunk.
| Pagebreak |
|---|
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
- Endpoint is registered with the SBC 1000/2000 (see Creating and Modifying Entries in Contact Registrant Tables).
- SBC's Signaling Group is configured to send requests to a server (see Creating and Modifying Entries in SIP Server Tables).
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:
...
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:
- The corresponding session is up.
- Invite requests are routed to the corresponding Signaling Group (the status is set to Up).
| Pagebreak |
|---|
Forward Register after Local Processing Mode - How Incoming Calls
...
Are Handled in the
...
SBC
...
Below are the components of a configuration that includes Forward Register after Local Processing Mode (configured through the SIP Signaling Group).
- Endpoint is registerd with the Sonus SBC.
- SBC has a Signaling Group configured to send requests to a Server.
- Signaling Group is configured with Fwd Register After Local Processing as the SIP Mode.
- A signaling group is assocated with both call origination and termination device.
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:
- Normal call flow for incoming call. In case the Server is down, there may be post dial delay in attempting to call the Server.
| Pagebreak |
|---|
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.
...
| Panel | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
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.
...
| Panel | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
| Pagebreak |
|---|
Verify Configuration for Contact Registrant
...
| Panel | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
Verify Forward Register Option
...
| Panel | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
| Pagebreak |
|---|
Overview
Content Tools