SBC Upper Registration

1 Configuration Steps
2 Use Case – Configuration Example

“Upper Registration”(also named as “Through Registration” or “Forward Registration”) is a feature Sangoma SBC provides to help remote users, outside of the Enterprise or Carrier networks, to access Enterprise PBX, Hosted PBX or Carrier Soft-switch in a secure and reliable way.

Sangoma SBC stands on the edge of local network and transparently passes registration coming from public network to an Enterprise PBX or Carrier Soft-switch. As a result, users are able to use their existing SIP account to register from outside of local network via Sangoma SBC. There is no need to have separate access credentials for those users accessing services from public networks.

Users registered with upper registration feature can then make and receive calls, just like using an internal phone extension.

Configuration Steps

The following outline the steps required to configure Sangoma SBC for Upper Registration. A more detailed use case configuration example can be found in the section “Use Case – Configuration Example”.

Create a SIP Profile for the PBX
- A dedicated SIP Profile must be created for the Enterprise PBX, this SIP Profile is reserved to be used by the designated PBX. Note that if there are more than one PBX, each PBX must have its own SIP Profile created in the SBC.

Create a Domain
- Create a Domain using the same domain name in the PBX. The domain configuration consists the location of the Registrar. When SBC receives a Registration request that matches the domain name, it forwards to the PBX.

Create Domain binding
- Bind the Domain to the SIP Profile that handles traffic from outside the Enterprise network.

Create Call Routing
- Specific call routing for registered users.

Use Case – Configuration Example

In this section, we use a typical use case to show you how to configure upper registration feature on Sangoma SBC.

Enterprise PBX/Carrier Soft Switch: IP address	192.168.100.108
SBC Internal IP address	192.168.100.66
SBC External IP address	10.10.2.10

We need to add:

Two Call Routing Profiles	“Inbound_Dialplan” and “Outbound_Dialplan”
Two SIP Profiles	“Internal_Sip_Profile” and “External_Sip_Profile”
Two Domains	Upper registration domain “10.10.2.10”

Call Routing Profile: “Inbound_Dialplan”

<extension name="Local_Extension_Inbound">
  <condition field="destination_number" expression="^(10[01][0-9]).*$">
    <action application="export" data="dialed_extension=$1"/>
    <action application="bridge" data="sip/Internal_Sip_Profile/${dialed_extension}@192.168.100.108"/>
  </condition>
</extension>

Call Route Profile: “Outbound_Dialplan”

<extension name="Local_Extension_Outbound">
  <condition field="destination_number" expression="^(10[01][0-9])@192.168.100.66.*$">
    <action application="export" data="dialed_extension=$1"/>
    <action application="bridge" data="${sofia_contact(External_Sip_Profile/${dialed_extension}@10.10.2.10)}"/>
  </condition>
</extension>

SIP Profile “Internal_Sip_Profile”

Navigate to “Configuration -> Signalling -> SIP Profiles”:

add a new sip profile “Internal_Sip_Profile”;

Make the following changes from default configuration:

“SIP IP Address”: choose the NIC you want to use for SIP listening: in this case it is “192.168.100.66”;
Set “Authenticate Calls” to “Disabled”
Set “Always Use Full Identification” to “Enabled”
Set “Routing Plan” to “Outbound_Dialplan”

!Security Warning: With Authenticate Calls set to Disable, make sure that your PBX/Soft Switch is set to authenticate incoming calls.

SIP Profile “External_Sip_Profile”

For sip profile “External_Sip_Profile”, it is similar to “Internal_Sip_Profile”.

Navigate to “Configuration -> Signalling -> SIP Profiles”,

add a new sip profile “External_Sip_Profile”;

Make the following changes from default configuration:

“SIP IP Address”: choose the NIC you want to use for SIP listening: in this case it is “10.10.2.10”;
Set “Authenticate Calls” to “Disabled”
Set “Always Use Full Identification” to “Enabled”
Set “Routing Plan” to “Inbound_Dialplan”

Upper Registration Domain “10.10.2.10”

Navigate to “Configuration -> Signalling -> Domains”,

add a new domain “10.10.2.10”;
Enable “Forward Registration”

The following screen shot first states:

*For any registration to domain “10.10.2.10”, Sangoma SBC will use sip profile “Internal_Sip_Profile” to forward it to IP “192.168.100.108”, port “5060” with transport UDP.

Bind Domain “10.10.2.10” to external sip profile

Go to “Configuration -> Signalling -> SIP Profiles”,

choose to modify sip profile “External_Sip_Profile”;
Click the “Bind” button, and then check the checkbox beside domain “10.10.2.10”;
Click “Bind” button in the message box.

Session Border Controller