Sonus Networks Network Border Switch 5200

Transcription

1 Sonus Networks Network Border Switch 5200 For use with AT&T s IP Toll Free Service (Using AVPN or MIS/PNT transport connections) NBS5200 Configuration Guide (ForAvaya Aura Communication Manager 6.0.1& Avaya Aura Session Manager 6.1.1)

2 Disclaimers and Restrictions This Customer Configuration Guide ("CCG") is offered as a convenience to AT&T's customers for informational purposes only. The specifications and information regarding the product in this CCG are subject to change without notice. While reasonable efforts have been made in the preparation of this publication, Sonus Networks and its suppliers assume no liability resulting from technical or editorial errors or omissions, or for any damages resulting from the use of this information. All statements, information, and recommendations in this CCG are presented without warranty of any kind, express or implied, and are provided AS IS. In no event shall Sonus be liable for any indirect, special, consequential, or incidental damages, including, without limitation, lost profits or loss or damage arising out of the use or inability to use this CCG, even if the user have been advised of the possibility of such damage. Unless specifically included in a written agreement with Sonus Networks, Sonus Networks has no obligation to develop or deliver any future release, upgrade, feature, enhancement or function. Copyright 2012Sonus Networks, Inc. All rights reserved. Sonus is a registered trademark of Sonus Networks, Inc. All other trademarks, service marks, registered trademarks or registered service marks may be the property of their respective owners.

3 Table of Contents 1 Introduction Special Notes Network Topology Call Routing for Virtual Extension Testing Call Routing for Vector Testing NBS5200 Hardware Configuration NBS5200 Software Configuration NBS5200 Configuration Configure Interfaces Configuring Zone Configure Static Routes Configure Profiles IP Signaling Profile Configure Global Avaya Configuration Troubleshooting... 84

4 NBS5200 Configuration Guide 4 1 Introduction This document provides a configuration guide for Sonus NBS5200 (Network Border Switch)when connecting to AT&T IP Toll Free service using AVPNor MIS/PNT transport. The Sonus NBS5200 is a Session Border Controller that connects disparate SIP trunks, SIP PBXs, and communication applications within an enterprise. It can also be used as a SIP routing and integration engine. The Sonus SBC is the point of connection between the Avaya Aura MES solution and AT&T IP Toll Free service and is used not only to secure the SIP trunk, but also to make adjustments to carrier and enterprise signaling for interoperability. 1.1 Special Notes Mid-call Re-INVITEs The Sonus NBS5200 does not send out the shufflingre-invites and Hold-Resume Re- INVITES from the Avaya Aura Session Manager to the Network unless there are changes in the media information. The Re-INVITES received from the Avaya Aura Session Manager with changes only in the media source information will not be relayed to the Network. However, changes in the media codecs, p-time or media attributes will be relayed to the Network G.711 Fax Calls G.711 faxing is not supported between Communication Manager and the AT&T IP Toll Free service. Communication Manager does not support the protocol negotiation that AT&T requires to have G.711 fax calls work. T.38 faxing is supported, as is Group 3 and Super Group 3 fax. Fax speeds are limited to 9600 in the configuration tested. In addition, Fax Error Correction Mode (ECM) is not supported by Communication Manager. Reference: Please refer Section2.2.1 Known Limitations of Avaya Configuration Guide Emergency 911/E911 Services Limitations and Restrictions AT&T provides 911/E911 calling capabilities but does not warrant that the equipment and software (example, IP PBX) reviewed in the customer configuration guide will properly operate with AT&T IP Toll Free to complete 911/E911 calls. Therefore, it is the Customer's responsibility to ensure proper operation with its equipment/software vendor. AT&T IP Toll Free services support E911/911 calling capabilities under certain Calling Plans. But, there are circumstances when that E911/911 service may not be available, as stated in the Service Guide for AT&T IP Toll Free found at Such circumstances include (but are not limited to): Relocation of the end user's CPE

5 NBS5200 Configuration Guide 5 Use of a non-native or virtual telephone number Failure in the broadband connection Loss of electrical power Delays that may occur in updating the Customer's location in the automatic location information database Please review the AT&T IP Toll Free Service Guide in detail to understand the limitations and restrictions. 1.2 Network Topology The figure above represents the equipment that was used for the AT&T IP Toll Free certification. The Avaya IP Phones used with the Avaya PBX can be configured to work with H.323 or SIP Protocol. To know the hardware and software version details used for the above setup, see NBS5200 Hardware Configuration. Note: This guide supports NBS5200 configurations for NBS5200 releases V02.00.X.

6 NBS5200 Configuration Guide Call Routing for Virtual Extension Testing The following diagram shows a schematic of the call routing when configured for Virtual Extension Testing. In this case the calls are routed in the setup directly based on the Dialed Number (DNIS Routing). During these tests the Avaya Session Manager is reconfigured to route the call to different Hunt Groups. Calls are Directly Routed based on Dialed Number (DNIS Routing) : Adaptation on SM modified to route the call to Different Hunt Groups Virtual Extension AVAYA AURA NBS HUNT GROUP HUNT GROUP HUNT GROUP

7 NBS5200 Configuration Guide Call Routing for Vector Testing The following diagram shows a schematic of the call routing when configured for Vectored Call Testing. In this case the call is established and the user will be prompted to enter the digits on the phone. Based on the user input (number), the call is routed to the configured Hunt Group. SM Adaptation applied to route the calls to Vector User gets the following Announcement: Welcome to SonusIOT Dial 1 to Reach Hunt Group 1 Dial 2 to Reach Hunt Group 2 Dial 3 to Reach Hunt Group 3 Calls are Routed based on User Input (Caller Entered Digit Routing) User: Dials 1 User: Dials 3 User: Dials 2 AVAYA AURA Virtual Extension NBS HUNT GROUP HUNT GROUP HUNT GROUP

8 NBS5200 Configuration Guide NBS5200 Hardware Configuration [root@iotsbx2 ~]# hwinfo ===================================================================== FRU Device Description :Builtin FRU Device (ID 0) Chassis Type : Rack Mount Chassis Chassis Part Number : Chassis Serial : Chassis Extra : C208 Board Mfg : Sonus Networks Inc. Board Product : SBS100 Board Serial : Board Part Number : Board Extra : C210C200C206 Product Manufacturer :Sonus Networks Inc. Product Name : SBS100 Product Part Number : Product Version : 06 Product Serial : Product Extra : 00:10:6B:2E:E4:BE FRU Device Description : FRU PS_TOP (ID 2) Chassis Type : Unspecified Product Manufacturer : ASTEC Product Name : DS Product Part Number : DS Product Version : 10 Product Serial : G087H P Product Extra : FRU Device Description : FRU SPS100 (ID 3) Device not present (Unknown (0x81)) FRU Device Description : FRU DB0 (ID 4) Device not present (Unknown (0x81)) FRU Device Description : FRU DB1 (ID 5) Device not present (Unknown (0x81)) =====================================================================

9 NBS5200 Configuration Guide NBS5200 Software Configuration [root@iotsbx2 ~]# swinfo =================================================== BMC: v BIOS: v ConnexIP OS: v1.7.2 SonusDB: sonusdb-v r000 EMA: ema-v r000 SBX: sbx-v r000 =================================================== Installed host role: active ===================================================

10 NBS5200 Configuration Guide 10 2 NBS5200 Configuration The NBS5200 configuration is possible using the CLI as well as the EMA. This guide lists the configuration in 3 steps 1. The CLI Commands used for configuring the NBS The CLI Output of the show commands for the configurations done using Step The GUI Screens of the EMA Workflow configuration as seen after the configuration using Step Configure Interfaces SBC5200 AVAYA AURA Setup (SM) SIP Trunk SIP Trunk AT&T IPFlex Reach SIP SIG: SIP SIG: (Internal) AddressContext: A1 Zone: INTERNAL Network Interface: pkt0 Media Interface: LIF1 SIP Trunk Name: AVAYA-SM-STG SIP SIG: (External) AddressContext: A1 Zone: EXTERNAL Network Interface: pkt1 Media Interface: LIF2 SIP Trunk Name: ATT-IPTF_STG AT&T IP: IP Interface Group Internal CLI Configuration Commands set addresscontext "A1" set addresscontext "A1" ipinterfacegroup "LIF1" set addresscontext "A1" ipinterfacegroup "LIF1" ipinterface "pkt0_v4" cename "IOTSBX2" portname "pkt0" ipaddress " " prefix "24" set addresscontext "A1" ipinterfacegroup "LIF1" ipinterface "pkt0_v4" mode "inservice" state "enabled" commit

11 NBS5200 Configuration Guide 11 show addresscontexta1ipinterfacegroup LIF1 ipinterface pkt0_v4 { cename IOTSBX2; portname pkt0; ipaddress ; prefix 24; modeinservice; state enabled; GUI Configuration

12 NBS5200 Configuration Guide IP Interface Group External CLI Configuration Commands set addresscontext "A1" ipinterfacegroup "LIF2" set addresscontext "A1" ipinterfacegroup "LIF2" ipinterface "pkt1_v4 " cename "IOTSBX2" portname "pkt1" ipaddress " " prefix "24" set addresscontext "A1" ipinterfacegroup "LIF2" ipinterface "pkt1_v4 " mode "inservice" state "enabled" commit show addresscontext A1 ipinterfacegroup LIF2 ipinterface pkt1_v4 { cename IOTSBX2; portname pkt1; ipaddress ; prefix 24; modeinservice; state enabled; GUI Configuration

13 NBS5200 Configuration Guide Configuring Zone Zone is used to group a set of objects for a particular customer environment Internal Zone (Towards Avaya Aura Session Manager) IP Peer CLI Configuration Commands set addresscontext "A1" zone "INTERNAL" ippeer "AVAYA-SM_IPP" ipaddress " " ipport "5060" commit admin@iotsbx2% show addresscontext A1 zone INTERNAL ippeer ippeer AVAYA-SM_IPP { ipaddress ; ipport 5060; policy { description ""; sip { fqdn ""; fqdnport 0; packetserviceprofile ""; ipsignalingprofile ""; GUI Configuration

14 NBS5200 Configuration Guide SIP Signaling Port CLI Configuration Commands set addresscontext "A1" zone "INTERNAL" sipsigport "1" ipinterfacegroupname "LIF1" ipaddressv4 " " set addresscontext "A1" zone "INTERNAL" sipsigport "1" mode "inservice" state "enabled" commit show addresscontext A1 zone INTERNAL sipsigport sipsigport 1 { ipinterfacegroupname LIF1; ipaddressv ; portnumber 5060; state enabled; transportprotocolsallowed sip-udp;

15 NBS5200 Configuration Guide 15 GUI Configuration SIP TrunkGroup CLI Configuration Commands set addresscontext "A1" zone "INTERNAL" id "3" set addresscontext "A1" zone "INTERNAL" siptrunkgroup "AVAYA-SM-STG" state "enabled" mode "inservice" set addresscontext "A1" zone "INTERNAL" siptrunkgroup "AVAYA-SM-STG" media mediaipinterfacegroupname "LIF1" sourceaddressfiltering "disabled" set addresscontext "A1" zone "INTERNAL" siptrunkgroup "AVAYA-SM-STG" ingressipprefix " " "32" set addresscontext "A1" zone "INTERNAL" siptrunkgroup "AVAYA-SM-STG" policy media packetserviceprofile "ATT-IPTF_PSP" set addresscontext "A1" zone "INTERNAL" siptrunkgroup "AVAYA-SM-STG" policy signaling ipsignalingprofile "ATT-IPTF_IPSP" commit show addresscontexta1 zone INTERNALsipTrunkGroup siptrunkgroup AVAYA-SM_STG {

16 NBS5200 Configuration Guide 16 state enabled; mode inservice; policy { carrier 0000; country 1; sipdomain ""; localizationvariantnorthamerica; digitparameterhandling { numberingplan NANP_ACCESS; ingressdmpmrule ""; egressdmpmrule ""; callrouting { elementroutingpriority DEFAULT_IP; media { packetserviceprofile ATT-IPTF_PSP; services { classofservice DEFAULT_IP; signaling { ipsignalingprofile ATT-IPTF_IPSP; signalingprofile ""; media { mediaipinterfacegroupname LIF1; ingressipprefix ;

17 NBS5200 Configuration Guide 17 GUI Configuration Sip Trunk Group: Fig (1 of 11)

18 NBS5200 Configuration Guide 18 Sip Trunk Group: Fig (2 of 11)

28 NBS5200 Configuration Guide External Zone (Towards AT&T IP-Flex Network) IP Peer CLI Configuration Commands set addresscontext "A1" zone "EXTERNAL" ippeer "ATT-IPP" ipaddress " " ipport "5060" set addresscontext "A1" zone "EXTERNAL"ipPeer "ATT-IPP-2" ipaddress " " ipport "5060" commit CLI Configuration AT&T provides two IP Addresses for redundancy, which can be configured here show addresscontexta1 zone EXTERNALipPeer ippeer ATT-IPP { ipaddress ; ipport 5060; policy { description ""; sip { fqdn ""; fqdnport 0; packetserviceprofile ""; ipsignalingprofile ""; ippeer ATT-IPP-2 { ipaddress ; ipport 5060; policy { description ""; sip { fqdn ""; fqdnport 0; packetserviceprofile ""; ipsignalingprofile "";

29 NBS5200 Configuration Guide 29 GUI Configuration

30 NBS5200 Configuration Guide SIP Signaling Port CLI Configuration Commands set addresscontext "A1" zone "EXTERNAL" sipsigport "2" ipinterfacegroupname "LIF2" ipaddressv4 " " set addresscontext "A1" zone "EXTERNAL" sipsigport "2" mode "inservice" state "enabled" commit show addresscontexta1 zone EXTERNALsipSigPort 2 ipinterfacegroupname LIF2; ipaddressv ; portnumber 5060; mode inservice; state enabled; dscpvalue 4; GUI Configuration

31 NBS5200 Configuration Guide SIP Trunk Group CLI Configuration Commands set addresscontext "A1" zone "EXTERNAL" id "2" set addresscontext "A1" zone "EXTERNAL" siptrunkgroup "ATT-IPTF_STG" state "enabled" mode "inservice" set addresscontext "A1" zone "EXTERNAL" siptrunkgroup "ATT-IPTF_STG" media maxptimedefault "20" mediaipinterfacegroupname "LIF2" sourceaddressfiltering "disabled" set addresscontext "A1" zone "EXTERNAL" siptrunkgroup "ATT-IPTF_STG" signaling relaynoninviterequest "enabled" set addresscontext "A1" zone "EXTERNAL" siptrunkgroup "ATT-IPTF_STG" policy signaling ipsignalingprofile "ATT-IPTF_IPSP" set addresscontext "A1" zone "EXTERNAL" siptrunkgroup "ATT-IPTF_STG" policy digitparameterhandlingegressdmpmrule "add011" set addresscontext "A1" zone "EXTERNAL" siptrunkgroup "ATT-IPTF_STG" ingressipprefix " " "32" set addresscontext "A1" zone "EXTERNAL" siptrunkgroup "ATT-IPTF_STG" policy media packetserviceprofile "ATT-IPTF_PSP" commit When using AT&T VPN Transport (AVPN), AT&T recommends using a 30ms ptime to reduce the bandwidth used per call.

32 NBS5200 Configuration Guide 32 show addresscontexta1 zone EXTERNALsipTrunkGroupATT-IPTF_STG state enabled; mode inservice; policy { carrier 0000; country 1; sipdomain ; localizationvariantnorthamerica; digitparameterhandling { numberingplan NANP_ACCESS; ingressdmpmrule ; egressdmpmrule ; callrouting { elementroutingpriority DEFAULT_IP; media { packetserviceprofileatt-iptf_psp; services { classofservice DEFAULT_IP; signaling { ipsignalingprofile ATT-IPTF_IPSP; media { maxptimedefault 30; mediaipinterfacegroupname LIF2; ingressipprefix ; [ok]

33 NBS5200 Configuration Guide 33 GUI Configuration Sip Trunk Group: Fig (1 of 11)

44 NBS5200 Configuration Guide Configure Static Routes CLI Configuration Commands set addresscontext "A1" staticroute " " "24" " " "LIF1" "pkt0_v4" set addresscontext "A1" staticroute " " "32" " " "LIF2" "pkt1_v4" set addresscontext "A1" staticroute " " "32" " " "LIF2" "pkt1_v4" commit show addresscontexta1staticroute staticroute LIF1 pkt0_v4 { preference 100; staticroute LIF2pkt1_v4 { preference 100; staticroute LIF2pkt1_v4 { preference 100; GUI Configuration

45 NBS5200 Configuration Guide Configure Profiles Codec Entry CLI Configuration Commands set profiles media codecentry "ATT-G729" codec "g729a" packetsize "20" set profiles media codecentry "ATT-G729" fax tonetreatment "faxrelay" set profiles media codecentry "ATT-G729" dtmf relay "rfc2833" commit set profiles media codecentry "ATT-G711U" packetsize "30" law "ULaw" set profiles media codecentry "ATT-G711U" fax tonetreatment "faxrelay" set profiles media codecentry "ATT-G711U" dtmf relay "rfc2833" commit set profiles media codecentry "ATT-G726" packetsize "30" law "ULaw" set profiles media codecentry "ATT-G726" fax tonetreatment "faxrelay" set profiles media codecentry "ATT-G726" dtmf relay "rfc2833" commit show profiles media codecentry codecentry ATT-G711U { codec g711; packetsize 30; preferredrtppayloadtype 100; fax { failurehandling continue; tonetreatmentfaxrelay; modem { failurehandling continue;

46 NBS5200 Configuration Guide 46 tonetreatment none; lawulaw; dtmf { relay rfc2833; removedigits enable; codecentry ATT-G726 { codec g726; codingrate 32; packetsize 30; preferredrtppayloadtype 100; fax { failurehandling continue; tonetreatmentfaxrelay; modem { failurehandling continue; tonetreatment none; dtmf { relay rfc2833; removedigits enable; codecentry ATT-G729 { codec g729ab; packetsize 30; preferredrtppayloadtype 100; fax { failurehandling continue; tonetreatmentfaxrelay; modem { failurehandling continue; tonetreatment none; dtmf { relay rfc2833; removedigits enable;

47 NBS5200 Configuration Guide 47 GUI Configuration ATT-G711U

48 NBS5200 Configuration Guide 48 ATT-G729

49 NBS5200 Configuration Guide 49 ATT-G729

50 NBS5200 Configuration Guide 50

51 NBS5200 Configuration Guide Packet Service Profile CLI Configuration Commands set profiles media packetserviceprofile"att-iptf_psp" codec codecentry1 "ATT-G729" codecentry2 "ATT- G711U"codecEntry3 ATT-G726 set profiles media packetserviceprofile "ATT-IPTF_PSP" t38 lowspeednumberofredundantpackets "1" numberofredundantpackets "1" set profiles media packetserviceprofile "ATT-IPTF_PSP" rtcpoptionsrtcp "enable" set profiles media packetserviceprofile "ATT-IPTF_PSP" datacallspacketsize "20" set profiles media packetserviceprofile "ATT-IPTF_PSP" preferredrtppayloadtypefordtmfrelay "100" commit show profiles media packetserviceprofile ATT-IPTF_PSP datacalls { preferredrtpdatapayloadtype 56; initialplayoutbufferdelay 50; packetsize 20; silencefactor 40; typeofservice 0; voiceinitialplayoutbufferdelay 10; rtcpoptions { rtcp enable; terminationforpassthrough packetlossthreshold 0; packetlossaction none; peerabsenceaction none; silenceinsertiondescriptor { g711sidrtppayloadtype 13; heartbeat enable; aal1payloadsize 47; codec { codecentry1 ATT-G729; codecentry2 ATT-G711U; codecentry3 ATT-G726; codecentry4 ""; packettopacketcontrol { transcode conditional;

52 NBS5200 Configuration Guide 52 conditionsinadditiontonocommoncodec { differentdtmfrelay differentpacketsize differentsilencesuppression honorofferpreference codecsallowedfortranscoding { thisleg ""; otherleg ""; flags { disallowdatacalls digitdetectsendenabled usedirectmedia validatepeersupportfordtmfevents t38 { dataratemanagementtype type2transferoftcf; ecm { ecmpreferred lowspeednumberofredundantpackets 1; maxbitrate 14.4Kbits_s; numberofredundantpackets 1; securertprtcp { cryptosuiteprofile ""; flags { allowfallback enablesrtp preferredrtppayloadtypefordtmfrelay 100; videocalls { maxvideobandwith 0; videobandwidthreductionfactor 0; audioonlyifvideoisprevented enable; mediapacketcos 0; honorremoteprecedence sendroutepspprecedence [ok]

57 NBS5200 Configuration Guide IP Signaling Profile CLI Configuration Commands set profiles signaling ipsignalingprofile "ATT-IPTF_IPSP" set profiles signaling ipsignalingprofile "ATT-IPTF_IPSP" commonipattributes flags addpathserviceroute "enable" minimizerelayingofmediachangesfromothercalllegall "enable" sendallallowedcodecsforlatemediainviteorreinvite "enable" sendptimeinsdp "enable" set profiles signaling ipsignalingprofile "ATT-IPTF_IPSP" egressipattributes flags disable2806compliance "enable" validateisubaddress "enable" set profiles signaling ipsignalingprofile "ATT-IPTF_IPSP" ingressipattributes flags sendsdpin200okif18xreliable "enable" set profiles signaling ipsignalingprofile "ATT-IPTF_IPSP" ingressipattributes flags sendsdpinsubsequent18x "enable" set profiles signaling ipsignalingprofile ATT-IPTF_IPSP commonipattributes relayflags statuscode4xx6xx commit show profiles signaling ipsignalingprofile ATT-IPTF_IPSP ipprotocoltypesiponly; 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

58 NBS5200 Configuration Guide 58 nocontentdisposition noportnumber5060 enable; nouserinfoincontactheader onlyselectedcodecinsessionrefresh pchgmsginfo rejectrefer requerypsxonregisterrefresh sdpolineonlycompares sendallallowedcodecsforlatemediainviteorreinvite senddirectmediainfoinsdpattribute sendptimeinsdp sessiontimerrefreshupdate setacceptheadertoapplicationsdponly setolinedash setsessionversionzero setslinedash skippsxqueryforrefer storepathheader storeservicerouteheader terminalportabilityinterworking calltransferflags { handleipaddressesnotpresentinnetworkselectortablenstrouteviatransferringiptg; forcererouteviapsxquery optiontaginrequireheader { suppressreplacetag optiontaginsupportedheader { suppressreplacetag relayflags { dialogeventpackage dtmfbody info message notify options regeventpackage refer sonusmediabody statuscode3xx statuscode4xx6xx enable;

59 NBS5200 Configuration Guide 59 thirdpartybodies transparencyflags { alertinformationheader authcodeheaders contactheader errorinfo fromheader historyinfo maxforwardsheader mwibody pchargingvectorheader pearlymedia pathheader qsigbody reasonheader referredbyheader requesturi routeheader servicerouteheader sipbody sipfragbody toheader tonebody unknownbody unknownheader egressipattributes { numberglobalizationprofile ""; flags { bgcftargetschemetransparency convertinactivetosendrecv disable2806compliance enable; disableoptionalregisterparameters map181or182messageto183 mapcontractornumberinpsiginfoheader suppressunregister ttcisupmapping usecalledpartyinrequesturi usecoloninsdpmediatypeparameter validateisubaddress

60 NBS5200 Configuration Guide 60 bci { bciinterworkencountered bciisdnaddess domainname { usesipdomainnameinfromfield usesipdomainnameinrequesturi isub { allownsapisub allowuserspecifiedisub includecalledpartyisub includecallingpartyisub numberportabilityattributes { npdioptionsincludenpdiyes; disablern privacy { transparency privacyinformationppreferredid; flags { includeprivacy enable; privacyrequiredbyproxy redirect { modeacceptredirection; contacthandlingmergereceivedcontacts; flags sipheadersandparameters { callforwarding { datamapping diversion; diversionheadertransparency includechargeinformationincludenone; destinationtrunkgroupoptionsincludenone; originatingtrunkgroupoptionsincludenone; flags { includecic includecpcinformation includenpi

61 NBS5200 Configuration Guide 61 includeolip includepkadn includepstnparameters includeqvalue skipcseqcheckinearlydialog transparencyfordestinationtrunkgroupparameter transport { type1 none; type2 none; type3 none; type4 none; ingressipattributes { flags { sip181supported sip182supported mapcalledpartycategoryinpsiginfoheader nosdpin180supported registrationexpiresinexpiresheader registrationsupport3xx send183oninitiatingdisconnecttreatment sendsdpin200okif18xreliable sendsdpinsubsequent18x carrierinformation { generateterminatingca generateterminatingcic [ok]

62 NBS5200 Configuration Guide 62 GUI Configuration Sip Signaling Profile: Fig (1 of 12)

63 NBS5200 Configuration Guide 63 IP Signaling Profile: Fig (2 of 12) IP Signaling Profile: Fig (3 of 12)

64 NBS5200 Configuration Guide 64 IP Signaling Profile: Fig (4 of 12)

78 NBS5200 Configuration Guide Configure Global Routing Label CLI Configuration Commands set global callrouting routinglabel "ATT-IPTF_RL" routinglabelroute 1 trunkgroup ATT-IPTF_STG ippeer ATT-IPTF_IPP commit set global callrouting routinglabel "AVAYA-SM_RL"routingLabelRoute 1 trunkgroup AVAYA-SM_STG ippeer AVAYA-SM_IPP commit admin@iotsbx2% show global callroutingroutinglabel routinglabel ATT-IPTF_RL { overflownumber ""; overflownoa none; overflownpi none; routeprioritizationtype sequence; script ""; action routes; routinglabelroute 1 { trunkgroup ATT-IPTF_STG; ippeer ATT-IPTF_IPP; proportion 0; cost ; inserviceinservice; testing normal; routinglabel AVAYA-SM_RL { overflownumber ""; overflownoa none; overflownpi none; routeprioritizationtype sequence; script ""; action routes; routinglabelroute 1 { trunkgroup AVAYA-SM_STG; ippeer AVAYA-SM_IPP; proportion 0; cost ; inserviceinservice; testing normal;

81 NBS5200 Configuration Guide Route CLI Configuration Commands set global callrouting route "trunkgroup" "ATT-IPTF_STG" "IOTSBX2" "standard" "Sonus_NULL" "1" "all" "all" "ALL" "none" "Sonus_NULL" routinglabel "AVAYA-SM-RL" commit CLI Configuration show global callrouting route routetrunkgroup ATT-IPTF_STG IOTSBX2 standard Sonus_NULL 1 all allall none Sonus_NULL { routinglabel AVAYA-SM_RL; [ok]

83 NBS5200 Configuration Guide 83 3 Avaya Configuration The Avaya Session Manager and Communication Manager configuration which is used along with the Sonus NBS5200 is as per the details provided in the Avaya Configuration Guide: Applications Notes for Avaya Aura Communication Manager 6.0.1, Avaya Aura Session Manager 6.1 and Acme Packet Net-Net with AT&T IP Toll Free SIP Trunk Service Issue 1.0 This guide is available online at In the Avaya Configuration Guide, Section Acme Packet SBC SIP Entity will be used for configuring the SIP Trunk to the Sonus NBS5200 instead of the Acme SBC. Section 8. Configure Acme Packet SBC will be replaced by this configuration guide, to configure the Sonus NBS5200 instead of the Acme SBC.

84 NBS5200 Configuration Guide 84 4 Troubleshooting Call traces can be gathered on an individual call by call basis. This is enabled by creating a Call Trace Filter on the NBS. When the filter is defined a calling and called number can be entered to capture a single call. This data is viewed in the EMS with the Call Trace screen within the Tools major screen. Assistance for troubleshooting can be obtained by calling the Sonus TAC center at This Customer Configuration Guide ("CCG") is offered as a convenience to AT&T's customers. The specifications and information regarding the product in this CCG are subject to change without notice. All statements, information, and recommendations in this CCG are believed to be accurate but are presented without warranty of any kind, express or implied, and are provided AS IS. Users must take full responsibility for the application of the specifications and information in this CCG. In no event shall AT&T or its suppliers be liable for any indirect, special, consequential, or incidental damages, including, without limitation, lost profits or loss or damage arising out of the use or inability to use this CCG, even if AT&T or its suppliers have been advised of the possibility of such damage.