Configuring the Sonus SBC 5000 for Level(3)

Transcription

Configuring the Sonus SBC 5000
for
Level(3) SIP Trunk Groups and
MS Lync 2013
Application Notes
Last Updated: July 31, 2014
Sonus Equipment
Type
Version
SBC 5200
SBC 5000
04.00.01R0
3rd Party Equipment
Type
Version
Lync 2013
PBX
5.0.8308.420
Copyright © 2014, Sonus and/or its affiliates. All rights reserved.
This document may not be reproduced or transmitted in any form or by any means, electronically or
mechanically, for any purpose, without the prior written permission of Sonus.
Sonus – Network Design Group
Contents
1
Document Overview ...................................................................... 4
2
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 5000 Series ............................................. 7
3.1
SBC Configuration Diagram.................................................................................................... 7
3.2
SBC Name Summaries ........................................................................................................... 8
3.2.1
SBC Name .......................................................................................................................... 8
3.2.2
Internal VLAN Names.......................................................................................................... 8
3.2.3
External VLAN Names ........................................................................................................ 8
3.3
SBC Configuration Workflow .................................................................................................. 9
3.4
General Configuration ........................................................................................................... 10
3.4.1
SIP Max PDU Size ............................................................................................................ 10
3.4.2
UDP Port Range for RTP (optional) .................................................................................. 10
3.4.3
DSP Resource Allocation .................................................................................................. 10
3.4.4
Codec Entry – G.711u ....................................................................................................... 10
3.4.5
Codec Entry – G.729 ......................................................................................................... 11
3.5
SBC Configuration for Internal VLAN .................................................................................. 11
3.5.1
IP Interface Group ............................................................................................................. 11
3.5.1.1
IP Static Route .................................................................................................................. 12
3.6
SBC Configuration for Lync 2013 ......................................................................................... 12
3.6.1
Profile Configuration .......................................................................................................... 12
3.6.1.1
Packet Service Profile (PSP)............................................................................................. 12
3.6.1.2
IP Signaling Profile (IPSP) ................................................................................................ 13
3.6.2
Address Context Configuration ......................................................................................... 13
3.6.2.1
Zone .................................................................................................................................. 13
3.6.2.2
SIP Signaling Port ............................................................................................................. 13
3.6.2.3
IP Peer............................................................................................................................... 14
3.6.2.4
SIP Trunk Group ............................................................................................................... 14
3.7
SBC Configuration for Fax (optional) .................................................................................... 15
3.7.1
2 of 31
3.7.1.1
3.7.1.2
3.7.2
3.7.2.1
Zone .................................................................................................................................. 16
3.7.2.2
3.7.2.3
IP Peer............................................................................................................................... 16
3.7.2.4
SIP Trunk Group ............................................................................................................... 17
3.8
SBC Configuration for External VLAN .................................................................................. 17
3.8.1
IP Interface Group ............................................................................................................. 17
3.8.1.1
IP Static Route .................................................................................................................. 18
3.9
SBC configuration for Level(3) SIP Trunk............................................................................. 18
3.9.1
3.9.1.1
3.9.1.2
3.9.2
3.9.2.1
Zone .................................................................................................................................. 19
3.9.2.2
3.9.2.3
IP Peer............................................................................................................................... 20
3.9.2.4
SIP Trunk Group ............................................................................................................... 20
3.10
Global Call Routing Configuration ........................................................................................ 21
3.10.1
Element Routing Priority.................................................................................................... 21
3.10.2
Lync 2013 PBX Routing Termination ................................................................................ 22
3.10.2.1
SBC Routing Label ............................................................................................................ 22
3.10.3
Level(3) Routing Termination ............................................................................................ 22
3.10.3.1
SBC Routing Label ............................................................................................................ 22
3.10.4
SBC Routes ....................................................................................................................... 23
4
4.1
Configuring Lync 2013 Communication Manager ........................ 25
Adding External DIDs to Lync 2013 ...................................................................................... 25
3 of 31
1 Document Overview
These Application Notes describe the configuration steps required for the Sonus Session Border Controller 5000
series (5100, 5110, 5200, 5210) to interoperate with the Lync2013 and Level(3) SIP Trunk Group. SBC 5000
series functionality was compliance tested using a SIP trunk to Level(3) from an SBC 5200.
The objective of the document is to describe the configuration procedures to be followed during interoperability
testing of SBC 5000 series with Level(3).
The interoperability tested was between Lync 2013, a Sonus SBC 5200, and a Level(3) SIP Trunk.
For additional information on Sonus SBC 5000 series, visit http://www.sonus.net
For additional information on Level(3), visit http://www.level3.com/
For additional information on Lync, visit http://microsoft.com
4 of 31
2 Introduction
This document provides a configuration guide for Sonus SBC 5000 Series (Session Border Controller) when
connecting to a Level(3) SIP Trunk Group and Lync 2013.
The Sonus SBC 5200 is a Session Border Controller that connects disparate SIP trunk groups, SIP PBXs, and
communication applications within an enterprise. It can also be used as a SIP routing and integration engine.
The Sonus SBC is the point of connection between the Lync 2013 and the Level(3) SIP Trunk Group.
2.1 Audience
This technical document is intended for telecommunication engineers with the purpose of configuring both the
Sonus SBC 5000 and aspects of the Lync 2013 product. There are 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 implementation of the
specifications and information in this guide.
Technical support on SBC 5000 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 5200
SBC 5000
04.00.01R0
3rd Party Equipment
Type
Version
Lync 2013
PBX
5.0.8308.420
5 of 31
2.3 Reference Configuration
This simulated enterprise site consisted of Polycom Phones serviced through a Lync 2013 PBX. SIP Trunk
Groups were used to connect the SBC 5200 externally to Level(3) and internally to the Lync 2013 PBX. The SBC
5200 was running software version 4.0.1 R0 during testing.
2.3.1 Network Topology
Lync 2013
Sonus
SBC 5000
PSTN
Internal IP Network
Figure 1 : Network Topology
The figure above represents the equipment used for the integration and certification testing. The SBC 5000 is
used to route and facilitate calls between Lync 2013 and the Level(3) SIP Trunk Groups.
The SBC 5200 has 4 media ports: Media0, Media1, Media2, and Media3. Typically, Media0 and Media1 are
used for external connectivity; and Media2 and Media3 are used for internal connectivity. If deploying an SBC
5200 using only two Media ports, then the convention should be to use Media0 (external) and Media2 (internal).
For more information on media port deployment options or other network connectivity queries, refer to the SBC
5000 Network Deployment Guide or contact your local Sales team for information regarding the Sonus Network
Design professional services offerings.
For this testing an SBC 5200 with only two media ports configured was used due to the limited media capacity
needed. Additional media ports could be cabled and provisioned, if additional media capacity is needed.
6 of 31
3 Configuring Sonus SBC 5000 Series
This section describes how to use the Sonus Command Line Interface (CLI) to configure the SBC 5000 Series.
The SBC can equally be configured and managed by the Embedded Management Application (EMA), which is a
web-based interface management system for the Sonus SBC 5000 Series. However, documentation of the
equivalent configuration steps via EMA is beyond the scope of this guide.
3.1 SBC Configuration Diagram
Internal
10.35.180.136:5068
IP Interface Group: TRUSTED
Zone: Collab-Demo-Trusted
SIP Sig Port: 192.168.192.10:5060
SIP Trunk Groups: IN-SIP-LYNC-2013-1
OUT-SIP-LYNC-2013-2
External
IP Interface Group: UNTRUSTED
Zone: UNTRUSTED
SIP Sig Port: 4.55.x.y:5060
SIP Trunk Group: TWO-WAY-LEVEL-3
Lync 2013
IN-SIP-LYNC-2013-1/
OUT-SIP-LYNC-2013-2
SIP over TCP
TWO-WAY-LEVEL-3
SIP over UDP
SIP over UDP
FAX
Fax via ATA
10.35.137.38:5060
2142964234
4.55.40.225
IP Interface Group: TRUSTED
Zone: ZONE_INT_VOIP
SIP Sig Port: 192.168.192.102:5060
SIP Trunk Groups: FAX
Figure 2: SBC 5000 SIP Trunk Diagram
The above diagram also shows the FAX Trunk Group. Fax machines are typically assigned their own Trunk
Group(s) which allows fax-specific Packet Service Profile (PSP) and IP Signaling Profile (IPSP)
configurations without affecting non-fax devices. This document shows a fax-specific Trunk Group, but it
does not include a Route or Routing Label to it. Call Routing to a specific Fax Trunk Group is usually done
by called number routing (vs. trunk group routing) which is beyond the scope of this document.
The SIP transport protocol preference is configured in the IP Signaling Profile and is assigned to the Trunk
Group. This would allow for different SIP signaling transport protocols to be used for the Lync 2013 PBX
trunk group and the fax machine trunk group, if they were setup to use the same SIP Signaling Port. In this
document and for this testing, different SIP Signaling Ports were used and the transport protocol was
assigned on this port.
7 of 31
3.2 SBC Name Summaries
3.2.1 SBC Name
The SBC has both a System Name and a Compute Element (CE) Name (also referred to as a Host or Element
Name) whose differentiation is relative to a High Availability deployment (one SBC active, one SBC standby).
Each SBC server in an HA pair will have its own unique CE Name, while the HA pair will have a single System
Name. Even an SBC deployed in standalone mode will have a separate System Name and CE Name.
To follow Sonus best practice naming conventions, each server’s CE Name will usually have a simple “a/b” suffix
appended to the System Name:
SBC System Name
SBC CE Name (active)
SBC CE Name (standby)
SBC01
SBC01a
SBC01b
3.2.2 Internal VLAN Names
Unique address contexts, other than “default”, are only needed when using overlapping IP address spaces. This
test configuration requires no such overlapping IP space, thus all configurations are in address context “default”.
Configuration Entity
Lync 2013
FAX (optional)
Address Context
default
default
Zone
ZONE_INT_VOIP
IP Peer
Collab-Demo-Trusted
IN-SIP-LYNC-2013-1
OUT-SIP-LYNC-2013-2
Lync-2013
IP Signaling Profile (IPSP)
DEFAULT-SIP-IPSP
FAX-IPSP
Packet Service Profile (PSP)
DEFAULT-IP-PSP
Routing Label
TO_LYNC2013
FAX-PSP
(not configured)
Faxes are originated only.
Trunk Group
FAX
FAX
3.2.3 External VLAN Names
Unique address contexts, other than “default”, are only needed when using overlapping IP address spaces. This
test configuration requires no such overlapping IP space, thus all configurations are in address context “default”.
Configuration Entity
Level(3)
Address Context
default
Zone
UNTRUSTED
Trunk Group
TWO-WAY-LEVEL-3
IP Peer
TWO-WAY-LEVEL-3
LEVEL-3-SIP-IPSP
LEVEL-3-PSP
Routing Label
TO-LEVEL-3
8 of 31
3.3 SBC Configuration Workflow
|---- Global Configuration
|
|----SIP Max PDU Size
|
|----SIP Domain
|
|----Media Port Range (optional)
|
|----DSP Resource Allocation
|
|----Codec Entry-G.711u
|
|----Codec Entry-G.729
|
|---- Internal side Configuration
|
|----IP Interface and IP Interface Group
|
|----IP Static Routes
|
|---- Lync 2013 Configuration
|
|----Configuring Profiles
|
|
|----Packet Service Profile
|
|
|----IP Signaling Profile
|
|----Configuring Address Context
|
|
|----DNS Group
|
|
|----Zone
|
|
|----SIP Signaling Port
|
|
|----IP Peer
|
|
|----SIP Trunk group
|
|---- Fax Configuration
|
|
|
|
|
|
|
|
|----Zone
|
|
|
|
|----IP Peer
|
|
|----SIP Trunk Group
|
|---- External side Configuration
|
|----IP Interface and IP Interface Group
|
|----IP Static Routes
|
|---- Level(3) Configuration
|
|
|
|
|
|
|
|
|----Zone
|
|
|
|
|----IP Peer
|
|
|----SIP Trunk Group
9 of 31
|
|
|---- Global Call Routing Configuration
|
|----Level(3) Routing
|
|
|----Routing Label
|
|----Lync 2013 Routing
|
|
|----Routing Label
|
|----Routing
3.4 General Configuration
3.4.1 SIP Max PDU Size
Increase the maximum SIP PDU size from 6kb to 60kb to accommodate larger SIP packets.
set global signaling sipSigControls maxPduSizeValue pdusize60kb
commit
3.4.2 UDP Port Range for RTP (optional)
The Sonus SBC 5000 series defaults to using the UDP port range of 1024-65148 for RTP (media) traffic. Many
enterprise networking devices, including security devices may assume a range of 16384-32767.
If required, the following configuration modifies the SBC to work within that more limited range with no changes
to the existing devices. This is a global change.
set system media mediaPortRange baseUdpPort 16384 maxUdpPort 32767
commit
3.4.3 DSP Resource Allocation
This configuration only applies if the SBC 5000 has been deployed with (hardware) DSP resources. If it has not,
executing this configuration step has no negative impact, but subsequent configuration sections (Packet Service
Profiles) assume the SBC has DSP resources for transcoding and/or tone generation
set system mediaProfile compression 90 tone 10
commit
3.4.4 Codec Entry – G.711u
Create a Codec Entry for the G711u codec with DTMF Relay configured for RFC2833, so that DTMF information
will be carried in the audio path as RTP events (e.g. 2833 method).
Parameter
Description
G711u_20ms_2833_T38
Name of codec entry
G711u
Codec selected, Law selected (G.711 specific)
20
Packet size in milliseconds
rfc2833
Type of DTMF Relay chosen: carriers DTMF as RTP events
faxRelayOrFallbackToG711
Fax treatment support for T.38 or G.711 fallback
fallbackToG711
Modem treatment support for G.711 fallback
10 of 31
set profiles
set profiles
set profiles
set profiles
commit
media
media
media
media
codecEntry
codecEntry
codecEntry
codecEntry
G711u_20ms_2833_T38
G711u_20ms_2833_T38
G711u_20ms_2833_T38
G711u_20ms_2833_T38
codec g711 packetSize 20 law ULaw
dtmf relay rfc2833 removeDigits enable
fax toneTreatment faxRelayOrFallbackToG711
modem toneTreatment fallbackToG711
3.4.5 Codec Entry – G.729
Create another Codec Entry for the G729 codec with DTMF Relay configured for RFC2833 so that DTMF
information will be carried in the audio path as RTP events (e.g. 2833 method).
Parameter
Description
G729ab_20ms_2833_T38
Name of codec entry
G729ab
Codec selected
20
Packet size in milliseconds
rfc2833
Type of DTMF Relay chosen: carriers DTMF as RTP events
faxRelayOrFallbackToG711
Fax treatment support for T.38 or G.711 fallback
fallbackToG711
Modem treatment support for G.711 fallback
set profiles
set profiles
set profiles
set profiles
commit
media
media
media
media
codecEntry
codecEntry
codecEntry
codecEntry
G729ab_20ms_2833_T38
G729ab_20ms_2833_T38
G729ab_20ms_2833_T38
G729ab_20ms_2833_T38
codec g729ab packetSize 20
dtmf relay rfc2833 removeDigits enable
fax toneTreatment faxRelayOrFallbacktoG711
modem toneTreatment fallbackToG711
3.5 SBC Configuration for Internal VLAN
3.5.1 IP Interface Group
The below configuration is for a Sonus 5200 system using a single port for Internal connectivity (the Sonus
convention is to use Media 2 and Media 3 ports for Internal connectivity). A similar configuration (not shown) for
the Sonus 51x0 system, which only has a total of two Media ports, would use the Media 1 port for Internal
connectivity per Sonus convention. SBC 5000 Media ports do not have dedicated Internal/External roles and,
while recommended, the Sonus convention does not have to be followed. For more information on Media port
deployment options or other network connectivity queries, refer to the SBC 5000 Network Deployment Guide or
contact your local Sales team for information regarding the Sonus Network Design professional services
offerings.
Create an IP Interface Group and assign it interfaces, including IP addresses.
Parameter
Description
default
Name of the address context
TRUSTED
IP Interface Group name for the internal side of the SBC
verde
SBC element name
PKT2
Name for IP Interface (on pkt2)
pkt2
Gigabit Ethernet port used for internal signaling and media
192.168.192.8
IP address for first internal media port
24
IP subnet prefix (subnet mask in CIDR format)
11 of 31
set addressContext
set addressContext
set addressContext
set addressContext
set addressContext
commit
3.5.1.1
default
default
default
default
default
ipInterfaceGroup
ipInterfaceGroup
ipInterfaceGroup
ipInterfaceGroup
ipInterfaceGroup
TRUSTED
TRUSTED
TRUSTED
TRUSTED
TRUSTED
ipInterface
ipInterface
ipInterface
ipInterface
PKT2
PKT2
PKT2
PKT2
ceName verde
portName pkt2
ipAddress 192.168.192.8 prefix 26
mode inService state enabled
IP Static Route
Create a default route to the subnet’s IP nexthop for the Interface and IP Interface Group.
Parameter
Description
default
0.0.0.0
Default route
0
192.168.192.1
IP nexthop for subnet
TRUSTED
PKT2
100
Preference of the route within the Interface Group
set addressContext default staticRoute 0.0.0.0 0 192.168.192.1 TRUSTED PKT2 preference 100
commit
3.6 SBC Configuration for Lync 2013
3.6.1 Profile Configuration
3.6.1.1
Create a PSP for the Lync 2013 SIP trunk group with a single codec specified. The PSP will be specified within
the SIP Trunk Group configuration. We used the G.711u codec for the purpose of interworking with Level(3)
SIP Trunks.
Parameter
Description
DEFAULT-IP-PSP
Name of the PSP for the Lync 2013 TG
G711u_20ms_2833_T38
Use of codec created earlier (global config section)
conditional
Only transcode if certain conditions are met
codecsAllowedForTranscoding
Specify transcode codecs for thisLeg and/or otherLeg
thisLeg
Specify codec list applicable to “thisLeg”
g711u
Only specify codecs on “thisLeg”
otherLeg
Not-specified; otherLeg should generally be omitted
184
ToS value in IP Header (TOS 184 = DSCP 46 = DiffServ EF)
101
RTP Payload type for Lync 2013 DTMF Relay
set profiles media packetServiceProfile DEFAULT-IP-PSP
12 of 31
codecsAllowedForTranscoding thisLeg g711u
commit
3.6.1.2
codec codecEntry1 G711u_20ms_2833_T38
packetToPacketControl transcode conditional
packetToPacketControl
preferredRtpPayloadTypeForDtmfRelay 101
typeOfService 184
Create an IPSP for the Lync 2013 PBX FAX SIP trunk group. The IPSP will be specified within the SIP Trunk
Group configuration.
A number of flags and parameters are configured with the IPSP for interoperability with a Lync PBX.
Parameter
Description
DEFAULT-SIP-IPSP
Name of the IPSP used for the MS Lync Trunk Group
set profiles signaling ipSignalingProfile DEFAULT-SIP-IPSP
set profiles signaling ipSignalingProfile DEFAULT-SIP-IPSP ipProtocolType sipOnly
set profiles signaling ipSignalingProfile DEFAULT-SIP-IPSP egressIpAttributes privacy transparency
disable
set profiles signaling ipSignalingProfile DEFAULT-SIP-IPSP egressIpAttributes privacyInformation
pAssertedId transparency disable
set profiles signaling ipSignalingProfile DEFAULT-SIP-IPSP ingressIpAttributes flags
noSdpIn180Supported enable sendSdpInSubsequent18x enable suppress183WithoutSdp enable
commit
3.6.2 Address Context Configuration
As mentioned earlier, as no overlapping IP addressing is used on the SBC in this document, all configurations
will be done under the “default” Address Context.
3.6.2.1
Zone
set addressContext default zone Collab-Demo-Trusted id 5
commit
3.6.2.2
SIP Signaling Port
A SIP Signaling Port is a logical address permanently bound to a specific Zone and is used to send and
receive SIP call signaling packets. In this case, it is bound to the Collab-Demo-Trusted Zone and will send
and receive SIP packets for the Lync 2013. The numeric identifier for the Zone and Signaling Port are
independent and do not need to match.
The SIP Signaling IP address can be the same as the IP address configured for the Media interface, but
having them match is not a requirement. In this case, they are the different. The SIP Signaling IP address
must always be in the same subnet as the Media interface IP address.
Parameter
Description
default
Collab-Demo-Trusted
Name of Zone for the Lync 2013
5
A unique numeric identifier (1-2048) for the signaling port
13 of 31
TRUSTED
sip_udp,sip_tcp
Transport protocols allowed for SIP signaling port
192.168.192.10
IPv4 address for the SIP Signaling Port for the SBC
set addressContext
set addressContext
sip_udp,sip_tcp
set addressContext
set addressContext
set addressContext
commit
3.6.2.3
default zone Collab-Demo-Trusted sipSigPort 5 ipInterfaceGroup TRUSTED
default zone Collab-Demo-Trusted sipSigPort 5 transportProtocolsAllowed
default zone Collab-Demo-Trusted sipSigPort 5 ipAddressV4 192.168.192.10
default zone Collab-Demo-Trusted sipSigPort 5 dscpValue 26
default zone Collab-Demo-Trusted sipSigPort 5 state enabled mode inService
IP Peer
Create an IP Peer with for the Lync 2013 PBX and assign it to the Collab-Demo-Trusted zone.
The IP Peer entity is used on egress while the ingress Ip Prefix parameter in the SIP Trunk Group is used on
ingress, when determining the applicable SIP Trunk Group to be used.
Parameter
Description
default
Collab-Demo-Trusted
Name of Zone for Lync 2013
Lync-2013
Name of IP Peer for Lync 2013
10.35.180.136
IP Address of Lync 2013
5068
Signaling port of Lync 2013
3.6.2.4
SIP Trunk Group
Create SIP Trunk Group(s) for the Lync 2013 PBX and assign the corresponding Profiles configured earlier in
this document. The SIP Trunk Group requires an explicit IP address (and mask) for the ingress Ip Prefix
parameter - an FQDN cannot be configured.
Parameter
Description
default
Collab-Demo-Trusted
IN-SIP-LYNC-2013-1
OUT-SIP-LYNC-2013-2
TRUSTED
10.35.180.136
IP Address of Lync 2013 (Ingress Ip Prefix)
32
IP prefix (subnet mask in CIDR format)
DEFAULT-SIP-IPSP
Earlier created IPSP is applied in the Trunk Group
DEFAULT-IP-PSP
Earlier created PSP is applied in the Trunk Group
Name of the SIP Trunk Group from the Lync 2013
set addressContext default zone Collab-Demo-Trusted sipTrunkGroup IN-SIP-LYNC-2013-1 media
mediaIpInterfaceGroupName TRUSTED
set addressContext default zone Collab-Demo-Trusted sipTrunkGroup IN-SIP-LYNC-2013-1 ingressIpPrefix
10.35.180.136 32
set addressContext default zone Collab-Demo-Trusted sipTrunkGroup IN-SIP-LYNC-2013-1 policy signaling
ipSignalingProfile DEFAULT-SIP-IPSP
14 of 31
set addressContext default zone Collab-Demo-Trusted sipTrunkGroup IN-SIP-LYNC-2013-1 policy media
packetServiceProfile DEFAULT-IP-PSP
set addressContext default zone Collab-Demo-Trusted sipTrunkGroup IN-SIP-LYNC-2013-1 state enabled mode
inService
commit
Create and execute similar CLI for OUT-SIP-LYNC-2013-2.
3.7 SBC Configuration for Fax (optional)
3.7.1.1
Create a PSP for the FAX SIP Trunk Group with G.711u and G.729 codecs. The PSP will be specified within the
SIP Trunk Group configuration. A Cisco PAP2T IAD was used for testing FAX functionality with Level(3) SIP
Trunk for the purpose of this interoperability test.
Parameter
Description
FAX-PSP
Name of the PSP for Faxing
G711u_20ms_2833_T38
G729ab_20ms_2833_T38
conditional
differentDtmfRelay
Allow transcoding for different DTMF relay behaviors
thisLeg
g711u
otherLeg
101
13
RTP Payload Type for G.711 SID packets
184
set profiles media packetServiceProfile FAX-PSP codec codecEntry1 G711u_20ms_2833_T38
set profiles media packetServiceProfile FAX-PSP codec codecEntry2 G729ab_20ms_2833_T38
set profiles media packetServiceProfile FAX-PSP packetToPacketControl
conditionsInAdditionToNoCommonCodec differentDtmfRelay enable
set profiles media packetServiceProfile FAX-PSP preferredRtpPayloadTypeForDtmfRelay 101
set profiles media packetServiceProfile FAX-PSP silenceInsertionDescriptor g711SidRtpPayloadType 13
set profiles media packetServiceProfile FAX-PSP typeOfService 184
commit
3.7.1.2
Create an IPSP for the FAX SIP trunk. The IPSP will be specified within the SIP Trunk Group configuration.
A number of flags and parameters are configured with the IPSP for interoperability with a fax machine.
15 of 31
Parameter
Description
FAX-IPSP
Name of the IPSP used for the FAX Trunk
set profiles signaling
transparency disable
sendSdpInSubsequent18x
commit
ipSignalingProfile
ipSignalingProfile
ipSignalingProfile
ipSignalingProfile
FAX-IPSP
FAX-IPSP ipProtocolType sipOnly
FAX-IPSP egressIpAttributes privacy transparency disable
FAX-IPSP egressIpAttributes privacyInformation pAssertedId
ipSignalingProfile FAX-IPSP ingressIpAttributes flags noSdpIn180Supported enable
enable suppress183WithoutSdp enable
3.7.2.1
Zone
set addressContext default zone ZONE_INT_VOIP id 8
commit
3.7.2.2
SIP Signaling Port
A SIP Signaling Port is a logical address permanently bound to a specific Zone and is used to send and
receive SIP call signaling packets. In this case, it is bound to the ZONE_INT_VOIP Zone and will send and
receive SIP packets for the fax machine.
Parameter
Description
default
ZONE_INT_VOIP
7
TRUSTED
sip_udp,sip_tcp
Transport protocols allowed for SIP signaling port
192.168.192.102
IPv4 address for the SIP Signaling Port for the SBC
set addressContext
set addressContext
set addressContext
set addressContext
set addressContext
commit
3.7.2.3
default
default
default
default
default
zone
zone
zone
zone
zone
ZONE_INT_VOIP
ZONE_INT_VOIP
ZONE_INT_VOIP
ZONE_INT_VOIP
ZONE_INT_VOIP
sipSigPort
sipSigPort
sipSigPort
sipSigPort
sipSigPort
7
7
7
7
7
ipInterfaceGroup TRUSTED
transportProtocolsAllowed sip_udp,sip_tcp
ipAddressV4 192.168.192.102
dscpValue 26
state enabled mode inService
IP Peer
Create an IP Peer with the signaling IP address of the Cisco /Linksys IAD and assign it to the ZONE_INT_VOIP
Zone. The IP Peer entity is used on egress. The ingress Ip Prefix parameter in the SIP Trunk Group is used on
ingress, when determining the applicable SIP Trunk Group to utilize.
16 of 31
Parameter
Description
default
ZONE_INT_VOIP
Name of Zone for the fax device
FAX
Name of IP Peer for fax device
10.35.137.38
IP Address for fax device
5060
SIP signaling port for fax device
set addressContext default zone ZONE_INT_VOIP ipPeer FAX
set addressContext default zone ZONE_INT_VOIP ipPeer FAX ipAddress 10.35.137.38
set addressContext default zone ZONE_INT_VOIP ipPeer FAX ipPort 5060
commit
3.7.2.4
SIP Trunk Group
Create a SIP Trunk group towards the Linksys PAP2T IAD and assign the corresponding Profiles configured
earlier in this document.
Parameter
Description
default
ZONE_INT_VOIP
Name of Zone for the fax device
FAX
Name of the SIP Trunk Group for the device
TRUSTED
10.35.137.38
IP Address for the device (ingress IP Prefix)
32
FAX-IPSP
FAX-PSP
set addressContext
set addressContext
set addressContext
set addressContext
set addressContext
commit
default
default
default
default
default
zone
zone
zone
zone
zone
ZONE_INT_VOIP
ZONE_INT_VOIP
ZONE_INT_VOIP
ZONE_INT_VOIP
ZONE_INT_VOIP
sipTrunkGroup
sipTrunkGroup
sipTrunkGroup
sipTrunkGroup
sipTrunkGroup
FAX
FAX
FAX
FAX
FAX
media mediaIpInterfaceGroupName TRUSTED
ingressIpPrefix 10.35.137.38 32
policy signaling ipSignalingProfile FAX
policy media packetServiceProfile FAX
3.8 SBC Configuration for External VLAN
3.8.1 IP Interface Group
The below configuration is for a Sonus 5200 using a single port for External connectivity (the Sonus
convention is to use Media 0 and Media 1 ports). Create an IP Interface Group and assign it interfaces,
including IP addresses.
Parameter
Description
default
UNTRUSTED
IP Interface Group name for the external side of the SBC
verde
SBC element name
17 of 31
PKT0
pkt0
Gigabit Ethernet port used for external signaling and media
63.145.56.60
IP address for first external media port
27
set addressContext
set addressContext
set addressContext
set addressContext
set addressContext
commit
3.8.1.1
default
default
default
default
default
ipInterfaceGroup
ipInterfaceGroup
ipInterfaceGroup
ipInterfaceGroup
ipInterfaceGroup
UNTRUSTED
UNTRUSTED
UNTRUSTED
UNTRUSTED
UNTRUSTED
ipInterface
ipInterface
ipInterface
ipInterface
PKT0
PKT0
PKT0
PKT2
ceName verde
portName pkt0
ipAddress 63.145.56.60 prefix 27
mode inService state enabled
IP Static Route
Create a default route to the subnet’s IP nexthop for the Interface and IP Interface Group.
Parameter
Description
default
0.0.0.0
Destination IP Network (default route)
0
63.145.56.33
IP Nexthop for subnet
UNTRUSTED
PKT0
100
Preference of the route within the Interface Group
set addressContext default staticRoute 0.0.0.0 0 63.145.56.33 UNTRUSTED PKT0 preference 100
commit
3.9 SBC configuration for Level(3) SIP Trunk
3.9.1.1
Create a PSP for the L3 SIP trunk group with G.711u and G.729 codecs.. The PSP will be specified within the
SIP Trunk Group configuration.
Parameter
Description
TWO-WAY-LEVEL-3-PSP
Name of the PSP for Level(3)
G711u_20ms_2833_T38
G729ab_20ms_2833_T38
conditional
differentDtmfRelay
Allow transcoding for different DTMF relay behaviors
thisLeg
g711u,g729
18 of 31
otherLeg
101
13
RTP Payload Type for G.711 SID packets
2
Number of redundant packets for FAX
184
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP codec codecEntry1 G711u_20ms_2833_T38
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP codec codecEntry2 G729ab_20ms_2833_T38
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP packetToPacketControl transcode conditional
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP packetToPacketControl
codecsAllowedForTranscoding thisLeg g711u,g729
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP packetToPacketControl
conditionsInAdditionToNoCommonCodec differentDtmfRelay enable
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP preferredRtpPayloadTypeForDtmfRelay 101
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP silenceInsertionDescriptor
g711SidRtpPayloadType 13
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP t38 numberOfRedundantPackets 2
set profiles media packetServiceProfile TWO-WAY-LEVEL-3-PSP typeOfService 184
commit
`
3.9.1.2
Create an IP Signaling Profile (IPSP) for the Level(3) SIP trunk. The IPSP will be specified within the SIP Trunk
Group configuration.
A number of flags and parameters are configured with the IPSP for interoperability with Level(3).
Parameter
Description
LEVEL-3-SIP
Name of the IPSP for Level(3) SIP Trunk
set profiles signaling ipSignalingProfile LEVEL-3-SIP
set profiles signaling ipSignalingProfile LEVEL-3-SIP ipProtocolType sipOnly
set profiles signaling ipSignalingProfile LEVEL-3-SIP ingressIpAttributes flags noSdpIn180Supported
enable sendSdpInSubsequent18x enabled suppress183WithoutSdp enable
commit
3.9.2.1
Zone
This Zone groups the set of objects that is used for the communication to the Level(3) SIP Trunk Group.
Parameter
Description
default
UNTRUSTED
Name of Zone for Level(3) SIP Trunk.
2
A unique numeric identifier (2-2048) for the zone
set addressContext default zone UNTRUSTED id 2
19 of 31
commit
3.9.2.2
SIP Signaling Port
A SIP signaling port is a logical address permanently bound to a specific zone and is used to send and
receive SIP call signaling packets. In this case it is bound to the Level(3) zone and will send and receive
SIP packets for the Level(3) SIP Trunk. The numeric identifier for the Zone and Signaling port are
independent and do not need to match.
The SIP signaling IP address can be the same as the IP address configured for the Media interface, but
having them match is not a requirement. In this case, they are the same. If they are different, the SIP
signaling IP address must always be in the same subnet as the Media interface IP address.
Parameter
Description
default
UNTRUSTED
Name of Zone for Level(3) SIP Trunk
2
UNTRUSTED
63.145.56.61
IPv4 address for this SIP Signaling Port
0
DiffServ Code Point value for SIP signaling traffic from SBC
set addressContext
set addressContext
set addressContext
set addressContext
commit
3.9.2.3
default
default
default
default
zone
zone
zone
zone
UNTRUSTED
UNTRUSTED
UNTRUSTED
UNTRUSTED
sipSigPort
sipSigPort
sipSigPort
sipSigPort
2
2
2
2
ipInterfaceGroup UNTRUSTED
ipAddressV4 63.145.56.61
dscpValue 0
IP Peer
Create an IP Peer with the signaling IP address of the Level(3) SIP Trunk and assign it to the EXTERNAL zone.
The IP Peer entity is used on egress. The ingressIpPrefix parameter in the sipTrunkGroup object is used on
ingress, for determining the applicable SIP Trunk Group.
Parameter
Description
default
UNTRUSTED
TWO-WAY-LEVEL-3
Name of IP Peer for Level(3) SIP Trunk
4.55.x.y
IP Address of Level(3) SIP peer
5060
SIP signaling port for Level(3) SIP Trunk
set addressContext default zone UNTRUSTED ipPeer TWO-WAY-LEVEL-3 ipAddress 4.55.x.y ipPort 5060
commit
3.9.2.4
SIP Trunk Group
Create a SIP Trunk Group to Level(3) and assign the corresponding Profiles configured earlier in this section.
Parameter
Description
20 of 31
default
UNTRUSTED
TWO-WAY-LEVEL-3
Name of the Level(3) SIP Trunk Group
UNTRUSTED
4.55.x.y
IP Address of Level(3) peer (Ingress Ip Prefix)
32
LEVEL-3-SIP
TWO-WAY-LEVEL-3-PSP
set addressContext default zone UNTRUSTED
UNTRUSTED
ipSignalingProfile LEVEL-3-SIP
packetServiceProfile TWO-WAY-LEVEL-3-PSP
commit
sipTrunkGroup TWO-WAY-LEVEL-3 media mediaIpInterfaceGroupName
sipTrunkGroup TWO-WAY-LEVEL-3 ingressIpPrefix 4.55.x.y 32
sipTrunkGroup TWO-WAY-LEVEL-3 policy signaling
sipTrunkGroup TWO-WAY-LEVEL-3 policy media
sipTrunkGroup TWO-WAY-LEVEL-3 state enabled mode inService
3.10 Global Call Routing Configuration
A Routing Label (RL) is a user-named object that contains a list of one or more next-hop peers - defined as
Routing Label Routes - that can reach a specified destination.
A Routing Label Route (RLR) defines a single peer (Trunk Group Name + IP Peer) to which the call can be
delivered. There may be many Routing Label Routes (1 to n) in a Routing Label.
For each call placed to a destination Routing Label, the SBC will advance through the list of RLRs until the call is
completed or the list is exhausted. The RL's Prioritization Type determines the order in which the list will be
processed.
Routing Labels are then assigned within the Route entity.
3.10.1 Element Routing Priority
The Element Routing Priority (ERP) Profile determines the priority or precedence for criteria used for call
routing. An ERP Profile is then applied in the Trunk Group entity.
When doing simple Trunk Group to Trunk Group routing (such as when there is only one internal PBX and
one external SIP trunk group), the SBC must have an ERP Profile which prioritizes the Trunk Group entity
above others. This allows routing of traffic from the ingress Trunk Group to the egress Trunk Group.
This prioritization can be accomplished by creating a new ERP Profile and applying it on all Trunk Groups or
by simply modifying the default ERP Profile (DEFAULT_IP). This document modifies the default ERP
Profile.
Parameter
Description
DEFAULT_IP
Name of the ERP Profile.
set profiles callRouting elementRoutingPriority DEFAULT_IP entry nationalType 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry nationalType 1 entityType trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry _private 2 entityType none
21 of 31
set profiles
set profiles
set profiles
trunkGroup
set profiles
set profiles
set profiles
set profiles
trunkGroup
set profiles
set profiles
set profiles
set profiles
set profiles
set profiles
trunkGroup
set profiles
set profiles
trunkGroup
set profiles
set profiles
trunkGroup
set profiles
set profiles
trunkGroup
set profiles
set profiles
set profiles
set profiles
commit
callRouting elementRoutingPriority DEFAULT_IP entry _private 1 entityType trunkGroup
callRouting elementRoutingPriority DEFAULT_IP entry nationalOperator 2 entityType none
callRouting elementRoutingPriority DEFAULT_IP entry nationalOperator 1 entityType
callRouting
callRouting
callRouting
callRouting
elementRoutingPriority
DEFAULT_IP
DEFAULT_IP
DEFAULT_IP
DEFAULT_IP
entry
entry
entry
entry
transit 2 entityType
transit 1 entityType
trunkGroupCutThrough
trunkGroupCutThrough
none
trunkGroup
2 entityType none
1 entityType
callRouting
callRouting
callRouting
callRouting
callRouting
callRouting
DEFAULT_IP
DEFAULT_IP
DEFAULT_IP
DEFAULT_IP
DEFAULT_IP
DEFAULT_IP
entry
entry
entry
entry
entry
entry
localOperator 2 entityType none
localOperator 1 entityType trunkGroup
userName 2 entityType none
userName 1 entityType trunkGroup
internationalOperator 2 entityType none
internationalOperator 1 entityType
callRouting elementRoutingPriority DEFAULT_IP entry longDistanceOperator 2 entityType none
callRouting elementRoutingPriority DEFAULT_IP entry longDistanceOperator 1 entityType
callRouting elementRoutingPriority DEFAULT_IP entry othertrunkGroupChosen 2 entityType none
callRouting elementRoutingPriority DEFAULT_IP entry othertrunkGroupChosen 1 entityType
callRouting elementRoutingPriority DEFAULT_IP entry internationalType 2 entityType none
callRouting elementRoutingPriority DEFAULT_IP entry internationalType 1 entityType
callRouting
callRouting
callRouting
callRouting
DEFAULT_IP
DEFAULT_IP
DEFAULT_IP
DEFAULT_IP
entry
entry
entry
entry
mobile
mobile
test 2
test 1
2 entityType none
1 entityType trunkGroup
entityType none
entityType trunkGroup
3.10.2 Lync 2013 PBX Routing Termination
3.10.2.1
SBC Routing Label
Create a Routing Label with a single Routing Label Route to bind the Lync 2013 Trunk Group with the IP
Peer
Parameter
Description
TO_LYNC2013
Name of the Routing Label for Lync 2013
Sequence
The prioritization of Routing Label Routes within a Routing Label
1
The first Routing Label Route within the Routing Label
OUT-SIP-LYNC-2013-2
Trunk Group for Lync 2013
Lync-2013
IP Peer for Lync 2013
set global callRouting routingLabel TO_LYNC2013 routePrioritizationType sequence action routes
routingLabelRoute 1 trunkGroup OUT-SIP-LYNC-2013-2 ipPeer Lync-2013 inService inService
commit
3.10.3 Level(3) Routing Termination
3.10.3.1
SBC Routing Label
Create a Routing Label with a single Routing Label Route to bind the Level(3) Trunk Group with the
Level(3) IP Peer.
22 of 31
Parameter
Description
TO-LEVEL-3
Name of the Routing Label for Level(3)
Sequence
The prioritization of Routing Label Routes within a Routing Label
1
The first Routing Label Route within the Routing Label
TWO-WAY-LEVEL-3
Trunk Group for Level(3)
TWO-WAY-LEVEL-3
IP Peer for Level(3)
set global callRouting routingLabel TO-LEVEL-3 routePrioritizationType sequence action routes
routingLabelRoute 1 trunkGroup TWO-WAY-LEVEL-3 ipPeer TWO-WAY-LEVEL-3 inService inService
commit
3.10.4 SBC Routes
Routing must be put in place to send calls to the correct destination. For the purpose of this interoperability test
we have used trunk group routing, but additional routing options may be used. See Appendix B for more
information.
Create Route entries for Trunk Group routing with Matching Criteria and a Route Label destination.
Parameter
Description
trunkGroup
standard
The entity type for the route
elementId1 – for an entityType of trunkGroup, value is the
ingress trunk group
elementId2 – for an entityType of trunkGroup, value is the SBC
System Name in all upper case (not hostname / element name)
The type of routing for the route
Sonus_NULL
Destination national number
Sonus_NULL
Destination country number
all
Call Type
all
Digit Type
ALL
Time Range Profile (note the capitalization)
none
Call Parameter Filter Profile
Sonus_NULL
Destination Domain Name
TO-LEVEL-3
Destination Routing Label
Parameter
Description
trunkGroup
standard
The entity type for the route
elementId1 – for an entityType of trunkGroup, value is the
ingress trunk group
elementId2 – for an entityType of trunkGroup, value is the SBC
System Name in all upper case (not hostname / element name)
The type of routing for the route
Sonus_NULL
Destination national number
Sonus_NULL
Destination country number
all
Call Type
IN-SIP-LYNC-2013-1
VERDE
TWO-WAY-LEVEL-3
VERDE
23 of 31
all
Digit Type
ALL
Time Range Profile (note the capitalization)
none
Call Parameter Filter Profile
Sonus_NULL
Destination Domain Name
TO_LYNC2013
Destination Routing Label
set global callRouting route trunkGroup IN-SIP-LYNC-2013-1 VERDE standard Sonus_NULL Sonus_NULL all all
ALL none Sonus_NULL routingLabel TO-LEVEL-3
commit
set global callRouting route trunkGroup TWO-WAY-LEVEL-3 VERDE standard Sonus_NULL Sonus_NULL all all
ALL none Sonus_NULL routingLabel TO_LYNC2013
commit
24 of 31
4 Configuring Lync 2013 Communication Manager
This section assumes that the Lync 2013 components have been installed along with Lync users. The user
should be familiar with Lync 2013 Server Administration. This section does not cover the basic installation of
Lync 2013
4.1 Adding External DIDs to Lync 2013
Routing for all outgoing DID calls or calls that route through Lync2013 to external phone numbers must be
configured in the Lync 2013 server.
Remote Desktop to the Lync 2013 Server and login as lync2013\administrator:
25 of 31
Select Voice Routing from the menu on the left and then select the Rout Tab to get to the routing table:
Since all our outgoing calls are destined to the Verde SBC, we will add all the DIDs to the Verde – SBC 5200.
Double click on the Verde SBC to bring up the GUI to add all the numbers that will be dialed out to.
26 of 31
To add a number simply enter in in the field and click on the “Add” button.
27 of 31
Click OK to go back to the routing screen. Here we will need to commit the changes for them to take effect.
From the pull down menu shown in the Diagram below, select from “Commit all” from the Commit menu.
28 of 31
29 of 31
Click okay and the routing is saved.
30 of 31
31 of 31

Configuring the Sonus SBC 5000 for Level(3)

Transcription

Similar documents

a flyer on making the transition to IP

Turn the page to see the prettiest little Camel Toe you`ve ever seen!

PJSIP - eLinux.org

Leaflet Homage Vox 2509 Kb

History Trunk Show - Gordon

Sonus® NetScore™

the flyer

CV News August 2006

IOT

Untitled - EXCELIA HIFI