SBC 1000/2000 Series Configuration Guide with Lync 2013

Transcription

SBC 1000/2000 Series Configuration Guide
with
Lync 2013 for Belgacom SIP Trunk
Deployments
Application Notes v1.0
P/N 550-06385 SBC1000
Last Updated: January 12, 2015
Sonus – Network Design Group
1
1.1
2
Document Overview ...................................................................... 4
Overview ................................................................................................................................. 4
Introduction .................................................................................... 5
2.1
Audience ................................................................................................................................. 5
2.2
Requirements .......................................................................................................................... 5
2.3
Reference Configuration ......................................................................................................... 6
2.3.1
Network Topology ............................................................................................................... 6
3
Configuring Sonus SBC 1000 and SBC 2000 Series ..................... 7
3.1
SBC Configuration Diagram.................................................................................................... 7
3.2
External Peer Side SBC Configuration ................................................................................... 7
3.2.1
Node Interfaces ................................................................................................................... 7
3.2.2
SIP profile .......................................................................................................................... 10
3.2.3
Media Profile ..................................................................................................................... 11
3.2.1
SIP Server Tables ............................................................................................................. 13
3.2.1
Hosts Table ....................................................................................................................... 13
3.2.2
Signaling Groups ............................................................................................................... 14
3.2.3
Call Routing Table ............................................................................................................. 15
3.2.4
Transformation Tables ...................................................................................................... 16
3.3
Internal Side SBC configuration ............................................................................................ 17
3.3.1
Node Interfaces ................................................................................................................. 17
3.3.2
SIP Profile ......................................................................................................................... 19
3.3.3
Media Profiles .................................................................................................................... 20
3.3.4
Signaling Group ................................................................................................................. 22
3.3.5
Sip Server Table ................................................................................................................ 23
3.3.6
3.3.7
3.4
Fax SBC configuration .......................................................................................................... 27
3.4.1
Node Interfaces ................................................................................................................. 27
3.4.2
SIP profile .......................................................................................................................... 29
3.4.3
Media Profiles .................................................................................................................... 30
3.4.4
SIP Server Tables ............................................................................................................. 32
3.4.5
Signaling Groups ............................................................................................................... 33
3.4.6
3.4.7
Copyright © 2015, Sonus and/or its affiliates. All rights reserved.
2 of 46
4
Lync Server 2013 configuration ................................................... 36
4.1
Lync 2013 Configuration Settings ......................................................................................... 36
4.1.1
This section covers the addition of the SBC into the Lync Server. ................................... 36
4.1.2
This section covers adding the SBC to the Lync Server 2013 routing. ............................. 40
5
SBC and Lync 2013 Specific Configurations ............................... 43
5.1
Initial Setup for All Calls ........................................................................................................ 43
5.1.1
Calling number manipulation ............................................................................................. 43
5.1.2
Called number ................................................................................................................... 43
5.2
Initiating Transfers with REFER ............................................................................................ 43
5.2.1
Call transfer via REFER method ....................................................................................... 43
5.3
Initiating Transfers with Re-INVITE ...................................................................................... 44
5.3.1
Call transfer via Re-Invite method ..................................................................................... 44
5.4
Call Hold................................................................................................................................ 44
5.4.1
Call Hold via RFC3264 ...................................................................................................... 44
5.5
Media System Configuration ................................................................................................. 45
6
Exceptions ................................................................................... 45
6.1
Lync 2013 Exceptions ........................................................................................................... 45
6.1.1
302 Moved temporarily ...................................................................................................... 45
6.2
SBC1000 Exceptions ............................................................................................................ 45
6.2.1
Fax V.34 ............................................................................................................................ 45
6.3
Customer Exceptions ............................................................................................................ 46
6.3.1
Calls using G.729 codec ................................................................................................... 46
6.3.2
Fax V.34 ............................................................................................................................ 46
3 of 46
1
Document Overview
These Application Notes describe the configuration steps required for the Sonus Session Border Controller
(SBC) 1000 and SBC 2000 to interoperate with the Lync 2013 system and a SIP trunk group to PSTN.
The objective of the document is to describe the configuration procedures to be followed during interoperability
testing of SBC 1000 and SBC 2000 with Lync 2013 server over SIP trunk to PSTN.
For additional information on Sonus SBC 1000 and SBC 2000 series, visit http://www.sonus.net
For additional information on Lync 2013, visit http://www.microsoft.com
1.1 Overview
The Sonus SBC 1000 and SBC 2000 session border controllers have been designed to use the same application
software, boot image and Survivable Branch Appliance software. They differ in the number of physical Ethernet
connections and processing power but are otherwise viewed from a software standpoint as being the same.
With this in mind, this particular effort was tested with an SBC 1000 but is fully applicable to an SBC 2000.
4 of 46
2 Introduction
This document provides a configuration guide for Sonus SBC 1000 Series (Session Border Controller) when
connecting to a SIP trunk group and a Lync 2013.
The Sonus SBC 1000 and SBC 2000 are Session Border Controllers that connects disparate SIP trunks, SIP
PBXs, and communication applications within an enterprise. The SBC can also be used as a SIP routing and
integration engine.
The Sonus SBC is the point of connection between the SIP trunk group to PSTN and the Lync 2013.
2.1 Audience
This technical document is intended for telecommunication engineers with the purpose of configuring the Sonus
SBC 1000 and SBC 2000 and aspects of the SIP trunk group together with Lync 2013 product. There will be
steps that require navigating the third-party and Sonus SBC Command Line Interface (CLI). Understanding the
basic concepts of IP/Routing and SIP/RTP is also necessary to complete the configuration and for
troubleshooting, if necessary.
This configuration guide is offered as a convenience to Sonus 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.
Technical support on SBC 1000 and SBC 2000 can be obtained through the following:

Phone: +1 888-391-3434 (Toll-free) or +1 978-614-8589 (Direct)

Web: http://www.sonus.net/company/maintenance/log-trouble-tickets
2.2 Requirements
The following equipment and software was used for the sample configuration provided:
Sonus Equipment
Type
Version
SBC 1000
SBC 1000
3.2.1 Build 322
3rd Party Equipment
Type
Version
Microsoft Lync 2013
Polycom CX600
Lync Edition
Polycom CX500
Lync Edition
Venta Fax
Mediation Server
5.0.8308.420
SIP Phone
4.0.7577.4066
SIP Phone
4.0.7577.4100
Fax softphone
7.3.227.568 I
5 of 46
2.3 Reference Configuration
A simulated enterprise site consisting of a Lync 2013 and a SIP trunk group to PSTN connected over the SBC
1000. The SBC 1000 was running software version 3.2.1 Build 322 during testing.
2.3.1 Network Topology
Lync 2013
Sonus
SBC 1000
Internal IP Network
Belgacom
Figure 1: Network Topology
The figure above represents the equipment used for the integration and certification testing. The SBC 1000 is
used to route and facilitate calls between the PSTN and the Lync 2013 system.
The SBC 1000 under test has 2 Ethernet ports configured. The SBC 2000 can have up to 4 physical Ethernet
ports and two physical T1/E1 ports. For more information on Media port deployment options or other network
connectivity queries, refer to the SBC 1000 Network Deployment Guide or contact your local Sales team for
information regarding the Sonus Network Design professional services offerings.
6 of 46
3 Configuring Sonus SBC 1000 and SBC 2000 Series
The SBC 1000 and SBC 2000 share a common code base and user interface. In this example, we are using an
SBC 1000.
3.1 SBC Configuration Diagram
Internal
10.35.180.136:5060
External
Signaling Group: To/From MS Lync 2013
Call Routing: To Lync 2013
Lync 2013
Signaling Group: To/From Belgacom
Call Routing: To PSTN
10.35.177.226:5060
216.110.2.230:5060
Lync 2013 Signaling Group
195.13.30.54:5060
SIP over TCP
SIP over UDP
Belgacom
SIP over UDP
Fax
10.35.137.39:5060
Call Routing: To Fax
Figure 2: SBC 1000 SIP Trunk Diagram
The above diagram also shows an optional Fax configuration. There are several ways to implement a fax
setup into a network; above is the scenario that was tested.
The Fax Trunk Group can share the same SIP signaling interface on the SBC.
3.2 External Peer Side SBC Configuration
3.2.1 Node Interfaces
The Sonus SBC 1000 allows you to configure the Identification information, Physical Data Layer, and Networking
Layer for the Ethernet ports. If you want to change the IP Address, you must configure the associated Logical
Interface or use the Modify Ethernet IP task found under the Tasks tab.
Below are the settings for the Ethernet connection between the Sonus SBC 1000 and Public internet.
7 of 46
3.2.1.1
Node Ports
Figure 3 External Port
8 of 46
3.2.1.2
Node Interfaces
Figure 4 Logical Interface
9 of 46
3.2.2 SIP profile
SIP Profiles control the how the Sonus SBC 1000/2000 communicates with SIP devices. They control important
characteristics such as: session timers, SIP header customization, SIP timers, MIME payloads, and option tags.
Below is the default SIP profile used for the SBC 1000 for this testing effort.
Figure 5: SIP profile
10 of 46
3.2.3 Media Profile
Media Profiles allow you to specify the individual voice and fax compression codecs and their associated
settings, for inclusion in a Media List. Different codecs provide varying levels of compression, allowing one to
reduce bandwidth requirements at the expense of voice quality. Below is the media profile used for the SBC
1000 and is for reference only.
3.2.3.1
Media Lists
Figure 6 :Media List
11 of 46
3.2.3.2
Voice Codec Profiles
Below are the voice codec profiles used for the SBC 1000 in this testing effort.
Figure 7: Voice codec configuration Default G711A
Figure 8: Voice codec configuration Default G729 20ms
Figure 9: Voice codec configuration T.38 support
12 of 46
3.2.3.3
SIP Server Tables
SIP Server Tables contain information about the SIP devices connected to the Sonus SBC 1000/2000.
The entries in the tables provide information about the IP Addresses, ports, and protocols used to
communicate with each server. The Table Entries also contain links to counters that are useful for
troubleshooting.
Figure 10: SIP Server table
3.2.1
Hosts Table
The Hosts Table feature allows you to edit the /etc/hosts file from the WebUI or through a REST interface. Each
line in the hosts file contains one IP address and at least one host name.
Hosts File Example:
127.0.0.1 localhost testux218
192.168.199.15 anon.who.com
192.168.72.99 somemachine.anywhere.com
192.168.99.215 anothermachine.nowhere.net
This allows applications on the Sonus SBC 1000/2000, such as SIP Signaling Groups, AD, RADIUS, etc to
resolve FQDNs when a DNS server is not reachable. We recommend that only a few, very critical, host-IP pairs
be stored on the Sonus SBC 1000/2000.
Figure 11: SIP Host table
13 of 46
3.2.2 Signaling Groups
Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared
configuration. They are the entity to which calls are routed, as well as the location from which Call Routes are
selected. They are also the location from which Tone Tables and Action Sets are selected. In the case of SIP,
they specify protocol settings and link to server, media and mapping tables.
Figure 12: SIP Signaling Group to Belgacom
14 of 46
3.2.3 Call Routing Table
Call Routing allows calls to be carried between signalling groups, thus allowing calls to be carried between ports,
and between protocols (like ISDN to SIP). Routes are defined by Call Routing Tables, which allow for flexible
configuration of which calls are carried, and how they are translated. These tables are one of the central
connection points of the system, linking Transformation Tables, Message translations, Cause Code Reroute,
Tables, Media Lists and the three types of Signaling Groups (ISDN, SIP and CAS).
Figure 13: Call Routing Table PSTN to Lync 2013
15 of 46
3.2.4 Transformation Tables
Transformation Tables facilitate the conversion of names, numbers and other fields when routing a call. They
can, for example, convert a public PSTN number into a private extension number, or into a SIP address (URI).
Every entry in a Call Routing Table requires a Transformation Table, and they are selected from there. In
addition, Transformation tables will be configurable as a reusable pool that Action Sets can reference.
Figure 14: Transformation Table Match +322797185X
16 of 46
3.3 Internal Side SBC configuration
Below are the settings for the Ethernet connection between the Sonus SBC 1000 and Lync2013.
3.3.1.1
Node Ports
Figure 15: Node Port
17 of 46
3.3.1.2
Node Interfaces
Figure 16: Logical Interface
18 of 46
3.3.2 SIP Profile
19 of 46
3.3.3 Media Profiles
3.3.3.1
Media Lists
Figure 18: Media List
20 of 46
3.3.3.2
Voice Codec Profiles
Below are the default voice codec profiles used for the SBC 1000 in this testing effort.
Figure 20: Voice codec configuration Default G711u
21 of 46
3.3.4 Signaling Group
Figure 21: Signaling Group
22 of 46
3.3.5 Sip Server Table
SIP Server Tables contain information about the SIP devices connected to the Sonus SBC 1000/2000. They in
essence emulate a traditional ‘SIP trunk group’. The entries in the tables provide information about the IP
Addresses, ports, and protocols used to communicate with each server. The Table Entries also contain links to
counters that are useful for troubleshooting.
Figure 22: Sip Server Table
23 of 46
Figure 23: SIP Call Routing Table To PSTN
24 of 46
Figure 24: Transformation Table Match Belguim National
Figure 25: Transformation Table Match +1212588102X
25 of 46
Figure 26: Transformation Table Match +1212588102X Redirected
Figure 27: Transformation Table Match ALL Redirected
26 of 46
3.4 Fax SBC configuration
Below are the settings for the Ethernet connection between the Sonus SBC 1000 and Fax.
3.4.1.1
Node Ports
Figure 28: Node Port
27 of 46
3.4.1.1 Node Interfaces
Figure 29: Logical Interface
28 of 46
3.4.2
SIP profile
29 of 46
3.4.3
Media Profiles
3.4.3.1
Media Lists
Figure 31: Media List
30 of 46
3.4.3.1 Voice Codec Profiles
Below are the voice codec profiles used for the SBC 1000 in this testing effort.
Figure 33: Voice codec configuration Default G729 20ms
Figure 34: Voice codec configuration T.38 support
31 of 46
3.4.4 SIP Server Tables
SIP Server Tables contain information about the SIP devices connected to the Sonus SBC 1000/2000. The
entries in the tables provide information about the IP Addresses, ports, and protocols used to communicate with
each server. The Table Entries also contain links to counters that are useful for troubleshooting.
Figure 35: SIP Server Table
32 of 46
3.4.5 Signaling Groups
Figure 36: Signaling Groups
33 of 46
Figure 37: Signaling Groups
34 of 46
Figure 38: Transformation Table Match +3227971855
35 of 46
4 Lync Server 2013 configuration
This section assumes that the Lync Server components have been installed along with Lync users. The user
should be familiar with Lync Server Topology Builder, Lync Server Control Panel and Lync Server management
Shell. This section does not cover the basic installation of Lync Server 2013.
4.1 Lync 2013 Configuration Settings
4.1.1 This section covers the addition of the SBC into the Lync Server.
The Lync Server topology needs to be modified by adding the SBC as a Gateway device. The Gateway device
will be the interface to the Verizon SIP Trunk.
1. Open Lync Server Topology builder and load the current topology.
2. Expand the topology and right click on the ‘PSTN Gateways’ link in the left hand pane. Select “New
IP/PSTN Gateway…” from the menu as shown and follow thru with the process.
36 of 46
Figure 39: Create New Gateway
37 of 46
Figure 40: Define the FQDN of the Gateway
38 of 46
Figure 41: Enable IPV4/IPV6
39 of 46
Figure 42: Define Trunk Port and Protocol
4.1.2 This section covers adding the SBC to the Lync Server 2013 routing.
In order for Lync Server 2013 to send calls to the Verizon SIP Trunk the SBC will have to be added to the
Routing.
1. Open Lync Server Control Panel and click on the Voice Routing link on the left hand pane.
2. Click on the Route tab on top of the right hand pane and scroll down to show the dialog below:
40 of 46
Figure 43: Add Routing
41 of 46
Figure 44: Select Trunk
Ensure the SBC is highlighted in the dialog shown above and click “OK’. At this point commit these changes to
the topology.
42 of 46
5 SBC and Lync 2013 Specific Configurations
Depending upon the type of call scenario desired will determine what settings are required for the SBC and
Microsoft Lync 2013 product.
5.1 Initial Setup for All Calls
5.1.1 Calling number manipulation
Transformation tables were required for the purpose of mapping preconfigured Lync 2013 user extensions to
established Belgacom SIP Trunk DIDs. This is not expected to be a requirement for deployment scenarios.
5.1.2 Called number
Normal calling pattern was to dial all digits in E.164 format for both national and international calls. Other dialing
patterns tested include Emergency calls.
5.2 Initiating Transfers with REFER
5.2.1 Call transfer via REFER method
Microsoft Lync Server 2013 needs additional configuration in order to enable SIP REFER Method. Refer support
needs to be set to Enable sending refer to gateway under Trunk Configuration profile assigned to the appropriate
SBC trunk.
43 of 46
Figure 45: Sip Server Table
5.3 Initiating Transfers with Re-INVITE
5.3.1 Call transfer via Re-Invite method
Transferring a call to another phone number is supported via the RFC3261 method. No special flag is required to
be set for this method. Ensure that on MS Lync 2013 under the “Trunk Configuration” element that REFER
support is set to “none”.
5.4 Call Hold
5.4.1 Call Hold via RFC3264
Placing a call on hold is via the RFC3264 method. This method is the preferred method for connections on
Belgacom SIP Trunks. This method involves sending a Re-INVITE with the parameter “a=inactive”. No special
flag is required to be set for this method.
44 of 46
5.5 Media System Configuration
Media port range was set with range from 10000-10020 for security purposes. This is not expected to be a
requirement for deployment scenarios
Figure 46: Media System Configuration
6 Exceptions
6.1 Lync 2013 Exceptions
6.1.1 302 Moved temporarily
Lync 2013 server will not send 302 Moved Temporarily towards the SBC, hence this method is not supported
according Microsoft Lync Interop Specification.
6.2 SBC1000 Exceptions
6.2.1 Fax V.34
Fax V.34 transmission is not supported over T.38v0
45 of 46
6.3 Customer Exceptions
6.3.1 Calls using G.729 codec
Test using G.729 in direction PSTN to PBX are excepted at this moment.
6.3.2 Fax V.34
Fax V.34 transmission is not supported over T.38v0
46 of 46

SBC 1000/2000 Series Configuration Guide with Lync 2013

Transcription

Similar documents

CV News August 2006

Untitled - EXCELIA HIFI

Sonus faber Il Cremonese

Sonus Faber.EN_mr_NEU.indd

LOUDSPEAKERS - Sonus Faber

a flyer on making the transition to IP

WHAT DOES PSTC Employees Federal Gredit DO WITH YOUR

Hi Fi News - Sonus Faber

Privacy Policy - SnoCope Credit Union

Passerelle GSM - voipsolutions.gr