sbc 5000 series configuration guide - interactive...

SBC 5000 Series Configuration Guide (For Interactive Intelligence - Interaction Center 4.0)

For use with AT&T’s IP Flexible Reach – Enhanced Features Service on MIS, MPLS PNT or AT&T VPN

Configuration Guide

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. Enhanced IP Flexible Reach Features Limitations .......................................................... 4

1.1.3. IP Flex Reach Features Limitations ................................................................................. 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 ......................................................................................... 24

2.6. ATT Side Configuration ..................................................................................................... 29

2.6.1. Configuring Profiles ....................................................................................................... 29

2.6.2. Configuring Address Context ......................................................................................... 41

2.7. Global Call Routing Configuration ..................................................................................... 47

2.7.1. Customer Side Routing ................................................................................................. 47

2.7.2. ATT Side Routing .......................................................................................................... 48

3. Interaction Center (IC) Configuration .............................................................. 51

4. Troubleshooting .............................................................................................. 64

SBC 5000 Series Configuration Guide 4

Copyright © 2013, Sonus Networks, Inc. All rights reserved.


1. Introduction This document provides a configuration guide for Sonus SBC 5000 Series V04.X (Session Border Controller) with Interactive Intelligence - Interaction Center 4.0 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 Call Forwarding Always – Network Based Call Forwarding Busy – Network Based Call Forwarding Not Reachable – Network Based Call Forwarding No Answer – Network Based Blind Call Transfer – Network Based Consultative Call Transfer(Attended) – Network Based Account code – Network Based Authorization code

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 5000 is the point of connection between the Interaction Center 4.0 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 V04.X.

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 non-native 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. Enhanced IP Flexible Reach Features Limitations

Interaction Center does not support Network-Based Consultative transfer - Unattended (transfer when call is ringing and before the transfer-to party answers the call).

http://new.serviceguide.att.com/

http://new.serviceguide.att.com/




AT&T Network based Sequential ringing - The number of ring cycles must be configured as 2 rings on the AT&T user management portal. If not the IC times out internally and the feature will not work.

Network-based Call Forwarding features are activated/deactivated through the AT&T portal. Interaction Center does not support dialing * codes.

Interaction Center does not support calls with *code followed by Account code and PSTN number.

1.1.3. IP Flex Reach Features Limitations

Interaction Center does not support Meet-me conference feature.

Interaction Center does not support PBX based Call Forward Unconditional.

1.2. Network Topology

The figure above represents the equipment that was used for the IPFR-EF certification.

The IP Phones used with the Interaction Center PBX can be configured to work with SIP Protocol.

Sig: SIP Media: RTP

SIP Trunk

IC 4.0

SIP Trunk

Sig: SIP Media: RTP/T38


Local PSTN

SBC 5000 Series

AT&T


Cisco IAD

POTS

FAX




To know the hardware and software version details used for the above setup, see Section 1.3 - Hardware/ Software Configuration

1.3. Hardware/Software Configuration

Equipment Software

Sonus SBC 5000 Series

BMC

BIOS

OS

SonusDB

EMA

SBC

V02.04.01

V02.02.00

V02.00.03-R000

V04.00.01-R000

V04.00.01-R000

V04.00.01-R000

Third-party Equipment

Interaction Center

4.0.4




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 SBC 5000 Series

2. The CLI Output of the “show” commands for the configurations done using Step 1.

2.1. Configuration Diagram

AT&T

IP Flexible Reach

SIP Trunk SIP Trunk

SBC 5000 Series

SIP SIG: 10.54.20.155

(Internal)

SIP SIG: 32.252.34.18

(External) AT&T IP: 12.194.20.75/

12.194.18.75AddressContext:IPDOMAIN

Zone: ATT_ZONE

Network Interface: pkt2

Media Interface: ATTIFG

SIP Trunk Name: ATT_TG

AddressContext: IPDOMAIN

Zone: CUST_ZONE

Network Interface: pkt1

Media Interface: CUSTIFG

SIP Trunk Name: CUST_TG

SIP SIG: 172.16.103.18

Customer Side ATT Side

Interactive

Intelligence 4.0

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




| | |----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 Description

G729A_T38_2833 Codec Entry for g729a codec with fax t38 and dtmf rfc2833

G711Ulaw_T38_2833 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 commit 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 commit

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 {


toneTreatment none;




}

dtmf {

relay rfc2833;

removeDigits enable;

}

admin@CUSTSBC% show profiles media codecEntry G711Ulaw_T38_2833

codec g711;

packetSize 30;

preferredRtpPayloadType 128;

fax {


toneTreatment faxRelay;

}

modem {


toneTreatment none;

}

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


CUST_PSP 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 commit

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 disable;

packetLossThreshold 0;

packetLossAction none;

}

peerAbsenceAction none;

silenceInsertionDescriptor {

g711SidRtpPayloadType 13;

heartbeat enable;

}

aal1PayloadSize 47;

codec {

codecEntry1 G729a_T38_2833;

codecEntry2 G711Ulaw_T38_2833;

codecEntry3 ;

codecEntry4 ;

}

packetToPacketControl {

transcode conditional;

conditionsInAdditionToNoCommonCodec {

differentDtmfRelay disable;

differentPacketSize disable;

differentSilenceSuppression disable;

honorOfferPreference disable;




}

codecsAllowedForTranscoding {

thisLeg "";

otherLeg "";

}

}

flags {

disallowDataCalls disable;

digitDetectSendEnabled disable;

useDirectMedia disable;

validatePeerSupportForDtmfEvents disable;

}

t38 {

dataRateManagementType type2TransferOfTcf;

ecm {

ecmPreferred disable;

}

lowSpeedNumberOfRedundantPackets 0;

maxBitRate 14.4Kbits_s;

numberOfRedundantPackets 0;

}

secureRtpRtcp {

cryptoSuiteProfile ;

flags {

allowFallback disable;

enableSrtp disable;

}

}

preferredRtpPayloadTypeForDtmfRelay 100;

videoCalls {

maxVideoBandwith 0;

videoBandwidthReductionFactor 0;

audioOnlyIfVideoIsPrevented enable;

}

mediaPacketCos 0;

honorRemotePrecedence disable;

sendRoutePSPPrecedence disable;




2) IP Signaling Profile

Create IP Signaling Profile with appropriate signaling flags towards customer side


CUST_IPSP IP Signaling 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 sendSdpInSubsequent18x enable commit

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 disable;

callHoldInterworking disable;

clearmodeForDataCalls disable;

createPChargingVector disable;

createPathHeader disable;

createServiceRouteHeader disable;

customizedSessionTimerBehavior disable;

disableAlsoHeader disable;

disableHostTranslation disable;

disableMediaLockDown disable;

disableReferToUriParameters disable;

discardReceivedReasonHeader disable;

doNotIncludeSsAttributeInReInvite disable;

endToEndBye disable;

includeIpPortsInFromAndToHeaders disable;

includeReasonHeader disable;

includeSsAttributeInInitialInvite disable;

includeTransportTypeInContactHeader disable;




insertPeerAddressAsTopRouteHeader disable;

mapCauseLocation disable;

mapSuspendResumeEventInPSvcInfoHeader disable;

mapUuiInPSigInfoHeader disable;

mimeCausePrecedeReasonHeaderCause disable;

minimizeRelayingOfMediaChangesFromOtherCallLegAll enable;

noContentDisposition disable;

noPortNumber5060 enable;

noUserinfoInContactHeader disable;

onlySelectedCodecInSessionRefresh disable;

pChgMsgInfo disable;

replaceHostOnViaHeader disable;

reQueryPsxOnRegisterRefresh disable;

sdpOlineOnlyCompares disable;

sendAllAllowedCodecsForLateMediaInviteOrReInvite enable;

sendDirectMediaInfoInSdpAttribute disable;

sendPtimeInSdp enable;

sessionTimerRefreshUpdate disable;

setAcceptHeaderToApplicationSdpOnly disable;

setOlineDash disable;

setSessionVersionZero disable;

setSlineDash disable;

skipPsxQueryForRefer disable;

storePathHeader disable;

storeServiceRouteHeader disable;

terminalPortabilityInterworking disable;

sendRtcpPortInSdp disable;

}

callTransferFlags {

handleIpAddressesNotPresentInNetworkSelectorTableNst

routeViaTransferringIptg;

forceReRouteViaPsxQuery disable;

}

optionTagInRequireHeader {

suppressReplaceTag disable;

}

optionTagInSupportedHeader {


}

relayFlags {

dialogEventPackage disable;

dtmfBody disable;

info disable;

message disable;

notify disable;

options disable;

regEventPackage disable;




refer enable;

sonusMediaBody disable;

statusCode3xx disable;

statusCode4xx6xx disable;

thirdPartyBodies disable;

force503to500Relay disable;

}

transparencyFlags {

alertInformationHeader disable;

authcodeHeaders disable;

contactHeader disable;

errorInfo disable;

fromHeader disable;

historyInfo disable;

maxForwardsHeader disable;

mwiBody disable;

pChargingVectorHeader disable;

pEarlyMedia disable;

pathHeader disable;

qsigBody disable;

reasonHeader disable;

referredByHeader disable;

requestURI disable;

routeHeader disable;

serviceRouteHeader disable;

sipBody disable;

sipfragBody disable;

toHeader disable;

toneBody disable;

unknownBody disable;

unknownHeader disable;

viaHeader disable;

}

}

egressIpAttributes {

numberGlobalizationProfile ;

flags {

bgcfTargetSchemeTransparency disable;

convertInactiveToSendrecv disable;

disable2806Compliance enable;

disableOptionalRegisterParameters disable;

map181Or182MessageTo183 disable;

mapContractorNumberInPSigInfoHeader disable;

suppressUnregister disable;

ttcIsupMapping disable;

useCalledPartyInRequestUri disable;

useColonInSdpMediaTypeParameter disable;




validateIsubAddress disable;

}

bci {

bciInterworkEncountered disable;

bciIsdnAddess disable;

}

domainName {

useSipDomainNameInFromField disable;

useSipDomainNameInRequestUri disable;

}

isub {

allowNsapIsub disable;

allowUserSpecifiedIsub disable;

includeCalledPartyIsub disable;

includeCallingPartyIsub disable;

}

numberPortabilityAttributes {

npdiOptions includeNpdiYes;

disableRn disable;

}

privacy {

transparency disable;

privacyInformation pAssertedId;

flags {

includePrivacy enable;

privacyRequiredByProxy disable;

msLyncPrivacySupport disable;

}

}

redirect {

mode acceptRedirection;

contactHandling mergeReceivedContacts;

flags {

skipCrankbackProfileAndAlwaysCrankback disable;

forceRequeryForRedirection disable;

}

}

sipHeadersAndParameters {

callForwarding {

dataMapping diversion;

diversionHeaderTransparency disable;

}

includeChargeInformation includeNone;

destinationTrunkGroupOptions includeNone;

originatingTrunkGroupOptions includeNone;

flags {

includeCic disable;




includeCpcInformation disable;

includeNpi disable;

includeOlip disable;

includePKAdn disable;

includePstnParameters disable;

includeQvalue disable;

skipCSeqCheckInEarlyDialog disable;

transparencyForDestinationTrunkGroupParameter disable;

}

}

transport {

type1 none;

type2 none;

type3 none;

type4 none;

}

}

ingressIpAttributes {

flags {

sip181Supported disable;


mapCalledPartyCategoryInPSigInfoHeader disable;

noSdpIn180Supported disable;

registrationExpiresinExpiresHeader disable;

send183OnInitiatingDisconnectTreatment disable;

sendSdpIn200OkIf18xReliable disable;

sendSdpInSubsequent18x enable;

}

carrierInformation {

generateTerminatingCa disable;

generateTerminatingCic disable;

}

}




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


CUST_PP 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 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 commit

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 none;

numberingPlanIndicator none;

numberLeadingPrefixDigits 0;

numberLeadingPrefixDigitsToStrip 0;

applyDmRule disable;

determineArea disable;

}






entry 17 0 11 31 {


digitType national;

dmPmRule "";







}



entry 18 0 11 31 {


digitType tollFree;

dmPmRule "";






determineArea enable;

}



entry 9 0 1 3 {


digitType national;

dmPmRule “”;







}





CUST_PP entry + 0 1 31

entry + 0 1 31 {

callType internationalType;

digitType international;

dmPmRule SIP_REMOVE_PLUS1;

natureOfAddress international;




applyDmRule enable;


}



entry 19 0 11 31 {


digitType national;

dmPmRule “”;







}



entry 011 0 2 31 {

callType internationalType;

digitType international;

dmPmRule "";







}




4) Numbering Plan

Create Numbering Plan by applying Prefix Profile created for customer side.


CUST_NUM_PLAN 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 commit

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 {

min 0;

max 0;}

line {

min 0;

max 0; }

exchangeCode {

min 0;

max 0;}

areaCode {

min 0;

max 0;}

}




5) SIP Adaptor Profile

Create SIP Adaptor Profile with appropriate cirteria/rules for manipulation of messages.

i. UPDATE-DTMF

This SMM rule is applied for outputAdaptorProfile of sipTrunk associated to Customer side. Includes DTMF payload type 100 in request/response towards Interaction Center if not available from ATT.


UPDATE-DTMF SMM rule for OutputAdaptor profile of sipTrunk to Customer 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 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 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 state enabled commit




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;

statusCode 200;

}

}

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";

}

to {

type messageBody;

messageBodyValue all;

}

regexp {

string " 18\\r\\n";

}

}

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";

}

to {

type messageBody;

messageBodyValue all;

}

regexp {

string "AVP 0\\r\\n";

}

}

}

}




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 5000 Series to be used on customer side to this IP interface.


CUSTIFG Media interface group name for customer

IPDOMAIN Address context name for customer domain

PKT1_V4 Media interface name for customer

pkt1 Gigabit Ethernet port used for signaling and media traffic towards customer

10.54.20.155 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 10.54.20.155 prefix 24 set addressContext IPDOMAIN ipInterfaceGroup CUSTIFG ipInterface PKT1_V4 mode inService state enabled commit




The output of show command for ip interface group is as given below:

admin@CUSTSBC% show addressContext IPDOMAIN ipInterfaceGroup CUSTIFG

ipInterface PKT1_V4 {

ceName CUSTSBC;

portName pkt1;

ipAddress 10.54.20.155;

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.


172.16.103.18 IP address of PBX on customer side

32 IP subnet prefix

10.54.20.1 Gateway IP

set addressContext IPDOMAIN staticRoute 172.16.103.18 32 10.54.20.1 CUSTIFG PKT1_V4 preference 100 commit

The output of show command for static route is as given below:

admin@CUSTSBC% show addessContext IPDOMAIN staticRoute

staticRoute 172.16.103.18 32 10.54.20.1 CUSTIFG PKT1_V4 {

preference 100;

}

3) Zone

Create Zone for customer domain and specify the id of the zone.


CUST_ZONE Customer zone name

set addressContext IPDOMAIN zone CUST_ZONE id 2 commit




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 Signaling Port with signaling IP/prefix of SBC 5000 Series to be used on customer side and assign it to IP interface group.


10.54.20.155 SIP signaling IP address of SBC towards customer

5060 SIP signaling port of SBC towards customer

set addressContext IPDOMAIN zone CUST_ZONE sipSigPort 1 ipInterfaceGroupName CUSTIFG ipAddressV4 10.54.20.155 portNumber 5060 set addressContext IPDOMAIN zone CUST_ZONE sipSigPort 1 ipInterfaceGroupName CUSTIFG transportProtocolsAllowed sip-udp set addressContext IPDOMAIN zone CUST_ZONE sipSigPort 1 mode inService state enabled commit

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 10.54.20.155;

portNumber 5060;

mode inService;

state enabled;

transportProtocolsAllowed sip-udp;

5) IP Peer

Create an IP Peer with signaling IP address of customer IP-PBX and assign it to customer zone.


CUST_IPP IP Peer name for customer IP-PBX

set addressContext IPDOMAIN zone CUST_ZONE ipPeer CUST_IPP ipAddress 172.16.103.18 ipPort 5060 commit




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.103.18;

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.


CUST_TG SIP Trunk towards Customer IP-PBX

set addressContext IPDOMAIN zone CUST_ZONE sipTrunkGroup CUST_TG media mediaIpInterfaceGroupName CUSTIFG sourceAddressFiltering disabled set addressContext IPDOMAIN zone CUST_ZONE sipTrunkGroup CUST_TG ingressIpPrefix 172.16.103.18 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 signaling messageManipulation outputAdapterProfile UPDATE-DTMF set addressContext IPDOMAIN zone CUST_ZONE sipTrunkGroup CUST_TG policy digitParameterHandling numberingPlan CUST_NUM_PLAN set addressContext IPDOMAIN zone CUST_ZONE sipTrunkGroup CUST_TG state enabled mode inService commit

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;

tgIPVersionPreference both-ipv4-and-ipv6;

digitParameterHandling {

numberingPlan CUST_NUM_PLAN;

}

callRouting {

elementRoutingPriority DEFAULT_IP;

}

media {

packetServiceProfile CUST_PSP;

}

services {

classOfService DEFAULT_IP;

}

signaling {

ipSignalingProfile CUST_IPSP;

}

featureControlProfile DEFAULT_IP;

}

signaling {

messageManipulation {

outputAdapterProfile UPDATE-DTMF;

}

}

media {

mediaIpInterfaceGroupName CUSTIFG;

sourceAddressFiltering disabled;

}

ingressIpPrefix 172.16.103.18 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

1) Packet Service Profile

Create Packet Service Profile towards ATT side with G729A as a first codec and G711ulaw as a second codec


ATT_PSP 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 commit

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;

packetSize 0;

}

silenceFactor 40;

typeOfService 0;

voiceInitialPlayoutBufferDelay 10;

rtcpOptions {




rtcp enable;

terminationForPassthrough disable;

packetLossThreshold 0;

packetLossAction none;

}

peerAbsenceAction none;

silenceInsertionDescriptor {

g711SidRtpPayloadType 13;

heartbeat enable;

}

aal1PayloadSize 47;

codec {

codecEntry1 G729a_T38_2833;

codecEntry2 G711Ulaw_T38_2833;

codecEntry3 ;

codecEntry4 ;

}

packetToPacketControl {

transcode conditional;

conditionsInAdditionToNoCommonCodec {

differentDtmfRelay disable;

differentPacketSize disable;

differentSilenceSuppression disable;

honorOfferPreference disable;

}

codecsAllowedForTranscoding {

thisLeg “ “;

otherLeg “ “;

}

}

flags {

disallowDataCalls disable;

digitDetectSendEnabled disable;

useDirectMedia disable;

validatePeerSupportForDtmfEvents disable;

}

t38 {

dataRateManagementType type2TransferOfTcf;

ecm {

ecmPreferred disable;

}

lowSpeedNumberOfRedundantPackets 0;

maxBitRate 14.4Kbits_s;

numberOfRedundantPackets 0;

}

secureRtpRtcp {

cryptoSuiteProfile ;




flags {

allowFallback disable;

enableSrtp disable;

}

}

preferredRtpPayloadTypeForDtmfRelay 100;

videoCalls {

maxVideoBandwith 0;

videoBandwidthReductionFactor 0;

audioOnlyIfVideoIsPrevented enable;

}

mediaPacketCos 0;

honorRemotePrecedence disable;

sendRoutePSPPrecedence disable;

2) IP Signaling Profile

Create IP Signaling Profile with appropriate signaling flags towards ATT side


ATT_IPSP IP Signaling Profile name on ATT side.

set profiles signaling ipSignalingProfile ATT_IPSP set profiles signaling ipSignalingProfile ATT_IPSP commonIpAttributes flags 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 sendSdpInSubsequent18x enable commit

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 {

addPathServiceRoute disable;

callHoldInterworking disable;

clearmodeForDataCalls disable;

createPChargingVector disable;

createPathHeader disable;

createServiceRouteHeader disable;

customizedSessionTimerBehavior disable;

disableAlsoHeader disable;




disableHostTranslation disable;

disableMediaLockDown disable;

disableReferToUriParameters disable;

discardReceivedReasonHeader disable;

doNotIncludeSsAttributeInReInvite disable;

endToEndBye disable;

includeIpPortsInFromAndToHeaders disable;

includeReasonHeader disable;

includeSsAttributeInInitialInvite disable;

includeTransportTypeInContactHeader disable;

insertPeerAddressAsTopRouteHeader disable;

mapCauseLocation disable;

mapSuspendResumeEventInPSvcInfoHeader disable;

mapUuiInPSigInfoHeader disable;

mimeCausePrecedeReasonHeaderCause disable;

minimizeRelayingOfMediaChangesFromOtherCallLegAll disable;

noContentDisposition disable;

noPortNumber5060 enable;

noUserinfoInContactHeader disable;

onlySelectedCodecInSessionRefresh disable;

pChgMsgInfo disable;

replaceHostOnViaHeader disable;

reQueryPsxOnRegisterRefresh disable;

sdpOlineOnlyCompares disable;

sendAllAllowedCodecsForLateMediaInviteOrReInvite enable;

sendDirectMediaInfoInSdpAttribute disable;

sendPtimeInSdp enable;

sessionTimerRefreshUpdate disable;

setAcceptHeaderToApplicationSdpOnly disable;

setOlineDash disable;

setSessionVersionZero disable;

setSlineDash disable;

skipPsxQueryForRefer disable;

storePathHeader disable;

storeServiceRouteHeader disable;

terminalPortabilityInterworking disable;

sendRtcpPortInSdp disable;

}

callTransferFlags {

handleIpAddressesNotPresentInNetworkSelectorTableNst

routeViaTransferringIptg;

forceReRouteViaPsxQuery disable;

}

optionTagInRequireHeader {


}

optionTagInSupportedHeader {





}

relayFlags {

dialogEventPackage disable;

dtmfBody disable;

info disable;

message disable;

notify disable;

options disable;

regEventPackage disable;

refer disable;

sonusMediaBody disable;

statusCode3xx disable;

statusCode4xx6xx disable;

thirdPartyBodies disable;

force503to500Relay disable;

}

transparencyFlags {

alertInformationHeader disable;

authcodeHeaders disable;

contactHeader disable;

errorInfo disable;

fromHeader disable;

historyInfo disable;

maxForwardsHeader disable;

mwiBody disable;

pChargingVectorHeader disable;

pEarlyMedia disable;

pathHeader disable;

qsigBody disable;

reasonHeader disable;

referredByHeader disable;

requestURI disable;

routeHeader disable;

serviceRouteHeader disable;

sipBody disable;

sipfragBody disable;

toHeader disable;

toneBody disable;

unknownBody disable;

unknownHeader disable;

viaHeader disable;

}

}

egressIpAttributes {

numberGlobalizationProfile ;

flags {




bgcfTargetSchemeTransparency disable;

convertInactiveToSendrecv disable;

disable2806Compliance enable;

disableOptionalRegisterParameters disable;

map181Or182MessageTo183 disable;

mapContractorNumberInPSigInfoHeader disable;

suppressUnregister disable;

ttcIsupMapping disable;

useCalledPartyInRequestUri disable;

useColonInSdpMediaTypeParameter disable;

validateIsubAddress disable;

}

bci {

bciInterworkEncountered disable;

bciIsdnAddess disable;

}

domainName {

useSipDomainNameInFromField disable;

useSipDomainNameInRequestUri disable;

}

isub {

allowNsapIsub disable;

allowUserSpecifiedIsub disable;

includeCalledPartyIsub disable;

includeCallingPartyIsub disable;

}

numberPortabilityAttributes {

npdiOptions includeNpdiYes;

disableRn disable;

}

privacy {

transparency disable;

privacyInformation pAssertedId;

flags {

includePrivacy enable;

privacyRequiredByProxy disable;

msLyncPrivacySupport disable;

}

}

redirect {

mode acceptRedirection;

contactHandling mergeReceivedContacts;

flags {

skipCrankbackProfileAndAlwaysCrankback disable;

forceRequeryForRedirection disable;

}

}




sipHeadersAndParameters {

callForwarding {

dataMapping diversion;

diversionHeaderTransparency disable;

}

includeChargeInformation includeNone;

destinationTrunkGroupOptions includeNone;

originatingTrunkGroupOptions includeNone;

flags {

includeCic disable;

includeCpcInformation disable;

includeNpi disable;

includeOlip disable;

includePKAdn disable;

includePstnParameters disable;

includeQvalue disable;

skipCSeqCheckInEarlyDialog disable;

transparencyForDestinationTrunkGroupParameter disable;

}

}

transport {

type1 none;

type2 none;

type3 none;

type4 none;

}

}

ingressIpAttributes {

flags {



mapCalledPartyCategoryInPSigInfoHeader disable;

noSdpIn180Supported disable;

registrationExpiresinExpiresHeader disable;

send183OnInitiatingDisconnectTreatment disable;

sendSdpIn200OkIf18xReliable disable;

sendSdpInSubsequent18x enable;

}

carrierInformation {

generateTerminatingCa disable;

generateTerminatingCic disable;

}

}




3) Prefix Profile

Create Prefix Profile with appropriate dial plan for handling incoming calls from ATT network.


ATT_PP 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 commit

The output of show command for prefix profile is as given below:


ATT_PP entry 7 0 10 31

entry 7 0 10 31 {


digitType national;

dmPmRule "";







}


ATT_PP entry 9 0 10 31

entry 9 0 10 31 {


digitType national;

dmPmRule "";







}




4) Numbering Plan

Create Numbering Plan by applying Prefix Profile created for ATT side.


ATT_NUM_PLAN 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 commit

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 {

min 0;

max 0;}

line {

min 0;

max 0; }

exchangeCode {

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 set profiles digitParameterHandling dmPmRule Add011 subRule 1 criteria MATCH_DDI ruleType digit digitManipulation digitStringManipulation replacement type variable value “” digitString billingNumber startDigitPosition 0 numberOfDigits 0 set profiles digitParameterHandling dmPmRule Add011 subRule 1 digitManipulation numberType callingNumber commit

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 {



numberLength noInput;

presentation none;

screening none;

includeInEgress none;

}

digitStringManipulation {

startDigitPosition 0;

numberOfDigits 0;

replacement {




type constant;

digitString calledNumber;


numberOfDigits 0;

value 011;

}

action none;

}

}

}

subRule 1 {

criteria MATCH_DDI;

ruleType digit;

digitManipulation {

numberType callingNumber;

numberParameterManipulation {

natureOfAddress national;


numberLength noInput;

presentation none;

screening none;

includeInEgress none;

}

digitStringManipulation {


numberOfDigits 1;

replacement {

type variable;

digitString billingNumber;


numberOfDigits 0;

value "";

}

action none;

}

}

}

admin@CUSTSBC% show profiles digitParameterHandling dmPmCriteria

SIP_MATCH_INTL_CD

criteriaType digit;

digitType calledNumber;

parameterPresenceCheck exists;

digitCriteria {

egressFlag {




value send;

operation ignore;

}

digitMatch {

value {


numberOfDigits 0;

matchValue 0;

}

operation ignore;

}

natureOfAddress {

value international;

operation equals;

}

numberingPlanIndicator {

value data;

operation ignore;

}

numberLength {

value 0;

operation ignore;

}

presentationMatch {

value none;

operation ignore;

}

screeningMatch {

value none;

operation ignore;

}

}

admin@CUSTSBC% show profiles digitParameterHandling dmPmCriteria

MATCH_DDI

criteriaType digit;

digitType callingNumber;

parameterPresenceCheck exists;

digitCriteria {

egressFlag {

value send;

operation ignore;

}

digitMatch {

value {


numberOfDigits 7;




matchValue 1978303;

}

operation equals;

}

natureOfAddress {

value international;

operation equals;

}

numberingPlanIndicator {

value data;

operation ignore;

}

numberLength {

value 0;

operation ignore;

}

presentationMatch {

value none;

operation ignore;

}

screeningMatch {

value none;

operation ignore;

}

}

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




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.


ATTIFG Media interface group name for ATT network

PKT2_V4 Media interface name for ATT network

pkt2 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 commit

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.


12.194.18.75 Primary IP address of ATT network.

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 commit

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.


ATT_ZONE ATT zone name

set addressContext IPDOMAIN zone ATT_ZONE id 3 commit




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


32.252.34.18 SIP signaling IP address of SBC towards ATT

5060 SIP signaling 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 commit

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.


ATT_IPP1 Primary IP address of the ATT network

ATT_IPP2 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 commit

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 {

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.


ATT_TG 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 set addressContext IPDOMAIN zone ATT_ZONE sipTrunkGroup ATT_TG state enabled mode inService commit

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;

tgIPVersionPreference both-ipv4-and-ipv6;

digitParameterHandling {

numberingPlan ATT_NUM_PLAN;

egressDmPmRule Add011 ;

}

callRouting {

elementRoutingPriority DEFAULT_IP;




}

media {

packetServiceProfile ATT_PSP;

}

services {

classOfService DEFAULT_IP;

}

signaling {

ipSignalingProfile ATT_IPSP;

signalingProfile ;

}

featureControlProfile DEFAULT_IP;

}

signaling {

relayNonInviteRequest enabled;

}

media {

maxPtimeDefault 30;

mediaIpInterfaceGroupName ATTIFG;

sourceAddressFiltering disabled;

}



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


CUST_RL Routing Label name on Customer side.

set global callRouting routingLabel CUST_RL routingLabelRoute 1 trunkGroup CUST_TG ipPeer CUST_IPP inService inService commit

The output of show command for routing label is as given below:

admin@CUSTSBC% show global callRouting routingLabel CUST_RL




overflowNumber ;

overflowNOA none;

overflowNPI none;

routePrioritizationType sequence;

script ;

action routes;

routingLabelRoute 1 {

trunkGroup CUST_TG;

ipPeer CUST_IPP;

proportion 0;

cost 1000000;

inService inService;

testing normal;

}

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 commit

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.


ATT_RL 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 commit

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 none;

overflowNPI none;

routePrioritizationType sequence;

script "";

action routes;


trunkGroup ATT_TG;

ipPeer ATT_IPP1;

proportion 0;

cost 1000000;


testing normal;

}


trunkGroup ATT_TG;

ipPeer ATT_IPP2;

proportion 0;

cost 1000000;


testing normal;

}

}

2) Route

Create Route to point to ATT routing label when call comes from Customer trunkgroup towards PSTN. Current example gives entry for Country +91.

set global callRouting route trunkGroup CUST_TG CUSTSBC standard Sonus_NULL 1 all all ALL none Sonus_NULL routingLabel ATT_RL set global callRouting route none Sonus_NULL Sonus_NULL standard 806789 91 all all ALL none Sonus_NULL routingLabel ATT_RL commit




The output of show command for route is as given below:

admin@CUSTSBC% show global callRouting route

route none Sonus_NULL Sonus_NULL standard 806789 91 all all ALL none

Sonus_NULL {

routingLabel ATT_RL;

}

route trunkGroup CUST_TG CUSTSBC standard Sonus_NULL 1 all all ALL none

Sonus_NULL {

routingLabel ATT_RL;

}




3. Interaction Center (IC) Configuration

The Interaction center 4.0 configuration, which is used along with the Sonus SBC 5000 Series is as per the details provided in the IC System Administration guide.

1. Configure lines in IC to create trunk between Interaction center and Sonus SBC

The line page has a vast majority of the configuration options required for SIP carrier setup. This is the section that configures the connection to the carrier’s servers, any authentication or registration information, and basic configuration. Two lines must be created, one for the Outbound connection and one for the stations.




Line Menu:

Active: The active box should be checked. This activates the line. If this box is not checked, the line will not be available for any function. This can also be affected by right clicking on the line in Interaction Administrator, dropping to the Set Active menu option, and selecting Yes. Domain Name: This box should contain the domain name or ip address of IC server which will go in From header. Enable T.38 Faxing: SIP carrier service supports the T.38 faxing protocol by default. Uncheck this option if you do not have (or wish to use) an analog to SIP capable FXS type device to connect an analog fax machine to the system.




Call Analysis Type: Select Call Analysis type as “Meida Server” so that media flow through IC server. Also check “Allow Deferred Answer” so that IC sends 180 Ringing, otherwise it directly sends 200 OK without 180 Ringing.




Identity (Out) Menu:

Calling Address: The phone number provided by the SIP carrier should be entered into this box. The number entered is used in the “From” header for outbound SIP calls. This field needs to be accurate, as number validation is done based on this number. Incorrect numbers can lead to some functionality (e.g. international calling, etc…) not working as expected or not working at all.




Audio Menu

Audio Path: Set the Audio Path to “Always In” so that media always flows via Media Server. DTMF Type & Payload: Set the DTMF Type as “RFC2833 only” and DTMF Payload as “100”.




Proxy Menu

Configure the Proxy IP to SBC 5000 signaling ip so that calls route via SBC. 2. Create stations in IC

To create stations go to “Stations “-> right panel -> right click “New”




Enter Station Name and select the Station type as “Stand-alone-Phone” and Station Template as “<Stand-alone Phone, SIP>” and click Next.




Addresses:

In the Addresses tab, configure the Station Extension, Identification Address, and the Contact line.

In the Station Extension field, give the desired extension, In identification address give the extension, mostly these two fields are same.

In the address field give the IP address of station through which it will get register. In contact line select the desired Line to use for this station.




General:

In the General tab, provide the MAC Address of the phone to be registered with IC as shown below.

Configure the Outbound ANI to the number to be displayed in “From” header.




3. Configuring the Dial plan, DID, and DNIS in I3.

This section explains the process of creating a regional dial plan in Interaction Administrator. To set up a dial plan in Interaction Administrator Select the Phone Numbers container and double-click Configuration in the right pane. Click on the Regional Dial Plan tab and click Dial Plan on the right side of the screen.

IC covers everything in its default dial plan. Therefore, change is not required for this.




DID & DNIS: To add and delete prefix in incoming and outgoing calls, we can create DID/DNIS. To configure DID/DNIS




4. Configuring codecs .

To configure the codec priority and ptime, select

Regionalization > <Default Location > Communication




5. Configure voice mail & auto-attendant.

To configure Auto Attendant, select User and then assign extension to default user “Operator”. Assign DID also for this user to dial from outside.

To retrieve Voicemail for a user, dial Auto-Attendant extension, once auto attendant prompt is heard dial 99 followed by voicemail username and password.




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 5000 Series. 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.

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

sbc 5000 series configuration guide - interactive...

Documents