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

Transcription

1 Configuring Sonus SBC 5100 with ADTRAN Total Access 924e Version A E Application Notes Last Updated: April 27, 2012 Sonus Networks Interoperability Test Lab

2 Contents 1 Document Overview Introduction Audience Requirements Test Scenario Reference Configuration Support Phase I - Configuring Adtran IAD Third-party Product Features Requirements Adding an Analog User Configuring the SIP Trunk Configuring Static Route Phase II Configuring Sonus SBC Basic Configuration Configuring the IP Peer Configuring the SIP Trunk Group Configuring the IP Signaling Profile Configuring the Packet Service Profile Configuring the Call Routing Phase III - Interoperability Testing Test Results Conclusion of 32 Sonus Networks Interoperability Test Lab

3 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 For additional information on Sonus SBC, visit Sonus Networks Interoperability Test Lab 3 of 32

4 2 Introduction IOT focuses on verifying inbound and outbound call flows between Sonus SBC 5100 and Adtran IAD, using SIP and RTP 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 Requirements The following equipments and software were used for the sample configuration provided: Equipment Sonus Networks Software SBC 5100 BMC BIOS ConnexIP OS SonusDB EMA SBX Third-party Equipments Adtran IAD POTS Phones 3.0.0R000 V2.0.0 V A12 sonusdb-v a022 ema- V A022 sbx- V A022 A 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 Outgoing calls from the Enterprise site through SBC 5100 Calls using various analog endpoints supported by the Adtran IAD solution Calls using various codecs 4 of 32 Sonus Networks Interoperability Test Lab

5 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 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 The following reference configuration shows connectivity between third-party product and SBC Figure 1 Sonus SBC 5100 with Adtran IAD Sonus Networks Interoperability Test Lab 5 of 32

6 2.5. Support Technical support on SBC 5100 can be obtained through the following: Phone: (978) or (888) (Toll-free) Web: 6 of 32 Sonus Networks Interoperability Test Lab

7 3 Phase I - Configuring Adtran IAD This section provides the procedures for configuring Adtran IAD 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. Sonus Networks Interoperability Test Lab 7 of 32

8 3.3. Adding an Analog User 1. Login to the Administration Portal of the Adtran IAD and access the User Accounts form. 2. Click Create new. 8 of 32 Sonus Networks Interoperability Test Lab

9 3. Select the Extension, for example, 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. Sonus Networks Interoperability Test Lab 9 of 32

10 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. 10 of 32 Sonus Networks Interoperability Test Lab

11 The Trunk Account Information screen appears. Sonus Networks Interoperability Test Lab 11 of 32

12 12 of 32 Sonus Networks Interoperability Test Lab

13 Sonus Networks Interoperability Test Lab 13 of 32

14 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. The Total Access 924e (2 nd Gen) screen appears. 14 of 32 Sonus Networks Interoperability Test Lab

15 9. Type in Group Name, for example NBS51K2 TG. 10. Click Add. The Edit Trunk Group screen appears. Sonus Networks Interoperability Test Lab 15 of 32

16 11. Click Add Members in Trunk Group Members. The Add Members to Trunk Group screen appears. 16 of 32 Sonus Networks Interoperability Test Lab

17 12. Click the Appropriate Trunk Account, for example NBS51K 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. Sonus Networks Interoperability Test Lab 17 of 32

18 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. 18 of 32 Sonus Networks Interoperability Test Lab

19 Sonus Networks Interoperability Test Lab 19 of 32

20 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 In the Destination Mask field, type in the Mask, for example In the Gateway Address field, type in the Gateway IP address, for example Click Add. 20 of 32 Sonus Networks Interoperability Test Lab

21 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 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 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 ipaddressv 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; ipaddressv ; portnumber 5060; mode inservice; Sonus Networks Interoperability Test Lab 21 of 32

22 state enabled; transportprotocolsallowed sip-udp; [ok][ :33:12] [edit] 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 ipport 5060 commit 2. Verify configuration using the show command. [edit] show addresscontext a1 zone Z2 ippeer ADTRAN_IPP ipaddress ; ipport 5060; policy { description ""; sip { fqdn ""; fqdnport 0; packetserviceprofile ""; ipsignalingprofile ""; [ok][ :41:41] 22 of 32 Sonus Networks Interoperability Test Lab

23 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 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] show addresscontext a1 zone Z2 siptrunkgroup ADTRAN_TG state enabled; mode inservice; policy { carrier 0000; country 1; sipdomain ""; localizationvariant northamerica; digitparameterhandling { numberingplan ingressdmpmrule ""; egressdmpmrule ""; NANP_ACCESS; callrouting { elementroutingpriority DEFAULT_IP; media { packetserviceprofile DEFAULT; services { classofservice DEFAULT_IP; signaling { ipsignalingprofile DEFAULT_SIP; signalingprofile ""; Sonus Networks Interoperability Test Lab 23 of 32

24 media { mediaipinterfacegroupname LIF2; ingressipprefix ; [ok][ :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 callholdinterworking clearmodefordatacalls createpchargingvector createpathheader createservicerouteheader customizedsessiontimerbehavior disablealsoheader disablehosttranslation disablemedialockdown disablerefertouriparameters discardreceivedreasonheader donotincludessattributeinreinvite endtoendbye includeipportsinfromandtoheaders includereasonheader includessattributeininitialinvite includetransporttypeincontactheader insertpeeraddressastoprouteheader mapcauselocation mapsuspendresumeeventinpsvcinfoheader mapuuiinpsiginfoheader 24 of 32 Sonus Networks Interoperability Test Lab

25 mimecauseprecedereasonheadercause minimizerelayingofmediachangesfromothercalllegall nocontentdisposition noportnumber5060 nouserinfoincontactheader onlyselectedcodecinsessionrefresh pchgmsginfo rejectrefer replacehostonviaheader requerypsxonregisterrefresh sdpolineonlycompares sendallallowedcodecsforlatemediainviteorreinvite senddirectmediainfoinsdpattribute sendptimeinsdp sessiontimerrefreshupdate setacceptheadertoapplicationsdponly setolinedash setsessionversionzero setslinedash skippsxqueryforrefer storepathheader storeservicerouteheader terminalportabilityinterworking sendrtcpportinsdp calltransferflags { handleipaddressesnotpresentinnetworkselectortablenst routeviatransferringiptg; forcererouteviapsxquery optiontaginrequireheader { suppressreplacetag optiontaginsupportedheader { suppressreplacetag relayflags { dialogeventpackage dtmfbody info message notify options regeventpackage refer sonusmediabody statuscode3xx statuscode4xx6xx thirdpartybodies transparencyflags { alertinformationheader authcodeheaders contactheader Sonus Networks Interoperability Test Lab 25 of 32

26 errorinfo fromheader historyinfo maxforwardsheader mwibody pchargingvectorheader pearlymedia pathheader qsigbody reasonheader referredbyheader requesturi routeheader servicerouteheader sipbody sipfragbody toheader tonebody unknownbody unknownheader viaheader egressipattributes { numberglobalizationprofile ""; flags { bgcftargetschemetransparency convertinactivetosendrecv disable2806compliance enable; disableoptionalregisterparameters map181or182messageto183 mapcontractornumberinpsiginfoheader suppressunregister ttcisupmapping usecalledpartyinrequesturi usecoloninsdpmediatypeparameter bci { validateisubaddress bciinterworkencountered bciisdnaddess domainname { usesipdomainnameinfromfield usesipdomainnameinrequesturi isub { allownsapisub allowuserspecifiedisub includecalledpartyisub includecallingpartyisub numberportabilityattributes { npdioptions includenpdi; disablern 26 of 32 Sonus Networks Interoperability Test Lab

27 privacy { transparency privacyinformation ppreferredid; flags { includeprivacy enable; privacyrequiredbyproxy mslyncprivacysupport redirect { mode acceptredirection; contacthandling mergereceivedcontacts; flags { skipcrankbackprofileandalwayscrankback forcerequeryforredirection sipheadersandparameters { callforwarding { datamapping diversion; diversionheadertransparency includechargeinformation includenone; destinationtrunkgroupoptions includenone; originatingtrunkgroupoptions includenone; flags { includecic transport { type1 none; type2 none; type3 none; type4 none; ingressipattributes { flags { sip181supported includecpcinformation includenpi includeolip includepkadn includepstnparameters includeqvalue skipcseqcheckinearlydialog transparencyfordestinationtrunkgroupparameter enable; sip182supported mapcalledpartycategoryinpsiginfoheader nosdpin180supported registrationexpiresinexpiresheader registrationsupport3xx send183oninitiatingdisconnecttreatment Sonus Networks Interoperability Test Lab 27 of 32

28 sendsdpin200okif18xreliable sendsdpinsubsequent18x carrierinformation { generateterminatingca generateterminatingcic [ok][ :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 peerabsenceaction none; silenceinsertiondescriptor { g711sidrtppayloadtype 19; heartbeat enable; aal1payloadsize 47; codec { codecentry1 G711-DEFAULT; codecentry2 G729A-DEFAULT; codecentry3 ""; codecentry4 ""; 28 of 32 Sonus Networks Interoperability Test Lab

29 packettopacketcontrol { transcode conditional; conditionsinadditiontonocommoncodec { differentdtmfrelay flags { t38 { differentpacketsize differentsilencesuppression honorofferpreference codecsallowedfortranscoding { thisleg ""; otherleg ""; disallowdatacalls digitdetectsendenabled usedirectmedia validatepeersupportfordtmfevents dataratemanagementtype ecm { ecmpreferred lowspeednumberofredundantpackets 1; type2transferoftcf; maxbitrate 14.4Kbits_s; numberofredundantpackets 1; securertprtcp { cryptosuiteprofile ""; flags { allowfallback enablesrtp preferredrtppayloadtypefordtmfrelay 101; videocalls { maxvideobandwith 0; videobandwidthreductionfactor 0; audioonlyifvideoisprevented enable; mediapacketcos 0; honorremoteprecedence sendroutepspprecedence [ok][ :13:54] Sonus Networks Interoperability Test Lab 29 of 32

30 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 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][ :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 proportion 0; cost ; ADTRAN_IPP; inservice inservice; testing normal; [ok][ :19:12] 30 of 32 Sonus Networks Interoperability Test Lab

31 5 Phase III - Interoperability Testing This section provides the details of verification tests performed to verify configuration of ADTRAN IAD and Sonus SBC Test Results Test case results are summarized in the following table. Table 1 Test cases ID Test Case P/F Basic SIP call with UDP PASS Basic SIP call with Minet Phone PASS Basic SIP call with Mitel Analog Phone PASS Conference call Feature via SBC 5100 PASS Conference call Feature via SBC 5100 PASS Conference call Feature via SBC 5100 PASS Call Forward Feature via SBC 5100 PASS Call Forward Feature via SBC 5100 PASS Call Forward Feature via SBC 5100 PASS Call Transfer Feature ( Blind ) via SBC 5100 PASS Call Transfer Feature ( Attended ) via SBC 5100 PASS Call Transfer Feature ( Blind ) with refer Relay Flag Enabled PASS Call Transfer Feature ( Attended ) with refer Relay Flag Enabled Basic Call with Codec Negotiation (G729, G711a,u), Mute, Unmute and Hold,Resume Call Transfer Feature with Codec Negotiation (G729, G711a,u). PASS PASS PASS Sonus Networks Interoperability Test Lab 31 of 32

32 6 Conclusion The Application Notes describe the configuration steps required for SBC 5100 to successfully interoperate with ADTRAN IAD. All feature and serviceability test cases were completed and passed. 32 of 32 Sonus Networks Interoperability Test Lab