dialogic bordernet4000 sbc quick start guide v1 2

COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED.

A guide to Installing and Configuring the Dialogic® Bordernet™ 4000 SBC and V-SBC

V1.2

COMPANY CONFIDENTIAL © COPYRIGHT 2013 DIALOGIC INC. ALL RIGHTS RESERVED. 2

Overview and scope of this document

This document describes how to initially setup and configure a Dialogic Bordernet 4000 SBC. It is intended as a supplement to the standard installation and configuration guides which are available from here: http://www.dialogic.com/en/manuals/bn-4000/bordernet4000sbc3.2.aspx

The sample network below will be used to demonstrate and configure several different routing and call manipulation scenarios.

Local networkInternet

Bordernet 4000 SBC or V-SBC

PBX and Voice server

MGMTNetwork MGMT pc

CarrierA

Proxy/Registrar serverSIP Phone

SIP Phone

Route

server


Contents

Supplemental Installation Information

Post Deployment tasks

Two complete deployment descriptions

Routing using Static Routes

Supporting SIP Phone registrations

Supplemental configuration (you need to configure a complete deployment before using these)

Routing calls using called party number

Load balancing and fault tolerant routing

Manipulation of called and calling party numbers

Routing using an external route server

Transcoding audio from any supported codec to G.711

Testing and debugging routes


Initial Installation and Deployment

This section adds some supplemental information to the standard Install and Setup guide (available from http://www.dialogic.com/webhelp/BorderNet/BorderNetSWSBC/BorderNet_Virtualized_SBC_Ins

tall_Set-Up_Guide_v2.pdf ) and should be read and implemented alongside that guide.


Initial Setup – V-SBC

Prerequisites:

Detailed prerequisites are in the Install and Setup guide which should be carefully consulted before proceeding.

The V-SBC is supported on VMware ESXI v5.0 and newer running on a 64bit CPU, minimum 2.4Ghz, 4GB memory, 40GB hard disk.

Two versions of the instance are available:

The standard version supports upto 1000 sessions and requires 2 CPUs and 4GB RAM

“High Cap” version supports upto 8000 sessions and requires 6 CPUs and 8GB RAM

Setup the VM networks before installation. You will need a management network and typically two session networks that carry the SIP/RTP traffic. An HA network is only needed if you wish to run HA pairs.

Installation

Follow the Install and Setup guide until the “Obtaining a license” section on page 20 then send the Platform Serial Number and License Request ID to Dialogic UK sales and they will generate and send a license.


Deployment – V-SBC

Deployment

Once you receive the license then follow the Install and Setup guide to deploy the V-SBC.

Note the following points :

The System Management IP is the address that will be used to manage the V-SBC from now on. The Utility IP address that was used for initial setup is not typically used again after this point.

The Inter-Task/HA link IP address must be entered even if HA is not being used. This address is active and so must not match any other IP address on that network.

Once deployment is complete the V-SBC will restart so that configuration can begin.

Note that after the restart you will access the V-SBC using the Management IP address. For security reasons the V-SBC will only accept management traffic from the same subnet as the management IP address, this can be later changed by editing ACLs (see below in post deployment section) but until you add an ACL your configuration PC must be on the same subnet as the SBC.


Post Deployment tasks

This section describes typical tasks such as adding Access Control Lists, creating users etc that are typically carried out after deployment and before initial SBC configuration.


Post Deployment – Adding users

After deployment you may want to add new users to manage access to the SBC. A typical example would be a ‘super user’ who has access to all management and configuration features, other users could be added with just viewing ability etc.

To add a super user follow this process:

Logon to the SBC Web UI using sysmanager/SYSMGR

Open System/User Management/Users

Select ‘Add New User’

Enter a name and password

Add the roles SYSTEM_ADMIN, TRACE_MANAGER & APPLICATION_ADMIN which will give this user rights to perform any function on the SBC

Save the user and login as the new user.


Post Deployment – Adding an ACL for Management

After deployment the SBC will not allow management access using the web UI unless your management PC is on the same IP subnet as the SBC.

If you wish to manage the SBC from another subnet then follow this process:

Logon to the SBC Web UI (so you will need to be on the same subnet for this step)

Open Application/Security Configuration/Access Control List

Select ‘add a new Access Control List’

For Application select ‘Management’

For Action select ‘Accept’

Enter the subnet or specific IP address

Eg 192.168.100.0 /24 is a subnet

192.168.100.101/32 is an address

For Local Entity select ‘https’

Save the ACL


Configuring a simple Static Route

This section describes how to configure the SBC to support a Static route for calls from CarrierA on the Internet to connect to the VoiceServer on the local LAN


Configuration Overview – Interconnect Static Route

To setup the V-SBC to route traffic from Carrier A on the Internet to the PBX/Voice server on the local LAN you will need to setup the following elements:

VLANs

Parameter, Media, Service and Security Profiles

SIP Interfaces

SIP Peers

SIP Interface/Peer links

Static Routes

The following pages will cover this setup using the sample network on the next page.


Network Schematic

Local network20.1.1.x

Internet



MGMT192.168.186.x

MGMT pc

192.168.186.75

SIP/RTP20.1.1.200

SIP/RTP10.1.1.200

CarrierA

SIP/RTP10.1.1.100 SIP/RTP

20.1.1.100

Proxy/Registrar server

SIP20.1.1.50

SIP/RTP10.18.1.113

SIP/RTP11.12.6.17

Route server

SIP20.1.1.25


Configuring Ethernet Links

System/Ethernet Links are pre-defined and associate traffic types (mgmt, session) with specific interfaces.

You can change their names (eg WAN, HA) to describe their function and so provide a configuration reference

In this example the interfaces have been named as below, e.g. Eth2 port will handle traffic from the Internet so has been named WAN_Interface etc.


Configuring VLANs

System/VLANs are used to apply IP address(es) to physical Ethernet ports on the SBC.

Each port can have multiple IP addresses or VLANs and these addresses will later be allocated to SIP or H.323 resources.

A VLAN ID of 0 is used to just apply IP address(es) to ports

You can have multiple addresses using VLAN ID 0 on each port

A VLAN ID of 1 – 4096 will be used as a 802.1Q VLAN Tag so can provide different VLANs and broadcast domains.

In this example two VLANs are created, one that will be used to connect to a particular carrier on the WAN port, one that will connect to all voice servers on the local LAN port.


Configuring Network Types

The SBC uses a ‘Network Type’ field in various options (eg SIP Interface, SIP Peer) to set some basic parameters and behaviour for the expected traffic type on that interface or peer.

There are five types of network defined, not all may be used in any installation

Interconnect

A peer level connection through a Public network, typically used for connections to carriers/operators etc

Local

A peer level connection to a trusted local network, so typically the resources on the internal network such as SIP servers.

Access-Public

Used to support Access connections (eg Class 5 or user services/endpoints that support registration etc) on the WAN

Access-Local

Used to support Access (eg Class 5 or user services/endpoints that support registration etc) on the local network

Access-Interconnect


Profile Overview

Profiles are used to apply commonly used values as a template.

There are several types of Profile, we will use four profiles to apply to SIP interfaces.

Parameter Profile (SIP Parameter Profile)

Contains SIP Timers, Session expiry values, support for 100REL/PRACK etc

Media Profile

Used to specify which codecs the SBC will offer and support

Security Profile

Handles session limits such as calls per second, max number of sessions

Service Profile

Controls routing, redirection and transparency etc

The Profiles are specific to each network type, eg whether the call is coming from a Interconnect peer or a local trusted server etc so you will need to define profiles for each network type that you will be using.


Configuring Profiles

As you will be using the Interconnect network type (to connect to Carrier A) and the Local network type (to connect to the local voice server) we first need to define the profiles that these connections will use.

First open Application/SIP/Parameter profile and create a Parameter Profile with network type Interconnect,

name it in a way that explains its function as you will reuse these profiles, egInterconnect_Reliable_Required and check that the default settings match your requirements.

Now repeat this for network type Local to create a local SIP Parameter profile.

Now repeat this, creating profiles for Interconnect and Local network types for

Application/SIP/Media

Application/Security Configuration/Security Profile

Application/Common/Service Profile

Use SystemInMsgProfiler and SystemOutMsgProfiler in the Incoming Message profiler and Outgoing Message Profiler selection

At the end you should have 8 new profiles; 4 Interconnect profiles and 4 Local profiles.


Configuring SIP Interfaces

A SIP Interface is an address that the SBC sends traffic from and expects to receive traffic to.

You will need to create a SIP Interface for the Interconnect side and one for the Local side so you can send and receive traffic from CarrierA and the Voice server.

Open Application/SIP/Interface, select ‘Add new SIP Interface’

Tip, create the Interface with the Status ‘Off’, once the remainder of the config is complete you can turn the status ‘On’ to enable traffic

Select the correct network type, in this case we will first create one with a Interconnect type

‘Associated Peers’ check box if selected means that only traffic from named SIP Peers will be accepted, an extra security feature.

In the Signalling IP select the VLAN defined earlier.

Signalling TOS needs to have a value, use 0 if you do not want to set TOS/QoS.

Select the Interconnect Parameter, Media, Service and Security profiles defined earlier

Now repeat this for network type Local to create a ‘Local’ SIP Interface.

for



Configuring SIP Peers

A SIP peer is an endpoint or range of endpoints that the SBC sends traffic to and expects to receive traffic from. The SBC will not process traffic from an endpoint unless it is in the list of peers.

A Peer can be a single entity eg a Carrier on a single IP address or a range of addresses eg SIP Phones on the Internet

You will need to create a SIP Peer on the Interconnect side to represent the CarrierA and one for the Local side to represent the Voice server.

Open Application/SIP/Peer, select ‘Add new SIP Peer’ Select the correct network type, in this case we will first create one with a Interconnect type

‘For a single address the ‘Source Type’ should be ‘Single’ and add the IP address and optionally port of the CarrierA then click the + button.

If you don’t add a port then calls from any port are accepted.

In the Destination FQDN/IP add the address you will send calls to, typically the same as the source.

TGRP needs to have a value, use 0 if you do not want to set it.

Do not select any of the profiles as they have been selected at the SIP Interface level.

Now repeat all these steps and create a Local SIP Peer, the VoiceServer.


Configuring Interface-Peers

A SIP Interface-Peer establishes the relationship between a SIP Interface and a Peer, so the SBC knows who to expect traffic from and on what interface.

Open Application/SIP/Interface-Peer, select ‘Add new SIP Interface-Peer’ Select the Interconnect Peer CarrierA that you defined before and the SIP Interface you created for the Interconnect side.

Select the ‘Connectivity Feature’ if you want the SBC to send SIP OPTIONS messages to the remote to check it is alive. This can be used in more advanced routing later.

Now repeat these steps to create a Local SIP Interface-Peer


Configuring Static Routes

A Static Route is as it sounds, basically you create a route between two SIP Peers/Interfaces so any calls coming in on one Peer/Interface will be routed to the other Peer/Interface.

They are very commonly used with the SBC, although more advanced routing can be used as well and will be demonstrated in other sections.

Open Application/Common/Static Routing, select ‘Add new Static Routing’

Select the Source Peer and Interface as CarrierA and the Interconnect SIP Interface, and the destination as Local SIP Interface and VoiceServer peer

You can create another Static route if you need traffic originating from the VoiceServer to go out to the CarrierA but if all traffic originates from the CarrierA you do not need the reverse route.

That concludes the setup of Static routes, and they are now ready to use.

Don’t forget to turn on the SIP Interface if you disabled it as suggested.


Supporting SIP Phone Registrations

This section describes how to configure the SBC to support SIP Phones on the Internet registering through the SBC to a local Registrar server


Configuration Overview – Supporting Phone Registration

To setup the V-SBC to route traffic from Phones on the Internet to the Registrar server on the local LAN you will need to setup the following elements:

VLANs

Parameter, Media, Service and Security Profiles

SIP Interfaces

SIP Peers

SIP Interface/Peer links

Static Routes

The following section will cover this setup using the sample network on the next page.


Network Schematic

Local network20.1.1.x

Internet



MGMT192.168.186.x

MGMT pc

192.168.186.75

SIP/RTP20.1.1.200

SIP/RTP10.1.1.200

CarrierA

SIP/RTP10.1.1.100 SIP/RTP

20.1.1.100

Proxy/Registrar server

SIP20.1.1.50

SIP/RTP10.18.1.113

SIP/RTP11.12.6.17

Route server

SIP20.1.1.25


Configuring VLANs

A VLAN is used to apply IP address(es) to physical Ethernet ports on the SBC.

Each port can have multiple IP addresses and these addresses will later be allocated to SIP or H.323 resources.

A VLAN ID of 0 is used to just apply IP address(es) to ports

You can have multiple addresses using VLAN ID 0 on each port

In this example a VLAN called WAN_Phone_Access has been added to the two that were created earlier for the Carrier and VoiceServer connections.

Its not necessary to create new VLANs for each connection but can be useful to keep traffic separate and make routing simpler etc


Configuring Network Types

The SBC uses the Network Type in various options (eg SIP Interface, SIP Peer) to set some basic parameters and behaviour for the expected traffic type on that interface or peer.

There are five types of network defined, not all may be used in any installation

Interconnect

A peer level connection through a Public network, typically used for connections to carriers/operators etc

Local

A peer level connection to a trusted local network, so typically the resources on the internal network such as SIP servers.

Access-Public

Used to support Access connections (eg Class 5 or user services/endpoints that support registration etc) on the WAN

Access-Local

Used to support Access (eg Class 5 or user services/endpoints that support registration etc) on the local network

Access-Interconnect


Profile Overview

Profiles are used to apply commonly used values as a template.

There are several types of Profile, we will use four profiles to apply to SIP interfaces.

Parameter Profile (SIP Parameter Profile)

Contains SIP Timers, Session expiry values, support for 100REL/PRACK etc

Media Profile

Used to specify which codecs the SBC will offer and support

Security Profile

Handles session limits such as calls per second, max number of sessions

Service Profile

Controls routing, redirection and transparency etc

The Profiles are specific to each network type, eg whether the call is coming from a Interconnect peer or a local trusted server etc so you will need to define profiles for each network type that you will be using.


Configuring Profiles

We will use the Access-Public network type (to connect to the phones) and the Access-Local network type (to connect to the local Registrar server) so we first need to define the profiles that these connections will use.

First open Application/SIP/Parameter profile and create a Parameter Profile with network type Access-Public

name it in a way that explains its function as you will often reuse these profiles, egAccess_Public_Phones and check that the default settings match your requirements.

Now repeat this for network type Access-Local to create a local SIP Parameter profile.

Now repeat these steps, creating profiles for Access-Public and Access-Local network types for :


Application/Security Configuration/Security Profile

Application/Common/Service Profile

Use SystemInMsgProfiler and SystemOutMsgProfiler in the Incoming Message profiler and Outgoing Message Profiler selection

At the end you should have 8 new profiles; 4 Access-Public profiles and 4 Access-Local profiles.


Configuring SIP Interfaces

A SIP Interface is an address that the SBC sends traffic from and expects to receive traffic to.

You will need to create a SIP Interface for the Access-Public side and one for the Access-Local side so you can send and receive traffic from the phones and the Registrar server.

Open Application/SIP/Interface, select ‘Add new SIP Interface’

Tip, create the Interface with the Status ‘Off’, once the remainder of the config is complete you can turn the status ‘On’ to enable traffic

Select the correct network type, in this case we will first create one with a Access-Public type

In the Signalling IP select the VLAN defined earlier.

Signalling TOS needs to have a value, use 0 if you do not want to set TOS/QoS.

Select the Interconnect Parameter, Media, Service and Security profiles defined earlier for Access-Public networks

Now repeat this for network type Access-Local to create a SIP Interface for the Registrar, using the existing Local VLAN.

If you are using a VLAN that is already in use eg you have configured the previous static route example you will need to chose a different port as 5060 is already in use by the VoiceServer SIP Interface, so you can chose port 5070 for example.


Configuring SIP Peers

A SIP peer is an endpoint or range of endpoints that the SBC sends traffic to and expects to receive traffic from. The SBC will not process traffic from an endpoint unless it is in the list of peers.

You will need to create one SIP Peer on the Access-Public side to represent all of the Phones and one SIP Peer for the Access-Local side to represent the Registrar.

Open Application/SIP/Peer, select ‘Add new SIP Peer’ Select the network type, in this case we will first create one with a Access-Public type

As the phones will be using any address on the 10.x.x.x and 11.x.x.x networks select ‘Source Type’ of ‘Group’ and add two ranges using the CIDR notation of 10.0.0.0/8 and 11.0.0.0/8

If you don’t add a port then calls from any port are accepted.

To select any possible addresses on the internet use two ranges 1.0.0.0/1 and 128.0.0.0/1

In the Destination FQDN/IP add any address as this will not be used.

TGRP needs to have a value, use 0 if you do not want to set it.

Do not select any of the profiles as they have been selected at the SIP Interface level.

Now repeat all these steps for the Access-Local SIP Peer, the Registrar.As this is a single host use Source Type ‘Single’

In the Source and Destination IP address list put just the address of the server


Configuring Interface-Peers

A SIP Interface-Peer establishes the relationship between a SIP Interface and a Peer, so the SBC knows who to expect traffic from and on what interface.

Open Application/SIP/Interface-Peer, select ‘Add new SIP Interface-Peer’ Select the Access-Public Peer ‘Phones’ that you defined before and the SIP Interface you created for the Access-Public side.

Now repeat these steps to create a Access-Local SIP Interface-Peer for the Registrar

Select the Connectivity Feature if you want to send SIP OPTIONS messages tp this peer to check it is alive.


Configuring Static Routes

A Static Route is as it sounds, basically you create a route between two SIP Peers/Interfaces so any calls coming in on one Peer/Interface will be routed to the other Peer/Interface.

They are very commonly used with the SBC, although more advanced routing can be used as well and will be demonstrated in other sections.

Open Application/Common/Static Routing, select ‘Add new Static Routing’

Select the Source Peer as ‘Any’ and Interface as the Access-Public SIP Interface

Select the Destination as the Access-Local SIP Interface and Registrar peer

That concludes the setup of a route supporting Phones that will register through the SBC.

Don’t forget to turn on the SIP Interface if you disabled it as suggested.


Routing Calls using the Called Party Number


Load Balancing and Fault Tolerant Routing


Manipulation of Called and Calling Numbers


Routing Calls using a Route Server


Transcoding Audio from any codec to G.711


Testing and Debugging Routes


Installing and using Wireshark

Full instructions are in the Maintenance and Troubleshooting guide available here:

Select Capture/Options.

Click ‘Manage Interfaces’ button

In the Interface Management screen click the ‘Add’ button

In the Remote Interface screen enter the Management IP address and port 2010 and username and password of a user that has TRACE_MANAGER privileges.

Click ‘Close’ button to close the Interface Management screen

You will see a list of the Session interfaces (eg eth2) and trace filters egSignallingNoMedia.

Select the option you require, eg SignallingNoMedia will show SIP & H323 on all session interfaces, eth2 will show all traffic types on eth2


Dialogic and Network Fuel among others as well as related logos, are either registered trademarks or trademarks of Dialogic Inc. and all companies controlling, controlled by, or under common control with Dialogic Inc. (“Dialogic”). The names of actual companies and products mentioned herein are the trademarks of their respective owners.

01/13

dialogic.com

dialogic bordernet4000 sbc quick start guide v1 2

Documents

dialogic bordernet

setup guide available

standard installation

deployment vsbcdeployment

initial installation

dialogic uk sales

license section

ha network