BroadSoft Partner Configuration Guide Mediatrix

BroadSoft Partner Configuration Guide Mediatrix
BroadSoft Partner Configuration Guide
Mediatrix Sentinel SBC
October 2015
Document Version 1.2
9737 Washingtonian Boulevard, Suite 350
Gaithersburg, MD 20878
Tel +1 301.977.9440
WWW.BROADSOFT.COM
BroadWorks® Guide
Copyright Notice
Copyright©2015 BroadSoft, Inc.
All rights reserved.
Any technical documentation that is made available by BroadSoft, Inc. is proprietary and
confidential and is considered the copyrighted work of BroadSoft, Inc.
This publication is for distribution under BroadSoft non-disclosure agreement only. No
part of this publication may be duplicated without the express written permission of
BroadSoft, Inc., 9737 Washingtonian Boulevard, Suite 350, Gaithersburg, MD 20878.
BroadSoft reserves the right to make changes without prior notice.
Trademarks
Any product names mentioned in this document may be trademarks or registered
trademarks of BroadSoft or their respective companies and are hereby acknowledged.
This document is printed in the United States of America.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 2 OF 29
Document Revision History
Version
Reason for Change
1.1
Introduced document for Media5 Mediatrix Sentinel SBC version Dgw2.0.32.599 validation with
BroadWorks Release 21.sp1.
1.2
Edited and published document.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 3 OF 29
Table of Contents
1
Overview .............................................................................................................................................6
2
Interoperability Status ......................................................................................................................7
2.1
Verified Versions...........................................................................................................................7
2.2
Interface Capabilities Supported..................................................................................................8
2.3 Known Issues ............................................................................................................................ 11
3
Mediatrix Sentinel SBC Configuration ....................................................................................... 13
3.1
Configuration Method ................................................................................................................ 14
3.2
System Configuration ................................................................................................................ 14
3.2.1
3.3
Configure Network Interfaces .......................................................................................... 14
SIP Configuration....................................................................................................................... 16
3.3.1
Configure SIP Core Side .................................................................................................. 16
3.3.1
Configure SIP Access Side .............................................................................................. 19
3.4 Remote Survivability Configuration .......................................................................................... 22
Appendix A: Reference Mediatrix Sentinel SBC Configuration .................................................... 24
References ............................................................................................................................................... 29
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 4 OF 29
Table of Figures
Figure 1 Application Diagram................................................................................................................... 13
Figure 2 Configuration Concepts ............................................................................................................. 14
Figure 3 Mediatrix Sentinel Network Interfaces ...................................................................................... 14
Figure 4 Interface Configuration .............................................................................................................. 15
Figure 5 Signaling and Media Port Configuration ................................................................................... 16
Figure 6 SIP Peer Configuration for BroadWorks................................................................................... 17
Figure 7 Survivability Timer...................................................................................................................... 18
Figure 8 Core-Side Registration Configuration ....................................................................................... 18
Figure 9 SIP Access-Side Registration Configuration and Calling Rule ............................................... 20
Figure 10 Routing Ruleset for Local Survivability of Registering Devices............................................. 20
Figure 11 SIP Access-Side Non-Register Configuration and Calling Rule ........................................... 21
Figure 12 Routing Ruleset for Local Survivability of Non-Registering Devices .................................... 21
Figure 13 Remote Survivability Configuration......................................................................................... 23
Figure 14 Network Status......................................................................................................................... 24
Figure 15 Configure SBC ......................................................................................................................... 25
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 5 OF 29
1
Overview
This guide describes the configuration procedures required for the Media5 Mediatrix
Sentinel SBC for interoperability with BroadWorks.
The Mediatrix Senttinel SBC is an enterprise SBC that has been validated with
BroadWorks.
This guide describes the specific configuration items that are important for use with
BroadWorks. It does not describe the purpose and use of all configuration items on the
Mediatrix Sentinel SBC. For those details, see the SBC Service User Guide for Mediatrix
Sentinel Units [1] supplied by Media5.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 6 OF 29
2
Interoperability Status
This section provides the known interoperability status of the Media5 Mediatrix Sentinel
SBC with BroadWorks. This includes the version(s) tested, the capabilities supported, and
known issues.
Interoperability testing validates that the device interfaces properly with BroadWorks via
the Session Initiation Protocol (SIP) interface. Qualitative aspects of the device or device
capabilities not affecting the SIP interface, such as performance, are not covered by
interoperability testing. Requests for information and/or issues regarding these aspects
should be directed to Media5.
2.1
Verified Versions
The following table identifies the verified Media5 Mediatrix Sentinel SBC and BroadWorks
versions and the month/year the testing occurred. If the device has undergone more than
one test cycle, versions for each test cycle are listed, with the most recent listed first.
Compatible Versions in the following table identify specific Mediatrix Sentinel SBC
versions that the partner has identified as compatible so should interface properly with
BroadWorks. Generally, maintenance releases of the validated version are considered
compatible and are not specifically listed here. For any questions concerning
maintenance and compatible releases, contact Media5.
NOTE: Interoperability testing is usually performed with the latest generally available (GA)
device firmware/software and the latest GA BroadWorks release and service pack at the time the
testing occurs. If there is a need to use a non-verified mix of BroadWorks and device software
versions, customers can mitigate their risk by self-testing the combination themselves using the
BroadWorks Session Border Controller Interoperability Test Plan [5].
Verified Versions
Date (mm/yyyy)
BroadWorks Release
Mediatrix Sentinel
SBC Verified Version
Mediatrix Sentinel
SBC Compatible
Versions
10/2015
Release 21.sp1
Dgw2.0.32.599
Any maintenance
revisions of the
verified version.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 7 OF 29
2.2
Interface Capabilities Supported
The Media5 Mediatrix Sentinel SBC has completed interoperability testing with
BroadWorks using the BroadWorks Session Border Controller Interoperability Test Plan
[5]. The results are summarized in the following table.
The BroadWorks test plan is composed of packages, each covering distinct
interoperability areas, such as “Basic” call scenarios and “Redundancy” scenarios. Each
package is composed of one or more test items, which in turn, are composed of one or
more test cases. The test plan exercises the SIP interface between the device and
BroadWorks with the intent to ensure interoperability sufficient to support the BroadWorks
feature set.
The Supported column in the following table identifies the Media5 Mediatrix Sentinel
SBC’s support for each of the items covered in the test plan packages, with the following
designations:

Yes
Test item is supported

No
Test item is not supported

NA
Test item is not applicable to the device type

NT
Test item was not tested
Caveats and clarifications are identified in the Comments column.
NOTE: DUT in the following table refers to the Device Under Test, which in this case is the
Media5 Mediatrix Sentinel SBC.
BroadWorks Session Border Controller Interoperability Test Plan Support Table
Test Plan Package
Test Plan Package Items
Basic
Call Origination
Yes
Call Termination
Yes
Session Audit
Yes
Session Timer
Yes
Ringback
Yes
Forked Dialog
Yes
Early UPDATE
Yes
Early-Session
Yes
181 Call Being Forwarded
Yes
DTMF – Inband
Yes
DTMF – RFC 2833
Yes
DTMF – DTMF Relay
Yes
Third-Party Call Control – Basic
Yes
Third-Party Call Control – Advanced
Yes
Message Waiting Indicator –
Unsolicited
Yes
BroadWorks
Services
Supported
Comments
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 8 OF 29
BroadWorks Session Border Controller Interoperability Test Plan Support Table
Test Plan Package
Access Device
Services – Call
Control Services
Access Device
Services –
Registration and
Authentication
Test Plan Package Items
Supported
Message Waiting Indicator – Solicited
Yes
Voice Portal Outcall
Yes
Advanced Alerting
Yes
Calling Line ID – Non-Trusted
Endpoint
Yes
Calling Line ID with Unicode
Characters – Non-Trusted Endpoint
Yes
Calling Line ID – Trusted Endpoint
Yes
Calling Line ID with Unicode
Characters – Trusted Endpoint
Yes
Diversion Header
Yes
History-Info Header
Yes
Deny Calls from Unregistered Users
Yes
Enterprise Trunking – Originating
Trunk Group (OTG)
Yes
Enterprise Trunking – Destination
Trunk Group (DTG)
No
Enterprise Trunking –Trunk Group
(TGRP)
No
Call Waiting
Yes
Call Hold
Yes
Call Transfer
Yes
Local Conference
Yes
Network Conference
Yes
Call Forwarding
Yes
Registration – Register Authentication
Yes
Registration – Maximum Registration
Yes
Registration – Minimum Registration
Yes
Authentication – Invite Authentication
Yes
Authentication – Re-Invite or Update
Authentication
Yes
Authentication – Refer Authentication
Yes
Authentication – Access Device
Authenticating BroadWorks
Yes
SIP Trunk GIN Registration – GIN
Register
No
SIP Trunk GIN Registration – Call to
PBX User
No
Comments
Network Conference initiated
by a Polycom phone will be
supported in Dgw2.0.33.x
version.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 9 OF 29
BroadWorks Session Border Controller Interoperability Test Plan Support Table
Test Plan Package
Test Plan Package Items
Supported
SIP Trunk GIN Registration – Call
from PBX User
No
SIP TrunkPilot Registration – Pilot
Register
Yes
SIP TrunkPilot Registration – Call to
PBX User
Yes
SIP TrunkPilot Registration – Call
from PBX User
Yes
Surrogate Registration – Pilot
Register
Yes
Surrogate Registration – Call to PBX
User
Yes
Surrogate Registration – Call from
PBX User
Yes
G711 Fax Passthrough
Yes
G711 Fax Fallback
Yes
T38 Fax Messaging
Yes
Advanced Phone
Services – Busy
Lamp Field
Busy Lamp Field
Yes
Maximum Monitored Users
Yes
Advanced Phone
Services – Feature
Key Synchronization
Do Not Disturb
Yes
Call Forwarding
Yes
Call Center Agent Logon/Logoff
Yes
Call Recording
Yes
Security Classification
Yes
Line-Seize Events
Yes
Call-Info Events
Yes
Multiple Call Arrangement
Yes
Bridging
Yes
Advanced Phone
Services – Call
Recording
Call Recording Controls
Yes
Call Recording Video
Yes
Advanced Phone
Services – Security
Classification
Security Classification
Yes
Redundancy
DNS SRV Lookup
Yes
Register Failover/Failback
Yes
Invite Failover/Failback
Yes
Bye Failover
Yes
Call Origination
Yes
Call Termination
Yes
Access Device
Services – Fax
Advanced Phone
Services – Shared
Call Appearance
Video – Basic Video
Calls
Comments
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 10 OF 29
BroadWorks Session Border Controller Interoperability Test Plan Support Table
Test Plan Package
Video – BroadWorks
Video Services
Video – BroadWorks
Video Conference
Remote Survivability
IPV6
2.3
Test Plan Package Items
Supported
Call Hold
Yes
Call Transfer
Yes
Auto Attendant
Yes
Auto Attendant – HD
Yes
Voice Messaging
Yes
Network Conference
Yes
Network Conference – HD
Yes
Collaborate – Video
Yes
Collaborate – Video– HD
Yes
Register
Yes
Local Calls – Without Subscriber Data
Yes
PSTN Calls – Without Subscriber
Data
Yes
SCA Call – Without Subscriber Data
No
Register for Subscriber Data
No
Local Calls – With Subscriber Data
No
PSTN Calls – With Subscriber Data
No
SCA Call – With Subscriber Data
No
Call Origination
No
Call Termination
No
Ringback
No
Call Control
No
Registration with Authentication
No
T38 Fax Messaging
No
Busy Lamp Field
No
Redundancy
No
Video
No
Dual Stack with Alternate Connectivity
No
Comments
Known Issues
This section lists the known interoperability issues between BroadWorks and specific
partner release(s). Issues identified during interoperability testing and known issues
identified in the field are listed.
The following table provides a description of each issue and, where possible, identifies a
workaround. The verified partner device versions are listed with an “X” indicating that the
issue occurs in the specific release. The issues identified are device deficiencies or bugs,
so typically not BroadWorks release dependent.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 11 OF 29
The Issue Number is a tracking number for the issue. If it is a Media5 issue, the issue
number is from Media5’s tracking system. If it is a BroadWorks issue, the issue number is
from BroadSoft’s tracking system.
For more information on any issues related to the particular partner device release, see
the partner release notes.
Issue Description
-----
None.
Partner Version
Dgw2.0.32.599
Issue Number
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 12 OF 29
3
Mediatrix Sentinel SBC Configuration
This section describes the configuration settings required for the Mediatrix Sentinel SBC
integration with BroadWorks, primarily focusing on the SIP interface configuration. The
Mediatrix Sentinel SBC configuration settings identified in this section have been derived
and verified through interoperability testing with BroadWorks. For configuration details not
covered in this section, see the SBC Service User Guide for Mediatrix Sentinel Units [1] for
Mediatrix Sentinel SBC.
Figure 1 Application Diagram
Typically, the Sentinel is deployed as a premise-based Session Border Controller. It sits
at the edge of a corporate network, transparently handling all SIP-based traffics between
IP phones, IP PBX, soft clients, ATA and the BroadSoft core switch. It provides SIP
mediation for interoperability and security, service continuity by handling server failover
seamlessly, as well as local survivability during WAN failure.
Conceptually, the configuration of the Sentinel SBC involves the following:

Configuring Network interfaces (the LAN and the WAN, as well as the SIP port and
RTP ports).

Configuring BroadWorks SIP Peer also known as, Call Agent (CA), for example,
wan_ip_trunk_ca; this is the SIP Peer facing BroadWorks. This includes binding the
SIP peer to the corresponding SIP and RTP interface, and applying the corresponding
rulesets (actions based on conditions).

Configuring SIP Access (Local Users) Peer (local_users_ca, this is the SIP peer
facing local SIP access devices like IP phones and ATA. This includes binding the
SIP Peer to the corresponding SIP and RTP interface, and applying the
corresponding ruleset.

Add the Routing Rulesets to direct traffics between the BroadWorks SIP Peer and the
Local Users SIP Peer.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 13 OF 29
Figure 2 Configuration Concepts
3.1
Configuration Method
The Mediatrix Sentinel can be configured with a configuration file using the Trivial File
Transfer Protocol (TFTP), HTTP, HTTPS for download, or Command Line Interface (CLI)
or through its embedded web GUI.
Configuration Files
Mediatrix Sentinel Configuration Files
Description
MediatrixSentinel_Dgw_2.0.32.599_STN
L-MX-D2000-22.zip
Contains the device firmware load.
Configuration File Name:
Contains configurable parameters for the session
controller device.
No default name, it could be an arbitrary
name, for example, mydevice.cfg.
Ruleset Files: No default name
The Sentinel is pre-loaded with some rulesets in the
factory. BroadWorks specific rulesets can be
downloaded from the Media5 Support Portal
(http://www.media5corp.com/en/support).
Ruleset is the building block for the SBC functions.
One can also create ruleset from the unit’s web GUI with
its powerful embedded ruleset editor.
3.2
System Configuration
This section describes system configuration items required for the Mediatrix Sentinel.
3.2.1
Configure Network Interfaces
This section describes how to configure the Mediatrix Sentinel network interfaces.
Figure 3 Mediatrix Sentinel Network Interfaces
ETH1 = WAN Uplink(10/100/100BaseT)
ETH2-5 = LAN (10/100/1000BaseT, 4-port switch)
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 14 OF 29
Step
Command
Description
Step 1
Log into the Mediatrix Web GUI.
By default, LAN (ETH2-5) has default IP
address 192.168.0.10, Uplink (ETH1) is
defaulted to DHCP; dial *#*0 from a
phone to check the Uplink IP address.
Default username: “public”.
No Password.
Step 2
Go to Network->Interfaces page.
Configure Network interface settings.
Step 3
Go to Network->Host page.
Configure DNS, NTP.
Figure 4 Interface Configuration
3.2.1.1
Configure SIP and Media Ports
Once the network interfaces are configured, the next step is to create SIP and Media
Interface ports for the SIP Peers.
Step
Command
Description
Step 1
Go to SBC → Configuration page, the SIP port and
Media Port settings are in the Signaling Interface
Configuration section and Media Interface
Configuration section respectively.
Step 2
Hit the “+” button to create new interface if
necessary. In most cases, you can reuse the
default interfaces.
Step 3
Set the port number for SIP port.
0 is equivalent to 5060 in SIP
ports.
Step 4
Set the port number range for Media port.
By default, the range is UDP port
10000-20000.
Step 3
If the SIP or Media interface is behind a NAT
firewall, put the public IP address in the Public
Address column for near-end NAT Traversal
handling.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 15 OF 29
Figure 5 Signaling and Media Port Configuration
3.3
SIP Configuration
This section identifies the Mediatrix Sentinel configuration to enable SIP on the access
and core side of the SBC.
3.3.1
3.3.1.1
Configure SIP Core Side
Configure SIP Parameters
This section describes how to configure SIP parameters such as, timers and headers.
3.3.1.2
Step
Command
Step 1
SIP Timer is not user configurable in this
release. Header manipulation is handled by
the pre-defined rulesets (in the SIP Peer
configuration step).
Description
Configure BroadWorks SIP Peers
This section describes how to configure the Mediatrix Sentinel with BroadWorks
Application Server and Network Server peer(s). SIP Peer is also known as Call Agent in
Mediatrix term.
Step
Command
Description
Step 1
Go to SBC → Configuration webpage.
Step 2
Edit the Call Agent wan_ip_trunk_ca.
wan_ip_trunk_ca is the Call Agent
facing BroadSoft.
Step 3
Check the Enable box.
This will turn on the BroadWorks SIP
Peer.
Step 4
Bind the Signaling and Media Interface to
Uplink network interfaces.
In this example, BroadWorks SIP Peer
traffics will use the WAN link (uplink).
Step 5
Enter BroadWorks Proxy FQDN in the Peer
Host.
You may also put an IP address there.
Step 6
In the Call Agent Ruleset section, hit “+” to
add ruleset.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 16 OF 29
Step
Command
Description
Step 7
In the ruleset drop down, select
“bw_core_side_generic”
If the bw_core_side_generic ruleset is
not available in the drop down, go to
Media5 Support Portal or contact your
Media5 support.
Step 8
Hit “Save”
Figure 6 SIP Peer Configuration for BroadWorks
3.3.1.3
Configure Survivability (Blacklisting) Timer
This section describes how to configure the Mediatrix Sentinel SIP Peer monitoring
settings.
By default, these monitor parameters are all set to “0”, that is, disabled. If local
survivability is not required, you can leave these values as is.
If survivability is required, you can fine tune with the following parameters:

Keep-Alive Interval – Frequency of the SIP Option keep-alive message (for example,
30 seconds).

Blacklisting Duration – this is the minimum duration of a SIP Peer will remain down
(for example, 60 seconds).

Blacklisting Delay – Delay (in milliseconds) a SIP Peer is considered down after
expiration of the SIP timer (for example, 1 milliseconds).

Blacklisting Error Codes – SIP Error Codes which will put down the SIP Peer (for
example, 503, 604).
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 17 OF 29
Figure 7 Survivability Timer
3.3.1.4
Configure Registration
This section describes how to configure the Mediatrix Sentinel core-side registration
settings.
Normally, it is not required the Mediatrix Sentinel SBC to register with BroadSoft. The IP
phones and SIP access devices behind the SBC will register to BroadSoft via the Sentinel
SBC as the SIP Outbound Proxy.
If you must require the Mediatrix to register (for example, surrogate registration), use the
following steps.
Step
Command
Step 1
Go to SBC -> Registration page.
Step 2
Put the SIP account username in the
User Name field.
Step 3
Put the SIP Caller Name in the
Friendly Name field.
Step 4
Domain is the BroadWorks SIP
Domain.
Step 5
Build the SIP Contact URI in the
Contact field.
Step 6
Go to SBC → Configuration Page,
enable registration_ca.
Step 7
Modify the wan_ip_trunk_ca, add the
“uac_authentication_out” ruleset.
Description
The Contact URI is in the form:
sip:username@wan_ip_address_of_Sentinel,
for example, sip:8198298749@1.1.1.1.
In the parameter field, enter the SIP
authentication username and password, for
example,
USERNAME=8198298749 PASSWORD=1234.
Figure 8 Core-Side Registration Configuration
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 18 OF 29
3.3.1.5
Configure Failover/Failback for BroadWorks Redundancy
This section describes how to configure the Mediatrix Sentinel failover and failback
mechanism to support BroadWorks redundant Application Servers and Network Servers.
3.3.1
3.3.1.1
Step
Command
Step 1
No Configuration is needed if FQDN (DNSSRV) is used in the SIP Peer host
Description
Configure SIP Access Side
Configuration for Registering Devices
This section describes how to configure the Mediatrix Sentinel for registering access
device peers such as SIP phones.
Step
Command
Description
Step 1
Go to SBC -> Configuration web page.
Step 2
Edit the Call Agent local_users_ca.
Step 3
Set this Call Agent to Enable.
Step 4
Bind this Call Agent to its corresponding SIP
and Media Interface.
This is the SIP and RTP ports used
for local traffics.
Step 5
Set the Peer Network.
This is the subnet where all these
SIP phones and ATAs locate, for
example, 10.0.0.0/8 for all phones
in the Class A 10.x.x.x subnet.
Step 6
In the Call Agent Ruleset, hit “+” button to add a
new ruleset entry, select from the drop down
menu
“bw_local_reg_users_with_generic_survivability
” ruleset.
There are parameters to
accommodate short extension
dialing (in survivable mode). In the
following example, all the local
extensions have prefix 242111,
and the length of the extension is
4, hence the parameter
LOCAL_EXT_PREFIX=242111
EXT_DIGIT_LEN=4.
Step 7
Click Save.
Step 8
Go back to SBC -> Configuration page.
Step 9
Add the Routing Ruleset (hit the “+” button),
“bw_route_with_basic_local_survivability”
ruleset.
Step 10
Click Apply to complete.
local_users_ca is the Call Agent
facing SIP Phones and ATA sitting
on the local network.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 19 OF 29
Figure 9 SIP Access-Side Registration Configuration and Calling Rule
Routing Ruleset
Figure 10 Routing Ruleset for Local Survivability of Registering Devices
3.3.1.2
Configuration for Non-registering Devices
This section describes how to configure the Mediatrix Sentinel for access devices that do
not register. This configuration includes surrogate registration on behalf of the nonregistering access device and any special considerations for NAT traversal with a static
peer.
Step
Command
Step 1
Follow the Steps in 3.3.1.4 to configure surrogate
registration on behalf of the non-registering access
device.
Step 2
Go to SBC → Configuration webpage.
Step 3
Create a SIP Peer (Call Agent) for the nonregistering device; if it is an IP PBX, you can reuse
the “lan_ip_pbx_ca” call agent.
Step 4
Set the SIP and Media interface (you can simply
reuse the default lan_s and lan_m interface unless
you need different port number).
Step 5
Set the Peer Host IP address.
Step 6
Add the
“bw_surrogate_registration_or_pilot_number”
ruleset.
Step 7
Click Save to exit.
Description
This is the IP address of the nonregistering device (for example,
192.168.1.104).
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 20 OF 29
Step
Command
Step 8
Go back to SBC → Configuration page.
Step 9
Add the Routing Ruleset
“bw_route_surrogate_reg_or_pilot_number_trunk”
ruleset.
Description
You will need to set the Pilot
number in the parameter field, for
example,
PILOT_NUM=2404986200.
And if you are not using
lan_ip_pbx_ca Call agent as the
IP PBX SIP Peer, you need to
include DEST_CA parameter as
well, for example,
DEST_CA = second_ip_pbx_ca.
Step 10
Click Apply to complete.
Figure 11 SIP Access-Side Non-Register Configuration and Calling Rule
Routing Ruleset:
Figure 12 Routing Ruleset for Local Survivability of Non-Registering Devices
3.3.1.3
Configuration for GIN Registering Devices
This section describes how to configure the Mediatrix Sentinel for IP-PBX and PBX
trunking gateways that register the main line only via Generate Implicit Numbers (GIN)
registration. Users behind the PBX device are implicitly registered.
GIN is not supported.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 21 OF 29
3.3.1.4
Configuration for Pilot Registering Devices
This section describes how to configure the Mediatrix Sentinel for IP-PBX and PBX
trunking gateways that register the main line only but do not support GIN. Users behind
the PBX device are implicitly registered.
3.4
Step
Command
Description
Step 1
Follow the Steps 2-10 in 3.3.1.2
The registration of the pilot number is
coming directly from the IP PBX, so
Step 1 to set up registration on the
Sentinel is no longer required. The rest
is the same as surrogate registration
setup.
Remote Survivability Configuration
This section describes the settings necessary for remote survivability when the
BroadWorks server(s) cannot be reached for call control. In this case, the session
controller facilitates calls between users behind the SBC as well as off-net calls.
Step
Command
Step 1
Remote survivability to facilitate calls among
local users is turned on automatically by the
default rulesets applied to the BroadWorks
and local user SIP Peers. No configuration is
required.
Step 2
Off-Net calls through a local voice interface
port (either a FXO or PRI) is possible by
routing call to the trunk_lines_ca Call Agent
The setup is similar to the following
scenario with the local SIP Proxy.
Off-Net calls through a local SIP proxy
(FXO/PRI gateway) is possible by routing
calls to its corresponding Call Agent
For example, you can use a local FXO
or PRI gateway for PSTN access as a
backup. The following examples shows
a configuration on the Mediatrix
Sentinel. The trunk_lines_ca SIP Peer
is assigned with the IP of this external
SIP gateway. The traffics are routed to
this gateway when a WAN or softswitch
outage is detected.
Step 3
Description
Instead of routing the traffics to an
external gateway, the call is routed
internally to one of the Sentinel’s PRI or
FXO port. Loopback interface is used.
For more information, contact your
Media5 Support or the Media5 website.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 22 OF 29
Figure 13 Remote Survivability Configuration
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 23 OF 29
Appendix A: Reference Mediatrix Sentinel SBC Configuration
The following is a reference configuration for the Mediatrix Sentinel SBC and is configured
for use with BroadWorks.
1)
Assign Network Parameters to the corresponding interfaces.
Figure 14 Network Status
2)
Configure the SBC (under SBC → Configuration)
−
Configure the SIP and Media interface for both local (lan_s and lan_m) and
traffics to the BroadSoft core (uplink_s and uplink_m). You will be asked to
restart the SBC service if the SIP or Media interface is re-configured, just follow
the instruction on the web GUI.
−
Enable the wan_ip_trunk_ca SIP Peer (Call Agent) – for BroadWorks
i. Set Peer Host (FQDN or IP address of the BroadWorks Application
server or the SBC).
ii. Add bw_core_side_generic ruleset.
iii. Set Call Agent Monitoring parameters if local survivability is required.
−
Enable the local_users_ca SIP Peer (Call Agents) – for local SIP phones/ATAs
iv. Set the Peer Network (subnet of the LAN).
v. Add bw_local_reg_users_with_generic_survivability ruleset – this
ruleset seamlessly handles normal traffics as well as providing local SIP
phones calling service during survivability mode.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 24 OF 29
vi. If you want short extension dialing, set the following parameters and
apply them to the above ruleset:
1.
LOCAL_EXT_PREFIX – prefix of the local extensions.
2.
EXT_DIGIT_LEN – digit length of local extensions.
3.
The final parameter will look like (local extension in the form
240498xxxx):
LOCAL_EXT_PREFIX=240498 EXT_DIGIT_LEN=4
−
Add the routing ruleset bw_route_with_basic_local_survivability to direct traffics
between the BroadWorks and Local IP phones SIP peers.
Click Apply to finish up the configuration. The following screen shot appears.
Figure 15 Configure SBC
Configuration Script Example
##################################################
# Configuration Script.
# Automatically generated on 29/09/2015 16:08:20.
##################################################
# System Name
: Mediatrix Sentinel
# Firmware
: Dgw 2.0.32.599
# Profile
: STNL-MX-D2000-22
# MAC Address
: 0090f80a9e6d
# Serial Number : 000900000M346140010
# Description
: Automatically generated on 29/09/2015 16:08:20.
##################################################
# Initiate a unit reboot only if the new hardware settings require it.
Conf.RebootIfNeeded
# Eth Service
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 25 OF 29
Eth.Vlan.DeleteAllRows
# Hoc Service
Hoc.SntpConfigSource = "Static"
Hoc.StaticSntpServers[Priority=1].HostName = "time.nrc.ca"
Hoc.DnsServersConfigSource = "Static"
Hoc.StaticDnsServers[Priority=1].IpAddress = "8.8.8.8"
Hoc.StaticHosts.DeleteAllRows
# Bni Service
# NOTE: The following commands remove the network interfaces and add them back. It is highly
recommended that they are executed only when the unit is in a locked state (see
EpAdm.UnitForceLock). Not doing so might result in unexpected behavior from the current calls in
progress.
Bni.NetworkInterfaces.DeleteAllRows
Bni.AddNetwork Idx=2
Bni.AddNetwork Idx=3
Bni.AddNetwork Idx=4
Bni.NetworkInterfaces[Idx=1].InterfaceName = "Rescue"
Bni.NetworkInterfaces[Idx=2].InterfaceName = "Uplink"
Bni.NetworkInterfaces[Idx=3].InterfaceName = "UplinkV6"
Bni.NetworkInterfaces[Idx=4].InterfaceName = "Lan1"
Bni.NetworkInterfaces[Idx=1].LinkName = "eth1"
Bni.NetworkInterfaces[Idx=2].LinkName = "eth1"
Bni.NetworkInterfaces[Idx=3].LinkName = "eth1"
Bni.NetworkInterfaces[Idx=4].LinkName = "eth2-5"
Bni.NetworkInterfaces[Idx=3].ConnectionType = "Ip6AutoConf"
Bni.NetworkInterfaces[Idx=1].StaticIpAddr = "192.168.0.1/24"
Bni.NetworkInterfaces[Idx=2].StaticIpAddr = "24.37.217.140/27"
Bni.NetworkInterfaces[Idx=3].StaticIpAddr = ""
Bni.NetworkInterfaces[Idx=4].StaticIpAddr = "10.1.120.248/16"
Bni.NetworkInterfaces[Idx=2].StaticDefaultRouter = "24.37.217.129"
Bni.NetworkInterfaces[Idx=4].StaticDefaultRouter = "10.1.0.1"
Bni.NetworkInterfaces[Idx=2].Activation = "Enable"
Bni.NetworkInterfaces[Idx=4].Activation = "Enable"
Bni.NetworkInterfaces[Idx=1].Priority = "100"
Bni.NetworkInterfaces[Idx=4].Priority = "30"
# Lfw Service
Lfw.LocalRules.DeleteAllRows
Lfw.ApplyConfig
# Sbc Service
Sbc.CallAgent.DeleteAllRows
Sbc.AddCallAgent Id=1
Sbc.AddCallAgent Id=101
Sbc.AddCallAgent Id=102
Sbc.AddCallAgent Id=103
Sbc.AddCallAgent Id=104
Sbc.AddCallAgent Id=105
Sbc.AddCallAgent Id=106
Sbc.AddCallAgent Id=107
Sbc.CallAgent[Id=1].Name = "registration_ca"
Sbc.CallAgent[Id=101].Name = "trunk_lines_ca"
Sbc.CallAgent[Id=102].Name = "phone_lines_ca"
Sbc.CallAgent[Id=103].Name = "lan_ip_pbx_ca"
Sbc.CallAgent[Id=104].Name = "wan_ip_trunk_ca"
Sbc.CallAgent[Id=105].Name = "local_users_ca"
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 26 OF 29
Sbc.CallAgent[Id=106].Name = "remote_users_ca"
Sbc.CallAgent[Id=107].Name = "secondary_ip_trunk_ca"
Sbc.CallAgent[Id=104].Enable = "Enable"
Sbc.CallAgent[Id=105].Enable = "Enable"
Sbc.CallAgent[Id=1].SignalingInterface = "1"
Sbc.CallAgent[Id=101].SignalingInterface = "2"
Sbc.CallAgent[Id=102].SignalingInterface = "1"
Sbc.CallAgent[Id=103].SignalingInterface = "2"
Sbc.CallAgent[Id=104].SignalingInterface = "3"
Sbc.CallAgent[Id=105].SignalingInterface = "2"
Sbc.CallAgent[Id=106].SignalingInterface = "3"
Sbc.CallAgent[Id=107].SignalingInterface = "3"
Sbc.CallAgent[Id=1].MediaInterface = "1"
Sbc.CallAgent[Id=101].MediaInterface = "2"
Sbc.CallAgent[Id=102].MediaInterface = "1"
Sbc.CallAgent[Id=103].MediaInterface = "2"
Sbc.CallAgent[Id=104].MediaInterface = "3"
Sbc.CallAgent[Id=105].MediaInterface = "2"
Sbc.CallAgent[Id=106].MediaInterface = "3"
Sbc.CallAgent[Id=107].MediaInterface = "3"
Sbc.CallAgent[Id=102].Gateway = "phone_lines_gw"
Sbc.CallAgent[Id=1].PeerHost = "127.0.0.1:5060"
Sbc.CallAgent[Id=101].PeerHost = "10.1.120.232"
Sbc.CallAgent[Id=104].PeerHost = "as.iop1.broadworks.net"
Sbc.CallAgent[Id=105].PeerNetwork = "10.1.0.0/16"
Sbc.CallAgent[Id=1].ForceTransport = "None"
Sbc.CallAgent[Id=101].ForceTransport = "None"
Sbc.CallAgent[Id=102].ForceTransport = "None"
Sbc.CallAgent[Id=103].ForceTransport = "None"
Sbc.CallAgent[Id=104].ForceTransport = "None"
Sbc.CallAgent[Id=105].ForceTransport = "None"
Sbc.CallAgent[Id=106].ForceTransport = "None"
Sbc.CallAgent[Id=107].ForceTransport = "None"
Sbc.CallAgentRuleset.DeleteAllRows
Sbc.AddCallAgentRuleset Id=57
Sbc.AddCallAgentRuleset Id=76
Sbc.AddCallAgentRuleset Id=77
Sbc.CallAgentRuleset[Id=57].CallAgent = "101"
Sbc.CallAgentRuleset[Id=76].CallAgent = "105"
Sbc.CallAgentRuleset[Id=77].CallAgent = "104"
Sbc.CallAgentRuleset[Id=76].Priority = "10"
Sbc.CallAgentRuleset[Id=77].Priority = "8"
Sbc.CallAgentRuleset[Id=57].Ruleset = "trunk_lines_local_call"
Sbc.CallAgentRuleset[Id=76].Ruleset = "bw_local_reg_users_with_generic_survivability"
Sbc.CallAgentRuleset[Id=77].Ruleset = "bw_core_side_generic"
Sbc.CallAgentRuleset[Id=76].Parameters = "LOCAL_EXT_PREFIX=240498 EXT_DIGIT_LEN=4"
Sbc.RoutingRules.DeleteAllRows
Sbc.AddRouteRuleset Id=13
Sbc.RoutingRules[Id=13].Priority = "11"
Sbc.RoutingRules[Id=13].Ruleset = "bw_route_with_basic_local_survivability"
Sbc.SignalingInterface.DeleteAllRows
Sbc.AddSignalingInterface Id=1
Sbc.AddSignalingInterface Id=2
Sbc.AddSignalingInterface Id=3
Sbc.SignalingInterface[Id=1].Name = "loop_s"
Sbc.SignalingInterface[Id=2].Name = "lan1_s"
Sbc.SignalingInterface[Id=3].Name = "uplink_s"
Sbc.SignalingInterface[Id=1].NetworkInterface = "Loop"
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 27 OF 29
Sbc.SignalingInterface[Id=2].NetworkInterface = "Lan1"
Sbc.SignalingInterface[Id=3].NetworkInterface = "Uplink"
Sbc.SignalingInterface[Id=1].Port = "5060"
Sbc.SignalingInterface[Id=2].Port = "5060"
Sbc.SignalingInterface[Id=3].Port = "5060"
Sbc.MediaInterface.DeleteAllRows
Sbc.AddMediaInterface Id=1
Sbc.AddMediaInterface Id=2
Sbc.AddMediaInterface Id=3
Sbc.MediaInterface[Id=1].Name = "loop_m"
Sbc.MediaInterface[Id=2].Name = "lan1_m"
Sbc.MediaInterface[Id=3].Name = "uplink_m"
Sbc.MediaInterface[Id=1].NetworkInterface = "Loop"
Sbc.MediaInterface[Id=2].NetworkInterface = "Lan1"
Sbc.MediaInterface[Id=3].NetworkInterface = "Uplink"
Sbc.MediaInterface[Id=1].PortRange = "20000-20999"
Sbc.MediaInterface[Id=2].PortRange = "20000-20999"
Sbc.MediaInterface[Id=3].PortRange = "20000-20999"
Sbc.PeerMonitoring[Id=104].KeepAliveInterval = "30"
Sbc.PeerMonitoring[Id=104].BlackListingDuration = "60"
Sbc.PeerMonitoring[Id=104].BlackListingDelay = "1"
# Snmp Service
# Web Service
# Restart all the services that require it.
Scm.RestartRequiredServices
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 28 OF 29
References
[1] Media5 Corporation 2015. SBC Service User Guide for Mediatrix Sentinel Units,
Release Dgw2.0.32. Available from Media5 at www.media5corp.com.
[2] BroadSoft, Inc. 2015. BroadWorks Redundancy Guide, Release 21.0. Available
from BroadSoft at xchange.broadsoft.com.
[3] BroadSoft, Inc. 2015. BroadWorks SIP Access Interface Interworking Guide,
Release 21.0. Available from BroadSoft at xchange.broadsoft.com.
[4] BroadSoft, Inc. 2015. BroadWorks SIP Trunking Solution Guide, Release 21.0.
Available from BroadSoft at xchange.broadsoft.com
[5] BroadSoft, Inc. 2015. BroadWorks Session Border Controller Interoperability Test
Plan, Release 21.0. Available from BroadSoft at xchange.broadsoft.com.
BROADSOFT PARTNER CONFIGURATION GUIDE – MEDIA5 MEDIATRIX SENTINEL SBC
2015 BROADSOFT INC.
©
20-BD5492-00
PAGE 29 OF 29
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising