Configuring Sonus SBC 5100
with
MITEL 3300 Integrated
Communications Platform
Release 4.2 SP2
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 - Configuring Mitel 3300 PBX ................................................... 6
3.1.
Third-party Product Features ......................................................................................................... 6
3.2.
Requirements ................................................................................................................................. 6
3.3.
Verifying License ........................................................................................................................... 6
3.4.
Adding a SIP User .......................................................................................................................... 9
3.5.
Configuring the SIP Trunk ............................................................................................................ 11
3.6.
Configuring the SIP Peer Profile .................................................................................................. 13
3.7.
Configuring the SIP Trunk Attributes ........................................................................................... 16
3.8.
Configuring the Class of Service .................................................................................................. 17
3.9.
Configuring the Automatic Route Selection ................................................................................. 26
3.10. Configuring the ARS Digit Modification ........................................................................................ 27
3.11. Configuring the ARS Digit Dialing ................................................................................................ 29
4 Phase II – Configuring the Sonus SBC 5100 ....................................... 31
4.1.
Basic Configuration ...................................................................................................................... 31
4.2.
Configuring the IP Peer ................................................................................................................ 32
4.3.
Configuring the SIP Trunk Group ................................................................................................. 33
4.4.
Configuring the IP Signaling Profile ............................................................................................. 34
4.5.
Configuring the Packet Service Profile ........................................................................................ 38
4.6.
Configuring the Call Routing ........................................................................................................ 40
5 Phase III - Interoperability Testing ....................................................... 41
5.1.
Test Results ................................................................................................................................. 41
6 Conclusion .......................................................................................... 42
2 of 42
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 Mitel 3300 Integrated Communications Platform using SIP trunks.
SBC 5100 is a robust solution that integrates security, call control, Quality of Service, advanced media
services and switching all within a compact platform. SBC 5100 functionality was compliance tested using
a SIP trunk to Mitel 3300 Integrated Communications Platform.
The objective of the document is to describe the procedure to be followed during Interoperability Testing
(IOT) of SBC 5100 with Mitel 3300 Integrated Communications Platform. It includes identifying the testing
environment, tools, topology, points, risks, and scope.
For additional information on Mitel, visit http://www.mitel.com
For additional information on Sonus SBC, visit http://www.sonusnet.com
Sonus Networks Interoperability Test Lab
3 of 42
2 Introduction
IOT focuses on verifying inbound and outbound call flows between Sonus SBC 5100 and Mitel 3300,
using SIP and RTP.
2.1. Audience
This technical document is intended for telecommunication engineers with the purpose of configuring
both the Sonus SBC and the third-party product. There will be steps that require navigating the thirdparty 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
Software
Sonus Networks
• SBC 5100
• BMC
• BIOS
• ConnexIP OS
• SonusDB
• EMA
• SBX
Third-party Equipments
• Mitel 3300 PBX
• SIP Phones
• POTS Phones
3.0.0R000
V2.0.0
V2.0.0
1.8.0-A7
sonusdb-V03.00.00-A011
ema- V03.00.00-A011
sbx- V03.00.00-A011
4.2 SP2 (10.2.2.10)
Other software
2.3. Test Scenario
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 42
•
Incoming calls to the Enterprise site through the SBC 5100
•
Outgoing calls from the Enterprise site through SBC 5100
•
Calls using various analog, digital and SIP endpoints supported by the Mitel 3300 PBX
solution
•
Calls using various codecs
Sonus Networks Interoperability Test Lab
•
Inbound and outbound fax calls
•
DTMF tone transmission using RFC 2833 with successful voice mail navigation
•
Telephony features such as hold, resume, transfer, conference, and call forwarding.
Serviceability testing focused on verifying the ability of SBC 5100 to recover from adverse conditions,
such as disconnecting/reconnecting the Ethernet cable and stopping/starting Sonus Networks SBC
5100 and Mitel 3300 PBX.
2.4. Reference Configuration
A simulated enterprise site consisting of Mitel 3300 PBX, Session Manager, System Manager, and
SBC 5100 version 3.0 was used during compliance testing. SIP trunks were used to connect SBC
5100 with Communication Manager via Session Manager. 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 SBC 5100.
Figure 1 Sonus SBC 5100 with Mitel 3300
2.5. Support
Technical support on 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 42
3 Phase I - Configuring Mitel 3300 PBX
This section provides the procedures for configuring Mitel 3300 PBX.
3.1. Third-party Product Features
The Mitel 3300 PBX has the following features:
•
•
•
•
•
•
•
•
•
Integrated Voice Mail
Automatic Call Distribution (ACD)
Data Networking
Networking
Teleworking
Conferencing and Collaboration
Message Waiting Light Indicators
Auto Attendant
Embedded Music-on-Hold
3.2. Requirements
The configurations on Mitel 3300 are carried out using the Microsoft Internet Explorer browser
version 6.0 and above.
3.3. Verifying License
Log in to the system to verify that the Mitel 3300 PBX has permissions for features illustrated in
these Application Notes. Verify that there is sufficient remaining capacity for SIP trunks. The license
file installed on the system controls the maximum permitted SIP Trunks and Calls through the PBX.
If the capacity is insufficient, contact an authorized Mitel 3300 PBX sales representative to make the
appropriate changes.
Verifying Mitel 3300 Licences
1. Login to the Administration Portal using Internet Explorer web browser and accessing the
Management IP Address of Mitel 3300 PBX.
6 of 42
Sonus Networks Interoperability Test Lab
2. Select the System Administration Tool
3. Select the License and Option Selection in the Navigation bar on the left hand screen.
4. The License and Option Selection screen displays all available licences.
Sonus Networks Interoperability Test Lab
7 of 42
8 of 42
Sonus Networks Interoperability Test Lab
3.4. Adding a SIP User
1.
Login to the Administration Portal of the Mitel 3300 PBX and access the User and Device
Configuration form.
2. Click Add.
Sonus Networks Interoperability Test Lab
9 of 42
3. Select the Service Type, for example, User and Device User.
4. Enter the user's Personal Information and Service Profile.
5. Click Save.
10 of 42
Sonus Networks Interoperability Test Lab
3.5. Configuring the SIP Trunk
Configure the SIP Trunk towards SBC 5100 on the Mitel 3300 PBX using the following steps.
Adding a SIP Trunk
1. Click the Voice Network > Network Element.
2. Click Add/Change.
The Network Elements screen appers.
.
Sonus Networks Interoperability Test Lab
11 of 42
3. Enter the name of the target ICP, for example, SIPTG_to_NBS5100.
4. Select Type as Other.
5. Enter the IP Address.
6. Click the SIP Peer check box.
7. Set SIP Peer Transport as UDP
8. Set SIP Peer Port as “5060”.
9. Click Save.
12 of 42
Sonus Networks Interoperability Test Lab
3.6. Configuring the SIP Peer Profile
Configure the SIP Peer Profile using the following procedure.
Adding the SIP Peer Profile
1. Click Trunks >SIP >SIP Peer Profile.
2. The SIP Peer Profile screen appears. Enter NBS51KSP in the SIP Peer Profile Label to
configure the target.
3. Select the target Network Element, for example, NBS51KSP.
4. Click IP Address.
5. Configure SIP Peer Profile.
6. Click Save.
Sonus Networks Interoperability Test Lab
13 of 42
14 of 42
Sonus Networks Interoperability Test Lab
.
Sonus Networks Interoperability Test Lab
15 of 42
3.7. Configuring the SIP Trunk Attributes
Configure the SIP Trunk Attributes using the following procedure.
Configuring the SIP Trunk Attribute
1. Select Trunks > SIP > SIP Peer Profile. The Trunk Attributes screen appears.
2. Perform the following setting in the Trunk Attributes screen.
3. Set the Class of Service value equal to Trunk Service value, for example, “4”.
4. Set the Dial In Trunks Incoming Digit Modification- Absorb to “0”.
5. Set the Trunk Label as target label, for example, NBS51K.
16 of 42
Sonus Networks Interoperability Test Lab
3.8. Configuring the Class of Service
Set the Class of Service configuration using the following steps.
Configuring the Class of Service Configuration
1. Select System Properties > System Feature Settings > Class of Service Options. The
Class of Service screen appears.
Sonus Networks Interoperability Test Lab
17 of 42
2. Perform the following setting in the Class of Service screen.
3. Enable all options as displayed in the following figure.
4. Click Save.
18 of 42
Sonus Networks Interoperability Test Lab
Sonus Networks Interoperability Test Lab
19 of 42
20 of 42
Sonus Networks Interoperability Test Lab
Sonus Networks Interoperability Test Lab
21 of 42
22 of 42
Sonus Networks Interoperability Test Lab
Sonus Networks Interoperability Test Lab
23 of 42
24 of 42
Sonus Networks Interoperability Test Lab
Sonus Networks Interoperability Test Lab
25 of 42
3.9. Configuring the Automatic Route Selection
Configure the Automatic Route Selection using the following procedure.
Configuring the Automatic Route Selection
1. Select Call Routing >Automatic Route Selection (ARS) > ARS Routes.
The ARS Routes screen appears.
2. Select the Route Number which is equal to the Trunk Number, for example,” 4”.
3. Set the Routing Medium as SIP Trunk.
4. In the SIP Peer Profile list, click NBS51KSP.
26 of 42
Sonus Networks Interoperability Test Lab
5. Enter the Digit Modification Number as “4”.
6. Click Save.
3.10. Configuring the ARS Digit Modification
Configure the ARS Digit Modification using the following procedure.
Configuring the ARS Digit Modification
1. Select Call Routing > Automatic Route Selection (ARS) > ARS Digit Modification Plans.
Sonus Networks Interoperability Test Lab
27 of 42
The ARS Digit Modification Plans screen appears.
2. Perform the following setting in the ARS Digit Modification Plans screen.
3. Set the Digit Modification Number as “4”.
4. Set the Number of Digits to Absorb as “3”.
5. Click Save.
28 of 42
Sonus Networks Interoperability Test Lab
3.11. Configuring the ARS Digit Dialing
Configure the ARS Digit Dialing using the following procedure.
Configuring the ARS Digit Dialing
1. Select Call Routing > Automatic Route Selection (ARS) > ARS Maximum Digits Dialed.
2. Add or change the ARS Digit Dialed configuration.
3. Enter the digits, for example, “145”, in the Digit Dialed box.
4. In the Number of Digits to Follow list, click Unknown.
5. Enter the Termination Number value same as the Route Number value, for example, “4”.
Sonus Networks Interoperability Test Lab
29 of 42
30 of 42
Sonus Networks Interoperability Test Lab
4 Phase II – Configuring the 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 pkt0_v4 mode
inService state enabled
commit
2. Configure the Zone and SIP Signaling port.
set addressContext a1 zone Z2 id 3 sipSigPort 1 ipInterfaceGroupName
LIF1 ipAddressV4 172.16.104.160
set addressContext a1 zone Z2 sipSigPort 1 transportProtocolsAllowed
sip-tcp portNumber 5060
set addressContext a1 zone Z2 sipSigPort 1 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;
Sonus Networks Interoperability Test Lab
31 of 42
portNumber
mode
state
transportProtocolsAllowed
5060;
inService;
enabled;
sip-udp;
}
[ok][2012-03-07 03:33:12]
[edit]
admin@NBS51K1%
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 Mitel 3300 PBX as IP Peer in the zone.
set addressContext a1 zone Z2 ipPeer MITEL_IPP ipAddress 10.54.20.111
ipPort 5060
commit
2. Verify Configuration using the show command.
[edit]
admin@NBS51K1% show addressContext a1 zone Z2 ipPeer MITEL_IPP
ipAddress 10.54.20.111;
ipPort
5060;
policy {
description
"";
sip {
fqdn
"";
fqdnPort 0;
}
packetServiceProfile "";
ipSignalingProfile
"";
}
[ok][2012-03-07 03:41:41]
32 of 42
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 IP Peer
1. Use the following command to configure the SIP Trunk Group for Mitel 3300 PBX.
set addressContext a1 zone Z2 sipTrunkGroup MITEL_TG media
mediaIpInterfaceGroupName LIF2
set addressContext a1 zone Z2 sipTrunkGroup MITEL_TG ingressIpPrefix
10.54.20.111 32
set addressContext a1 zone Z2 sipTrunkGroup MITEL_TG policy signaling
ipSignalingProfile DEFAULT_SIP
set addressContext a1 zone Z2 sipTrunkGroup MITEL_TG policy media
packetServiceProfile DEFAULT
set addressContext a1 zone Z2 sipTrunkGroup MITEL_TG mode inService
state enabled
commit
2. Verify configuration using the show command.
[edit]
admin@NBS51K1% show addressContext a1 zone Z2 sipTrunkGroup MITEL_TG
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
33 of 42
signalingProfile
"";
}
}
media {
mediaIpInterfaceGroupName LIF2;
}
ingressIpPrefix 10.54.20.111 32;
[ok][2012-03-07 03:35:51]
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
34 of 42
DEFAULT_SIP
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
mapUuiInPSigInfoHeader
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;
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
35 of 42
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;
36 of 42
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
registrationSupport3xx
Sonus Networks Interoperability Test Lab
disable;
disable;
disable;
disable;
disable;
disable;
37 of 42
send183OnInitiatingDisconnectTreatment disable;
sendSdpIn200OkIf18xReliable
disable;
sendSdpInSubsequent18x
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 "";
codecEntry4 "";
38 of 42
Sonus Networks Interoperability Test Lab
}
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
39 of 42
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 MITEL_RL routingLabelRoute 1
trunkGroup MITEL_TG ipPeer MITEL_IPP inService inService
commit
2. Configure the Standard Route.
set global callRouting route none Sonus_NULL Sonus_NULL standard 6020 1
all all ALL none Sonus_NULL routingLabel MITEL_RL
commit
3. Verify configuration using the show command.
[edit]
admin@NBS51K1% show global callRouting route
route trunkGroup NAT_TG NBS51K1 standard Sonus_NULL 1 all all ALL none
Sonus_NULL {
routingLabel MITEL_RL;
[ok][2012-03-07 04:16:44]
[edit]
admin@NBS51K1% show global callRouting routingLabel MITEL_RL
overflowNumber
"";
overflowNOA
none;
overflowNPI
none;
routePrioritizationType sequence;
script
"";
action
routes;
routingLabelRoute 1 {
trunkGroup MITEL_TG;
ipPeer
MITEL_IPP;
proportion 0;
cost
1000000;
inService inService;
testing
normal;
}
[ok][2012-03-07 04:19:12]
40 of 42
Sonus Networks Interoperability Test Lab
5 Phase III - Interoperability Testing
This section provides the details of verification tests performed to verify configuration of Mitel 3300
PBX and Sonus SBC 5100.
5.1. Test Results
Test case results are summarized in the following table.
Table 1 Test cases
ID
Test Case
P/F
617283
Basic SIP call Origination with UDP
PASS
617284
Basic SIP call Termination with UDP
PASS
617287
Call Forward Unconditional with Adtran EP.
PASS
617288
Call Forward Busy with Adtran EP
PASS
617289
Conference call Feature via SBC 5100
PASS
617290
Conference call Feature via SBC 5100
PASS
617291
Conference call Feature via SBC 5100
PASS
617292
Call Forward Feature via SBC 5100
PASS
617293
Call Forward Feature via SBC 5100
PASS
617294
Call Forward Feature via SBC 5100
PASS
617295
Call Transfer Feature ( Blind )
PASS
617296
Call Transfer Feature ( Blind )
PASS
617297
Call Transfer Feature ( Attended )
PASS
617301
Basic Call with Codec Negotiation (G729, G711a,u), Mute,
Unmute and Hold,Resume
PASS
617302
Codec Negotiation Conference.
PASS
617303
Codec Negotiation Attended Transfer.
PASS
617304
Leave Voice Mail
PASS
617305
Retrieve Voice Mail
PASS
617306
Leave and Retrieve Voice Mail on Other PBX
PASS
617307
Call Conference with ADTRAN EP
PASS
Sonus Networks Interoperability Test Lab
41 of 42
6 Conclusion
The Application Notes describe the configuration steps required for SBC 5100 to successfully
interoperate with Mitel 3300 PBX. All feature and serviceability test cases were completed and
passed.
42 of 42
Sonus Networks Interoperability Test Lab