Configuring Sonus SBC 5100 with ADTRAN Total Access 924e Version A E

Sonus Networks Interoperability Test Lab

ADTRAN Total Access 924e

Version A2.06.00.E

with

Configuring Sonus SBC 5100

Application Notes

Last Updated: April 27, 2012

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 ... 6

3

Phase I - Configuring Adtran IAD ... 7

3.1. Third-party Product Features ... 7

3.2. Requirements ... 7

3.3. Adding an Analog User ... 8

3.4. Configuring the SIP Trunk ... 10

3.5. Configuring Static Route ... 20

4

Phase II – Configuring Sonus SBC 5100 ... 21

4.1. Basic Configuration ... 21

4.2. Configuring the IP Peer ... 22

4.3. Configuring the SIP Trunk Group ... 23

4.4. Configuring the IP Signaling Profile ... 24

4.5. Configuring the Packet Service Profile ... 28

4.6. Configuring the Call Routing ... 30

5

Phase III - Interoperability Testing ... 31

5.1. Test Results ... 31

Sonus Networks Interoperability Test Lab

3 of 32

1 Document Overview

These Application Notes describe the configuration steps required for Sonus Session Border Controller 5100 (SBC 5100), to interoperate with Adtran IAD 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 utilizing a SIP trunk to Adtran IAD. The objective of the document is to describe the procedure to be followed during Interoperability Testing (IOT) of SBC 5100 with Adtran IAD.

It includes identifying the testing environment, tools, topology, points, risks, and scope.

For additional information on Adtran, visit http://www.adtran.com/

2 Introduction

IOT focuses on verifying inbound and outbound call flows between Sonus SBC 5100 and Adtran IAD, 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 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.

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 3.0.0R000 V2.0.0 V2.0.0 1.8.0-A12 sonusdb-V03.00.00-A022 ema- V03.00.00-A022 sbx- V03.00.00-A022 Third-party Equipments • Adtran IAD

• POTS Phones A2.06.00.E

Other software

2.3. Test Scenario

SBC 5100 was used as a Session Border Controller (SBC) at an enterprise site consisting of Adtran IAD. 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: • Incoming calls to the Enterprise site through the SBC 5100

Sonus Networks Interoperability Test Lab

5 of 32 • 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 of the Ethernet cable and stopping/starting of Sonus SBC 5100 and Adtran IAD.

2.4. Reference Configuration

A simulated enterprise site consisting of Adtran IAD, Session Manager, System Manager, and SBC 5100 version 3.0 were 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.

This 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.

2.5. Support

Technical support on SBC 5100 can be obtained through the following: • Phone: (978) 614-8589 or (888) 391-3434 (Toll-free)

Sonus Networks Interoperability Test Lab

7 of 32

3 Phase I - Configuring Adtran IAD

This section provides the procedures for configuring Adtran IAD.

3.1. Third-party Product Features

The Adtran IAD has the following features: • Automatic Call Distribution (ACD) • Networking

• Teleworking

• Conferencing and Collaboration • Embedded Music-on-Hold

3.2. Requirements

The configurations on Adtran IAD are carried out using the Microsoft Internet Explorer browser version 6.0 and above.

3.3. Adding an Analog User

1. Login to the Administration Portal of the Adtran IAD and access the User Accounts form.

Sonus Networks Interoperability Test Lab

9 of 32 3. Select the Extension, for example, 3182.

4. Enter the user's First name and Last name.

5. Select Phone Type as Analog Station and corresponding Phone Port. 6. Click Apply and Add Another User.

3.4. Configuring the SIP Trunk

Configure the SIP Trunk towards NBS 5100 on the Adtran IAD using the following steps.

Adding a SIP Trunk

1. Click Trunk Accounts.

2. Type in the Trunk Name and select SIP in the Type options. 3. Click Add.

Sonus Networks Interoperability Test Lab

11 of 32 The Trunk Account Information screen appears.

4. Type in the Trunk Name, for example NBS51K2.

5. In the SIP Settings tab, type in the suitable SIP Server Address and SIP Server Port. 6. Select valid Codec Group.

7. Click Apply.

8. Click Trunk Groups.

Sonus Networks Interoperability Test Lab

15 of 32 9. Type in Group Name , for example NBS51K2 TG.

10. Click Add.

The Edit Trunk Group screen appears.

11. Click Add Members in Trunk Group Members. The Add Members to Trunk Group screen appears.

Sonus Networks Interoperability Test Lab

17 of 32 12. Click the Appropriate Trunk Account, for example NBS51K2.

13. Click Add Selected Trunks.

14. Select all the boxes under Outbound Call Templates .

15. Under Detailed View – Permit/Restriction Call Templates , click Configure Advanced

Templates.

The Add/Delte Permit Templates screen appears.

16. Under Add/Delete Permit Templates, in the Template field type in the number patterns from/to which the calls must be allowed. For example, 55XX.

17. Click Add. 18. Click Apply.

3.5. Configuring Static Route

Add a Static Route using the following steps. 1. Select Data > Route Table .

2. In the Destination Address field, type in the Destination IP Address , for example 172.16.104.0.

3. In the Destination Mask field, type in the Mask, for example 255.255.255.0.

4. In the Gateway Address field, type in the Gateway IP address, for example 10.54.18.1. 5. Click Add.

Sonus Networks Interoperability Test Lab

21 of 32

4 Phase II – Configuring 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 Z1 id 2 sipSigPort 1 ipInterfaceGroupName LIF1 ipAddressV4 172.16.103.160

set addressContext a1 zone Z1 sipSigPort 1 transportProtocolsAllowed sip-tcp portNumber 5060

set addressContext a1 zone Z1 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; portNumber 5060;

state enabled; transportProtocolsAllowed 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 Adtran IAD as IP Peer in the zone.

set addressContext a1 zone Z2 ipPeer ADTRAN_IPP ipAddress 10.54.18.12 ipPort 5060

commit

2. Verify configuration using the show command. [edit]

admin@NBS51K1% show addressContext a1 zone Z2 ipPeer ADTRAN_IPP ipAddress 10.54.18.12; ipPort 5060; policy { description ""; sip { fqdn ""; fqdnPort 0; } packetServiceProfile ""; ipSignalingProfile ""; } [ok][2012-03-07 03:41:41]

Sonus Networks Interoperability Test Lab

23 of 32

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 Adtran IAD. set addressContext a1 zone Z2 sipTrunkGroup ADTRAN_TG media mediaIpInterfaceGroupName LIF2

set addressContext a1 zone Z2 sipTrunkGroup ADTRAN_TG ingressIpPrefix 10.54.18.12 32

set addressContext a1 zone Z2 sipTrunkGroup ADTRAN_TG policy signaling ipSignalingProfile DEFAULT_SIP

set addressContext a1 zone Z2 sipTrunkGroup ADTRAN_TG policy media packetServiceProfile DEFAULT

set addressContext a1 zone Z2 sipTrunkGroup ADTRAN_TG mode inService state enabled

commit

2. Verify configuration using the show command. [edit]

admin@NBS51K1% show addressContext a1 zone Z2 sipTrunkGroup ADTRAN_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; signalingProfile "";

} } media { mediaIpInterfaceGroupName LIF2; } ingressIpPrefix 10.54.18.12 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 DEFAULT_SIP ipProtocolType sipOnly; commonIpAttributes { flags { addPathServiceRoute disable; callHoldInterworking disable; clearmodeForDataCalls disable; createPChargingVector disable; createPathHeader disable; createServiceRouteHeader disable; customizedSessionTimerBehavior disable; disableAlsoHeader disable; disableHostTranslation disable; disableMediaLockDown disable; disableReferToUriParameters disable; discardReceivedReasonHeader disable; doNotIncludeSsAttributeInReInvite disable; endToEndBye disable; includeIpPortsInFromAndToHeaders disable; includeReasonHeader disable; includeSsAttributeInInitialInvite disable; includeTransportTypeInContactHeader disable; insertPeerAddressAsTopRouteHeader disable; mapCauseLocation disable;

Sonus Networks Interoperability Test Lab

25 of 32 mimeCausePrecedeReasonHeaderCause disable; minimizeRelayingOfMediaChangesFromOtherCallLegAll disable; noContentDisposition disable; noPortNumber5060 disable; noUserinfoInContactHeader disable; onlySelectedCodecInSessionRefresh disable; pChgMsgInfo disable; rejectRefer disable; replaceHostOnViaHeader disable; reQueryPsxOnRegisterRefresh disable; sdpOlineOnlyCompares disable; sendAllAllowedCodecsForLateMediaInviteOrReInvite disable; sendDirectMediaInfoInSdpAttribute disable; sendPtimeInSdp disable; sessionTimerRefreshUpdate disable; setAcceptHeaderToApplicationSdpOnly disable; setOlineDash disable; setSessionVersionZero disable; setSlineDash disable; skipPsxQueryForRefer disable; storePathHeader disable; storeServiceRouteHeader disable; terminalPortabilityInterworking disable; sendRtcpPortInSdp 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; contactHeader disable;

errorInfo disable; fromHeader disable; historyInfo disable; maxForwardsHeader disable; mwiBody disable; pChargingVectorHeader disable; pEarlyMedia disable; pathHeader disable; qsigBody disable; reasonHeader disable; referredByHeader disable; requestURI disable; routeHeader disable; serviceRouteHeader disable; sipBody disable; sipfragBody disable; toHeader disable; toneBody disable; unknownBody disable; unknownHeader disable; viaHeader 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; }

Sonus Networks Interoperability Test Lab

27 of 32 } 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 disable; sip182Supported disable; mapCalledPartyCategoryInPSigInfoHeader disable; noSdpIn180Supported disable; registrationExpiresinExpiresHeader disable; registrationSupport3xx disable; 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 "";

Sonus Networks Interoperability Test Lab

29 of 32 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]

4.6. Configuring the Call Routing

Configure the Call Routing using the following procedure. 1. Configure the Routing Label.

set global callRouting routingLabel ADTRAN_RL routingLabelRoute 1 trunkGroup ADTRAN_TG ipPeer ADTRAN_IPP inService inService

commit

2. Configure the Standard Route.

set global callRouting route none Sonus_NULL Sonus_NULL standard 318 1 all all ALL none Sonus_NULL routingLabel ADTRAN_RL

commit

3. Verify configuration using the show command. [edit]

admin@NBS51K1% show global callRouting route

route trunkGroup ADTRAN_TG NBS51K1 standard Sonus_NULL 1 all all ALL none Sonus_NULL {

routingLabel ADTRAN_RL; [ok][2012-03-07 04:16:44] [edit]

admin@NBS51K1% show global callRouting routingLabel ADTRAN_RL overflowNumber ""; overflowNOA none; overflowNPI none; routePrioritizationType sequence; script ""; action routes; routingLabelRoute 1 { trunkGroup ADTRAN_TG; ipPeer ADTRAN_IPP; proportion 0; cost 1000000; inService inService; testing normal; } [ok][2012-03-07 04:19:12]

Sonus Networks Interoperability Test Lab

31 of 32

5 Phase III - Interoperability Testing

This section provides the details of verification tests performed to verify configuration of ADTRAN IAD 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

617308 Basic SIP call with UDP PASS

617309 Basic SIP call with Minet Phone PASS

617310 Basic SIP call with Mitel Analog Phone PASS

617311 Conference call Feature via SBC 5100 PASS

617312 Conference call Feature via SBC 5100 PASS

617313 Conference call Feature via SBC 5100 PASS

617314 Call Forward Feature via SBC 5100 PASS

617315 Call Forward Feature via SBC 5100 PASS

617316 Call Forward Feature via SBC 5100 PASS

617317 Call Transfer Feature ( Blind ) via SBC 5100 PASS

617318 Call Transfer Feature ( Attended ) via SBC 5100 PASS

617321 Call Transfer Feature ( Blind ) with refer Relay Flag Enabled PASS

617322

Call Transfer Feature ( Attended ) with refer Relay Flag

Enabled PASS

617319

Basic Call with Codec Negotiation (G729, G711a,u), Mute,

Unmute and Hold,Resume PASS

617320

Call Transfer Feature with Codec Negotiation (G729,

6 Conclusion

The Application Notes describe the configuration steps required for SBC 5100 to successfully