SBC 5000 Series Configuration Guide (For Cisco Unified Communications Manager 9.1)

Configuration Guide SBC 5000 Series Configuration Guide (For Cisco Unified Communications Manager 9.1) For use with AT&T s IP Flexible Reach Enhanced Features Service on MIS, MPLS PNT or AT&T VPN

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.

Contents 1. Introduction... 4 1.1. Special Notes... 4 1.1.1. Emergency 911/E911 Services Limitations and Restrictions... 4 1.1.2. Mid-call Re-INVITEs... 4 1.1.3. Blind Call Transfer... 5 1.2. Network Topology... 5 1.3. Hardware/ Software Configuration... 6 2. SBC 5000 Series Configuration... 7 2.1. Configuration Diagram... 7 2.2. Naming Conventions... 7 2.3. Configuration Workflow... 8 2.4. Global Configuration... 9 2.4.1. Codec Entry... 9 2.5. Customer Side Configuration... 10 2.5.1. Configuring Profiles... 10 2.5.2. Configuring Address Context... 27 2.6. ATT Side Configuration... 32 2.6.1. Configuring Profiles... 32 2.6.2. Configuring Address Context... 49 2.7. Global Call Routing Configuration... 55 2.7.1. Customer Side Routing... 55 2.7.2. ATT Side Routing... 56 3. CUCM Configuration... 59 4. Troubleshooting... 60

SBC 5000 Series Configuration Guide 4 1. Introduction This document provides a configuration guide for Sonus SBC 5000 Series (Session Border Controller) when connecting to AT&T IPFR-EF service using AVPN or MIS/PNT transport. This configuration guide supports basic and enhanced IP Flexible Reach features. The below list gives the IP Flexible Reach - Enhanced Features (IPFR-EF) verified using this configuration guide. The complete list of IPFR-EF features can be found in AT&T IP Flexible Reach service guide at http://new.serviceguide.att.com Network Based Sequential Ring Network Based Simultaneous Ringing Network Based Call Forwarding Always Network Based Call Forwarding Busy Network Based Call Forwarding Not Reachable Network Based Call Forwarding No Answer The Sonus SBC 5000 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 Cisco Communication Manager 9.1 and AT&T IPFR-EF service and is used not only to secure the SIP trunk, but also to make adjustments to carrier and enterprise signaling for interoperability. Note: This guide supports SBC 5000 Series configurations for releases V03.X or higher 1.1. Special Notes 1.1.1. Emergency 911/E911 Services Limitations and Restrictions Emergency 911/E911 Services Limitations and Restrictions - Although AT&T provides 911/E911 calling capabilities, AT&T does not warrant or represent that the equipment and software (e.g., IP PBX) reviewed in this customer configuration guide will properly operate with AT&T IPFR-EF to complete 911/E911 calls; therefore, it is Customer s responsibility to ensure proper operation with its equipment/software vendor. While AT&T IPFR-EF services support E911/911 calling capabilities under certain Calling Plans, there are circumstances when that E911/911 service may not be available, as stated in the Service Guide for AT&T IPFR-EF found at http://new.serviceguide.att.com. Such circumstances include, but are not limited to, relocation of the end user s CPE, use of a nonnative or virtual telephone number, failure in the broadband connection, loss of electrical power, and delays that may occur in updating the Customer s location in the automatic location information database. Please review the AT&T IPFR-EF Service Guide in detail to understand the limitations and restrictions. 1.1.2. Mid-call Re-INVITEs The Sonus SBC 5000 does not send out the shuffling Re-INVITES and Hold-Resume Re- INVITES from the Cisco Unified Communications Manager to the Network unless there are changes in the media information.

SBC 5000 Series Configuration Guide 5 The Re-INVITES received from the CUCM 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. 1.1.3. Blind Call Transfer The IP Flexible Reach Enhanced Feature Network Based Blind Call Transfer is not supported by this configuration since Cisco CUCM 9.1 does not support sending REFER 1.2. Network Topology CCM Subscriber SIP Trunk SBC SIP Trunk Sig: Skinny/SIP Media: RTP CCM Publis h Sig: SIP Media: RTP/T38 Sig: SIP Media: RTP/T38 AT&T Sig: Skinny P Cisco Voice/Fax Gateway 2911 Sig: SIP Media: RTP/T38 Cisco Unity Voicemail Server & Auto Attendant Local PSTN F The figure above represents the equipment that was used for the IPFR-EF certification. The Cisco IP Phones used with the CUCM PBX can be configured to work with Skinny or SIP Protocol. To know the hardware and software version details used for the above setup, see Section 1.3 - Hardware/ Software Configuration

SBC 5000 Series Configuration Guide 6 1.3. Hardware/ Software Configuration Equipment Software Sonus SBC 5000 Series BMC BIOS OS SonusDB EMA SBC V02.00.00 V02.00.00 V01.08.00-R000 V03.00.01-R001 V03.00.01-R001 V03.00.01-R001 Third-party Equipments CUCM 9.1

SBC 5000 Series Configuration Guide 7 2. SBC 5000 Series Configuration This section describes how to use the Sonus Command Line Interface (CLI) to configure and manage the SBC 5000 Series. This guide lists the configuration in 2 steps 1. The CLI Commands used for configuring the SBC5000 2. The CLI Output of the show commands for the configurations done using Step 1. 2.1. Configuration Diagram Customer Side SBC 5000 ATT Side CUCM 9.1 SIP Trunk SIP Trunk AT&T IP Flexible Reach SIP SIG: 172.16.102.24 SIP SIG: 172.16.104.164 (Internal) AddressContext: IPDOMAIN Zone: CUST_ZONE Network Interface: pkt1 Media Interface: CUSTIFG SIP Trunk Name: CUST_TG SIP SIG: 32.252.34.18 (External) AT&T IP: 12.194.20.75/ 12.194.18.75 AddressContext:IPDOMAIN Zone: ATT_ZONE Network Interface: pkt2 Media Interface: ATTIFG SIP Trunk Name: ATT_TG 2.2. Naming Conventions Entity Customer side ATT Side IP Interface Group CUSTIFG ATTIFG IP Peer CUST_IPP ATT_IPP1, ATT_IPP2 IP Signaling Profile CUST_IPSP ATT_IPSP Numbering Plan CUST_NUM_PLAN ATT_NUM_PLAN Packet Service Profile CUST_PSP ATT_PSP Prefix Profile CUST_PP ATT_PP Trunkgroup CUST_TG ATT_TG Zone CUST_ZONE ATT_ZONE Routing Label CUST_RL ATT_RL

SBC 5000 Series Configuration Guide 8 2.3. Configuration Workflow ---- Global Configuration ----Codec Entry ---- Customer Side Configuration ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile ----Prefix Profile ----Numbering Plan ----DM/PM Rule ----SIP Adaptor Profiles ----Configuring Address Context ----IP Interface Group ----Static Route ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunkgroup ---- Network Side Configuration ----Configuring Profiles ----Packet Service Profile ----IP Signaling Profile ----Prefix Profile ----Numbering Plan ----DM/PM Rule ---- SIP Adaptor Profiles ----Configuring Address Context ----IP Interface Group ----Static Route ----Zone ----SIP Signaling Port ----IP Peer ----SIP Trunkgroup

SBC 5000 Series Configuration Guide 9 ---- Global Call Routing Configuration ----Customer Side Routing ----Routing Label ----Route ----ATT Side Routing ----Routing Label ----Route 2.4. Global Configuration 2.4.1. Codec Entry Create the codec entry for G729A and G711Ulaw codecs with t38 fax treatment and rfc2833 method for dtmf Parameter G729A_T38_2833 G711Ulaw_T38_2833 Description Codec Entry for g729a codec with fax t38 and dtmf rfc2833 Codec Entry for g711ulaw codec with fax t38 and dtmf rfc2833 set profiles media codecentry G729A_T38_2833 codec g729a packetsize 30 set profiles media codecentry G729A_T38_2833 fax tonetreatment faxrelay set profiles media codecentry G729A_T38_2833 dtmf relay rfc2833 set profiles media codecentry G711Ulaw_T38_2833 codec g711 packetsize 30 law ULaw set profiles media codecentry G711Ulaw_T38_2833 fax tonetreatment faxrelay set profiles media codecentry G711Ulaw_T38_2833 dtmf relay rfc2833 The output of show command for codec entry is as given below: admin@custsbc% show profiles media codecentry G729A_T38_2833 codec g729a; packetsize 30; preferredrtppayloadtype 128; fax { failurehandling continue; tonetreatment faxrelay; modem {

SBC 5000 Series Configuration Guide 10 failurehandling continue; tonetreatment dtmf { relay rfc2833; removedigits enable; admin@custsbc% show profiles media codecentry G711Ulaw_T38_2833 codec g711; packetsize 30; preferredrtppayloadtype 128; fax { failurehandling continue; tonetreatment faxrelay; modem { failurehandling continue; tonetreatment law ULaw; dtmf { relay rfc2833; removedigits enable; 2.5. Customer Side Configuration 2.5.1. Configuring Profiles Create profiles with specific set of characteristics correspond to customer IP-PBX. It includes configuration of following entities on customer side. 1. Packet Service Profile 2. IP Signaling Profile 3. Prefix profile 4. Numbering Plan 5. DM/PM Rule 6. SIP Adaptor Profiles 1) Packet Service Profile Create Packet Service Profile towards customer side with G729A as a first codec and G711ulaw as a second codec

SBC 5000 Series Configuration Guide 11 Parameter CUST_PSP Description Packet Service Profile name towards Customer side with rtcp enabled and preferred rtp payload for dtmf 100 set profiles media packetserviceprofile CUST_PSP codec codecentry1 G729A_T38_2833 codecentry2 G711Ulaw_T38_2833 set profiles media packetserviceprofile CUST_PSP t38 lowspeednumberofredundantpackets 0 numberofredundantpackets 0 set profiles media packetserviceprofile CUST_PSP rtcpoptions rtcp enable set profiles media packetserviceprofile CUST_PSP preferredrtppayloadtypefordtmfrelay 100 honorremoteprecedence enable The output of show command for packet service profile is as given below: admin@custsbc% show profiles media packetserviceprofile CUST_PSP datacalls { preferredrtpdatapayloadtype 56; initialplayoutbufferdelay 50; packetsize 0; silencefactor 40; typeofservice 0; voiceinitialplayoutbufferdelay 10; rtcpoptions { rtcp enable; terminationforpassthrough packetlossthreshold 0; packetlossaction peerabsenceaction silenceinsertiondescriptor { g711sidrtppayloadtype 13; heartbeat enable; aal1payloadsize 47; codec { codecentry1 G729a_T38_2833; codecentry2 G711Ulaw_T38_2833; codecentry3 ; codecentry4 ; packettopacketcontrol {

SBC 5000 Series Configuration Guide 12 transcode conditional; conditionsinadditiontonocommoncodec { differentdtmfrelay differentpacketsize differentsilencesuppression honorofferpreference codecsallowedfortranscoding { thisleg ""; otherleg ""; flags { disallowdatacalls digitdetectsendenabled usedirectmedia validatepeersupportfordtmfevents t38 { dataratemanagementtype type2transferoftcf; ecm { ecmpreferred lowspeednumberofredundantpackets 0; maxbitrate 14.4Kbits_s; numberofredundantpackets 0; securertprtcp { cryptosuiteprofile ; flags { allowfallback enablesrtp preferredrtppayloadtypefordtmfrelay 100; videocalls { maxvideobandwith 0; videobandwidthreductionfactor 0; audioonlyifvideoisprevented enable; mediapacketcos 0; honorremoteprecedence enable; sendroutepspprecedence

SBC 5000 Series Configuration Guide 13 2) IP Signaling Profile Create IP Signaling Profile with appropriate signaling flags towards customer side Parameter CUST_IPSP Description IP Signalling Profile name on Customer side. set profiles signaling ipsignalingprofile CUST_IPSP set profiles signaling ipsignalingprofile CUST_IPSP commonipattributes flags minimizerelayingofmediachangesfromothercalllegall enable sendallallowedcodecsforlatemediainviteorreinvite enable sendptimeinsdp enable set profiles signaling ipsignalingprofile CUST_IPSP commonipattributes relayflags refer enable set profiles signaling ipsignalingprofile CUST_IPSP egressipattributes flags disable2806compliance enable set profiles signaling ipsignalingprofile CUST_IPSP egressipattributes privacy privacyinformation passertedid set profiles signaling ipsignalingprofile CUST_IPSP ingressipattributes flags sendsdpin200okif18xreliable enable sendsdpinsubsequent18x enable The output of show command for ip signaling profile is as given below: admin@custsbc% show profiles signaling ipsignalingprofile CUST_IPSP ipprotocoltype siponly; commonipattributes { flags { addpathserviceroute callholdinterworking clearmodefordatacalls createpchargingvector createpathheader createservicerouteheader customizedsessiontimerbehavior disablealsoheader disablehosttranslation disablemedialockdown disablerefertouriparameters discardreceivedreasonheader donotincludessattributeinreinvite endtoendbye includeipportsinfromandtoheaders includereasonheader includessattributeininitialinvite

SBC 5000 Series Configuration Guide 14 includetransporttypeincontactheader insertpeeraddressastoprouteheader mapcauselocation mapsuspendresumeeventinpsvcinfoheader mapuuiinpsiginfoheader mimecauseprecedereasonheadercause minimizerelayingofmediachangesfromothercalllegall enable; nocontentdisposition noportnumber5060 enable; nouserinfoincontactheader onlyselectedcodecinsessionrefresh pchgmsginfo replacehostonviaheader requerypsxonregisterrefresh sdpolineonlycompares sendallallowedcodecsforlatemediainviteorreinvite enable; senddirectmediainfoinsdpattribute sendptimeinsdp enable; 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

SBC 5000 Series Configuration Guide 15 regeventpackage refer enable; sonusmediabody statuscode3xx statuscode4xx6xx thirdpartybodies force503to500relay transparencyflags { alertinformationheader authcodeheaders contactheader 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

SBC 5000 Series Configuration Guide 16 usecoloninsdpmediatypeparameter validateisubaddress bci { bciinterworkencountered bciisdnaddess domainname { usesipdomainnameinfromfield usesipdomainnameinrequesturi isub { allownsapisub allowuserspecifiedisub includecalledpartyisub includecallingpartyisub numberportabilityattributes { npdioptions includenpdiyes; disablern privacy { transparency privacyinformation passertedid; 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 {

SBC 5000 Series Configuration Guide 17 includecic includecpcinformation includenpi includeolip includepkadn includepstnparameters includeqvalue skipcseqcheckinearlydialog transparencyfordestinationtrunkgroupparameter transport { type1 type2 type3 type4 ingressipattributes { flags { sip181supported sip182supported mapcalledpartycategoryinpsiginfoheader nosdpin180supported registrationexpiresinexpiresheader send183oninitiatingdisconnecttreatment sendsdpin200okif18xreliable enable; sendsdpinsubsequent18x enable; carrierinformation { generateterminatingca generateterminatingcic 3) Prefix Profile Create Prefix Profile with appropriate dial plan for handling outgoing calls to ATT network. The configuration below shown with country US (+1). Parameter CUST_PP Description Prefix Profile name on Customer side. set profiles digitparameterhandling prefixprofile CUST_PP entry 0 0 1 1 numberleadingprefixdigits 0 numberleadingprefixdigitstostrip 0 calltype nationaltype digittype national set profiles digitparameterhandling prefixprofile CUST_PP entry 17 0 11 31 numberleadingprefixdigits 0 numberleadingprefixdigitstostrip 0 calltype nationaltype digittype national

SBC 5000 Series Configuration Guide 18 set profiles digitparameterhandling prefixprofile CUST_PP entry 18 0 11 31 numberleadingprefixdigits 0 numberleadingprefixdigitstostrip 1 calltype nationaltype digittype tollfree determinearea enable set profiles digitparameterhandling prefixprofile CUST_PP entry 9 0 1 3 numberleadingprefixdigits 0 numberleadingprefixdigitstostrip 0 calltype nationaltype digittype national set profiles digitparameterhandling prefixprofile CUST_PP entry + 0 1 31 numberleadingprefixdigits 1 numberleadingprefixdigitstostrip 1 calltype internationaltype digittype international dmpmrule SIP_REMOVE_PLUS1 natureofaddress international applydmrule enable set profiles digitparameterhandling prefixprofile CUST_PP entry 19 0 11 31 numberleadingprefixdigits 1 numberleadingprefixdigitstostrip 1 calltype nationaltype digittype national set profiles digitparameterhandling prefixprofile CUST_PP entry 011 0 2 31 numberleadingprefixdigits 3 numberleadingprefixdigitstostrip 3 calltype internationaltype digittype international The output of show command for prefix profile is as given below: admin@custsbc% show profiles digitparameterhandling prefixprofile CUST_PP entry 0 0 1 1 entry 0 0 1 1 { calltype nationaltype; digittype national; dmpmrule ""; natureofaddress numberingplanindicator numberleadingprefixdigits 0; numberleadingprefixdigitstostrip 0; applydmrule determinearea admin@custsbc% show profiles digitparameterhandling prefixprofile CUST_PP entry 17 0 11 31 entry 17 0 11 31 { calltype nationaltype; digittype national; dmpmrule ""; natureofaddress numberingplanindicator numberleadingprefixdigits 0; numberleadingprefixdigitstostrip 0; applydmrule determinearea

SBC 5000 Series Configuration Guide 19 admin@custsbc% show profiles digitparameterhandling prefixprofile CUST_PP entry 18 0 11 31 entry 18 0 11 31 { calltype nationaltype; digittype tollfree; dmpmrule ""; natureofaddress numberingplanindicator numberleadingprefixdigits 0; numberleadingprefixdigitstostrip 1; applydmrule determinearea enable; admin@custsbc% show profiles digitparameterhandling prefixprofile CUST_PP entry 9 0 1 3 entry 9 0 1 3 { calltype nationaltype; digittype national; dmpmrule ; natureofaddress numberingplanindicator numberleadingprefixdigits 0; numberleadingprefixdigitstostrip 0; applydmrule determinearea admin@custsbc% show profiles digitparameterhandling prefixprofile CUST_PP entry + 0 1 31 entry + 0 1 31 { calltype internationaltype; digittype international; dmpmrule SIP_REMOVE_PLUS1; natureofaddress international; numberingplanindicator numberleadingprefixdigits 1; numberleadingprefixdigitstostrip 1; applydmrule enable; determinearea admin@custsbc% show profiles digitparameterhandling prefixprofile CUST_PP entry 19 0 11 31 entry 19 0 11 31 { calltype nationaltype;

SBC 5000 Series Configuration Guide 20 digittype national; dmpmrule ; natureofaddress numberingplanindicator numberleadingprefixdigits 1; numberleadingprefixdigitstostrip 1; applydmrule determinearea admin@custsbc% show profiles digitparameterhandling prefixprofile CUST_PP entry 011 0 2 31 entry 011 0 2 31 { calltype internationaltype; digittype international; dmpmrule ""; natureofaddress numberingplanindicator numberleadingprefixdigits 3; numberleadingprefixdigitstostrip 3; applydmrule determinearea 4) Numbering Plan Create Numbering Plan by applying Prefix Profile created for customer side. Parameter CUST_NUM_PLAN Description Numbering Plan name on Customer side. set profiles digitparameterhandling numberingplan CUST_NUM_PLAN prefixprofile CUST_PP set profiles digitparameterhandling numberingplan CUST_NUM_PLAN prefixprofile CUST_PP lengths nationalnumber min 0 max 0 set profiles digitparameterhandling numberingplan CUST_NUM_PLAN prefixprofile CUST_PP lengths subscribernumber min 0 max 0 set profiles digitparameterhandling numberingplan CUST_NUM_PLAN prefixprofile CUST_PP lengths line min 0 max 0 set profiles digitparameterhandling numberingplan CUST_NUM_PLAN prefixprofile CUST_PP lengths exchangecode min 0 max 0 set profiles digitparameterhandling numberingplan CUST_NUM_PLAN prefixprofile CUST_PP lengths areacode min 0 max 0

SBC 5000 Series Configuration Guide 21 The output of show command for numbering plan is as given below: admin@custsbc% show profiles digitparameterhandling numberingplan CUST_NUM_PLAN prefixprofile CUST_PP; lengths { nationalnumber { min 0; max 0; subscribernumber { line { min 0; max 0; min 0; max 0; exchangecode { min 0; max 0; areacode { min 0; max 0; 5) DM/PM Rule Create DM/PM (digit/parameter manipulation) rule and apply it to ingressdmpmrule on sip trunk group towards IP-PBX side. The purpose of this DM/PM rule is to convert 4-digit Subscriber Number received in Diversion header into 10-digit TN by prefixing with NPA- NXX. This configuration will change based on the customer s DDI range assigned by AT&T. This must be AT&T IPFR recognizable TN. The below example shows the conversion of 978-303-XXXX TNs, where subscriber numbers (XXXX) are getting prefixed with 978-303 (NPA-NXX). set profiles digitparameterhandling dmpmcriteria RDN_Exists criteriatype digit digittype redirecting parameterpresencecheck exists set profiles digitparameterhandling dmpmrule RDN_Change subrule 0 criteria RDN_Exists ruletype digit digitmanipulation numbertype originalcallednumber digitstringmanipulation replacement type constant digitstring callingnumber numberofdigits 10 value 978303

SBC 5000 Series Configuration Guide 22 The output of show command for zone is as given below: admin@custsbc% show profiles digitparameterhandling dmpmrule RDN_Change subrule 0 { criteria RDN_Exists; ruletype digit; digitmanipulation { numbertype originalcallednumber; numberparametermanipulation { natureofaddress numberingplanindicator numberlength noinput; presentation screening includeinegress digitstringmanipulation { startdigitposition 0; numberofdigits 0; replacement { type constant; digitstring callingnumber; startdigitposition 0; numberofdigits 10; value 978303; action 6) Sip Adaptor Profiles The following SMM is applied on outputadaptorprofile of siptrunk associated to customer network.

SBC 5000 Series Configuration Guide 23 IP-PBX SBX Internal Interface siptrunk: CUST_TG PSP: 18, 0 SBX External Interface siptrunk: ATT_TG PSP: 18, 0 AT&T SIP Interface AT&T RMV-PCMU-UPDATE-DTMF Applied as Output Adaptor Profile (2) SIP: Requests/Reponse mline: 18 0 100 mline: 18 100 aline: PCMU/8000 (1) SIP: Request/Response mline: 18 0 100 aline: PCMU/8000 Rule 1 (1) SIP: Request/Response Mline: 18 (2) SIP: New Request/Response mline: 18 100 aline: telephone-event/8000 aline: fmtp:100 0-15 OR Rule 2 (1) SIP: Request/Response Mline: 0 (2) SIP: New Request/Response mline: 0 100 aline: telephone-event/8000 aline: fmtp:100 0-15 Rule 1: Removes PCMU codec from SDP for all incomng request from ATT Rule 2: Includes DTMF payload type 100 in response if not available in request SDP from IP- PBX Parameter RMV-PCMU-UPDATE-DTMF Description SMM rule for outputadaptor profile of siptrunk to CUST side set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 criterion 1 type message set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 criterion 1 message messagetypes all methodtypes invite set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 criterion 2 type messagebody set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 criterion 2 messagebody condition regexmatch

SBC 5000 Series Configuration Guide 24 set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 criterion 2 messagebody regexp string "(18\s0)" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 action 1 type messagebody operation regsub from type "value" value "18 100" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 action 1 from type "value" value "18 100" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 action 1 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 action 1 regexp string "(18\s0\s100)" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 action 2 type messagebody operation regdel set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 action 2 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 1 action 2 regexp string "a=rtpmap:0 PCMU/8000\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 criterion 1 type message set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 criterion 1 message messagetypes all methodtypes "invite ack" statuscode 200 set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 action 1 type messagebody operation regsub from type "value" value " 18 100\\r\\na=rtpmap:100 telephone-event/8000\\r\\na=fmtp:100 0-15\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 action 1 from type "value" value " 18 100\\r\\na=rtpmap:100 telephone-event/8000\r\na=fmtp:100 0-15\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 action 1 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 action 1 regexp string " 18\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 action 2 type messagebody operation regsub from type value value "AVP 0 100\\r\\na=rtpmap:100 telephone-event/8000\\r\\na=fmtp:100 0-15\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 action 2 from type value value "AVP 0 100\\r\\na=rtpmap:100 telephone-event/8000\\r\\na=fmtp:100 0-15\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 action 2 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF rule 2 action 2 regexp string "AVP 0\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-UPDATE-DTMF state enabled The output of show command for numbering plan is as given below

SBC 5000 Series Configuration Guide 25 admin@custsbc% show profiles signaling sipadaptorprofile RMV-PCMU- UPDATE-DTMF state enabled; rule 1 { criterion 1 { type message; message { messagetypes all; methodtypes invite; criterion 2 { type messagebody; messagebody { condition regex-match; regexp { string "(18\s0)"; action 1 { type messagebody; operation regsub; from { type value; value "18 100"; to { type messagebody; messagebodyvalue all; regexp { string "(18\s0\s100)"; matchinstance one; action 2 { type messagebody; operation regdel; to { type messagebody; messagebodyvalue all; regexp { string "a=rtpmap:0 PCMU/8000\\r\\n"; matchinstance one;

SBC 5000 Series Configuration Guide 26 rule 2 { applymatchheader one; applymatchhdrrange undefined; criterion 1 { type message; message { messagetypes all; methodtypes invite,ack; statuscode 200; statusrange 0; action 1 { type messagebody; operation regsub; from { type value; value " 18 100\\r\\na=rtpmap:100 telephoneevent/8000\\r\\na=fmtp:100 0-15\\r\\n"; to { type messagebody; messagebodyvalue all; regexp { string " 18\\r\\n"; matchinstance one; action 2 { type messagebody; operation regsub; from { type value; value "AVP 0 100\\r\\na=rtpmap:100 telephoneevent/8000\\r\\na=fmtp:100 0-15\\r\\n"; to { type messagebody; messagebodyvalue all; regexp { string "AVP 0\\r\\n"; matchinstance one;

SBC 5000 Series Configuration Guide 27 2.5.2. Configuring Address Context Configure address context correspond to a specific IP Addressing domain. It includes configuration of following entities on customer side: 1. IP Interface Group 2. Static route 3. Zone 4. SIP Signaling Port 5. IP Peer 6. SIP Trunkgroup 1) IP Interface Group Create IP Interface Group on customer side and assign IP interface to the same. Also, assign media ip/prefix of SBC to be used on customer side to this IP interface. Parameter CUSTIFG IPDOMAIN PKT1_V4 pkt1 Description Media interface group name for customer Address context name for customer domain Media interface name for customer Gigabit Ethernet port used for signaling and media traffic towards customer 172.16.104.164 Media IP address of SBC towards customer 24 IP subnet prefix of media interface set addresscontext IPDOMAIN ipinterfacegroup CUSTIFG set addresscontext IPDOMAIN ipinterfacegroup CUSTIFG ipinterface PKT1_V4 set addresscontext IPDOMAIN ipinterfacegroup CUSTIFG ipinterface PKT1_V4 cename CUSTSBC set addresscontext IPDOMAIN ipinterfacegroup CUSTIFG ipinterface PKT1_V4 portname pkt1 set addresscontext IPDOMAIN ipinterfacegroup CUSTIFG ipinterface PKT1_V4 ipaddress 172.16.104.164 prefix 24 set addresscontext IPDOMAIN ipinterfacegroup CUSTIFG ipinterface PKT1_V4 mode inservice state enabled The output of show command for ip interface group is as given below:

SBC 5000 Series Configuration Guide 28 admin@custsbc% show addresscontext IPDOMAIN ipinterfacegroup CUSTIFG ipinterface PKT1_V4 { cename CUSTSBC; portname pkt1; ipaddress 172.16.104.164; prefix 24; mode inservice; state enabled; 2) Static route Create a Static route for the IP-PBX on Customer side. A static route indicates the nexthop gateway and IP interface that is used for a particular peer network IP prefix. Parameter Description 172.16.102.24 IP address of PBX on customer side 32 IP subnet prefix 172.16.104.1 Gateway IP set addresscontext IPDOMAIN staticroute 172.16.102.24 32 172.16.104.1 CUSTIFG PKT1_V4 preference 100 The output of show command for static route is as given below: admin@custsbc% show addesscontext IPDOMAIN staticroute staticroute 172.16.102.24 32 172.16.104.1 CUSTIFG PKT1_V4 { preference 100; 3) Zone Create Zone for customer domain and specify the id of the zone. Parameter CUST_ZONE Description Customer zone name set addresscontext IPDOMAIN zone CUST_ZONE id 2

SBC 5000 Series Configuration Guide 29 The output of show command for zone is as given below: admin@custsbc% show addresscontext IPDOMAIN zone CUST_ZONE id 2; 4) SIP Signaling Port Create Sip Signalling Port with signaling ip/prefix of SBC to be used on customer side and assign it to IP interface group. Parameter Description 172.16.104.164 SIP signalling IP address of SBC towards customer 5060 SIP signalling port of SBC towards customer set addresscontext IPDOMAIN zone CUST_ZONE sipsigport 1 ipinterfacegroupname CUSTIFG ipaddressv4 172.16.104.164 portnumber 5060 set addresscontext IPDOMAIN zone CUST_ZONE sipsigport 1 ipinterfacegroupname CUSTIFG transportprotocolsallowed sip-udp,sip-tcp set addresscontext IPDOMAIN zone CUST_ZONE sipsigport 1 mode inservice state enabled The output of show command for sip signaling port is as given below: admin@custsbc% show addresscontext IPDOMAIN zone CUST_ZONE sipsigport 1 ipinterfacegroupname CUSTIFG; ipaddressv4 172.16.104.164; portnumber 5060; mode inservice; state enabled; transportprotocolsallowed sip-udp,sip-tcp; 5) IP Peer Create an IP Peer with signaling IP address of customer IP-PBX and assign it to customer zone. Parameter CUST_IPP Description IP Peer name for customer IP-PBX set addresscontext IPDOMAIN zone CUST_ZONE ippeer CUST_IPP ipaddress 172.16.102.24 ipport 5060

SBC 5000 Series Configuration Guide 30 The output of show command for ip peer is as given below: admin@custsbc% show addresscontext IPDOMAIN zone CUST_ZONE ippeer CUST_IPP ippeer CUST_IPP { ipaddress 172.16.102.24; ipport 5060; policy { description ; sip { fqdn ; fqdnport 0; packetserviceprofile ; ipsignalingprofile ; 6) SIP Trunk Group Create SIP Trunk Group towards customer IP-PBX and assign corresponding profiles on the same. Parameter CUST_TG Description SIP Trunk towards Customer IP-PBX set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG media maxptimedefault 30 mediaipinterfacegroupname CUSTIFG sourceaddressfiltering disabled set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG signaling relaynoninviterequest enabled set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG ingressipprefix 172.16.102.24 32 set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG policy media packetserviceprofile CUST_PSP set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG policy signaling ipsignalingprofile CUST_IPSP set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG policy digitparameterhandling numberingplan CUST_NUM_PLAN set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG policy digitparameterhandling ingressdmpmrule RDN_Change set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG signaling messagemanipulation outputadapterprofile RMV-PCMU-UPDATE-DTMF set addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG state enabled mode inservice

SBC 5000 Series Configuration Guide 31 The output of show command for sip trunkgroup is as given below: admin@custsbc% show addresscontext IPDOMAIN zone CUST_ZONE siptrunkgroup CUST_TG state enabled; mode inservice; policy { carrier 0000; country 1; sipdomain ; localizationvariant northamerica; digitparameterhandling { numberingplan CUST_NUM_PLAN; ingressdmpmrule RDN_Change; egressdmpmrule ; callrouting { elementroutingpriority DEFAULT_IP; media { packetserviceprofile CUST_PSP; toneandanncouncementprofile ; services { classofservice DEFAULT_IP; signaling { ipsignalingprofile CUST_IPSP; signalingprofile ; signaling { timers { sessionkeepalive 0; sessionminse 0; messagemanipulation { outputadapterprofile RMV-PCMU-UPDATE-DTMF; relaynoninviterequest enabled; media { maxptimedefault 30;

SBC 5000 Series Configuration Guide 32 mediaipinterfacegroupname CUSTIFG; sourceaddressfiltering disabled; ingressipprefix 172.16.102.24 32; 2.6. ATT Side Configuration 2.6.1. Configuring Profiles Create profiles with specific set of characteristics correspond to ATT network. It includes configuration of following entities on ATT side. 1. Packet Service Profile 2. IP Signaling Profile 3. Prefix profile 4. Numbering Plan 5. DM/PM Rule 6. SIP Adaptor Profiles 1) Packet Service Profile Create Packet Service Profile towards ATT side with G729A as a first codec and G711ulaw as a second codec Parameter ATT_PSP Description Packet Service Profile name towards ATT side with rtcp enabled and preferred rtp payload for dtmf 100 set profiles media packetserviceprofile ATT_PSP codec codecentry1 G729A_T38_2833 codecentry2 G711Ulaw_T38_2833 set profiles media packetserviceprofile ATT_PSP t38 lowspeednumberofredundantpackets 0 numberofredundantpackets 0 set profiles media packetserviceprofile ATT_PSP rtcpoptions rtcp enable set profiles media packetserviceprofile ATT_PSP preferredrtppayloadtypefordtmfrelay 100 honorremoteprecedence enable The output of show command for packet service profile is as given below: admin@custsbc% show profiles media packetserviceprofile ATT_PSP datacalls { preferredrtpdatapayloadtype 56; initialplayoutbufferdelay 50;

SBC 5000 Series Configuration Guide 33 packetsize 0; silencefactor 40; typeofservice 0; voiceinitialplayoutbufferdelay 10; rtcpoptions { rtcp enable; terminationforpassthrough packetlossthreshold 0; packetlossaction peerabsenceaction silenceinsertiondescriptor { g711sidrtppayloadtype 13; heartbeat enable; aal1payloadsize 47; codec { codecentry1 G729a_T38_2833; codecentry2 G711Ulaw_T38_2833; codecentry3 ; codecentry4 ; packettopacketcontrol { transcode conditional; conditionsinadditiontonocommoncodec { differentdtmfrelay differentpacketsize differentsilencesuppression honorofferpreference codecsallowedfortranscoding { thisleg ; otherleg ; flags { disallowdatacalls digitdetectsendenabled usedirectmedia validatepeersupportfordtmfevents t38 { dataratemanagementtype type2transferoftcf; ecm { ecmpreferred

SBC 5000 Series Configuration Guide 34 lowspeednumberofredundantpackets 0; maxbitrate 14.4Kbits_s; numberofredundantpackets 0; securertprtcp { cryptosuiteprofile ; flags { allowfallback enablesrtp preferredrtppayloadtypefordtmfrelay 100; videocalls { maxvideobandwith 0; videobandwidthreductionfactor 0; audioonlyifvideoisprevented enable; mediapacketcos 0; honorremoteprecedence enable; sendroutepspprecedence 2) IP Signaling Profile Create IP Signaling Profile with appropriate signaling flags towards ATT side Parameter ATT_IPSP Description IP Signalling Profile name on ATT side. set profiles signaling ipsignalingprofile ATT_IPSP set profiles signaling ipsignalingprofile ATT_IPSP commonipattributes flags minimizerelayingofmediachangesfromothercalllegall enable sendallallowedcodecsforlatemediainviteorreinvite enable sendptimeinsdp enable set profiles signaling ipsignalingprofile ATT_IPSP egressipattributes flags disable2806compliance enable set profiles signaling ipsignalingprofile ATT_IPSP egressipattributes privacy privacyinformation passertedid set profiles signaling ipsignalingprofile ATT_IPSP ingressipattributes flags sendsdpin200okif18xreliable enable sendsdpinsubsequent18x enable The output of show command for ip signaling profile is as given below: admin@custsbc% show profiles signaling ipsignalingprofile ATT_IPSP ipprotocoltype siponly; commonipattributes { flags {

SBC 5000 Series Configuration Guide 35 addpathserviceroute callholdinterworking clearmodefordatacalls createpchargingvector createpathheader createservicerouteheader customizedsessiontimerbehavior disablealsoheader disablehosttranslation disablemedialockdown disablerefertouriparameters discardreceivedreasonheader donotincludessattributeinreinvite endtoendbye includeipportsinfromandtoheaders includereasonheader includessattributeininitialinvite includetransporttypeincontactheader insertpeeraddressastoprouteheader mapcauselocation mapsuspendresumeeventinpsvcinfoheader mapuuiinpsiginfoheader mimecauseprecedereasonheadercause minimizerelayingofmediachangesfromothercalllegall enable; nocontentdisposition noportnumber5060 enable; nouserinfoincontactheader onlyselectedcodecinsessionrefresh pchgmsginfo replacehostonviaheader requerypsxonregisterrefresh sdpolineonlycompares sendallallowedcodecsforlatemediainviteorreinvite enable; senddirectmediainfoinsdpattribute sendptimeinsdp enable; sessiontimerrefreshupdate setacceptheadertoapplicationsdponly setolinedash setsessionversionzero setslinedash skippsxqueryforrefer storepathheader storeservicerouteheader terminalportabilityinterworking sendrtcpportinsdp calltransferflags {

SBC 5000 Series Configuration Guide 36 handleipaddressesnotpresentinnetworkselectortablenst routeviatransferringiptg; forcererouteviapsxquery optiontaginrequireheader { suppressreplacetag optiontaginsupportedheader { suppressreplacetag relayflags { dialogeventpackage dtmfbody info message notify options regeventpackage refer sonusmediabody statuscode3xx statuscode4xx6xx thirdpartybodies force503to500relay transparencyflags { alertinformationheader authcodeheaders contactheader errorinfo fromheader historyinfo maxforwardsheader mwibody pchargingvectorheader pearlymedia pathheader qsigbody reasonheader referredbyheader requesturi routeheader servicerouteheader sipbody sipfragbody toheader tonebody

SBC 5000 Series Configuration Guide 37 unknownbody unknownheader viaheader egressipattributes { numberglobalizationprofile ; flags { bgcftargetschemetransparency convertinactivetosendrecv disable2806compliance enable; disableoptionalregisterparameters map181or182messageto183 mapcontractornumberinpsiginfoheader suppressunregister ttcisupmapping usecalledpartyinrequesturi usecoloninsdpmediatypeparameter validateisubaddress bci { bciinterworkencountered bciisdnaddess domainname { usesipdomainnameinfromfield usesipdomainnameinrequesturi isub { allownsapisub allowuserspecifiedisub includecalledpartyisub includecallingpartyisub numberportabilityattributes { npdioptions includenpdiyes; disablern privacy { transparency privacyinformation passertedid; flags { includeprivacy enable; privacyrequiredbyproxy mslyncprivacysupport

SBC 5000 Series Configuration Guide 38 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 transport { type1 type2 type3 type4 ingressipattributes { flags { sip181supported sip182supported mapcalledpartycategoryinpsiginfoheader nosdpin180supported registrationexpiresinexpiresheader send183oninitiatingdisconnecttreatment sendsdpin200okif18xreliable enable; sendsdpinsubsequent18x enable; carrierinformation {

SBC 5000 Series Configuration Guide 39 generateterminatingca generateterminatingcic 3) Prefix Profile Create Prefix Profile with appropriate dial plan for handling incoming calls from ATT network. Parameter ATT_PP Description Prefix Profile name on ATT side. set profiles digitparameterhandling prefixprofile ATT_PP entry 7 0 10 31 numberleadingprefixdigits 0 numberleadingprefixdigitstostrip 0 calltype nationaltype digittype national determinearea enable set profiles digitparameterhandling prefixprofile ATT_PP entry 9 0 10 31 numberleadingprefixdigits 0 numberleadingprefixdigitstostrip 0 calltype nationaltype digittype national determinearea enable The output of show command for prefix profile is as given below: admin@custsbc% show profiles digitparameterhandling prefixprofile ATT_PP entry 7 0 10 31 entry 7 0 10 31 { calltype nationaltype; digittype national; dmpmrule ""; natureofaddress numberingplanindicator numberleadingprefixdigits 0; numberleadingprefixdigitstostrip 0; applydmrule determinearea enable; admin@custsbc% show profiles digitparameterhandling prefixprofile ATT_PP entry 9 0 10 31 entry 9 0 10 31 { calltype nationaltype; digittype national; dmpmrule ""; natureofaddress numberingplanindicator numberleadingprefixdigits 0; numberleadingprefixdigitstostrip 0; applydmrule

SBC 5000 Series Configuration Guide 40 determinearea enable; 4) Numbering Plan Create Numbering Plan by applying Prefix Profile created for ATT side. Parameter ATT_NUM_PLAN Description Numbering Plan name on ATT side. set profiles digitparameterhandling numberingplan ATT_NUM_PLAN prefixprofile ATT_PP set profiles digitparameterhandling numberingplan ATT_NUM_PLAN prefixprofile ATT_PP lengths nationalnumber min 0 max 0 set profiles digitparameterhandling numberingplan ATT_NUM_PLAN prefixprofile ATT_PP lengths subscribernumber min 0 max 0 set profiles digitparameterhandling numberingplan ATT_NUM_PLAN prefixprofile ATT_PP lengths line min 0 max 0 set profiles digitparameterhandling numberingplan ATT_NUM_PLAN prefixprofile ATT_PP lengths exchangecode min 0 max 0 set profiles digitparameterhandling numberingplan ATT_NUM_PLAN prefixprofile ATT_PP lengths areacode min 0 max 0 The output of show command for numbering plan is as given below: admin@custsbc% show profiles digitparameterhandling numberingplan ATT_NUM_PLAN prefixprofile ATT_PP; lengths { nationalnumber { min 0; max 0; subscribernumber { line { min 0; max 0; min 0; max 0; exchangecode {

SBC 5000 Series Configuration Guide 41 min 0; max 0; areacode { min 0; max 0; 5) DM/ PM Rule (for International calls from US) Create DM/PM (digit manipulation/parameter manipulation) rule and apply it to egressdmpmrule on sip trunk group towards ATT side. The purpose of the DM/PM rule is to add a prefix of 011 to all the outgoing international calls dialed from US. An example for this configuration is as shown below. set profiles digitparameterhandling dmpmrule Add011 subrule 0 criteria SIP_MATCH_INTL_CD ruletype digit digitmanipulation digitstringmanipulation replacement type constant value 011 digitstring callednumber startdigitposition 0 numberofdigits 0 set profiles digitparameterhandling dmpmrule Add011 subrule 0 digitmanipulation numbertype callednumber The output of show command for DM/PM rule is as given below: admin@custsbc% show profiles digitparameterhandling dmpmrule Add011 subrule 0 { criteria SIP_MATCH_INTL_CD; ruletype digit; digitmanipulation { numbertype callednumber; numberparametermanipulation { natureofaddress numberingplanindicator numberlength noinput; presentation screening includeinegress digitstringmanipulation { startdigitposition 0; numberofdigits 0; replacement { type constant; digitstring callednumber;

SBC 5000 Series Configuration Guide 42 startdigitposition 0; numberofdigits 0; value 011; action admin@custsbc% show profiles digitparameterhandling dmpmcriteria SIP_MATCH_INTL_CD criteriatype digit; digittype callednumber; parameterpresencecheck exists; digitcriteria { egressflag { value send; operation ignore; digitmatch { value { startdigitposition 0; numberofdigits 0; matchvalue 0; operation ignore; natureofaddress { value international; operation equals; numberingplanindicator { value data; operation ignore; numberlength { value 0; operation ignore; presentationmatch { value operation ignore; screeningmatch { value operation ignore;

SBC 5000 Series Configuration Guide 43 6) SIP Adaptor Profile Create SIP Adaptor Profile with appropriate cirteria/rules for manipulation of messages traversing from Core side. i. RMV-PCMU-FROM-RESPONSE The following SMM is applied on inputadaptorprofile of siptrunk associated to ATT network. Customer side PBX SBX Internal Interface siptrunk: CUST_TG PSP: 18, 0 SBX External Interface siptrunk: ATT_TG PSP: 18, 0 AT&T SIP Interface AT&T RMV-PCMU-FROM-RESPONSE Applied as Input Adaptor Profile (2) SIP: 180/183/200 mline: 117 18 0 100 mline: 18 100 aline: PCMU/8000 (1) SIP: 180/183/200 mline: 117 18 0 100 aline: PCMU/8000 Rule 1 (2) SIP: INVITE mline: 117 18 0 100 mline: 18 100 aline: PCMU/8000 (1) SIP: INVITE mline: 117 18 0 100 aline: PCMU/8000 Rule 2 Rule 1: Removes PCMU payload type for SIP Responses: 180,183,200 Rule 2: Removes PCMU payload type for SIP INVITE method Parameter RMV-PCMU-FROM-RESPONSE Description SMM rule for inputadaptor profile of siptrunk to ATT side set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 criterion 1 type message

SBC 5000 Series Configuration Guide 44 set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 criterion 1 message messagetypes responseall set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 criterion 2 type messagebody set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 criterion 2 messagebody condition regexmatch set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 criterion 2 messagebody regexp string "(18\s0)" set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 action 1 type messagebody operation "regsub" from type value value 18 set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 action 1 from type value value 18 set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 action 1 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 action 1 regexp string "18 0" set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 action 2 type messagebody operation regdel set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 action 2 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 1 action 2 regexp string "a=rtpmap:0 PCMU/8000\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 criterion 1 type message set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 criterion 1 message messagetypes requestall set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 criterion 2 type messagebody set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 criterion 2 messagebody condition regexmatch set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 criterion 2 messagebody regexp string "(18\s0)" set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 action 1 type messagebody operation regsub from type value value 18 set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 action 1 from type value value 18 set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 action 1 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 action 1 regexp string "18 0"

SBC 5000 Series Configuration Guide 45 set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 action 2 type messagebody operation regdel set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 action 2 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE rule 2 action 2 regexp string "a=rtpmap:0 PCMU/8000\\r\\n" set profiles signaling sipadaptorprofile RMV-PCMU-FROM-RESPONSE state enabled The output of show command for SMM Rule is as given below: admin@custsbc% show profiles signaling sipadaptorprofile RMV-PCMU-FROM- RESPONSE state enabled; rule 1 { criterion 1 { type message; message { messagetypes responseall; criterion 2 { type messagebody; messagebody { condition regex-match; regexp { string "(18\s0)"; action 1 { type messagebody; operation regsub; from { type value; value 18; to { type messagebody; messagebodyvalue all; regexp { string "18 0";

SBC 5000 Series Configuration Guide 46 action 2 { type messagebody; operation regdel; to { type messagebody; messagebodyvalue all; regexp { string "a=rtpmap:0 PCMU/8000\\r\\n"; rule 2 { criterion 1 { type message; message { messagetypes requestall; criterion 2 { type messagebody; messagebody { condition regex-match; regexp { string "(18\s0)"; action 1 { type messagebody; operation regsub; from { type value; value 18; to { type messagebody; messagebodyvalue all; regexp { string "18 0"; action 2 { type messagebody; operation regdel;

SBC 5000 Series Configuration Guide 47 to { type messagebody; messagebodyvalue all; regexp { string "a=rtpmap:0 PCMU/8000\\r\\n"; ii. UPDATE DTMF This SMM rule is applied for outputadaptorprofile of siptrunk associated to ATT side. Rule 1: Includes DTMF payload type 100 in request/response towards ATT if not available from IP-PBX. Also, if message from CUCM contains a=sendonly, it will be converted to a=sendrcv towards ATT Parameter UPDATE-DTMF Description SMM rule for OutputAdaptor profile of siptrunk to ATT side set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 criterion 1 type message set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 criterion 1 message messagetypes all methodtypes invite,ack statuscode 200 set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 1 type messagebody operation regsub from type value value "18 100\\r\\na=rtpmap:100 telephone-event/8000\\r\\na=fmtp:100 0-15\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 1 from type value value "18 100\\r\\na=rtpmap:100 telephone-event/8000\r\na=fmtp:100 0-15\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 1 to type messagebody messagebodyvalue all

SBC 5000 Series Configuration Guide 48 set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 1 regexp string " 18\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 2 type messagebody operation regsub from type value value "AVP 0 100\\r\\na=rtpmap:100 telephone-event/8000\\r\\na=fmtp:100 0-15\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 2 from type value value "AVP 0 100\\r\\na=rtpmap:100 telephone-event/8000\\r\\na=fmtp:100 0-15\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 2 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 2 regexp string "AVP 0\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 3 type messagebody operation regsub from type value value "a=sendrecv\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 3 from type value value "a=sendrecv\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 3 to type messagebody messagebodyvalue all set profiles signaling sipadaptorprofile UPDATE-DTMF rule 1 action 3 regexp string "a=sendonly\\r\\n" set profiles signaling sipadaptorprofile UPDATE-DTMF state enabled The output of show command for SMM Rule is as given below: admin@custsbc% show profiles signaling sipadaptorprofile UPDATE-DTMF state enabled; rule 1 { criterion 1 { type message; message { messagetypes all; methodtypes invite,ack; statuscode 200; action 1 { type messagebody; operation regsub; from { type value; value " 18 100\\r\\na=rtpmap:100 telephoneevent/8000\r\na=fmtp:100 0-15\\r\\n"; to { type messagebody; messagebodyvalue all; regexp { string " 18\\r\\n";

SBC 5000 Series Configuration Guide 49 action 2 { type messagebody; operation regsub; from { type value; value "AVP 0 100\\r\\na=rtpmap:100 telephoneevent/8000\\r\\na=fmtp:100 0-15\\r\\n"; to { type messagebody; messagebodyvalue all; regexp { string "AVP 0\\r\\n"; action 3 { type messagebody; operation regsub; from { type value; value "a=sendrecv\\r\\n"; to { type messagebody; messagebodyvalue all; regexp { string "a=sendonly\\r\\n"; 2.6.2. Configuring Address Context Configure address context correspond to a specific IP Addressing domain. It includes configuration of following entities on customer side: 1. IP Interface Group 2. Static route 3. Zone 4. SIP Signaling Port 5. IP Peer 6. SIP Trunkgroup

SBC 5000 Series Configuration Guide 50 1) IP Interface Group Create IP Interface Group on ATT side and assign IP interface to the same. Also, assign media ip/prefix to be used on ATT side to this IP interface. Parameter ATTIFG PKT2_V4 pkt2 Description Media interface group name for ATT network Media interface name for ATT network Gigabit Ethernet port used for signaling and media traffic towards ATT network 32.252.34.18 Media IP address of SBC towards ATT 29 IP subnet prefix of media interface set addresscontext IPDOMAIN ipinterfacegroup ATTIFG set addresscontext IPDOMAIN ipinterfacegroup ATTIFG ipinterface PKT2_V4 set addresscontext IPDOMAIN ipinterfacegroup ATTIFG ipinterface PKT2_V4 cename CUSTSBC set addresscontext IPDOMAIN ipinterfacegroup ATTIFG ipinterface PKT2_V4 portname pkt2 set addresscontext IPDOMAIN ipinterfacegroup ATTIFG ipinterface PKT2_V4 ipaddress 32.252.34.18 prefix 29 set addresscontext IPDOMAIN ipinterfacegroup ATTIFG ipinterface PKT2_V4 mode inservice state enabled The output of show command for ip interface group is as given below: admin@custsbc% show addresscontext IPDOMAIN ipinterfacegroup ATTIFG ipinterface PKT2_V4 { cename CUSTSBC; portname pkt2; ipaddress 32.252.34.18; prefix 29; mode inservice; state enabled; 2) Static route Create a Static route for the ATT network. A static route indicates the nexthop gateway and IP interface that is used for a particular peer network IP prefix. Parameter Description 12.194.18.75 Primary IP address of ATT network.

SBC 5000 Series Configuration Guide 51 12.194.20.75 Secondary IP address of ATT network. 32 IP subnet prefix 32.252.34.17 Gateway IP set addresscontext IPDOMAIN staticroute 12.194.18.75 32 32.252.34.17 ATTIFG PKT2_V4 preference 100 set addresscontext IPDOMAIN staticroute 12.194.20.75 32 32.252.34.17 ATTIFG PKT2_V4 preference 100 The output of show command for static route is as given below: admin@custsbc% show addesscontext IPDOMAIN staticroute staticroute 12.194.18.75 32 32.252.34.17 ATTIFG PKT2_V4 { preference 100; staticroute 12.194.20.75 32 32.252.34.17 ATTIFG PKT2_V4 { preference 100; 3) Zone Create Zone for ATT domain and specify the id of the zone. Parameter ATT_ZONE Description ATT zone name set addresscontext IPDOMAIN zone ATT_ZONE id 3 The output of show command for zone is as given below: admin@custsbc% show addresscontext IPDOMAIN zone ATT_ZONE id 3; 4) SIP Signaling Port Create Sip Signalling Port and specify the SIP signaling IP and Signaling port. Also, assign signaling ip/prefix to be used on ATT side to this IP interface.

SBC 5000 Series Configuration Guide 52 Parameter Description 32.252.34.18 SIP signalling IP address of SBC towards ATT 5060 SIP signalling port of SBC towards ATT set addresscontext IPDOMAIN zone ATT_ZONE sipsigport 2 ipinterfacegroupname ATTIFG ipaddressv4 32.252.34.18 portnumber 5060 set addresscontext IPDOMAIN zone ATT_ZONE sipsigport 2 ipinterfacegroupname ATTIFG transportprotocolsallowed sip-udp,sip-tcp set addresscontext IPDOMAIN zone ATT_ZONE sipsigport 2 mode inservice state enabled The output of show command for sip signaling port is as given below: admin@custsbc% show addresscontext IPDOMAIN zone ATT_ZONE sipsigport 2 ipinterfacegroupname ATTIFG; ipaddressv4 32.252.34.18; portnumber 5060; mode inservice; state enabled; transportprotocolsallowed sip-udp,sip-tcp; 5) IP Peer Create an IP peer and specify the ATT IPBE (IP Border Element) IPs on ATT zone. Parameter ATT_IPP1 ATT_IPP2 Description Primary IP address of the ATT network Secondary IP address of the ATT network set addresscontext IPDOMAIN zone ATT_ZONE ippeer ATT_IPP1 ipaddress 12.194.20.75 ipport 5060 set addresscontext IPDOMAIN zone ATT_ZONE ippeer ATT_IPP2 ipaddress 12.194.18.75 ipport 5060 The output of show command for ip peer is as given below: admin@custsbc% show addresscontext IPDOMAIN zone ATT_ZONE ippeer ippeer ATT_IPP1 { ipaddress 12.194.20.75; ipport 5060; policy {

SBC 5000 Series Configuration Guide 53 description ""; sip { fqdn ""; fqdnport 0; packetserviceprofile ""; ipsignalingprofile ""; ippeer ATT_IPP2 { ipaddress 12.194.18.75; ipport 5060; policy { description ""; sip { fqdn ""; fqdnport 0; packetserviceprofile ""; ipsignalingprofile ""; 6) SIP Trunk Group Create SIP Trunk Group towards ATT network and assign corresponding profiles on the same. Parameter ATT_TG Description Sip Trunk towards ATT domain. set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG media maxptimedefault 30 mediaipinterfacegroupname ATTIFG sourceaddressfiltering disabled set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG signaling relaynoninviterequest enabled set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG ingressipprefix 12.194.20.75 32 set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG ingressipprefix 12.194.18.75 32 set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG policy media packetserviceprofile ATT_PSP set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG policy signaling ipsignalingprofile ATT_IPSP set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG policy digitparameterhandling numberingplan ATT_NUM_PLAN set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG policy digitparameterhandling egressdmpmrule Add011

SBC 5000 Series Configuration Guide 54 set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG signaling message Manipulation inputadaptorprofile RMV-PCMU-FROM-RESPONSE set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG signaling message Manipulation ouputadaptorprofile UPDATE-DTMF set addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG state enabled mode inservice The output of show command for sip trunkgroup is as given below: admin@custsbc% show addresscontext IPDOMAIN zone ATT_ZONE siptrunkgroup ATT_TG state enabled; mode inservice; policy { carrier 0000; country 1; sipdomain ; localizationvariant northamerica; digitparameterhandling { numberingplan ATT_NUM_PLAN; ingressdmpmrule ; egressdmpmrule Add011 ; callrouting { elementroutingpriority DEFAULT_IP; media { packetserviceprofile ATT_PSP; toneandanncouncementprofile ; services { classofservice DEFAULT_IP; signaling { ipsignalingprofile ATT_IPSP; signalingprofile ; signaling { messagemanipulation { inputadapterprofile RMV-PCMU-FROM-RESPONSE; outputadapterprofile UPDATE-DTMF;

SBC 5000 Series Configuration Guide 55 relaynoninviterequest enabled; media { maxptimedefault 30; mediaipinterfacegroupname ATTIFG; sourceaddressfiltering disabled; ingressipprefix 12.194.18.75 32; ingressipprefix 12.194.20.75 32; 2.7. Global Call Routing Configuration 2.7.1. Customer Side Routing Configure call routing to select customer trunkgroup when call characteristics matches. It includes configuration of following entities on customer side: 1) Routing Label Create Routing Label to bind customer trunkgroup with customer IP peer Parameter CUST_RL Description Routing Label name on Customer side. set global callrouting routinglabel CUST_RL routinglabelroute 1 trunkgroup CUST_TG ippeer CUST_IPP inservice inservice The output of show command for routing label is as given below: admin@custsbc% show global callrouting routinglabel CUST_RL overflownumber ; overflownoa overflownpi routeprioritizationtype sequence; script ; action routes; routinglabelroute 1 { trunkgroup CUST_TG; ippeer CUST_IPP; proportion 0; cost 1000000; inservice inservice; testing normal;

SBC 5000 Series Configuration Guide 56 2) Route Create Route to point to Customer routing label when call comes from ATT trunkgroup set global callrouting route trunkgroup ATT_TG CUSTSBC standard Sonus_NULL 1 all all ALL none Sonus_NULL routinglabel CUST_RL The output of show command for route is as given below: admin@custsbc% show global callrouting route route trunkgroup ATT_TG CUSTSBC standard Sonus_NULL 1 all all ALL none Sonus_NULL{ routinglabel CUST_RL 2.7.2. ATT Side Routing Configure call routing to select ATT trunkgroup when call characteristics matches. It includes configuration of following entities on ATT side: 1) Routing Label Create Routing Label to bind ATT trunkgroup with ATT IP peer. Parameter ATT_RL Description Routing Label name on ATT side. set global callrouting routinglabel ATT_RL routinglabelroute 1 trunkgroup ATT_TG ippeer ATT_IPP1 inservice inservice set global callrouting routinglabel ATT_RL routinglabelroute 2 trunkgroup ATT_TG ippeer ATT_IPP2 inservice inservice The output of show command for routing label is as given below: admin@custsbc% show global callrouting routinglabel ATT_RL routinglabel ATT_RL { overflownumber ""; overflownoa overflownpi routeprioritizationtype sequence; script ""; action routes; routinglabelroute 1 { trunkgroup ATT_TG; ippeer ATT_IPP1;

SBC 5000 Series Configuration Guide 57 proportion 0; cost 1000000; inservice inservice; testing normal; routinglabelroute 2 { trunkgroup ATT_TG; ippeer ATT_IPP2; proportion 0; cost 1000000; inservice inservice; testing normal; 2) Route Create Route to point to ATT routing label when call comes from Customer trunkgroup set global callrouting route trunkgroup CUST_TG CUSTSBC standard Sonus_NULL 1 all all ALL none Sonus_NULL routinglabel ATT_RL The output of show command for route is as given below: admin@custsbc% show global callrouting route route trunkgroup CUST_TG CUSTSBC standard Sonus_NULL 1 all all ALL none Sonus_NULL{ routinglabel ATT_RL Create Route to point to ATT routing label when customer dials Feature Access Codes. set profiles callrouting elementroutingpriority DEFAULT_IP entry username 2 entitytype trunkgroup set global callrouting route trunkgroup CUST_TG CUSTSBC username *72 Sonus_NULL all all ALL none Sonus_NULL routinglabel ATT_RL set global callrouting route trunkgroup CUST_TG CUSTSBC username *73 Sonus_NULL all all ALL none Sonus_NULL routinglabel ATT_RL set global callrouting route trunkgroup CUST_TG CUSTSBC username *90 Sonus_NULL all all ALL none Sonus_NULL routinglabel ATT_RL set global callrouting route trunkgroup CUST_TG CUSTSBC username *91 Sonus_NULL all all ALL none Sonus_NULL routinglabel ATT_RL set global callrouting route trunkgroup CUST_TG CUSTSBC username *92 Sonus_NULL all all ALL none Sonus_NULL routinglabel ATT_RL

SBC 5000 Series Configuration Guide 58 set global callrouting route trunkgroup CUST_TG CUSTSBC username *93 Sonus_NULL all all ALL none Sonus_NULL routinglabel ATT_RL set global callrouting route trunkgroup CUST_TG CUSTSBC username *94 Sonus_NULL all all ALL none Sonus_NULL routinglabel ATT_RL set global callrouting route trunkgroup CUST_TG CUSTSBC username *95 Sonus_NULL all all ALL none Sonus_NULL routinglabel ATT_RL The output of show command for route is as given below: admin@iotsbx3% show global callrouting route trunkgroup CUST_TG CUSTSBC username route trunkgroup CUST_TG CUSTSBC username *72 Sonus_NULL all all ALL none Sonus_NULL { routinglabel ATT_RL; route trunkgroup CUST_TG CUSTSBC username *73 Sonus_NULL all all ALL none Sonus_NULL { routinglabel ATT_RL; route trunkgroup CUST_TG CUSTSBC username *90 Sonus_NULL all all ALL none Sonus_NULL { routinglabel ATT_RL; route trunkgroup CUST_TG CUSTSBC username *91 Sonus_NULL all all ALL none Sonus_NULL { routinglabel ATT_RL; route trunkgroup CUST_TG CUSTSBC username *92 Sonus_NULL all all ALL none Sonus_NULL { routinglabel ATT_RL; route trunkgroup CUST_TG CUSTSBC username *93 Sonus_NULL all all ALL none Sonus_NULL { routinglabel ATT_RL; route trunkgroup CUST_TG CUSTSBC username *94 Sonus_NULL all all ALL none Sonus_NULL { routinglabel ATT_RL; route trunkgroup CUST_TG CUSTSBC username *95 Sonus_NULL all all ALL none Sonus_NULL { routinglabel ATT_RL;

SBC 5000 Series Configuration Guide 59 3. CUCM Configuration The CUCM 9.1 configuration which is used along with the Sonus SBC 5000 Series is as per the details provided in the Cisco Configuration Guide: AT&T IPFR-EF Service on MIS, MPLS PNT or AT&T VPN: Connecting Cisco Unified Communications Manager 9.1 with Cisco Unified Border Element Release using SIP. This guide is available online at the following location: http://www.cisco.com/en/us/solutions/collateral/ns340/ns414/ns728/ns833/1190421.pdf Following are the differences in the configuration as compared to those used in the CUCM 9.1 configuration guide provided above. In the above doc, in the CUCM Configuration, there are 3 Regions, whereas in this setup there shall be only one Default (G711) Region.

SBC 5000 Series Configuration Guide 60 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 SBC. 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 1-888-391-3434. 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