Configuring Sonus SBC 5100
with
Cisco CallManager Express
Application Notes
Last Updated: April 27, 2012
Sonus Networks Interoperability Test Lab
Contents
1 Document Overview .............................................................................. 3
2 Introduction ........................................................................................... 4
2.1.
Audience ........................................................................................................................................ 4
2.2.
Requirements ................................................................................................................................. 4
2.3.
Test Scenario ................................................................................................................................. 4
2.4.
Reference Configuration ................................................................................................................ 5
2.5.
Support ........................................................................................................................................... 5
3 Phase I - Configure CME....................................................................... 6
3.1.
Verify License ................................................................................................................................. 6
3.2.
Configuring the Cisco CME ............................................................................................................ 6
4 Phase II - Configure Sonus SBC 5100 .................................................. 9
4.1.
Basic Configuration ........................................................................................................................ 9
4.2.
Configuring the IP Peer ................................................................................................................ 10
4.3.
Configuring the SIP Trunk Group ................................................................................................. 11
4.4.
Configuring the IP Signaling Profile ............................................................................................. 12
4.5.
Configuring the Packet Service Profile ........................................................................................ 16
4.6.
Configuring the Call Routing ........................................................................................................ 18
5 Phase III - Interoperability Testing ....................................................... 19
5.1.
Test Results ................................................................................................................................. 19
6 Conclusion .......................................................................................... 20
2 of 20
Sonus Networks Interoperability Test Lab
1 Document Overview
These Application Notes describe the configuration steps required for Sonus Session Border
Controller 5100 (SBC 5100) to interoperate with Cisco Call Manager Express using SIP trunks.
Sonus SBC 5100 is a robust solution that integrates security, call control, Quality of Service,
advanced media services and switching all within a compact platform. SBC5100 was compliance
tested utilizing a SIP trunk to Cisco Call Manager Express.
The objective of the document is to describe the procedure to be followed during IOT of SBC 5100
with Cisco Call Manager Express 8.6. It includes identifying the testing environment, tools, topology,
points, risks, and scope.
For additional information on Cisco CME, visit http://www.cisco.com
For additional information on Sonus SBC, visit http://www.sonusnet.com
Sonus Networks Interoperability Test Lab
3 of 20
2 Introduction
The interoperability compliance testing focuses on verifying inbound and outbound call flows
between Sonus SBC 5100 and Cisco Call Manager Express.
2.1. Audience
This technical document is intended for telecommunication engineers with the purpose of configuring
the Sonus SBC and the third-party product. There will be steps that require navigating the third-party
product 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.
2.2. Requirements
The following equipments and software were used for the sample configuration provided:
Equipment
Sonus Networks
• SBC 5100
• BMC
• BIOS
• ConnexIP OS
• SonusDB
• EMA
• SBX
Software
3.0.0R000
v1.12.0
v1.5.25
v1.7.2
sonusdb-V03.00.00-A011
ema- V03.00.00-A011
sbx- V03.00.00-A011
Third-party Equipments
•
Cisco 2951
15.1(4)M1
Other software
2.3. Test Scenario
Sonus SBC 5100 was used at an enterprise site consisting of Cisco Call Manager Express. SIP
trunks were used to connect SBC 5100 to the enterprise site and to a simulated PSTN/Service
Provider.
The following features and functionality were covered during compliance testing:
4 of 20
•
Incoming calls to the Enterprise site through Sonus SBC 5100
•
Outgoing calls from the Enterprise site through Sonus SBC 5100
•
Calls using various codecs
•
DTMF tone transmission using RFC 2833
•
Telephony features such as hold, resume, transfer, conference, and call forwarding.
Sonus Networks Interoperability Test Lab
Serviceability testing focused on verifying the ability of Sonus SBC 5100 to recover from adverse
conditions, such as disconnecting/reconnecting the Ethernet cable and stopping/starting Sonus SBC
5100 and Call Manager Express.
2.4. Reference Configuration
A simulated enterprise site consisting of Cisco Call Manager Express Version 8.6 and Sonus SBC
5100 Version 3.0 were used during the compliance testing. SIP trunks were used to connect Sonus
SBC 5100 with Call Manager Express. SBC 5100 was also connected to a simulated PSTN/Service
Provider via a SIP trunk. The configuration allowed the enterprise site to use SIP trunking for calls to
and from the simulated PSTN/Service Provider via SBC 5100.
The following reference configuration shows connectivity between third-party product and Sonus
SBC 5100.
Figure 1 Sonus SBC 5100 with Cisco Call Manager Express
2.5. Support
Technical support on Sonus SBC 5100 can be obtained through the following:
•
Phone: (978) 614-8589 or (888) 391-3434 (Toll-free)
•
Web: http://sonusnetworks.force.com/PortalLoginPage
Sonus Networks Interoperability Test Lab
5 of 20
3 Phase I - Configure CME
This section provides the procedures for configuring Cisco Call Manager Express. Third-party
product features are:
•
Call Back
•
Call Pickup
•
Call Park
•
Music on Hold
•
Call Transfer
•
Call Forward
3.1. Verify License
Log in to the System to verify that the Call Manager Express license has valid permissions for
features illustrated in these Application Notes. Issue the command “show license” on the CLI of Call
Manager Express to view a detailed report.
3.2. Configuring the Cisco CME
The Cisco Router 2951 was used as the Cisco Call Manager Express.
Configuration on the Cisco Router
voice service voip
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback
none
sip
registrar server expires max 1200 min 300
!
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 ilbc
!
!
voice register global
mode cme
load 7962 P0S3-08-9-00
create profile sync 0951143459393176
!
!
!
!
license udi pid CISCO2951/K9 sn FGL153810V4
hw-module pvdm 0/0
6 of 20
Sonus Networks Interoperability Test Lab
dial-peer voice 2 voip
description "Towards NBS51K1"
destination-pattern 4444
session protocol sipv2
session target ipv4:172.16.104.160
session transport udp
dtmf-relay rtp-nte
codec g711ulaw
dial-peer voice 100 voip
description "Towards NBS 5100"
destination-pattern 5512
session protocol sipv2
session target ipv4:172.16.104.160
session transport udp
dtmf-relay rtp-nte
codec g711ulaw
telephony-service
no auto-reg-ephone
max-ephones 20
max-dn 50
ip source-address 10.54.18.197
load 7962 P003-08-9-00
max-conferences 8 gain -6
call-forward pattern ....
moh music-on-hold.au
multicast moh 239.10.16.4 port
transfer-system full-consult
transfer-pattern 4...
create cnf-files version-stamp
!
!
ephone-dn 1 dual-line
number 5600001
pickup-group 111
name CME-Phone1
call-forward busy 5512
call-forward noan 5512 timeout
huntstop channel
no huntstop
!
!
ephone-dn 2
number 5600002
pickup-group 111
name CME-Phone2
call-forward busy 6666
!
!
ephone 1
mac-address 2037.0617.E5E1
port 2000
16384
7960 Apr 01 2012 14:12:28
10
Sonus Networks Interoperability Test Lab
7 of 20
busy-trigger-per-button 1
blf-speed-dial 3 4444 label "Polycom"
type 7962
keep-conference
button 1:1
!
!
!
ephone 2
mac-address E8BA.70FB.DE50
type 7962
keep-conference
button 1:2
!
8 of 20
Sonus Networks Interoperability Test Lab
4 Phase II - Configure Sonus SBC 5100
This section provides a snapshot of SBC 5100 configuration used during compliance testing. SBC
5100 is configured for customers by Sonus Networks. Use the figures and partial configuration
supplied by Sonus Networks for reference alone. Additional configurations are required based on the
network requirements.
4.1. Basic Configuration
This is the basic configuration required to invoke the Logical Interfaces for signaling and media.
1. Configure Address Context and Logical Interface.
set addressContext a1 ipInterfaceGroup LIF2 ipInterface pkt1_v4 ceName
NBS51K1 portName pkt1 ipAddress 172.16.104.160 prefix 24
set addressContext a1 ipInterfaceGroup LIF2 ipInterface pkt1_v4 mode
inService state enabled
commit
2. Configure the Zone and SIP Signaling port.
set addressContext a1 zone Z2 id 3 sipSigPort 2 ipInterfaceGroupName
LIF2 ipAddressV4 172.16.104.160
set addressContext a1 zone Z2 sipSigPort 2 transportProtocolsAllowed
sip-udp portNumber 5060
set addressContext a1 zone Z2 sipSigPort 2 mode inService state enabled
commit
3. Verify Configuration using the show command.
[edit]
admin@NBS51K1% show addressContext a1 zone Z2 sipSigPort
sipSigPort 2 {
ipInterfaceGroupName
LIF2;
ipAddressV4
172.16.104.160;
portNumber
5060;
mode
inService;
state
enabled;
transportProtocolsAllowed sip-udp;
}
[ok][2012-04-02 03:33:12]
[edit]
admin@NBS51K1%
Sonus Networks Interoperability Test Lab
9 of 20
4.2. Configuring the IP Peer
Configure the IP Peer on SBC 5100 using the following procedure.
Procedure to configure IP Peer
1. Configure the IP Address of the Cisco CME as IP Peer in the zone.
set addressContext a1 zone Z2 ipPeer CME ipAddress 10.54.18.197 ipPort
5060
commit
2. Verify Configuration using the show command.
[edit]
admin@NBS51K1% show addressContext a1 zone Z2 ipPeer CME
ipAddress 10.54.18.197;
ipPort
5060;
policy {
description
"";
sip {
fqdn
"";
fqdnPort 0;
}
packetServiceProfile "";
ipSignalingProfile
"";
}
10 of 20
Sonus Networks Interoperability Test Lab
4.3. Configuring the SIP Trunk Group
Configure the IP Peer on SBC 5100 using the following procedure.
Configuring the SIP Trunk Group
1. Use the following command to configure the SIP Trunk Group for Cisco CME.
set addressContext a1 zone Z2 sipTrunkGroup CME_STG media
mediaIpInterfaceGroupName LIF2
set addressContext a1 zone Z2 sipTrunkGroup CME_STG ingressIpPrefix
10.54.18.197 32
set addressContext a1 zone Z2 sipTrunkGroup CME_STG policy signaling
ipSignalingProfile DEFAULT_SIP
set addressContext a1 zone Z2 sipTrunkGroup CME_STG policy media
packetServiceProfile DEFAULT
set addressContext a1 zone Z2 sipTrunkGroup CME_STG mode inService
state enabled
commit
2. Verify configuration using the show command.
[edit]
admin@NBS51K1% show addressContext a1 zone Z2 sipTrunkGroup CME_STG
state enabled;
mode inService;
policy {
carrier
0000;
country
1;
sipDomain
"";
localizationVariant northAmerica;
digitParameterHandling {
numberingPlan
NANP_ACCESS;
ingressDmPmRule "";
egressDmPmRule "";
}
callRouting {
elementRoutingPriority DEFAULT_IP;
}
media {
packetServiceProfile DEFAULT;
}
services {
classOfService DEFAULT_IP;
}
signaling {
ipSignalingProfile DEFAULT_SIP;
Sonus Networks Interoperability Test Lab
11 of 20
signalingProfile
"";
}
}
media {
mediaIpInterfaceGroupName LIF2;
}
ingressIpPrefix 10.54.18.197 32;
4.4. Configuring the IP Signaling Profile
Use the default IP Signaling Profile with the following modifications.
Modifying the IP Signaling Profile
1. Configure the RFC2806 compliance.
set profiles signaling ipSignalingProfile DEFAULT_SIP
egressIpAttributes flags disable2806Compliance enable
commit
2. Configure the Number Globalization Profile.
delete profiles signaling ipSignalingProfile DEFAULT_SIP
egressIpAttributes numberGlobalizationProfile
commit
3. Use the show command and verify the configuration.
admin@NBS51K1% show profiles signaling ipSignalingProfile
ipProtocolType sipOnly;
commonIpAttributes {
flags {
addPathServiceRoute
callHoldInterworking
clearmodeForDataCalls
createPChargingVector
createPathHeader
createServiceRouteHeader
customizedSessionTimerBehavior
disableAlsoHeader
disableHostTranslation
disableMediaLockDown
disableReferToUriParameters
discardReceivedReasonHeader
doNotIncludeSsAttributeInReInvite
endToEndBye
includeIpPortsInFromAndToHeaders
includeReasonHeader
includeSsAttributeInInitialInvite
includeTransportTypeInContactHeader
insertPeerAddressAsTopRouteHeader
mapCauseLocation
mapSuspendResumeEventInPSvcInfoHeader
mapUuiInPSigInfoHeader
12 of 20
DEFAULT_SIP
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
Sonus Networks Interoperability Test Lab
mimeCausePrecedeReasonHeaderCause
minimizeRelayingOfMediaChangesFromOtherCallLegAll
noContentDisposition
noPortNumber5060
noUserinfoInContactHeader
onlySelectedCodecInSessionRefresh
pChgMsgInfo
rejectRefer
replaceHostOnViaHeader
reQueryPsxOnRegisterRefresh
sdpOlineOnlyCompares
sendAllAllowedCodecsForLateMediaInviteOrReInvite
sendDirectMediaInfoInSdpAttribute
sendPtimeInSdp
sessionTimerRefreshUpdate
setAcceptHeaderToApplicationSdpOnly
setOlineDash
setSessionVersionZero
setSlineDash
skipPsxQueryForRefer
storePathHeader
storeServiceRouteHeader
terminalPortabilityInterworking
sendRtcpPortInSdp
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
}
callTransferFlags {
handleIpAddressesNotPresentInNetworkSelectorTableNst
routeViaTransferringIptg;
forceReRouteViaPsxQuery
disable;
}
optionTagInRequireHeader {
suppressReplaceTag disable;
}
optionTagInSupportedHeader {
suppressReplaceTag disable;
}
relayFlags {
dialogEventPackage disable;
dtmfBody
disable;
info
disable;
message
disable;
notify
disable;
options
disable;
regEventPackage
disable;
refer
disable;
sonusMediaBody
disable;
statusCode3xx
disable;
statusCode4xx6xx
disable;
thirdPartyBodies
disable;
}
transparencyFlags {
alertInformationHeader disable;
authcodeHeaders
disable;
Sonus Networks Interoperability Test Lab
13 of 20
contactHeader
errorInfo
fromHeader
historyInfo
maxForwardsHeader
mwiBody
pChargingVectorHeader
pEarlyMedia
pathHeader
qsigBody
reasonHeader
referredByHeader
requestURI
routeHeader
serviceRouteHeader
sipBody
sipfragBody
toHeader
toneBody
unknownBody
unknownHeader
viaHeader
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
disable;
}
}
egressIpAttributes {
numberGlobalizationProfile "";
flags {
bgcfTargetSchemeTransparency
disable;
convertInactiveToSendrecv
disable;
disable2806Compliance
enable;
disableOptionalRegisterParameters
disable;
map181Or182MessageTo183
disable;
mapContractorNumberInPSigInfoHeader disable;
suppressUnregister
disable;
ttcIsupMapping
disable;
useCalledPartyInRequestUri
disable;
useColonInSdpMediaTypeParameter
disable;
validateIsubAddress
disable;
}
bci {
bciInterworkEncountered disable;
bciIsdnAddess
disable;
}
domainName {
useSipDomainNameInFromField disable;
useSipDomainNameInRequestUri disable;
}
isub {
allowNsapIsub
disable;
allowUserSpecifiedIsub disable;
includeCalledPartyIsub disable;
includeCallingPartyIsub disable;
}
numberPortabilityAttributes {
npdiOptions includeNpdi;
14 of 20
Sonus Networks Interoperability Test Lab
disableRn
disable;
}
privacy {
transparency
disable;
privacyInformation pPreferredId;
flags {
includePrivacy
enable;
privacyRequiredByProxy disable;
msLyncPrivacySupport
disable;
}
}
redirect {
mode
acceptRedirection;
contactHandling mergeReceivedContacts;
flags {
skipCrankbackProfileAndAlwaysCrankback disable;
forceRequeryForRedirection
disable;
}
}
sipHeadersAndParameters {
callForwarding {
dataMapping
diversion;
diversionHeaderTransparency disable;
}
includeChargeInformation
includeNone;
destinationTrunkGroupOptions includeNone;
originatingTrunkGroupOptions includeNone;
flags {
includeCic
disable;
includeCpcInformation
disable;
includeNpi
disable;
includeOlip
disable;
includePKAdn
disable;
includePstnParameters
disable;
includeQvalue
disable;
skipCSeqCheckInEarlyDialog
disable;
transparencyForDestinationTrunkGroupParameter enable;
}
}
transport {
type1 none;
type2 none;
type3 none;
type4 none;
}
}
ingressIpAttributes {
flags {
sip181Supported
sip182Supported
mapCalledPartyCategoryInPSigInfoHeader
noSdpIn180Supported
registrationExpiresinExpiresHeader
Sonus Networks Interoperability Test Lab
disable;
disable;
disable;
disable;
disable;
15 of 20
registrationSupport3xx
send183OnInitiatingDisconnectTreatment
sendSdpIn200OkIf18xReliable
sendSdpInSubsequent18x
disable;
disable;
disable;
disable;
}
carrierInformation {
generateTerminatingCa disable;
generateTerminatingCic disable;
}
}
[ok][2012-03-07 04:09:08]
4.5. Configuring the Packet Service Profile
Use the Default Packet Service Profile with the following modifications.
Modifying the Packet Service Profile
1. Configure the DTMF relay in the Codec Entry.
set profiles media codecEntry G711-DEFAULT dtmf relay rfc2833
commit
2. Configure the DTMF Preferred Payload type in the Packet Service Profile.
set profiles media packetServiceProfile DEFAULT
preferredRtpPayloadTypeForDtmfRelay 101
commit
3. Verify the configuration using the show command.
[edit]
admin@NBS51K1% show profiles media packetServiceProfile DEFAULT
dataCalls {
preferredRtpDataPayloadType 56;
initialPlayoutBufferDelay
50;
packetSize
20;
}
silenceFactor
40;
typeOfService
0;
voiceInitialPlayoutBufferDelay
10;
rtcpOptions {
rtcp disable;
}
peerAbsenceAction
none;
silenceInsertionDescriptor {
g711SidRtpPayloadType 19;
heartbeat
enable;
}
aal1PayloadSize
47;
codec {
codecEntry1 G711-DEFAULT;
codecEntry2 G729A-DEFAULT;
codecEntry3 "";
16 of 20
Sonus Networks Interoperability Test Lab
codecEntry4 "";
}
packetToPacketControl {
transcode conditional;
conditionsInAdditionToNoCommonCodec {
differentDtmfRelay
disable;
differentPacketSize
disable;
differentSilenceSuppression disable;
honorOfferPreference
disable;
}
codecsAllowedForTranscoding {
thisLeg "";
otherLeg "";
}
}
flags {
disallowDataCalls
disable;
digitDetectSendEnabled
disable;
useDirectMedia
disable;
validatePeerSupportForDtmfEvents disable;
}
t38 {
dataRateManagementType
type2TransferOfTcf;
ecm {
ecmPreferred disable;
}
lowSpeedNumberOfRedundantPackets 1;
maxBitRate
14.4Kbits_s;
numberOfRedundantPackets
1;
}
secureRtpRtcp {
cryptoSuiteProfile "";
flags {
allowFallback disable;
enableSrtp
disable;
}
}
preferredRtpPayloadTypeForDtmfRelay 101;
videoCalls {
maxVideoBandwith
0;
videoBandwidthReductionFactor 0;
audioOnlyIfVideoIsPrevented
enable;
}
mediaPacketCos
0;
honorRemotePrecedence
disable;
sendRoutePSPPrecedence
disable;
[ok][2012-03-07 04:13:54]
Sonus Networks Interoperability Test Lab
17 of 20
4.6. Configuring the Call Routing
Configure the Call Routing using the following procedure.
Configuring the Call Routing
1. Configure the Routing Label.
set global callRouting routingLabel CME_RL routingLabelRoute 1
trunkGroup CME_STG ipPeer CME inService inService
commit
2. Configure the Standard Route.
set global callRouting route none Sonus_NULL Sonus_NULL standard 56 1
all all ALL none Sonus_NULL routingLabel CME_RL
commit
3. Verify configuration using the show command.
[edit]
admin@NBS51K1% show global callRouting route
route none Sonus_NULL Sonus_NULL standard 56 1 all all ALL none
Sonus_NULL {
routingLabel CME_RL;
} [ok][2012-04-02 04:16:44]
[edit]
admin@NBS51K1% show global callRouting routingLabel CME_RL
overflowNumber
"";
overflowNOA
none;
overflowNPI
none;
routePrioritizationType sequence;
script
"";
action
routes;
routingLabelRoute 1 {
trunkGroup CME_STG;
ipPeer
CME;
proportion 0;
cost
1000000;
inService inService;
testing
normal;
}
[ok][2012-04-02 22:15:20]
18 of 20
Sonus Networks Interoperability Test Lab
5 Phase III - Interoperability Testing
This section provides the tests that can be performed to verify configuration of Cisco Call Manager
Express and Sonus SBC 5100.
5.1. Test Results
The following table lists a summary of the test case results.
ID
Test Case
616349
Basic SIP call with hold, mute and DTMF.
617227
Basic SIP call with G711alaw
617229
BLF-Speed-Dial via SBC 5100
617230
Gpickup feature
616350
Conference Call
616352
Conference Call with , Mute, Unmute and Hold, Resume, DTMF
617373
Verify Call Conference Hosting at CME with Teles IAD
616353
Call Forward Feature
616355
Call Forward Feature via SBC 5100 with Mute and UnMute, Hold
and Resume, DTMF
617221
Call Forward Busy Feature via SBC 5100
617222
Call Forward Unconditional Feature via SBC 5100
617223
Call Forward No Answer Feature via SBC 5100
P/F
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Pass
Sonus Networks Interoperability Test Lab
Pass
Pass
Pass
19 of 20
6 Conclusion
The Application Notes describe the configuration steps required for SBC 5100 to successfully
interoperate with Cisco Call Manager Express 8.6. All feature and serviceability test cases were
completed and passed.
20 of 20
Sonus Networks Interoperability Test Lab