Configuring Sonus SBC 5100 with AVAYA IP OFFICE R7

Transcription

1 Configuring Sonus SBC 5100 with AVAYA IP OFFICE R7 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 the Avaya IP Office Third-party Product Features Requirements Verifying License Adding a SIP User Configuring the SIP Trunk Configuring a Short Code for the SIP Trunk Saving the Configuration 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 27 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 Avaya IP Office 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 Avaya IP Office. The objective of the document is to describe the procedure to be followed during Interoperability Testing (IOT) of SBC 5100 with Avaya IP Office. It includes identifying the testing environment, tools, topology, points, risks, and scope. For additional information on Avaya, visit For additional information on Sonus SBC, visit Sonus Networks Interoperability Test Lab 3 of 27

4 2 Introduction IOT focuses on verifying inbound and outbound call flows between Sonus SBC 5100 and Avaya IP Office, using SIP and RTP Audience This technical document is intended for telecommunication engineers for configuring 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 Avaya IP Office SIP Phones POTS Phones 3.0.0R000 V2.0.0 V A7 sonusdb-v a011 ema- V A011 sbx- V A011 Version 9.0 ( 12 ) Other software 2.3. Test Scenario SBC 5100 was used as a Session Border Controller (SBC) at an enterprise site consisting of Avaya IP Office. SIP trunks were used to connect SBC 5200 to the enterprise site and to a simulated PSTN/Service Provider. TLS and SRTP were used at the enterprise. 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, digital and SIP endpoints supported by the Avaya IP Office solution 4 of 27 Sonus Networks Interoperability Test Lab

5 Calls using various codecs 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 Avaya IP Office Reference Configuration A simulated enterprise site consisting of Avaya IP Office, 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. The 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 Avaya IP Office 2.5. Support Technical support on SBC 5100 can be obtained through the following: Phone: (978) or (888) (Toll-free) Web: Sonus Networks Interoperability Test Lab 5 of 27

6 3 Phase I - Configuring the Avaya IP Office This section provides the procedures for configuring Avaya IP Office Third-party Product Features The Avaya IP Office 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 Avaya IP Office are carried out using the Microsoft Internet Explorer browser version 6.0 and above Verifying License Log in to the system to verify that the Avaya IP Office has permissions for features illustrated in these Application Notes. Verify that there is sufficient remaining capacity for SIP trunks. The license file installed in the system, controls the maximum permitted SIP Trunks and calls through the PBX. In case of insufficient capacity, contact an authorized Avaya IP Office sales representative for appropriate changes. Verifying Avaya IP Office Licences 1. Login to the Administration Portal of Avaya IP Office PBX using valid credentials. 2. Select the Sonus IP Office in the left navigation bar. 3. Scroll down the License list to view all available licences. 6 of 27 Sonus Networks Interoperability Test Lab

7 4. Click the desired field for the available licenses information. Sonus Networks Interoperability Test Lab 7 of 27

8 3.4. Adding a SIP User 1. Login to the Administration Portal of the Avaya IP Office and access the Extension form. 2. Click the Create a new record. 3. Click the SIP Extension option. The SIP Extension: 8010* screens opens. 4. Enter the required details. 8 of 27 Sonus Networks Interoperability Test Lab

9 5. Access the User form, and Click Create a New Record. 6. The User option is displayed. Click this option to open a new page. 7. Type in user s Name and Extension. Sonus Networks Interoperability Test Lab 9 of 27

10 8. Click OK to add the new user. 10 of 27 Sonus Networks Interoperability Test Lab

11 3.5. Configuring the SIP Trunk Configure the SIP Trunk towards SBC 5100 in the IP Office using the following steps. Adding a SIP Trunk 1. Access the Line Form and Click Create a New Record. 2. Click SIP Line. 3. In the New Record Page, enter the required Line Number in the Line Number Field. 4. Select the Transport tab and type in the ITSP Proxy Address, for example as shown in the following figure. Sonus Networks Interoperability Test Lab 11 of 27

12 5. Click OK to add the newly created SIP Line Configuring a Short Code for the SIP Trunk Configure the Short Code (Incoming Number Format routed to a SIP Line) using the following procedure. Adding the Short Code 1. Access the Short Code form as shown in the following figure. 12 of 27 Sonus Networks Interoperability Test Lab

13 2. Click the Create a New Record option to see a new page. 3. In the Code field, type in an appropriate value. For example, 3xxx if the incoming number has four digits and if it starts with In the Telephone Number field, type in the appropriate value, for example 3N if 3xxx is the Short Code. 5. In Line Group Id field, select the SIP Line Id which this number conforms to. 6. Click OK to add the new short code. Sonus Networks Interoperability Test Lab 13 of 27

14 3.7. Saving the Configuration Use the following steps to save all completed configurations to the IP Office. 1. Click SAVE, the Send Configuration window opens. 2. Click OK. 3. Type in valid credentials in the field and click OK to save the configuration. 14 of 27 Sonus Networks Interoperability Test Lab

15 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 { Sonus Networks Interoperability Test Lab 15 of 27

16 ipinterfacegroupname LIF2; ipaddressv ; portnumber 5060; mode inservice; 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 IPOFFICE 500 PBX as IP Peer in the zone. set addresscontext a1 zone Z2 ippeer IPOFFICE_IPP ipaddress ipport 5060 commit 2. Verify Configuration using the show command. [edit] show addresscontext a1 zone Z2 ippeer IPOFFICE_IPP ipaddress ; ipport 5060; policy { description ""; sip { fqdn ""; fqdnport 0; packetserviceprofile ""; ipsignalingprofile ""; [ok][ :41:41] 16 of 27 Sonus Networks Interoperability Test Lab

17 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 IP OFFICE 500 PBX. set addresscontext a1 zone Z2 siptrunkgroup IPOFFICE_TG media mediaipinterfacegroupname LIF2 set addresscontext a1 zone Z2 siptrunkgroup IPOFFICE_TG ingressipprefix set addresscontext a1 zone Z2 siptrunkgroup IPOFFICE_TG policy signaling ipsignalingprofile DEFAULT_SIP set addresscontext a1 zone Z2 siptrunkgroup IPOFFICE_TG policy media packetserviceprofile DEFAULT set addresscontext a1 zone Z2 siptrunkgroup IPOFFICE_TG mode inservice state enabled commit 2. Verify configuration using the show command. [edit] show addresscontext a1 zone Z2 siptrunkgroup IPOFFICE_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 17 of 27

18 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 mimecauseprecedereasonheadercause minimizerelayingofmediachangesfromothercalllegall 18 of 27 Sonus Networks Interoperability Test Lab

19 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 errorinfo fromheader historyinfo Sonus Networks Interoperability Test Lab 19 of 27

20 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 privacy { transparency 20 of 27 Sonus Networks Interoperability Test Lab

21 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 includecpcinformation includenpi includeolip includepkadn includepstnparameters includeqvalue skipcseqcheckinearlydialog transparencyfordestinationtrunkgroupparameter enable; transport { type1 none; type2 none; type3 none; type4 none; ingressipattributes { flags { sip181supported sip182supported mapcalledpartycategoryinpsiginfoheader nosdpin180supported registrationexpiresinexpiresheader registrationsupport3xx send183oninitiatingdisconnecttreatment sendsdpin200okif18xreliable sendsdpinsubsequent18x carrierinformation { Sonus Networks Interoperability Test Lab 21 of 27

22 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] 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 ""; packettopacketcontrol { transcode conditional; conditionsinadditiontonocommoncodec { differentdtmfrelay 22 of 27 Sonus Networks Interoperability Test Lab

23 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 23 of 27

24 4.5. 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 IPOFFICE_RL routinglabelroute 1 trunkgroup IPOFFICE_TG ippeer IPOFFICE_IPP inservice inservice commit 2. Configure the Standard Route. set global callrouting route none Sonus_NULL Sonus_NULL standard 21 1 all all ALL none Sonus_NULL routinglabel IPOFFICE_RL commit 3. Verify configuration using the show command. [edit] admin@nbs51k1% show global callrouting route route trunkgroup IPOFFICE_TG NBS51K1 standard Sonus_NULL 1 all all ALL none Sonus_NULL { routinglabel IPOFFICE_RL; [ok][ :16:44] [edit] admin@nbs51k1% show global callrouting routinglabel IPOFFICE_RL overflownumber ""; overflownoa none; overflownpi none; routeprioritizationtype sequence; script ""; action routes; routinglabelroute 1 { trunkgroup IPOFFICE_TG; ippeer proportion 0; cost ; IPOFFICE_IPP; inservice inservice; testing normal; [ok][ :19:12] 24 of 27 Sonus Networks Interoperability Test Lab

25 5 Phase III - Interoperability Testing This section provides the details of verification tests performed to verify configuration of IPOFFICE 500 PBX 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 Origination with UDP PASS Basic SIP call Termination with UDP PASS Basic SIP call Origination with TCP PASS Basic SIP call Origination with TCP PASS Basic SIP Call with Mitel Phone PASS Basic SIP Call with Adtran Phone PASS Conference call Feature via SBC 5100 PASS Conference call Feature via SBC 5100 PASS Conference call Feature via SBC 5100 PASS Conference Call with TCP EPs 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 via SBC 5100 PASS Call Transfer Feature via SBC 5100 PASS Call Transfer Feature via SBC 5100 PASS Call Transfer Feature via SBC 5100 PASS Call Transfer Feature ( Attended ) with refer relay flag enable PASS Basic Call with Codec negotiation ( G711, G7129 ), mute unmute and hold, resume. PASS Codec Negotiation Attended transfer. PASS Codec Negotiation Conference. PASS Sonus Networks Interoperability Test Lab 25 of 27

26 Leave and Retrieve Voice mail. PASS Leave and Retrieve Voice mail. PASS Leave and Retrieve Voice mail. PASS Leave and Retrieve Voice mail. PASS 26 of 27 Sonus Networks Interoperability Test Lab

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