FRAFOS ABC SBC Installation Guide

FRAFOS ABC SBC Installation GuideRelease 2.0.2

FRAFOS GmbH

December 04, 2013

Contents

1 FRAFOS ABC SBC requirements 21.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3 Virtual Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 FRAFOS ABC SBC Virtual Image 32.1 Virtual Image overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.2 VM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.3 VM initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.4 VM SBC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 FRAFOS ABC SBC repository 53.1 Client certificate request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.2 Certificate and FRAFOS repository configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 53.3 FRAFOS repository initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4 FRAFOS ABC SBC installation 7

5 FRAFOS ABC SBC initial configuration 85.1 SBC interfaces overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85.2 GUI interface (XMI) configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

6 Initial services configuration 106.1 Deployment mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106.2 Hostnames and IMI addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116.3 Generate and distribute SSH keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126.4 Generate and distribute Corosync Authentication key . . . . . . . . . . . . . . . . . . . . . . . . 136.5 Configuring cluster parameters and services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156.6 Second node configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176.7 Cluster connection verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

7 User accounts and login 187.1 Default users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187.2 Configuring user accounts: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

8 FRAFOS ABC SBC license 19

9 System interfaces 20

10 SBC interfaces 2110.1 Virtual IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2110.2 Signaling and Media interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

11 SBC services status 23

12 Hardware specific configuration 2512.1 Network adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2512.2 Mysql server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

i

12.3 Sbc threads number settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

13 FRAFOS support 27

ii

FRAFOS ABC SBC Installation Guide, Release 2.0.2

This document describes hardware and software requirements, installation procedure for single node and high-availability (two nodes in pair) deployment. It also deals with users administrations, licensing key management,system (network) and SBC interfaces desctiption and configuration.

Contents 1

Chapter 1

FRAFOS ABC SBC requirements

1.1 Hardware

FRAFOS ABC SBC is distributed as hardware and also software based solution. It’s performance depends mainlyon used processor and memory.

Minimum hardware:

• CPU: one processor

• memory: 512 MB RAM

• HDD: 6 GB

Recommended hardware:

• CPU: Dual-core x86 64bit 2.8 GHz processor

• memory: 4GB RAM

• HDD: 500 GB

1.2 Software

FRAFOS ABC SBC is installed on CentOS operating system (version 6.4 - x86_64 architecture).

1.3 Virtual Image

For demo purposes FRAFOS ABC SBC is delivered as a virtual machine that can be imported into virtualizationsoftware – VMware Player or other VMware products (VMware Workstation, WMware ESX,. . . ), VirtualBox orother virtualization platforms that support OVA or VMX formats.

FRAFOS ABC SBC VM can be downloaded from FRAFOS internal web site.

For information how to import, configure and use the virtual image, please follow FRAFOS ABC SBC VirtualImage chapter.

2

http://www.frafos.com/free-trial/

Chapter 2

FRAFOS ABC SBC Virtual Image

2.1 Virtual Image overview

FRAFOS ABC SBC VM can be downloaded in Vmware format or OVF format. It comes pre-configured withall required interfaces (see SBC interfaces overview for different interface types) and also with initial basic SBCconfiguration.

For access to VM console, use “root” username with “frafos” password.

Important: It is highly recommended to change the root password!!!

2.2 VM Interfaces

There are two physical interfaces configured:

• eth0 - 192.168.1.110/24 (default gw 192.168.1.1)

• eth1 - 10.0.1.110/24

User should modify the IP addresses to follow his network topology. In CentOS, system interfaces can be config-ured (use any text editor) in networking scripts:

% /etc/sysconfig/network-scripts/ifcfg-ethX

When all the interfaces are configured, restart the network sevice (or reboot) the machine:

% service network restart

Note: If user is connected using ssh to the machine, it may happen user is disconnected...

2.3 VM initialization

As the interfaces configuration has changed, user has to perform initial configuration of the ABC SBC services(like configure GUI access and management interfaces)

Follow chapter FRAFOS ABC SBC initial configuration to update the GUI access configuration.

Follow chapter Initial services configuration to update the HA and management configuration.

Follow chapter User accounts and login to access GUI and modify user’s access (security).

3


From GUI, user can modify the SBC interfaces configuration to use the real system IP addresses etc. Using ‘edit’link, update all the Signaling and Media interfaces in order to use the real system’s IP addresses.

Important: After changing all needed interfaces, it is necessary to activate network configuration using ‘activate’link shown in GUI warning message.

Now your ABC SBC should have correctly configured (updated) all interfaces.

2.4 VM SBC configuration

FRAFOS ABC SBC virtual image is pre-configured with basic configuration.

This is configuration when FRAFOS ABC SBC serves as an border controller to connect public users with privatePBX or proxy.

Public users are defined with IP netmask 0.0.0.0/0 which means “users from every IP address”. Users has toregister through ABC SBC to proxy/PBX server. The SBC does performs “registration cache” action, where ittranslates contacts in REGISTER requests to an “alias” and with this alias SBC is registering to the proxy/PBX.

In the oposite direction, when request is coming from proxy/PBX, SBC performs “re-targeting” and translatesalias (that is in R-URI) to original user’s contact.

There are several other actions which are described in the Configuration guide.

For more information or any questions regarding configuration, please contact FRAFOS support.

2.4. VM SBC configuration 4

Chapter 3

FRAFOS ABC SBC repository

FRAFOS ABC SBC is installed from FRAFOS public repository.

3.1 Client certificate request

FRAFOS public repository is accessible using SSL client certificate. Certificate is generated by FRAFOS fromclient certificate request. This request is created using customer (replace “company” with company name):

% openssl req -new -nodes -days 365 -out company_req.pem -keyout company_key.pem

Customer has to specify:

• Country Name

• State (optional)

• Locality Name (city)

• Organization Name (company)

• Organization Unit Name (optional)

• Common Name (company name)

• Email Address (company contact)

• Challenge password (used in case of certificate revocation)

Important: Created certificate request (company_req.pem) has to be sent to FRAFOS and the certificate will beissued.

3.2 Certificate and FRAFOS repository configuration

Client and FRAFOS CA certificate and repository configuration file is distributed by FRAFOS in format of com-pressed archive file “frafos_abcsbc_2.0_repo.tar.gz” file that includes:

Copy the archive to the server (e.g. into /root/ directory) and extract the archive using:

% tar zfx frafos_abcsbc_2.0_repo.tar.gz

It will create a directory “frafos_abcsbc_2.0_repo” with following files:

• company_cert.pem

• frafos_ca_cert.pem

5


• frafos_abcsbc_repo.sh

Run “frafos_abcsbc_repo.sh” script with parameter of company name (used when generating request)

% ./frafos_abcsbc_repo.sh company

This command creates “/etc/frafos/certs” directory and copies “company_cert.pem” and “frafos_ca_cert.pem”there.

Important: Administrator has to copy the “company_key.pem” file to this directory!

It also creates FRAFOS ABC SBC repository configuration file “Frafos.repo” in “/etc/yum.repos.d/” directory.

3.3 FRAFOS repository initialization

Once the FRAFOS repository is configured, administrator has to update CentOS package database on the system:

% yum makecache

Make sure that yum DB is successfully updated with FRAFOS repository content:

yum makecacheLoaded plugins: fastestmirrorLoading mirror speeds from cached hostfile

* base: centos...

* extras: ftp...

* updates: ftp......frafos-2.0-official | 2.9 kB 00:00frafos-2.0-official/filelists_db | 1.5 MB 00:01frafos-2.0-official/other_db | 182 kB 00:00...updates/other_db | 387 kB 00:02Metadata Cache Created

Important: If the package database is not successfully updated (e.g. could not get frafos-2.0-official info),contact FRAFOS support .

3.3. FRAFOS repository initialization 6

Chapter 4

FRAFOS ABC SBC installation

Before FRAFOS ABC SBC installation SELinux should be set to permissive or disabled mode:

• update /etc/selinux/config accordingly,

• from command line use setenforce 0 to set the mode on a running system temporarily.

Note: With SELinux configured in enforcing mode you may encounter various kind of problems (messagelogging, CDRs) so it is highly recommended not to use SELinux in this mode on machines running FRAFOSABC SBC.

Important: Please check Hardware specific configuration installation guide section before continuing the instal-lation. The recommended Mysql server setting have to be applied before installing the Sbc application.

FRAFOS ABC SBC is installed from repository using:

% yum install frafos-sbc

The installation process is non-interactive and all required packages are installed from standard CentOS orFRAFOS repositories.

For installation output details, administrator can check installation log file:

% less /var/log/yum.log

Important: In case of any error or problem during installation, contact FRAFOS support .

7

Chapter 5

FRAFOS ABC SBC initial configuration

5.1 SBC interfaces overview

FRAFOS ABC SBC uses for management and signaling four types of interfaces:

• XMI - External Management Interface - for GUI, SNMP, SSH and other services that should be accessibleoutside of the setup

• IMI - Internal Management Interface - used for inter-node communication (in HA pair node)

• SI - Signaling Interface - for SIP signaling (can be configured several SI interfaces)

• MI - Media Interface - for media (RTP) processing (can be configured several MI interfaces)

Important: Before initial FRAFOS ABC SBC configuration, it is important to have all the SBC interfacesconfigured and working (IP address and routing set) and also has set hostnames.

5.2 GUI interface (XMI) configuration

In order to enable GUI interface, initial XMI configuration is needed. Run:

% sbc-init-gui

Specify the IP address that will be used for XMI interface.

8


Error: If the IP address is not configured on the system, error dialog screen is shown. Enter a valid configuredIP address.

If the XMI configration is successful, administrator can access FRAFOS ABC SBC GUI interface using Webbrowser at configured IP address.

5.2. GUI interface (XMI) configuration 9

Chapter 6

Initial services configuration

Even if FRAFOS ABC SBC will not be deployed as high-availability (active/standby) cluster, service manager(pacemaker and monit) have to be configured with IMI interface. Script “sbc-ha-init” will guide you through thecman / corosync / pacemaker configuration:

% sbc-ha-init

Important:

1. If FRAFOS ABC SBC is deployed as cluster, both nodes has to be running and has to be accessible.

2. If any of the configuration step fails, contact FRAFOS support . In many cases, the problem is causedbecause the remote node is not accessible from the local host.

6.1 Deployment mode

First step is to configure deployment mode:

• Active/Standby pair mode

• Single mode - only one machine will be used

10


Important: There is no difference in following steps regarding single mode or HA pair mode on the first (onlyfirst) node setup. Every configuration step that has to be performed differently on the second node is noted in“Second node” subsection.

6.2 Hostnames and IMI addresses

6.2.1 First node

In following steps administator configure hostnames of node(s) and IP address(s) that will be used as IMI inter-faces.

• Local hostname - determined automatically from system

• Local IP address - local IMI IP address

• Remote hostname - hostname of the remote node (not configured in single mode)

• Remote IP address - remote IMI IP address (not configured in single mode)

6.2. Hostnames and IMI addresses 11


With these records (hostname, IP address), “/etc/hosts” file is updated.

6.2.2 Second node

Specify the correct hostnames and IP address with respect to this current (second node). E.g. local IP address - IPaddress on this second node used for IMI interface. Remote hostname and IP address should be same as for localhostname and IP address configured on first node.

6.3 Generate and distribute SSH keys

Generate SSH key for root user. This key is used for ssh access between both nodes.

6.3. Generate and distribute SSH keys 12


Important: do not specify any passphrase for the key.

Next the key is distributed to the remote machine.

6.4 Generate and distribute Corosync Authentication key

Corosync is a service that manage cluster nodes, their status, configuration etc. In order to corosync services onboth nodes can communicate to each other, authentication key has to be generated and distributed.

6.4. Generate and distribute Corosync Authentication key 13


6.4.1 First node

Note: This procedure may take serveral minutes...

When the authentication key is generated, it is distributed to the remote node.

6.4.2 Second node

Do not re-generate and distribute corosync authentication key - select “No”.

6.4. Generate and distribute Corosync Authentication key 14


6.5 Configuring cluster parameters and services

6.5.1 First node

In the next steps, CMAN and cluster configuration is automatically configured based on previously providedinformation, distributed to the remote machine and started. Administrator has to only confirm the steps.

Note: Initializing Pacemaker step may take some time...

At the end of this configuration process, administrator should see the confirmation dialog screen that configurationis successfully done...

6.5. Configuring cluster parameters and services 15


6.5.2 Second node

Do not re-generate and distribute cluster configuration file - select “No”.

6.5. Configuring cluster parameters and services 16


6.6 Second node configuration

In case of single node deployment, skip this step. For the second node configuration, repeat steps 5.1 - 5.5 on theremote machine with the attention to “Second node” subsections.

6.7 Cluster connection verification

Basic cluster configuration can be verified using:

% pcs status

Where both nodes should be seen Online:

[root@sbct2 ~]# pcs statusLast updated: Thu Jun 20 12:34:12 2013Last change: Thu Jun 20 12:12:21 2013 via cibadmin on sbct1tack: cmanCurrent DC: sbct1 - partition with quorumVersion: 1.1.9-123.el6-1.1.92 Nodes configured, unknown expected votes0 Resources configured.

Online: [ sbct1 sbct2 ]

Full list of resources:

Note: Be sure you have correctly configured iptables (firewall). CentOS iptables initial setting is very restrictive.

6.6. Second node configuration 17

Chapter 7

User accounts and login

7.1 Default users

By default, there are preconfigured user groups and accounts.

Default user groups:

• sbcusers - access to SBC related configuration (no rights to system configuration - networking, users,firewall etc.)

• sbcadmins - access to all configuration

Default users:

• sbcuser - password: Sbc.User!

• sbcadmin - password: Admin.SbC1?

• root - password equals to system root user

Important: It is highly recommended to change the default user accounts (remove or change password).

7.2 Configuring user accounts:

User accounts can be configured in GUI using System -> Users’ screen.

Note: Only “sbcadmin” and “root” users have rights to create or modify user accounts.

To create a new user, use ‘Create a new Webmin user’ link on Webmin Users page. Specify:

• Username

• Member of group (“sbcusers” or “sbcadmins”)

• Password

Additionally parameters like Inactivity logout time, IP access control and other restrictions can be set in ‘Securityand limits options’.

Important: For two nodes cluster deployment, users has to be configured on both nodes.

18

Chapter 8

FRAFOS ABC SBC license

By default, FRAFOS ABC SBC is installed with demo version, which is limited to 90s call duration and withoutany HA replication. Also features like transcoding and others are disabled.

FRAFOS issues license files according to the agreement between FRAFOS and customer.

License file has to be imported to SBC using ‘System -> License’ link. Using ‘Choose File’ button administratorselects the proper license file from local disk. After applying the changes, license file is automatically uploadedto the server and loaded.

Important: For two nodes cluster deployment, license file has to be imported on both nodes.

19

Chapter 9

System interfaces

System (network) interfaces can be configured either by manual editing network configuration files in CentOS orusing ‘System -> Networking’ screen.

To create/modify interface use ‘Network interfaces’ page. Several types, like simple system network interface(e.g. eth1), VLAN tagged interface (e.g. eth1.100) or bonded interface (e.g. bond0) can be configured and use inSBC configuration.

20

Chapter 10

SBC interfaces

As mentioned in SBC interfaces overview section, SBC uses four interfaces. So far (using GUI and HA initializa-tion scripts), XMI and IMI interfaces are configured.

For two nodes cluster deployment, Virtual IP addresses for signaling and media interfaces should be used.

10.1 Virtual IP address

Virtual IP address is used in two cluster node deployment and assigned to currently active node. Virtual IP isconfigured in ‘HA -> Virtual IP’ screen.

Administrator specifies System interface (e.g. eth1) and the Virtual IP address that should be assign to it.

10.2 Signaling and Media interfaces

Signaling (SI) and Media (MI) interfaces can be configured in ‘System -> Interfaces’ configuration screen.

SBC interface (not only SI or MI), is defined using:

• Interface name: internal unique identificator of the interface - [a-z, A-Z, 0-9]

21


• Interface type: Signaling, Media, External mgmt., Internal mgmt.

• Interface description: description (alias) for interface, that is used in GUI configuration

• System interface: system physical/logical interface (eth1, eth1.123 - VLAN tagged, bond1 - bonded inter-face)

• IP address: select box including system configured IP address and Virtual IP address configured for partic-ular system interface

• Ports: for SI - SIP port, for MI - RTP port range is specified

Important: When SBC interfaces are configured, GUI warning message with link to activate Network configu-ration is shown. No network/SBC interfaces changes are applied until ‘activate’ link is used. When the Networkconfiguration changes are applied, all services using network configuration are restarted (e.g. SIP and RTP pro-cesses, GUI and SNMP daemons etc..). This may cause service disruption!

Important: In two nodes cluster deployment, administrator has to configure interfaces on both nodes. Be carefullto use the same interface name (identificators) for same signaling interfaces on both nodes! This is important forsuccessful call restoration on the standby node - to use the same inbound/outbound SI and MI interfaces.

10.2. Signaling and Media interfaces 22

Chapter 11

SBC services status

After successfull SBC interface configuration, administrator can check the system status using ‘HA -> Status’screen.

It shows cluster (or single) node status with respect to cluster communication and services (resources) ststate.If everything is correct, then cluster contains two nodes, both are online. Resources (VIPs, ser, sems, ms-redis-server) are started on the active node.

From the node command line, status can be shown using:

% pcs status

Important: If not all services (resources) are correctly running, contact FRAFOS support .

23


24

Chapter 12

Hardware specific configuration

Depending on the hardware used for Sbc deployment, there may be some fine-tuning needed to get maximumperformance.

12.1 Network adapters

If Sbc is configured to work as RTP media relay and high number of concurrent calls is expected, a good choiceof hardware used is critical, specifically netwotk adapter used. The RTP media traffic means high packets persecond rates, with many small packets passing through. Some network adapters have bad throughput under suchconditions. Important things to consider when choosing a network adapter are:

• More receive and transmit packet queues are better. Each queue should be using separate interrupt.

• The adapter method of distributing packets to individual queuses should include not only IP addresses intothe “hash” calculation algorithm, but should include also IP packets port mumbers. (Otherwise the trafficmay end up in just one or two queues in case Sbc talking to other device on just one IP address.)

• The adapter should be able to buffer packets received and issue interrupt only after some amount of thepackets, or some time passed. This can be usually configured using “coalesce” adapter options.

There is a configuration file prepared to allow fine-tuning of settings related to network adapters:

% /etc/frafos/sbc-tunings.conf

The settings are applied after server is rebooted, or manually by running “sbc-tunings.sh” command. Systemadministrator may un-comment and edit the settings in config file, depending on particular hardware used. Thesettings are:

• Network interfaces on which a “receive packet steering” kernel feature should be enabled. Recommendedsetting is to enable it on network interface used as media interface.

• Ehernet adapter coalescing options and rx/tx ring parameters. These affect how many packet the adaptermay buffer before issuing an interrupt. There is no recommended setting, as the values highly depend onethernet adapter used.

• Network interfaces on which the individual interrupts for receive and transmit queues should be staticallybound to individual CPUs. If running on multi-CPU or multi-core platform, the recommended setting is toenable this option for all network interfaces used as media interface.

• Option to unload kernel modules for connection tracking, to disable connection tracking completely. Rec-ommended setting is to stop connection tracking, but also firewall rules used on Sbc have to be consideredas those may need connection tracking active. Note: the default firewall rules that come with Sbc do not useconnection tracking.

25


12.2 Mysql server settings

Depending on particular hardware used for Sbc installation, also these tuning options for better Mysql serverperformance may be usefull, specifically in case of frequent and many event records expected to be stored:

query_cache_type = 0query_cache_size = 0innodb_flush_log_at_trx_commit = 2innodb_file_per_tableinnodb_flush_method=O_DIRECTinnodb_log_file_size=1Ginnodb_buffer_pool_size=4G

System administrator should add the previous options to Mysql server configuration file “[mysqld]” section:

% /etc/my.cnf

The options can be tuned depending on server memory available.

Important: These Mysql server setting have to be applied before Sbc is installed, because they affect the waySbc database is created during installation.

12.3 Sbc threads number settings

The number of main Sbc “sems” process threads affects performance. It is important especially when trying to getmaximum number of concurrent calls or maximum calls per second rates from Sbc. The optimal settings dependquite a lot on number of CPU cores of the server used and also on the type of traffic being processed. As a generalrule, for high number of concurrent calls including RTP media with relatively low calls per second rate lowernumber of threads performs better, while for high calls per second rate with SIP only and no RTP media highernumber of threads performs better.

The default value for number of threads is 16. The recommended settings are:

• for SIP+RTP traffic use number of threads equal to number of CPU cores multiplied by 4

• for SIP only traffic (no media) use number of threads equal to number of CPU cores multiplied by 16

The threads number settings can be modified manually after logging to Sbc system by editing this file:

% /etc/frafos/templates/sems/sems.conf.tmpl

The section with the threads number settings is:

# PERFORMANCE TUNINGsession_processor_threads={{ sems.session_processor_threads | default (’16’) }}media_processor_threads={{ sems.media_processor_threads | default (’16’) }}sip_server_threads={{ sems.sip_server_threads | default (’16’) }}rtp_receiver_threads={{ sems.rtp_receiver_threads | default (’16’) }}

After modifying the values main Sbc “sems” process configuration file has to be re-created and applicationrestarted:

% sbc-create-config sems

% pcs resource disable sems; sleep 5; pcs resource enable sems

12.2. Mysql server settings 26

Chapter 13

FRAFOS support

email: [email protected]

phone: +493057706930

Vladimir Broz

Manager Support and Services

email: [email protected]

27

mailto:[email protected]

mailto:[email protected]

FRAFOS ABC SBC Installation Guide

Documents