Best Practice - Authentication Registration with Service Provider

Introduction

This section describes how to configure an SBC 1000, SBC 2000 or SBC SWe Lite to interconnect with a Service Provider (SP) through SIP authenticated registration. This section gives the main guidelines only on this specific topic, so technical readers should have prior knowledge and experience using each of these products.

Use the Easy Config Wizard to complete the initial setup, then add or modify the relevant items.

Software Versions

Any GA versions running on any SBC Edge products.
Feature supported since release 4.

Architecture

The sample configuration detailed below includes two SBC SWe Lites. One is the customer SBC Edge, with its configuration described in the following sections. The second one simulates a Service Provider SBC, ‘Sip.operator.net’ requiring SIP Registration authentication.

Architecture

Prerequisites

Configure the SBC Edge for DNS resolution; this configuration resolves the SP FQDNs provided by the Service Provider and configured in the SBC Edge. This configuration is done at the System level as shown:

SBC Configuration

Configuring the SBC Edge

Follow the steps below to configure the SBC Edge for the SIP Service Provider registration with authentication scenario.

Remote Authorization Table

Create a Remote Authorization Table on the SBC Edge, and create one entry in this table with the authentication information provided by the SIP Service Provider.
In the example below, the Remote Authorization table, SIP SP Remote Auth Table, is first created. An entry is then created with realm “ribbon.fr”, Authentication ID “ABCDEFGH” and associated password, as expected by the SP SBC. Ensure the From URI User Match field is set to Regex, and configure the Match Regex field as (.*) if the From for the Register request is different to the Authentication ID.

Create Remote Authorization Entry

Remote Authorization Entry Created

Contact Registrant Table

Create a Contact Registrant Table on the SBC Edge, and create at least one entry with the information provided by the SIP Service Provider. It is the phone number(s) that is used during registration and calls.

In the sample below, the SIP SP Contact Registrant Table is first created.

Create Contact Registrant Table

Set Type of Address of Record to Remote, if you want to send Register with SP SBC FQDN instead of the SBC Edge IP.

Contact Registrant Table

SIP Server Table

Create a SIP Server Table on the SBC Edge. It contains the information from the distant SIP Service Provider SBC that the SBC Edge needs to register to and send calls to.

In the example below, the distant SP SBC is “sip.operator.net”, distant port is “5060” and the protocol expected by the distant is “UDP”.
Configure the Remote Authorization Table and the Contact Registrant Table created earlier, with the sub-parameters as below:

Create SIP Server Table

If the Service Provider SBC supports Monitor through SIP OPTIONS messages, you can enable it in the Transport section.

SIP Profile

If the Service Provider needs some special SIP parameters, create a SIP Profile accordingly and associate with the SP Signaling Group.

In the sample below, a SIP Profile is created to present the SP SBC FQDN in the From field:

Create a SIP Profile

SIP Signaling Group

Select the SIP Server Table created earlier, the SIP Profile if required and configure the correct Federated FQDN, Port, and Protocol when you configure the SIP Signaling Group that will connect the SBC Edge with the SP SBC.

The example below matches the different sample objects configuration done earlier.

Check and Logs

Registration check

When the configuration is complete and connection is possible between the SBC Edge and Service Provider SBC Edge, you can check the status of the registration in the Contact Registrant Table by clicking the Registration Status link.

Registration Status - Contact Registrant Table

Alternatively, check the display option Sessions in the Signaling Group Table. 

Registration Status - Signaling Group Table

Log Sample

To collect the trace in the Syslog, select the correct subsystems. For this, click Apply Log Profile and choose the Profile Name Audio – SIP.

Select Subsystem

Here is a sample SIP Debug Log from the SBC Edge displayed with LX tool. The log shows the Register steps with authentication.
In the Register flow, the SBC Edge is 192.168.123.75 and the Service Provider SBC Edge is 192.168.123.89/sip.operator.net

SIP Debug Log

1. The SBC Edge sends REGISTER.

   SBC sends REGISTER

   

2. Service provider SBC Edge replies with 401 Unauthorized to ask credentials for registration on realm 'sip.operator.net’.

   401 Unauthorized

   

3. The SBC Edge sends REGISTER with its credentials.

   Customer SBC sends Register

   

4. The service provider SBC Edge replies with 200 OK when credentials match and are accepted.

   200 OK Response

   
   
   Incoming and outgoing calls are now accepted.