This document outlines the configuration best practices for the Ribbon QSBC when deployed in Access Network with End Points and BroadSoft with both Hosted and Premise mode.
Ribbon QSBC is a network element deployed to protect SIP based Voice over Internet Protocol (VoIP) networks. Early deployments of SBCs were focused on the borders between two service provider networks in a peering environment. This role has now expanded to include significant deployments between a service provider's access network and a backbone network to provide service to residential and/or enterprise customers.
BroadSoft is a platform for Unified Communications as a Service.
It is not the goal of this guide to provide detailed configurations that will meet the requirements of every customer. Use this guide as a starting point and build the QSBC and BroadSoft configurations in consultation with network design and deployment engineers.
This is a technical document intended for telecommunications engineers with the purpose of configuring Ribbon QSBCs in Access Deployment with BroadSoft. Steps will require navigating the Product Guide as well as the Operations Guide. Understanding the basic concepts of TCP/UDP, IP/Routing, and SIP/RTP is needed to complete the configuration and any necessary troubleshooting.
This configuration guide is offered as a convenience to Ribbon customers. The specifications and information regarding the product in this guide are subject to change without notice. All statements, information, and recommendations in this guide are believed to be accurate but are presented without warranty of any kind, express or implied, and are provided “AS IS”. Users must take full responsibility for the application of the specifications and information in this guide.
The sample configuration in this document uses the following equipment and software:
|BroadSoft||BroadSoft Network Server||Rel_22.0_1.1123|
|BroadSoft Application Server & MS||Rel_22.0_1.1123|
This section covers the QSBC deployment topology and the Interoperability Test Lab Topology.
The following lab topology diagram shows connectivity between Broadsoft and Ribbon QSBC.
|SSH login to the QSBC|
1. Create Vnet for both the realms.
Replace "x.x.x.x" with the SBC's Ethernet interface (eth) Gateway IP address (example eth2 IP) and "y.y.y.y" with the SBC's Ethernet interface (eth) Gateway IP address (example eth3 IP).
2. Create the realm and associate it to the Vnet created above.
Replace "x.x.x.x" with the SBC's Ethernet interface (eth) IP address (example eth2 IP), and "y.y.y.y" with its netmask.
Provide mediapool id configured in mdevices.xml (example medpool 1).
Replace "c.c.c.c" with the SBC's Ethernet interface (eth) IP address (example eth3 IP), and "y.y.y.y" with its netmask.
Provide mediapool id configured in mdevices.xml (example medpool 2).
3. Create the endpoints.
The endpoints can be created dynamically or statically.
The endpoint in QSBC for the real phones are created dynamically, hence the following configuration should be done.
The Broadsoft Application server and Network server will be added as static endpoints. The static endpoints can be created as follows.
Replace "x.x.x.x" with Broadsoft Network server ip and p with port. Replace "y.y.y.y" with BroadSoft Application server Ip and "p" with port info.
We can have two different "p" for the same endpoint if using two different port values.
4. Add calling plan and calling route with QSBC peer to peer mode (will not be needed for hosted scenario).
1. Clear the DNS cache.
2. Configure QSBC For SRV Query only at endpoint level.
Where proxy2 is Broadsoft Application server endpoint name and proxy1 is Network server endpoint name with <uport> as 1.
3. Create a zone file to resolve the Ip's of Broadsoft Application server and Broadsoft Network server.
Example for DNS zone file with SRV record:
Replace "x.x.x.x" with Broadsoft Primary Application server Ip and "y.y.y.y" with Broadsoft Secondary Application server IP.
Replace "t.t.t.t" with your DNS IP and "z.z.z.z" with Broadsoft Network server IP.
Replace broadsoft.com with domain name of Broadsoft Application server, and replace ns1 with Broadsoft Network server domain name.
If issues occur during the license upload, manually copy the license file "iserverlc.xml" to /usr/local/nextone/bin/ location in QSBC, and restart it using "ist;iss".
SBCs must direct SIP requests to the BroadWorks Network Server to determine the hosting Application Server for the user. The Network Server responds to the SBC’s request with a 302 Redirect, and the 302 supplies the Application Server address, hence SBC will send the request to the Application server.
All requests inbound to the SBC from BroadWorks will originate from the Application Server, so the SBC must be configured to accept requests from Application Server address.
The following are the configurations to work in a hosted setup environment, where the initial signal goes to Network Server and then to AS.
1. Create an IEdge group for the Redirect Server using the following command.
With this command, you are adding one IEdge group on your SBC.
<iedge group name> is the name you want to assign to the group you are creating.
2. Assign the Redirect Server endpoint to the IEdge group you just created using the following command.
where: proxy1 <uport> identifies the Redirect Server endpoint and <iedge group name> identifies the IEdge group you just created for it.
3. For the Application Server endpoint pointed to by the Request-URI in incoming messages, set the netserver_group option to the IEdge group for the Redirect Server using the following command
where: proxy2 <uport> identifies the Application Server endpoint and <iedge group name> is the IEdge group for the Redirect Server to which the incoming.
QSBC - BroadSoft Premise Scenario Configuration
The SBC sends SIP requests directly to the BroadWorks Application Server. All requests inbound to the SBC from BroadWorks originate from the Application Server, so the SBC must be configured to accept requests from Application Server address.
For Premise setup, disable the netserver_group configuration on AS endpoint using the following command:
Refer to Section C for advanced scenario configuration.
Follow the sequence below to configure BroadSoft.
Enter the credentials and click login.
From the Broadsoft home page:
Click on Assign Services to assign or un-assign services and service packs for a user. If a service or service pack is unassigned the service data that has been filled out will be lost.
Use this page to display the service packs and individual services available to be assigned to a user.
Using this page, you can also:
Assign service packs to a user
Un-assign service packs from a user
Ensure all the required services like Authentication and supplementary services like Call Forwarding, Call Transfer, Call Waiting, etc. are assigned to the user.
Navigate to Profile > Users > Utilities and select Authentication.
Use this screen to change the user's authentication password. This password is used to authenticate an IP phone, which allows calls to be made over Internet Protocol (IP) based networks.
The authentication password and username can be different from the system password and user ID that are used at initial system login. While you can choose to use the same name and password for authentication and initial login, they allow access to different services. The password restrictions may differ.
As required, enable or disable the services to handle the incoming calls by navigating to Profile > Users > Incoming Calls.
This page displays menu items used to handle incoming calls. You can activate or deactivate some services by turning them on or off on the page for the service. To access these pages, click on the link for that service.
Ensure QSBC SipSg IP (configured towards Broadsoft) is allowed in the Network server in order to receive 3xx Redirect response with multiple AS FQDNs in Contact header. Open the browser and enter Broadsoft Network Server IP.
Provide the admin username and password, and click Login.
Navigate to Network > Routing NEs, and click Add.
This page allows the user to add routing network elements (NEs). Once added, the routing NE appears on the Routing NEs page.
A routing NE is a network element that provides connectivity to remote networks, for example, the PSTN. A routing NE is a system provider-owned device. It can either be a network gateway or a proxy server used to "front" network gateways.
Navigate to Network > Routing NE Addrs, and click Add.
From this screen, add routing network element (NE) addresses. Once added, the routing NE address displays on the Routing NE Addrs screen.
Execute the following commands to relay SUBSCRIBE messages with Auth header.
Execute the following commands so that QSBC goes for a SRV query.
Take TCP dump to capture DNS query on QSBC.
Execute the following commands to relay REFER messages with Auth header.
Execute the following command to disable the session expires timer.
Execute the following command to change the session expires timer and min-sec timer.
For Network Conference, add the FMM to have FQDN instead of IP in "REFER-TO" header of out going (towards BSFT) REFER message.
File fmmConfiguration.fmm has the following FMM:
Copy the file “fmmConfiguration.fmm” on Q-SBC let say at /usr/local/nextone/fmm/ fmmConfiguration.fmm
Run the following commands:
Execute the following commands to modify the expires header and min sec header.
Execute the following command to change the port.
Execute the following command to increase the size of sip message buffer.
|1||Basic Registration with Authentication|
|2||Basic Registration with reg-key|
|3||3xx Response handling with maddr|
|9||Music on Hold|
|11||Local Ringback followed by Remote Ringback|
|14||Anonymous call: Trusted and Non-trusted endpoint|
|15||Calling Name with Unicode Characters|
|16||DIVERSION Header: Single and Multiple Redirects|
|25||DNS SRV query|
This detailed reference configuration guide describes the configuration steps for the Ribbon QSBC in Access deployment with Broadsoft Application Server in Hosted and Premise mode.