Configuring the Sonus SBC 5000 with Cisco Unified Communication

Transcription

Configuring the Sonus SBC 5000 with
Cisco Unified Communication Manager 10.5 for
Verizon Deployments
Application Notes
Rev. 1.0
Last Updated: March 10, 2015
Revision History
Revision
Date
Revised By
Comments
1
3/1/2015
Paul Axtell
Initial Publication
© 2015 Sonus Networks, Inc
Contents
1 Document Overview .............................................................................. 4
1.1
Glossary .................................................................................................................................. 4
2 Introduction ........................................................................................... 5
2.1
Audience ................................................................................................................................. 5
2.2
Requirements .......................................................................................................................... 5
2.3
Reference Configuration ......................................................................................................... 6
2.4
Features tested with Verizon SIP Trunk ................................................................................. 6
3 Interworking Architecture ....................................................................... 8
3.1
Cisco Functionality .................................................................................................................. 8
3.2
Cisco Components .................................................................................................................. 8
Cisco Unified Communication Manager .............................................................................. 8
4 Configuring Sonus SBC 5000 Series ..................................................... 9
4.1
SBC Naming Conventions ...................................................................................................... 9
4.2
SBC Configuration Workflow ................................................................................................ 10
4.3
Global Configuration ............................................................................................................. 11
UDP Port Range for RTP (media) ..................................................................................... 11
DSP Resources ................................................................................................................. 11
Codec Entry for G.711U_20ms_2833_T38 ....................................................................... 11
Codec Entry for G.711A_20ms_2833_T38 ....................................................................... 12
Codec Entry for G729A_20ms_2833_T38 ........................................................................ 12
Address Reachability Service Profile ................................................................................ 13
4.4
Internal Side SBC Configuration ........................................................................................... 14
IP Interface Group ............................................................................................................. 14
IP Static Route .................................................................................................................. 14
4.5
SBC Configuration for Cisco UCM ........................................................................................ 15
Profile Configuration .......................................................................................................... 15
Packet Service Profile (PSP)............................................................................................. 15
IP Signaling Profile (IPSP) ................................................................................................ 16
Address Context Configuration ......................................................................................... 16
Zone .................................................................................................................................. 16
SIP Signaling Port ............................................................................................................. 17
IP Peer............................................................................................................................... 17
SIP Trunk Group ............................................................................................................... 18
© 2015 Sonus Networks
2
4.6
External Side SBC Configuration .......................................................................................... 19
IP Interface Group ............................................................................................................. 19
IP Static Route .................................................................................................................. 20
4.7
SBC Configuration for SIP Carrier ........................................................................................ 21
Profile Configuration .......................................................................................................... 21
Packet Service Profile (PSP)............................................................................................. 21
IP Signaling Profile (IPSP) ................................................................................................ 22
Address Context Configuration ......................................................................................... 22
Zone .................................................................................................................................. 22
SIP Signaling Port ............................................................................................................. 23
IP Peer............................................................................................................................... 23
SIP Trunk Group ............................................................................................................... 24
4.8
Global Call Routing Configuration ........................................................................................ 25
Element Routing Priority.................................................................................................... 25
Cisco Routing .................................................................................................................... 26
Routing Label .................................................................................................................... 26
SIP Carrier Routing ........................................................................................................... 27
Routing Label .................................................................................................................... 27
Routing .............................................................................................................................. 27
5 Cisco configuration .............................................................................. 29
5.1
CUCM 10.5 Configuration Settings ....................................................................................... 29
Login to CUCM .................................................................................................................. 29
SIP Trunk Security Profile ................................................................................................. 30
SIP Profile ......................................................................................................................... 31
Create a New TG .............................................................................................................. 34
Create New Route Group .................................................................................................. 39
Create a New Route List ................................................................................................... 40
Create a New Route Pattern ............................................................................................. 41
© 2015 Sonus Networks
3
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 Cisco UCM system. SBC 5000 series functionality was
compliance tested using a VZ SIP trunk to Cisco UCM Server from an SBC 5200.
The objective of this document is to describe the procedure to be followed during interoperability testing of the
SBC 5000 series and Cisco UCM with a Verizon Sip trunk. Testing was based on a test plan provided by Verizon
for the functionality required for certification as a solution supported on the IP network.
The interoperability tested was between SIP and PSTN clients, Cisco UCM, Verizon SIP trunk and Sonus SBC
5200.
For additional information on Sonus SBC 5000 series, visit http://www.sonusnet.com.
For additional information on Cisco, visit http://www.cisco.com.
1.1
Term
Glossary
Definition
AOC
Advice Of Charge
B2B UA
Back to Back User Agent
CP
Calling Party
CPD
Call Progress Detection
CPE
Customer Premise Equipment – Cisco SIP Server is the CPE device in
this case.
CTI
Computer Telephony Integration
DNIS
Dialed Number Identification Service
IP
Internet Protocol
MS
Media Server
PBX
Private Branch Exchange
PSX
Policy Server Exchange
SDOP
Signaled Digits Out-Pulsed
SIP
Session Initiation Protocol
UUI
User to User Information
4
2 Introduction
This is a configuration guide for Sonus SBC 5000 Series (Session Border Controller) when connecting to the
Cisco SIP Server and other internal PBX system.
The Sonus SBC 5200 is a Session Border Controller that connects disparate SIP trunks, 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 Cisco System and local PBX System that hosts internal
SIP phones. The Sonus SBC is also the point of connection to external carrier SIP trunk providers for SIP Carrier
connection. In this case, the internal PBX is out of scope of this document.
2.1
Audience
This document is intended for telecommunication engineers for the purpose of configuring both the Sonus SBC
5xx0 and aspects of the Cisco UCM products. There will be steps that require navigating the third-party and
Sonus SBC Command Line Interface (CLI). Understanding the basic concepts of TCP/UDP, IP/Routing, and
SIP/RTP are also necessary to complete the configuration and for troubleshooting, if necessary.
Technical support on SBC 5000 can be obtained through the following:

Phone: (978) 614-8589 or (888) 391-3434 (Toll-free)

Web: http://sonusnetworks.force.com/PortalLoginPage
2.2
Requirements
The following equipment and software was used for the sample configuration provided:
Sonus Equipment
SBC 5200
BMC
BIOS
ConnexIP OS
SonusDB
EMA
SBC
Type
SBC 5000
Version
V02.05.00
V02.04.00
V02.02.00-R000
V04.02.00-R000
V04.02.00-R000
V04.02.00-R000
3rd Party Equipment
Type
Version
Cisco UCM
SIP Server
10.5.1.11005-2
Cisco 7942G
SIP phone
Canon Faxphone L100
Venta Fax
Fax machine
Fax softphone
Boot Load: tnp42.9-3-1-57.bin
Load File: SIP42.9-3-1SR4-1S
7.3.227.568 I
5
2.3
Reference Configuration
A simulated enterprise site consists of the following elements: Cisco Unified Communication Manager (CUCM)
10.5 and an SBC 5200 system running software version 4.2.0 R0. Verizon SIP trunks were used to connect the
SBC to the Cisco UCM.
Cisco 10.5
Sonus
SBC 5000
Verizon
Internal IP Network
Figure 2.1
Network Topology
The figure above represents the equipment that was used for the Cisco integration and certification testing. The
Sonus SBC 5200 was used to route the calls to and from Verizon SIP trunk to and from the Cisco UCM and SIP
endpoints, depending on the test being run.
2.4
Features tested with Verizon SIP Trunk
The following features were tested and supported with the Verizon IP SIP Trunk – Enhanced Features service:

Basic Call Tests Hop-off to PSTN

Basic Call Tests Hop-on from PSTN

International Call

Simultaneous Calls

Calling Number Privacy

Call Hold and Resume

PBX-Based 3-Way Call Conference

PBX-Based Unattended Call Transfer

PBX-Based Attended Call Transfer

PBX-Based Call Forwarding
6

PBX-Based Meet-Me Conference Bridge

FAX Tests with T.38 (SG3 FAX Machine at CPE Site)

FAX Tests with G.711 (SG3 FAX Machine at CPE Site)

Network-based Call Forward

Network-Based Call Forwarding – Busy (CFB)

Network-Based Call Forwarding - Ring No Answer (CFRNA)

Network-Based Call Forwarding - Not Reachable (CF-NR)

Network-Based Blind Call Transfer

Network-Based Consultative Call Transfer (Attended)
7
3 Interworking Architecture
This section discusses general architectural issues.
3.1
Cisco Functionality

General Cisco functionality provides the UCM application

All the SIP Phones will register with Cisco Unified Communication Manager
3.2
Cisco Components
Cisco Unified Communication Manager
Cisco Unified Communications Manager software is the call-processing component of the Cisco Unified
Communications system. Cisco Unified Communications Manager extends enterprise telephony features and
capabilities to packet telephony network devices such as IP phones, media processing devices, voice over IP
(VoIP) gateways, and multimedia applications. Additional services such as unified messaging, multimedia
conferencing, collaborative contact centers, and interactive multimedia response systems are made possible
through Cisco Unified Communications Manager open telephony APIs. Cisco Unified Communications Manager
offers a suite of integrated voice applications and utilities, including the Cisco Unified Communications Manager
Attendant Console, an ad-hoc conferencing application, the Cisco Unified Communications Manager Bulk
Administration Tool, the Cisco Unified Communications Manager CDR (call detail record) Analysis and Reporting
Tool, the Cisco Unified Communications Manager Real-Time Monitoring Tool, and the Cisco Unified
Communications Manager Assistant application.
The dial plan feature in Unified Communications Manager enable you to:
•
Route calls based on the physical location context of the caller.
• Represent calling and called party numbers in a global form such as that described by the International
Telecommunications Union's E.164 recommendation.
•
Present calls to users in a format based on local dialing habits.
• Present calls to external networks (for example, the PSTN) in a manner compatible with the local
requirements for calling party number, called party number, and their respective numbering types.
• Derive the global form of the calling party number on incoming calls from gateways, based on the calling
number digits and the numbering type.
For additional information, go to:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_general_information.html
8
4 Configuring Sonus SBC 5000 Series
This section describes how to use the Sonus Command Line Interface (CLI) to configure and manage 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 document.
Internal
External
IP Interface Group: IPIG_INTERNAL
Zone: ZONE_INTERNAL
SIP Port: 10.35.177.247:5060
SIP TrunkGroup: CISCO-CUCM-10.5
IP Interface Group: IPIG_EXTERNAL
Zone: ZONE_EXTERNAL
SIP Port: 10.35.177.188:5060
SIP TrunkGroup: CARRIER_VZ
Cisco UCM
10.5
Sonus
5200
Verizon
SBC
CISCO-CUCM-10.5
CARRIER-VZ
Figure 4.1
4.1
SBC 5000 SIP Trunk Diagram
SBC Naming Conventions
Unique address contexts are needed only when using overlapping IP address space. This deployment assumes
no such overlapping IP space; thus, all configurations are in Address Context “default”.
9
4.2
SBC Configuration Workflow
|---- Global Configuration
|
|----Media Port Range
|
|---- DSP Resources
|
|----Codec Entry
|
|---- Internal side Configuration
|
|----IP Interface and IP Interface Group
|
|----IP Static Routes
|
|---- Cisco Configuration
|
|----Configuring Profiles
|
|
|----Packet Service Profile
|
|
|----IP Signaling Profile
|
|----Configuring Address Context
|
|
|----Zone
|
|
|----SIP Signaling Port
|
|
|----IP Peer
|
|
|----SIP Trunk Group
|
|---- Internal Agent Side Configuration (optional)
|
|
|
|
|
|
|
|
|----Zone
|
|
|
|
|----IP Peer
|
|
|
|---- External side Configuration
|
|----IP Interface and IP Interface Group
|
|----IP Static Routes
|
|---- Carrier Configuration
|
|
|
|
|
|
|
|
|----Zone
|
|
|
|
|----IP Peer
|
|
|
|---- Remote Agent Configuration
|
|
|
|
|
10
|
|
|
|----Zone
|
|
|
|
|----IP Peer
|
|
|
|---- Global Call Routing Configuration
|
|----Cisco Side Routing
|
|
|----Routing Label
|
|----Carrier Side Routing
|
|
|----Routing Label
|
|----Agent Routing
|
|----Routing
4.3
Global Configuration
UDP Port Range for RTP (media)
The Sonus SBC 5000 series defaults to using a UDP port range of 1024-65148 for RTP (media) traffic. Many
enterprise networking devices, including security devices, may assume a range of 16384-32767. The following
configuration modifies the SBC to work within the designated VZ range with no changes to the existing devices.
This configuration is optional for the SBC but required by VZ.
set system media mediaPortRange baseUdpPort 20001 maxUdpPort 30000
commit
DSP Resources
Ensure that the SBC has DSP resources allocated for compression/transcoding. Packet Service Profiles,
configured later in this document, will use Conditional Transcoding, which will only function properly if the SBC
has been deployed with DSP resources that have been allocated for transcoding.
set system mediaProfile compression 90 tone 10
commit
Codec Entry for G.711U_20ms_2833_T38
Create Codec Entry for the G711u codec with DTMF Relay configured for RFC2833 so DTMF information is
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
20
Packet size in milliseconds
rfc2833
Type of DTMF Relay chosen: carriers DTMF in signaling protocol
set profiles media codecEntry G711U_20ms_2833_T38 codec g711 law ULaw packetSize 20
set profiles media codecEntry G711U_20ms_2833_T38 dtmf relay rfc2833
set profiles media codecEntry G711U_20ms_2833_T38 fax toneTreatment faxRelay
commit
11
Codec Entry for G.711A_20ms_2833_T38
Create Codec Entry for the G711a codec with DTMF Relay configured for RFC2833 so DTMF information is
Parameter
Description
G711A_20ms_2833_T38
Name of codec entry
G711A
Codec selected
20
rfc2833
set profiles media codecEntry G711A_20ms_2833_T38 codec g711 law ALaw packetSize 20
set profiles media codecEntry G711A_20ms_2833_T38 dtmf relay rfc2833
set profiles media codecEntry G711A_20ms_2833_T38 fax toneTreatment faxRelay
commit
Codec Entry for G729A_20ms_2833_T38
Create Codec Entry for the G729 codec with DTMF Relay configured for RFC2833 so DTMF information is
Parameter
Description
G729A_20ms_2833_T38
Name of codec entry
G729A
Codec selected
20
rfc2833
set profiles media codecEntry G729A_20ms_2833_T38 codec g729a packetSize 20
set profiles media codecEntry G729A_20ms_2833_T38 dtmf relay rfc2833
set profiles media codecEntry G729A_20ms_2833_T38 fax toneTreatment faxRelay
commit
12
Address Reachability Service Profile
Create an Address Reachability Service (ARS) Profile for Cisco servers, which will be applied to the Cisco SIP
Trunk Group. ARS allows peers to be blacklisted when unresponsive, allowing faster route-advancing.
Parameter
Description
CISCO_ARS
Name of Address Reachability Service (ARS) Profile
Types of algorithms used for blacklisting endpoints: SIP INVITE
timeouts and 503 w/retry-after response.
Type of recovery mechanism for blacklisted endpoints. Probe
mechanism is a SIP OPTIONS message.
blkListAlgorithms timeouts,retryafter
recoveryAlgorithm probe
set profiles services sipArsProfile CISCO_ARS
set profiles services sipArsProfile CISCO_ARS blkListAlgorithms timeouts,retryafter
set profiles services sipArsProfile CISCO_ARS blkListAlgRetryAfterType sip-503
set profiles services sipArsProfile CISCO_ARS blkListAlgTimeoutsType sip-invite
set profiles services sipArsProfile CISCO_ARS blkListAlgTimeoutsNumTimeouts 4
set profiles services sipArsProfile CISCO_ARS blkListAlgTimeoutsDuration 120
set profiles services sipArsProfile CISCO_ARS recoveryAlgorithm probe
set profiles services sipArsProfile CISCO_ARS recoveryAlgProbeInterval 30
set profiles services sipArsProfile CISCO_ARS recoveryAlgProbeNumResponses 6
set profiles services sipArsProfile CISCO_ARS recoveryAlgProbeDuration 240
commit
13
4.4
Internal Side SBC Configuration
IP Interface Group
The following configuration is for a Sonus 52x0 system using Media 0 port for Internal connectivity. SBC 5000
Media ports do not have dedicated Internal/External roles and, while recommended, the Sonus convention does
not need 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 Administrator’s Guide (NDAG) professional services offerings.
Create an IP Interface Group and assign it interfaces, including IP addresses.
Parameter
Description
default
Name of the address context
IPIG_INTERNAL
IP Interface Group name for the internal side of the SBC
LITTLE
SBC element name
IPIF_INTERNAL
Name for IP Interface (on pkt0)
pkt0
Gigabit Ethernet port used for internal signaling and media
10.35.177.246
IP address for the first internal media port
26
IP subnet prefix (subnet mask in CIDR format)
set addressContext default ipInterfaceGroup IPIG_INTERNAL
commit
set addressContext default ipInterfaceGroup IPIG_INTERNAL ipInterface IPIF_INTERNAL ceName LITTLE
set addressContext default ipInterfaceGroup IPIG_INTERNAL ipInterface IPIF_INTERNAL portName pkt0
set addressContext default ipInterfaceGroup IPIG_INTERNAL ipInterface IPIF_INTERNAL ipAddress
10.35.177.246 prefix 26
set addressContext default ipInterfaceGroup IPIG_INTERNAL ipInterface IPIF_INTERNAL mode inService state
enabled
commit
IP Static Route
Create a default route to the subnet’s IP nexthop for the IP Interface Group and Interfaces.
Parameter
Description
default
0.0.0.0
Default route
0
10.35.177.193
IP Nexthop for subnet
IPIG_INTERNAL
IPIF_INTERNAL
100
Preference of the route within the Interface Group
set addressContext default staticRoute 0.0.0.0 0 10.35.177.193 IPIG_INTERNAL IPIF_INTERNAL preference
100
commit
14
4.5
SBC Configuration for Cisco UCM
Profile Configuration
Packet Service Profile (PSP)
Create a Packet Service Profile (PSP) for the Cisco SIP trunk with a single codec specified. The PSP is specified
within the SIP Trunk Group configuration.
Parameter
Description
PSP_CISCO
Name of the Cisco PSP
G729A_20ms_2833_T38
Use the codecs created earlier (global config section)
G711U_20ms_2833_T38
G711A_20ms_2833_T38
Conditional
Only transcode, if certain conditions are met
G729A, G771U, G711A
Codecs on this leg
differentDtmfRelay
Allow transcoding for different DTMF relay behaviors
differentPacketSize
Allow transcoding for different codec packet sizes
set profiles media packetServiceProfile PSP_CISCO
set profiles media packetServiceProfile PSP_CISCO codec codecEntry1 G729A_20ms_2833_T38
set profiles media packetServiceProfile PSP_CISCO codec codecEntry2 G711U_20ms_2833_T38
set profiles media packetServiceProfile PSP_CISCO codec codecEntry3 G711A_20ms_2833_T38
set profiles media packetServiceProfile PSP_CISCO preferredRtpPayloadTypeForDtmfRelay 101
set profiles media packetServiceProfile PSP_CISCO packetToPacketControl transcode conditional
set profiles media packetServiceProfile PSP_CISCO packetToPacketControl codecsAllowedForTranscoding
thisLeg g711u
set profiles media packetServiceProfile PSP_CISCO packetToPacketControl
conditionsInAdditionToNoCommonCodec differentDtmfRelay enable differentPacketSize enable
differentSilenceSuppression enable
commit
15
IP Signaling Profile (IPSP)
Create a IP Signaling Profile (IPSP) for the Cisco SIP trunk. The IPSP will be specified within the SIP Trunk
Group configuration and in order to relay a 4xx, 5xx and 6xx message from Cisco to Verizon, the flag below must
be checked. If the Cisco doesn’t send back a Reason header on a 4xx, 5xx or 6xx message this flag is not
required to be enabled. If the Reason header is present the SBC will turn a 404 into a 502.
Parameter
Description
CISCO_IPSP
Name of the SIP Carrier IPSP
Enable this flag to relay the error status codes (4xx, 5xx, or 6xx)
in response to initial INVITE requests (does not apply to reINVITEs). Provision this flag on the trunk group that receives the
error response (the egress leg of the call).
Status Code4xx6xx
set profiles signaling ipSignalingProfile CISCO_IPSP
set profiles signaling ipSignalingProfile CISCO_IPSP commonIpAttributes relayFlags statusCode4xx6xx
enable
commit
Address Context Configuration
As mentioned earlier, as no overlapping IP addressing is used on the SBC in this document, all configuration is
under the default Address Context.
Zone
Parameter
Description
default
ZONE_INTERNAL
Name of the Cisco Zone
4
A unique numeric identifier (2-2048) for the zone
set addressContext default zone ZONE_INTERNAL id 4
commit
16
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.
Parameter
Description
default
ZONE_INTERNAL
IPIG_INTERNAL
sip-udp, sip-tcp
Transport protocols allowed for SIP signaling to Cisco SIP
10.35.177.247
IPv4 address for the SIP Signaling Address for the SBC
5060
SIP signaling TCP/UDP port of SBC
26
DiffServ Code Point value for SIP signaling traffic from SBC
set addressContext default zone ZONE_INTERNAL sipSigPort 15 ipInterfaceGroup IPIG_ZONE_INTERNAL
set addressContext default zone ZONE_INTERNAL sipSigPort 15 transportProtocolsAllowed sip-udp,sip-tcp
set addressContext default zone ZONE_INTERNAL sipSigPort 15 ipAddressV4 10.35.177.247
set addressContext default zone ZONE_INTERNAL sipSigPort 15 portNumber 5060 dscpValue 26
set addressContext default zone ZONE_INTERNAL sipSigPort 15 state enabled mode inService
commit
IP Peer
Create a IP Peer with the signaling IP addresses of the Cisco SIP Servers and assign it to the Cisco Zone.
The IP Peer entity is used on egress, while the ingressIpPrefix parameter in the sipTrunkGroup entity is used on
ingress, for determining the applicable SIP Trunk Group.
These two IP Peers represent an active-standby pair of Cisco SIP Servers for redundancy.
Parameter
Description
default
ZONE_INTERNAL
PEER-CISCO-10
Name of the Cisco IP Peer
10.35.180.109
IP Address of Cisco SIP Server
5060
SIP signaling TCP/UDP port of Cisco SIP Server
set addressContext default zone ZONE_INTERNAL ipPeer PEER-CISCO-10 ipAddress 10.35.180.109 ipPort 5060
commit
17
SIP Trunk Group
Create a SIP Trunk Group ZONE_INTERNAL for the Cisco SIP Server and assign the corresponding Profiles
configured earlier in this document.
Parameter
Description
default
ZONE_INTERNAL
CISCO-CUCM-10.5
10.35.180.109
Name of the SIP Trunk Group for the Cisco SIP
IP Interface Group name for the ZONE_INTERNAL side of the
SBC
IP Address of Cisco SIP Server
32
IP prefix (subnet mask in CIDR format)
PSP_CISCO
Earlier created PSP is applied in the Trunk Group
CISCO_ARS
ARS Profile
IPIG_ZONE_INTERNAL
set addressContext default zone ZONE_INTERNAL sipTrunkGroup CISCO-CUCM-10.5 media
mediaIpInterfaceGroupName ZONE_INTERNAL
set addressContext default zone ZONE_INTERNAL sipTrunkGroup CISCO-CUCM-10.5 ingressIpPrefix
10.35.180.109 32
set addressContext default zone ZONE_INTERNAL sipTrunkGroup CISCO-CUCM-10.5 policy signaling
ipSignalingProfile CISCO_IPSP
set addressContext default zone ZONE_INTERNAL sipTrunkGroup CISCO-CUCM-10.5 policy media
packetServiceProfile PSP_CISCO
set addressContext default zone ZONE_INTERNAL sipTrunkGroup CISCO-CUCM-10.5 services sipArsProfile
CISCO_ARS
set addressContext default zone ZONE_INTERNAL sipTrunkGroup CISCO-CUCM-10.5 signaling methods publish
reject register reject subscribe reject
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CISCO-CUCM-10.5 signaling rel100Support
disabled
set addressContext default zone ZONE_INTERNAL sipTrunkGroup CISCO-CUCM-10.5 state enabled mode inService
commit
18
4.6
External Side SBC Configuration
IP Interface Group
The following configuration is for a Sonus 52x0 system using Media 2 port for external connectivity and Media
Port 3 due to the Verizon requirement of separating RTP from the signaling VPN tunnel. If this requirement is not
levied on all Verizon SIP trunks then it’s possible to use one media port for both signaling and RTP. SBC 5000
Media ports do not have dedicated Internal/External roles and, while recommended, the Sonus convention does
not need 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 Administrator’s Guide? (NDAG) professional services offerings.
Create an IP Interface Group and assign interfaces; including IP addresses.
Parameter
Description
default
IPIG_EXTERNAL
IP Interface Group name for the external side of the SBC
LITTLE
SBC element name
IPIF_EXTERNAL
pkt2
Gigabit Ethernet port used for external signaling and media
10.35.177.165
IP address for the first external media port
26
Create an IP Interface Group for RTP only and assign interfaces; including IP addresses.
Parameter
Description
default
IPIG_EXTERNAL_2
LITTLE
SBC element name
IPIF_EXTERNAL_2
Pkt3
Gigabit Ethernet port used for external signaling and media
216.110.2.228
IP address for the first external media port
28
set addressContext default ipInterfaceGroup IPIG_EXTERNAL
commit
set addressContext default ipInterfaceGroup IPIG_EXTERNAL ipInterface IPIF_EXTERNAL ceName LITTLE
set addressContext default ipInterfaceGroup IPIG_EXTERNAL ipInterface IPIF_EXTERNAL portName pkt2
set addressContext default ipInterfaceGroup IPIG_EXTERNAL ipInterface IPIF_EXTERNAL ipAddress
10.35.177.165 prefix 26
set addressContext default ipInterfaceGroup IPIG_EXTERNAL ipInterface IPIF_EXTERNAL mode inService state
enabled
set addressContext default ipInterfaceGroup IPIG_EXTERNAL_2
commit
set addressContext default ipInterfaceGroup IPIG_EXTERNAL_2 ipInterface IPIF_EXTERNAL_2 ceName LITTLE
set addressContext default ipInterfaceGroup IPIG_EXTERNAL_2 ipInterface IPIF_EXTERNAL_2 portName pkt3
19
set addressContext default ipInterfaceGroup IPIG_EXTERNAL_2 ipInterface IPIF_EXTERNAL_2 ipAddress
10.35.177.165 prefix 28
set addressContext default ipInterfaceGroup IPIG_EXTERNAL_2 ipInterface IPIF_EXTERNAL_2 mode inService
state enabled
commit
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
10.35.177.193
IPIG_INTERNAL
IPIF_INTERNAL
100
Parameter
Description
default
0.0.0.0
Default route
0
10.35.177.129
IPIG_EXTERNAL
IPIF_EXTERNAL
100
Parameter
Description
default
0.0.0.0
Default route
0
216.110.2.225
IPIG_EXTERNAL_2
IPIF_EXTERNAL_2
100
set addressContext default staticRoute 0.0.0.0 0 10.35.177.129 IPIG_EXTERNAL IPIF_EXTERNAL preference
100
set addressContext default staticRoute 0.0.0.0 0 10.35.177.193 IPIG_INTERNAL IPIF_INTERNAL preference
100
set addressContext default staticRoute 0.0.0.0 0 216.10.2.225 IPIG_EXTERNAL_2 IPIF_EXTERNAL_2 preference
100
20
commit
4.7
SBC Configuration for SIP Carrier
This section only applies if callers ingress the enterprise via a SIP Carrier. If callers ingress the enterprise via
local PSTN circuits (PRI or CAS trunks), then a SIP Trunk Group would need to be built to whatever Media
Gateway is terminating the PSTN circuits (such as a Sonus GSX9000 Media Gateway). This section is also for a
generic SIP Carrier. If one is available, refer to the Sonus SBC 5000 Application Note that is specific to your
carrier.
Profile Configuration
Packet Service Profile (PSP)
Create a Packet Service Profile (PSP) for the SIP trunk with a single codec specified. The PSP is specified within
the SIP Trunk Group configuration.
Parameter
Description
PSP_VZ
Name of the PSP for SIP Carrier
G729A_20ms_2833_T38
Use of codec created earlier (global config section)
G711U_20ms_2833_T38
G711A_20ms_2833_T38
Conditional
Only transcode if certain conditions are met
G729A , G711U, G711A
Codecs on this leg
differentDtmfRelay
Allow transcoding for different DTMF relay behaviors
differentPacketSize
Allow transcoding for different codec packet sizes
set profiles media packetServiceProfile PSP_VZ
set profiles media packetServiceProfile PSP_VZ codec codecEntry1 G729A_20ms_2833_T38
set profiles media packetServiceProfile PSP_VZ codec codecEntry2 G711U_20ms_2833_T38
set profiles media packetServiceProfile PSP_VZ codec codecEntry3 G711A_20ms_2833_T38
set profiles media packetServiceProfile PSP_VZ preferredRtpPayloadTypeForDtmfRelay 101
set profiles media packetServiceProfile PSP_VZ packetToPacketControl transcode conditional
set profiles media packetServiceProfile PSP_VZ packetToPacketControl codecsAllowedForTranscoding
thisLeg g711u
set profiles media packetServiceProfile PSP_VZ packetToPacketControl
conditionsInAdditionToNoCommonCodec differentDtmfRelay enable differentPacketSize enable
commit
21
IP Signaling Profile (IPSP)
Create an IP Signaling Profile (IPSP) for the SIP Carrier SIP trunk. The IPSP is specified within the SIP Trunk
Group configuration.
Parameter
Description
VZ_IPSP
Name of the SIP Carrier IPSP
If enabled, the 2806 Compliance Code is disabled, and no phone
context or user=phone parameters are signaled in egress
messages.
By default, the SBC includes SDP in outbound 180 messages.
When enabled, the SBC does not include SDP in outbound 180
messages. It converts the 180 message to a 183 message
instead. When disabled, the SBC includes SDP in outbound 180
messages.
Disable2806Compliance
NoSdpIn180Supported
Never send 183 without SDP.
Suppress183WithoutSdp
set profiles signaling ipSignalingProfile VZ_IPSP
set profiles signaling ipSignalingProfile VZ_IPSP egressIpAttributes flags disable2806Compliance enable
set profiles signaling ipSignalingProfile VZ_IPSP ingressIpAttributes flags noSdpIn180Supported eable
set profiles signaling ipSignalingProfile VZ_IPSP ingressIpAttributes flags suppress183WithoutSdp enable
commit
Address Context Configuration
As mentioned earlier, as no overlapping IP addressing is used on the SBC in this document, all configuration will
be done under the default Address Context.
Zone
This Zone groups the set of objects used for the communication to the SIP Carrier.
Parameter
Description
default
ZONE_EXTERNAL
Name of the SIP Carrier Zone
20
A unique numeric identifier (2-2048) for the zone
set addressContext default zone ZONE_EXTERNAL id 20
commit
22
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 SIP Carrier zone and will send and receive SIP packets
for the SIP Carrier.
NOTE: Verizon requires UDP on its SIP trunk therefore only udp is selected for the SIP signaling port.
Parameter
Description
default
ZONE_EXTERNAL
4
A unique numeric identifier (1-2048) for the signaling port
IPIG_EXTERNAL
sip-udp
Transport protocols allowed for SIP signaling to SIP Carrier
10.35.177.188
IPv4 address for the SIP Signaling Address for the SBC
5060
SIP signaling TCP/UDP port of SBC
46
DiffServ Code Point value for SIP signaling traffic from SBC
set addressContext default zone ZONE_EXTERNAL sipSigPort 20 ipInterfaceGroup IPIG_EXTERNAL
set addressContext default zone ZONE_EXTERNAL sipSigPort 20 transportProtocolsAllowed sip-udp
set addressContext default zone ZONE_EXTERNAL sipSigPort 20 ipAddressV4 10.35.177.188
set addressContext default zone ZONE_EXTERNAL sipSigPort 20 portNumber 5060 dscpValue 46
set addressContext default zone ZONE_EXTERNAL sipSigPort 20 state enabled mode inService
commit
IP Peer
Create an IP Peer with the signaling IP address of the SIP Carrier peer and assign it to the SIP Carrier 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
ZONE_EXTERNAL
PEER_CARRIER_VZ
Name of the SIP Carrier IP Peer
63.79.179.178
IP Address of SIP Carrier SIP Server
5060
SIP signaling TCP/UDP port of SIP Carrier SIP Server
set addressContext default zone ZONE_EXTERNAL ipPeer PEER_CARRIER_VZ ipAddress 63.79.179.178 ipPort 5060
commit
23
SIP Trunk Group
Create a SIP Trunk Group externally for the SIP Carrier and assign the corresponding Profiles configured earlier
in this document.
Parameter
Description
default
ZONE_EXTERNAL
CARRIER_VZ
Name of the SIP Trunk Group for SIP Carrier
EXTERNAL_IPIG
63.79.179.178
IP Address of SIP Carrier SIP Server
32
IP prefix (subnet mask in CIDR format)
PSP_VZ
Earlier created PSP is applied in the Trunk Group
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CARRIER_VZ media mediaIpInterfaceGroupName
IPIG_EXTERNAL
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CARRIER_VZ ingressIpPrefix 63.79.179.178 32
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CARRIER_VZ policy signaling
ipSignalingProfile VZ_IPSP
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CARRIER_VZ policy media packetServiceProfile
PSP_VZ
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CARRIER_VZ policy digitParameterHandling
numberingPlan NANP_ACCESS
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CARRIER_VZ signaling methods publish reject
register reject subscribe reject
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CARRIER_VZ signaling rel100Support disabled
set addressContext default zone ZONE_EXTERNAL sipTrunkGroup CARRIER_VZ state enabled mode inService
commit
24
4.8
Global Call Routing Configuration
A Routing Label (RL) is a user-named object that contains a list of one or more nexthop peers - defined as
Routing Label Routes - that can reach a specified destination.
A Routing Label Route (RLR) defines a single peer (Trunk Group + 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 peers (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.
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 providing support for SIP Registration-based endpoints (sometimes referred to as an Access environment
to differentiate it from Trunking), 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 Trunk Group of the SIP Server for
messages lacking called/calling numbers (e.g. SIP Registrations, etc…)
This prioritization can be accomplished by creating a new ERP profile and applying it on all the Access-related
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 default object for the profile; in this case, the ERP.
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
set profiles callRouting elementRoutingPriority DEFAULT_IP entry _private 1 entityType trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry nationalOperator 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry nationalOperator 1 entityType
trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry transit 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry transit 1 entityType trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry carrierCutThrough 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry carrierCutThrough 1 entityType
trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry localOperator 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry localOperator 1 entityType trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry userName 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry userName 1 entityType trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry internationalOperator 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry internationalOperator 1 entityType
trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry longDistanceOperator 2 entityType none
25
set profiles callRouting elementRoutingPriority DEFAULT_IP entry longDistanceOperator 1 entityType
trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry otherCarrierChosen 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry otherCarrierChosen 1 entityType
trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry internationalType 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry internationalType 1 entityType
trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry mobile 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry mobile 1 entityType trunkGroup
set profiles callRouting elementRoutingPriority DEFAULT_IP entry test 2 entityType none
set profiles callRouting elementRoutingPriority DEFAULT_IP entry test 1 entityType trunkGroup
commit
Cisco Routing
Routing Label
Create a Routing Label with a single Routing Label Route to bind the Cisco SIP Trunk Group with the Cisco SIP
IP Peer.
Parameter
Description
RL_TO_CISCO
Name of the Routing Label for Cisco SIP
Sequence
The prioritization of Routing Label Routes within a Routing Label
1
The first Routing Label Route within the Routing Label
CISCO-CUCM-10.5
Trunk Group for Cisco SIP
PEER-CISCO-10.5
IP Peer for Cisco SIP
set global callRouting routingLabel RL_TO_CISCO routePrioritizationType sequence action routes
routingLabelRoute 1 trunkGroup CISCO-CUCM-10.5 ipPeer PEER-CISCO-10.5 inService inService
commit
26
SIP Carrier Routing
Routing Label
Create a Routing Label with a single Routing Label Route to bind the SIP Carrier Trunk Group with the SIP
Carrier IP Peers.
Parameter
Description
RL_TO_CARRIER_VZ
Name of the Routing Label for SIP Carrier
Sequence
The prioritization of Routing Label Routes within a Routing Label
1
The first Routing Label Route within the Routing Label
CARRIER_VZ
Trunk Group for SIP Carrier
PEER_CARRIER_VZ
IP Peer for SIP Carrier
set global callRouting routingLabel RL_TO_CARRIER_VZ routePrioritizationType sequence action routes
routingLabelRoute 1 trunkGroup CARRIER_VZ ipPeer PEER_CARRIER_VZ inService inService
commit
Routing
Routing is the final step in the SBC configuration which must be provisioned in order to send calls to the correct
destination. Within the Route entity, all available Route Match Criteria are used to determine the most specific
match which is linked to Routing Labels (destinations). The result of a Route match is a Routing Label. Routing
Labels were created in earlier sections of this document.
For the purposes of this Application Note, routing was kept simple and limited to lab scenarios.
Only trunk group routing was applied for calls from/to Cisco and to/from carrier. Calls from carrier trunk group
CARRIER_VZ are routed to the Cisco servers (via the RL_TO_CISCO Route Label which maps to the CISCOCUCM-10.5 Trunk Group and Cisco IP Peer) and calls from Cisco (via the RL_TO_CARRIER_VZ Route Label
which maps to the CARRIER_VZ Trunk Group and carrier IP Peers)
In practice, call routing configuration will likely revolve around the enterprise’s dial plan. For specific help in
planning and/or implementing your routing contact your local Sales team for information regarding the Sonus
Routing Design (SSDB) professional services offerings.
Create Route entries for Trunk Group routing with Matching Criteria and a Route Label destination.
Parameter
Description
trunkGroup
standard / username
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)
CARRIER_VZ
LITTLE
27
none
Call Parameter Filter Profile
Sonus_NULL
Destination Domain Name
RL_TO_CISCO
Destination Routing Label
set global callRouting route trunkGroup CARRIER_VZ LITTLE standard Sonus_NULL Sonus_NULL all all ALL
none Sonus_NULL routingLabel RL_TO_CISCO
commit
Parameter
Description
trunkGroup
standard / username
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
RL_TO_CARRIER_VZ
Destination Routing Label
CISCO-CUCM-10.5
LITTLE
set global callRouting route trunkGroup CISCO-CUCM-10.5 LITTLE standard Sonus_NULL Sonus_NULL all all
ALL none Sonus_NULL routingLabel RL_TO_CARRIER_VZ
commit
28
5 Cisco configuration
This section assumes that the CUCM 10.5 components have been installed. The user should be familiar with
administration and configuration of CUCM 10.5. This section does not cover the installation of CUCM 10.5.
5.1
CUCM 10.5 Configuration Settings
The CUCM 10.5 was configured per the details provided in the Cisco Configuration and Administration Guide:
This guide is available online at the following location:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/10_5_2/CUP0_BK_CEB3E82E_00_configadmin-guide-imp-1052.html
In order to connect Cisco CUCM 10.5 PBX to the SBC 5000 the following objects must be created and properly
associated.
1.
2.
3.
4.
Trunk Group (TG)
Route Group (RG)
Route List (RL)
Route Pattern (RP)
Login to CUCM
Login to the Administration Portal of the Communication Manager, type in valid credentials and login.
Figure 5.1
CUCM Administration Page
29
SIP Trunk Security Profile
From the menu bar:
1. Select System > Security Profile > SIP Trunk Security Profile.
2. Select the Device Security Mode.
3. Select the Transport Type.
This certification utilized UDP between Cisco and the Sonus SBC.
Figure 5.2
Security Trunk Profile
30
SIP Profile
From the menu bar, select Device > Device Settings > SIP Profile.
Figure 5.3
SIP Profile
31
Figure 5.4
SIP Profile (cont’d)
32
Figure 5.5
Figure 5.6
33
Create a New TG
From the menu bar:
1. Select Device > Trunk.
2. Click the “Add New” button.
3. Select a Trunk Type.
4. Select a Device Protocol.
5. Click Next.
Figure 5.7
Trunk Group
34
Figure 5.8
Trunk Group (cont’d)
35
Figure 5.9
36
Figure 5.10
37
Figure 5.11
38
Create New Route Group
From the menu bar:
1. Select Call Routing > Route-Hunt > Route Group
2. Click Add New..
(Note that the TG must already be added and will be displayed as an Available Devices under the Find
Devices to Add to Route Group area.
3. Select the appropriate TG.
4. Click Add to Route.
5. Enter a Route Group Name (refer to CUCM 10.5 guide for more detail).
Figure 5.12
Route Group
39
Create a New Route List
From the menu bar:
1. Select Call Routing > Route-Hunt > Route List.
2. Click Add New.
3. Enter the Name.
4. Enter a Description,
5. Click Add Route Group.
6. On the next screen, select the Route Group that was just created (refer to CUCM 10.5 guide for more
detail).
Figure 5.13
Route List
40
Create a New Route Pattern
From the menu bar:
1. Select Call Routing > Route-Hunt > Route Pattern.
2. Click Add New.
3. Enter the Route Pattern.
4. Click Save.
Figure 5.14
Route Pattern
41
Figure 5.15
Route Pattern (cont’d)
42

Configuring the Sonus SBC 5000 with Cisco Unified Communication

Transcription

Similar documents

Cisco Recruitment Session* When

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

the flyer

ZX50 SPEC V3

VS-GW1200-4G Datasheet

Passerelle GSM - voipsolutions.gr

the Konftel 300IP for innovative teleconferences

crescent village - Prime Commercial, Inc.