SES and Comunication Manager

8/13/2019 SES and Comunication Manager

1/102

JRF; Reviewed:SPOC 2/4/2010

Solution & Interoperability Test Lab Application Notes2010 Avaya Inc. All Rights Reserved.

1 of 102VzB_IPT2CPE_SES

Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Avaya Aura

Communication Manager 5.2 and Avaya Aura SIP

Enablement Services (SES) 5.2, with the Verizon Business IP

Trunk Service Offer in a SIP Trunk Redundant (2-CPE)

EnvironmentIssue 1.2

Abstract

These Application Notes describe the steps to configure the Avaya SIP trunk architecture withVerizon Business IP Trunk Service Offer in a SIP Trunk Redundant (2-CPE) environment.The SIP Trunk Redundant (2-CPE) architecture provides for redundant SIP trunking betweenthe Verizon Business IP Trunk service offer and the Avaya SIP telephony solution consistingof Avaya Aura Communication Manager (version 5.2), Avaya Aura SIP EnablementServices (version 5.2), and various Avaya telephones.

The Verizon Business IP Trunk service offer referenced within these Application Notes isdesigned for business customers with an Avaya SIP telephony solution. The service provideslocal and/or long Distance PSTN calling via standards-based SIP trunks directly, without theneed for additional TDM enterprise gateways or TDM cards and the associated maintenancecosts.

Information in these Application Notes has been obtained through DevConnect compliancetesting and additional technical discussions. Testing was conducted by the VerizonInteroperability Test Lab with support from the Avaya Solution and Interoperability Test Lab.


2/102


3/102




3.2.10 EMEA Avaya Aura Communication Manager Extensions..................................493.2.11 Save EMEA Avaya Aura Communication Manager Provisioning.......................49

3.3. Avaya SIP Endpoint Configuration ..........................................................................503.3.1 Add a Station for the SIP Endpoint...........................................................................503.3.2 Configure Off-PBX Telephone Station Mapping .....................................................51

3.3.3 Save EMEA Avaya Aura Communication Manager Changes.............................524. Configure Avaya Aura SIP Enablement Services (SES)......................................534.1. Domestic Avaya AuraSIP Enablement Services Servers ....................................534.1.1 Primary Avaya Aura SIP Enablement Services Server........................................534.1.2 Domestic Secondary Avaya Aura SIP Enablement Services Server....................76

4.2. EMEA Avaya Aura SIP Enablement Services Specific Provisioning..................774.2.1 Primary Avaya Aura SIP Enablement Services Server........................................774.2.2 EMEA Secondary Avaya Aura SIP Enablement Services Server........................80

5. Verizon Business IP Trunk Service Offer Configuration .........................................815.1. Domestic and EMEA Inbound (to CPE) and Outbound numbers ............................815.2. Fully Qualified Domain Name (FQDN)s .................................................................81

5.3. Verizon DNS Information.........................................................................................826. Interoperability Compliance Testing....................................................................826.1. General Test Approach .............................................................................................826.2. Test Results ...............................................................................................................82

7. Verification Steps......................................................................................................837.1. Call scenarios ............................................................................................................837.1.1 Domestic ...................................................................................................................837.1.2 EMEA .......................................................................................................................84

8. Troubleshooting Tools and Techniques ....................................................................848.1. Avaya Aura Communication Manager.................................................................848.2. Avaya Aura SIP Enablement Services..................................................................84

9. Support ......................................................................................................................929.1. Avaya ........................................................................................................................929.2. Verizon ......................................................................................................................92

10. References .................................................................................................................9210.1. Avaya ........................................................................................................................9210.2. Verizon ......................................................................................................................9210.3. RFCs .........................................................................................................................93

11. APPENDIX A: Specifying Pattern Strings in Address Maps ...................................9411.1. Address Map Caveats ...............................................................................................9411.1.1 Over-lapping Address Map Strings ..........................................................................9411.1.2 Using a Plus Sign (+) in a Host Map. .......................................................................95

12. APPENDIX B: Configuring Avaya Aura SIP Enablement Services Host Maps.9612.1. Avaya Aura Communication Manager Provisioning for Host Map Routing.......9612.2. Avaya Aura SIP Enablement Services Provisioning for Host Map Routing........97

13. APPENDIX C: Avaya Aura SIP Enablement Services TimerB Value andMultiple DNS SRV Response Entries. ...................................................................101


4/102




1. IntroductionThese Application Notes describe the steps to configure the Avaya SIP trunk architecture with theVerizon Business IP Trunk Service offer in a SIP Trunk Redundant (2-CPE) environment. TheVerizon SIP Trunk Redundant (2-CPE) architecture provides for redundant SIP trunks between theVerizon Business IP Trunk service offer and an Avaya SIP telephony solution customer premises

equipment (CPE) consisting of Avaya Aura Communication Manager (version 5.2), AvayaAura SIP Enablement Services (version 5.2), and various Avaya SIP and H.323 telephones.

Note- The Verizon SIP Trunk Redundant (2-CPE) architecture is a service option and its use isnot a requirement of the Verizon Business IP Trunk service offer.

The Verizon Business IP Trunk service offer described in these Application Notes is designed forbusiness customers using Avaya Aura Communication Manager and Avaya Aura SIPEnablement Services. The service provides local and/or long-distance calls (with PSTN endpoints)via standards-based SIP trunks. These trunks connect to the Avaya systems directly, without theneed for additional TDM enterprise gateways or TDM cards and the associated maintenance costs.

Verizon Business and Avaya developed the SIP Trunk Redundant (2-CPE) architecture to ensurethat SIP trunk calls can be automatically rerouted to bypass SIP trunk failures due to network orcomponent outages.

NoteThe Avaya Aura CommunicationManager and Avaya Aura SIP EnablementServicesprovisioning described in these Application Notes are also applicable on non SIP Trunk Redundant(2-CPE) architectures.

1.1. Verizon Business IP Trunk Service Offer Overview

The Verizon Business IP Trunk service offer described within these Application Notes is designedfor business customers using Avaya Aura CommunicationManager and Avaya Aura SIPEnablement Services. The service provides local and/or long-distance calls (with PSTN endpoints)via standards-based SIP trunks. These trunks connect to the Avaya systems directly, without theneed for additional TDM enterprise gateways or TDM cards and the associated maintenance costs.

Single site users can choose combined local and long distance service packages that are availablein 200+ metropolitan service areas or a long distance package only. Multi-site or campusconfigurations may only choose long distance service.

Outbound long distance voice and fax services include domestic direct-dial calling within the

United States. They may also include integrated dedicated toll-free service, enabling customers touse a single, cost-effective connection for incoming toll-free calls and outbound VoIP traffic.International Europe, Middle East, and Africa (EMEA) dialing is also supported.

G.711 fax is supported over the Verizon Business IP Trunk service offer.


5/102




NoteAn optional supported for G.711 fax configuration is the use of an Audio Codes MP-202Gateway between Avaya Aura CommunicationManager and the fax device. See reference [10]for more information.

The Verizon Business IP Trunk service offer is delivered to the enterprise customer location using

Verizon Business Internet Dedicated Access (IDA). Although through not described in theseApplication Notes, Verizon Business also supports service connections for their IP Trunk serviceoffer using Private IP (PIP) service connections.

1.2. The SIP Trunk Redundant (2-CPE) Architecture Option

The SIP Trunk Redundant (2-CPE) architecture described in Section 1is based on a customerlocation having two Avaya Aura SIP EnablementServices (SES) servers. One is designated asthe Primary and one as the Secondary. Both Avaya Aura SIP EnablementServices areprovisioned identically except each will have a unique IP address. Avaya Aura CommunicationManager is provisioned with SIP trunks for local SIP calls, as well as SIP Trunks for inboundand outbound off network SIP calls. Local SIP calls are those between SIP, H.323, and legacy

stations provisioned on Avaya Aura CommunicationManager. This local traffic also includesother SIP messages such as SIP phone registration, state updates, etc. Off network traffic includesall SIP messaging between the Avaya Aura CommunicationManager/ Avaya Aura SIPEnablement Services environment and other destinations. These local and off network SIP trunksare provisioned between Avaya Aura CommunicationManager and both Avaya Aura SIPEnablement Services servers (see Figure 1). Both of the Avaya Aura SIP EnablementServicesservers are provisioned with the sameFully Qualified Domain Name (FQDN).

Note- See Section 1.5for more information on FullyQualified Domain Names (FQDN).

Voice and G.711 fax calls utilize their own inbound and outbound trunks. This allows specificvoice and fax parameters to be provisioned (e.g. codec selection). See Sections 3.1.6 and 3.2.7formore information on SIP trunk provisioning.

For inbound calls (to CPE), the Verizon network may either send calls alternatively to the Primaryand Secondary SIP Enablement Services servers or it may send calls to the Secondary SIPEnablement Services server only if calls cannot complete via the Primary. The method chosen isbased on Verizon service provisioning for that particular customer. These SIP calls will be sent toAvaya Aura CommunicationManager from the Avaya Aura SIP EnablementServices on oneof the associated inbound SIP trunks.

For outbound calls (from CPE), Avaya Aura CommunicationManager is provisioned to selectthe Primary outbound SIP trunks first. The Secondary outbound SIP trunks are only used ifoutbound calls via the Primary trunks fail. In the reference configurationDomain Based Routingwas used for outbound calls (see Section 1.5for more information on Domain Based Routing).Domain Based Routing relies on the Verizon network to provide call destination routinginformation to the Avaya Aura SIP EnablementServices.


6/102




Local SIP trunks are used for calls between Avaya SIP telephones and Avaya H.323 and legacytelephones, as well as other Avaya SIP telephone/Avaya Aura CommunicationManagercommunications. See Section 3.1.6for a description of the SIP trunks used and their provisioning.

In the tested SIP Trunk Redundant (2-CPE) configuration, the Verizon network uses two Session

Border Controllers (SBCs) between the Verizon Business IP trunk service offer network and theAvaya CPE. This adds an additional layer of redundancy.

Figure 1: The SIP Trunk Redundant (2-CPE) Architecture

1.3. The SIP Trunk Redundant (2-CPE) Reference ConfigurationFigures 2 and3illustrate two sample SIP Trunk Redundant (2-CPE) solutions. These are theconfigurations that were used for the DevConnectcompliance testing. One configuration was usedto test United States domesticdialing and the other was used to test Europe, Middle East, andAfrica (EMEA) dialing.


7/102




1.3.1 Domestic and EMEA Common Architecture

The following architectural requirements were used in both the Domestic and EMEA testenvironments and are discussed in detail in subsequent sections.

Primary and Secondary Avaya Aura SIP EnablementServices servers.o Identical provisioning except for unique IP addresses.

o Primary and Secondary Avaya Aura SIP EnablementServices servers assignedthe same Fully Qualified Domain Name (FQDN).

o Communication Manager Server Maps for inbound calls.o No Host Maps required for outbound calls.

Avaya Aura CommunicationManager.o Separate Primary and Secondary SIP trunks for Inbound Voice traffic.

Signaling Groups defined with Far-end Domain fields. Signaling Groups defined with Near-end port 5061.

o Separate Primary and Secondary SIP trunks for Outbound Voice traffic. Signaling Groups defined with Far-end Domain field of the Verizon Fully

Qualified Domain Name (FQDN).

Signaling Groups defined with Near-end port 5061.o Separate Primary and Secondary SIP trunks for Inbound G.711 fax traffic.

Signaling Groups defined with Far-end Domain field. Signaling Groups defined with Near-end port 5062.

o Separate Primary and Secondary SIP trunks for Outbound G.711 fax traffic. Signaling Groups defined with Far-end Domain field of the Verizon Fully

Qualified Domain Name (FQDN). Signaling Groups defined with Near-end port 5062.

o Separate Primary and Secondary SIP trunks for Local SIP telephone traffic. Signaling Groups defined with Far-end Domain field of the Avaya Aura

SIP Enablement Services Fully Qualified Domain Name (FQDN).

Signaling Groups defined with Near-end port 5061.o Voice traffic uses G.729A and G.711Mu codecs.o Fax traffic uses G.711Mu and G.711A codecs.o Voice stations assigned a Class of Restriction (COR) with a higher Facility

Restriction Level (FRL).o Fax stations assigned a Class of Restriction (COR) with a lower Facility Restriction

Level (FRL).o Outbound Voice and G.711 fax calls utilize Look Ahead Routing (LAR) to select

Primary and Secondary SIP Trunks based on the calling station COR/FRL.o Outbound Voice and G.711 fax calls will only select their associated Secondary

trunks if the initial call via the Primary trunk fails.

1.3.2 Domestic DialingAvaya Components

The simulated domestic customer location included: An Avaya S8500 Media Server with an Avaya G650 Media Gateway. The S8500

served as the host processor for Avaya Aura CommunicationManager. Avaya 4600 Series IP telephones using the H.323 software bundle. Avaya 9600 Series IP telephones using the SIP software bundle.


8/102




Two Avaya S8500 SIP Enablement Services servers.

1.3.3 Domestic Dialing Example

The following are examples of domestic outbound and inbound voice and G.711 fax calls. SeeSections 3.1and 4.1for Domestic Avaya Aura CommunicationManager and Avaya Aura

SIP Enablement Services provisioning.

Given: Voice station 1001 Fax station 1004 Voice Primary Inbound SIP trunk 12 and Secondary SIP trunk 13 Voice Primary Outbound SIP trunk 14 and Secondary SIP trunk 15 Fax Primary Inbound SIP trunk 20 and Secondary SIP trunk 21 Fax Primary Outbound SIP trunk 18 and Secondary SIP trunk 19

Inbound Inbound voice calls to 1001 match theAvaya Aura SIP EnablementServices

Communication Manager voice Map that has the Contact with port 5061o Calls arrive on Inbound voice trunk 12 (Primary) or 13 (secondary) and connect to station

1001 using G729 or G711 codecs Inbound G.711 fax calls to 1004 match the Avaya Aura SIP EnablementServices

Communication Manager fax Map that has the Contact with port 5062o Calls arrive on Inbound fax trunk 20 (Primary) or 21 (Secondary) on port 5062 and connect

to fax station 1004 using G711 codecs All inbound Communication Manager Signaling groups use a Far-end domain to

accept calls from all foreign domains.

Outbound Communication Manager stations dial 9 and number 530352xxxx

o

ARS sends the call to Route Pattern 16 Route Pattern 16 is configured as follows: Voice Trunk 14 (Primary) and FRL 2 Voice Trunk 15 (Secondary) and FRL 2 Fax Trunk 18 (Primary) and FRL 1 FaxTrunk 19 (Secondary) and FRL 1

o Voice stations are set to COR 1 which has the higher FRL priority

2 set. These voice calls will select trunk 14 then 15 and go out onport 5061 using G729 or G711 codecs.

o Fax stations are set to COR 2 which has the lower FRL priority 1

set. These G.711 fax calls will select trunk 18 then 19 and go outon port 5062 using G711 codecs.

o All outbound Communication Manager Signaling groups send calls to the Far-end domain

of schst1n0004.icpiptrunksit2.gsiv.com (Broadsoft Fully Qualified Domain Name (FQDN)). No SIP Enablement Services Host Maps (used for outbound calls) are required.


9/102




Figure 2: The SIP Trunk Redundant (2-CPE) Reference Configuration for Domestic Dialing

1.3.4 EMEA DialingAvaya Components

The Avaya SIP telephony solution used as a simulated domestic customer location included: An Avaya S8300 Media Server with an Avaya G350 Media Gateway. The S8300

served as the host processor for Avaya Aura CommunicationManager. Avaya 4600 Series IP telephones using the H.323 software bundle. Avaya 9600 Series IP telephones using the SIP software bundle. Two Avaya S8500 SIP Enablement Services servers.

1.3.5 EMEA Dialing Example

The following are examples of outbound and inbound voice and G.711 fax calls. See Sections 3.2and 4.2for Avaya Aura CommunicationManager and Avaya Aura SIP EnablementServicesprovisioning.

Given: Voice station 1031 Fax station 1039


10/102




Voice Primary Inbound SIP trunk 12 and Secondary SIP trunk 13 Voice Primary Outbound SIP trunk 14 and Secondary SIP trunk 15 Fax Primary Inbound SIP trunk 20 and Secondary SIP trunk 21 Fax Primary Outbound SIP trunk 18 and Secondary SIP trunk 19

Inbound Inbound voice calls to 1031 match theAvaya Aura SIP EnablementServices

Communication Manager voice Map that has the Contact with port 5061o Calls arrive on Inbound voice trunk 12 (Primary) or 13 (secondary) and connect to station

1031 using G729 or G711 codecs Inbound G.711 fax calls to 1039 match the Avaya Aura SIP EnablementServices

Communication Manager fax Map that has the Contact with port 5062o Calls arrive on Inbound fax trunk 20 (Primary) or 21 (Secondary) on port 5062 and connect

to fax station 1039 using G711 codecs All inbound Communication Manager Signaling groups use a Far-end domain to

accept calls from all foreign domains.

Outbound

Communication Manager stations dial 9 and number 00441189056849o ARS sends the call to Route Pattern 16 Route Pattern 16 is configured as follows:

Voice Trunk 14 (Primary) and FRL 2 Voice Trunk 15 (Secondary) and FRL 2 Fax Trunk 18 (Primary) and FRL 1 FaxTrunk 19 (Secondary) and FRL 1

o Voice stations are set to COR 1 which has the higher FRL priority

2 set. These voice calls will select trunk 14 then 15 and go out onport 5061 using G729 or G711 codecs.

o Fax stations are set to COR 2 which has the lower FRL priority 1

set. These G.711 fax calls will select trunk 18 then 19 and go outon port 5062 using G711 codecs.

o All outbound Communication Manager Signaling groups send calls to the Far-end domainof schst1n0004.emeaiptrunksit2.gsiv.com (Broadsoft Fully Qualified Domain Name(FQDN)).

NoAvaya Aura SIP EnablementServices Host Maps (used for outbound calls)are required.


11/102




Figure 3: The SIP Trunk Redundant (2-CPE) Reference Configuration for EMEA Dialing

1.3.6 Reference Configuration - Verizon Interoperability Test Lab

The DevConnect compliance testing was conducted by the Verizon System Interoperability TestLab in Richardson, Texas with support from the Avaya Solution and Interoperability Test Lab inLincroft, New Jersey.

In the reference configuration, the Verizon Business solution included managed IP access service.Verizon Business is responsible for the configuration of this service and therefore those details arenot included within these Application Notes.

Figure 4shows the reference configuration used for the DevConnect compliance testing.


12/102




Figure 4: DevConnect Compliance Testing SIP Trunk Redundant (2-CPE) Reference

Configuration

1.4. Avaya SIP Trunks

The public SIP trunks to the Verizon Business IP Trunk service offer works with any combinationof Avaya analog, H.323 and SIP telephones. In the Avaya SIP trunk architecture, the AvayaAura SIP EnablementServices functions as a SIP proxy through which all incoming andoutgoing SIP messages flow to the Verizon Business IP Trunk service offer. Avayas SIPEnablement Services also supports protocol conversion between Verizons SIP/UPD trunktermination and Avayas Communication Managers SIP/TLS (default) or SIP/TCP trunkinterface. There is no direct SIP signaling path between the Verizon Business IP Trunk serviceoffer and Avaya Aura CommunicationManager or Avaya SIP endpoints.

For incoming calls, the Avaya Aura SIP EnablementServices uses Communication ManagerServer Maps to direct the incoming SIP messages to Avaya Aura CommunicationManager.Once the message arrives at Avaya Aura CommunicationManager, further incoming calltreatment such as incoming digit translations, class of service restrictions, etc., may be performed.


13/102




All outgoing calls to the PSTN are processed within Avaya Aura CommunicationManager andare subject to outbound features such as Automatic Route Selection, digit manipulation, class ofservice restrictions and Look Ahead Routing (see Section 3.1.8). Once Avaya AuraCommunication Manager selects a SIP trunk for the outbound call, the SIP signaling is routed tothe appropriate Avaya Aura SIP EnablementServices. Based on how the Avaya Aura

Communication Manager SIP trunking is defined, the Avaya Aura SIP EnablementServicesmay use Host Maps (see Appendix B), an Outbound Proxy, or Domain Based Routing with DNSlookups (see Section 1.5below) to direct the outbound SIP calls. Domain Based Routing was usedfor outbound calls in the reference configuration.

Outbound Calling

Method

Avaya Aura

Communication Manager

Outbound SIP Trunk Far

End Fully Qualified Domain

Name (FQDN)

Avaya Aura SIP

Enablement Services Call

Routing Method

Avaya Aura SIP

Enablement ServicesHost Maps

Avaya Aura SIP Enablement

Services SIP Fully QualifiedDomain Name (FQDN)

Host Maps

Domain Based Routing Foreign Fully QualifiedDomain Name (FQDN)

Outbound Proxy or DNSlookup.

Table 1: SIP Trunk Outbound Call Routing Methods

1.5. Domain Based Routing for Outbound calls

In the reference configuration, the Avaya Aura SIP EnablementServices uses DNS lookups todirect outbound calls to proper the Verizon Business Service destination. This method is referredto asDomain Based Routing. When Domain Based Routing is used, Avaya AuraCommunication Manager specifies a foreign Fully Qualified Domain Name (FQDN) in the

outbound SIP trunk provisioning. A foreign Fully Qualified Domain Name (FQDN) is one thatdoes notmatch the SIP Domain specified for the Avaya Aura SIP EnablementServices (seeSection 4). The Fully Qualified Domain Name (FQDN) used for the outbound SIP trunk was theFully Qualified Domain Name (FQDN) of the Verizon Session Border Controller (SBC). Thisforeign domain is specified as the destination for the INVITE sent by Avaya AuraCommunications Manager to the Avaya Aura SIP EnablementServices. The Avaya Aura SIPEnablement Services then does a DNS query to the Verizon DNS server for this foreign domainand forwards the INVITE based on the DNS response. When a foreign Fully Qualified DomainName (FQDN) is specified in conjunction with Domain Based Routing, no other outbound callroute provisioning (e.g. Host Maps) is required for the Avaya Aura SIP EnablementServicesother than provisioning a DNS IP address(s). This provides the most flexible outbound route

provisioning for the CPE as all the call route decisions take place in the Verizon network. In thereference configuration, the Verizon network used two SBCs. Both of these SBCs were specifiedin the DNS SRV responses to the Avaya Aura SIP EnablementServices. This provided anadditional layer of redundancy.

NoteThere is an alternative method for configuring Domain Base Routing where AvayaAura CommunicationManager that doesuse Avaya Aura SIP EnablementServices Host


14/102




Maps. This alternative method for configuring Domain Base Routing is described in reference[11].

1.5.1 Specifying Domains

The terms Fully Qualified Domain Name (FQDN) and Domain are sometimes used

interchangeably even though they have different meanings. Typically domainmeans just thatadomain name such as company.com. An Fully Qualified Domain Name (FQDN) typically includesa host namewith the domainbig.company.com. In the reference configuration, Verizon suppliedFully Qualified Domain Name (FQDN)s to be used by both EMEA and Domestic as well assupplying an Fully Qualified Domain Name (FQDN) for the Verizon service node for use in DNSqueries.

1.5.2 Domain Based Routing Provisioning Example

The following steps describe how Domain Based Routing may be provisioned on Avaya AuraCommunication Manager and the Avaya Aura SIP EnablementServices.

1. Avaya Aura CommunicationManagera. Avaya Aura CommunicationManager has theAuthoritative Domainfield of the

ip-network-regionform (see Section 3.1.4) provisioned with the Fully QualifiedDomain Name (FQDN) of the Avaya Aura SIP EnablementServices SIP Domain(see Section 4.1). This is the region associated with IP telephones or the regionassociated with the C-LAN/Procr for legacy phones.

b. Avaya Aura CommunicationManager will use this value in the INVITEFromheader.

c. The Avaya Aura CommunicationManager outbound trunk has aforeign FullyQualified Domain Name (FQDN) specified in the Far-End Domain field of the

associated Signaling Group form. The term Foreign means that the Fully QualifiedDomain Name (FQDN) does notmatch the Fully Qualified Domain Name (FQDN)specified in the SIP Domainfield of the Avaya Aura SIP EnablementServices.Avaya Aura CommunicationManager will use this foreign Fully QualifiedDomain Name (FQDN) in theRequest URI of the INVITE.

d. Avaya Aura CommunicationManager sends the INVITE to the Avaya AuraSIP Enablement Services.

2. Avaya Aura SIP EnablementServicesa. The Avaya Aura SIP EnablementServices compares theRequest URIof the

INVITE received from Avaya Aura Communications Manager to its SIP Domain

and sees that it is notauthorative for the foreign Fully Qualified Domain Name(FQDN). Therefore, the Avaya Aura SIP EnablementServices will notlook atany provisionedHost Maps, making them unnecessary.

b. The Avaya Aura SIP EnablementServices will then do aDNS SRV lookupbasedon theDNS server(s)that has been provisioned in the Avaya Aura SIPEnablement Services (see Section 4.1). The Avaya Aura SIP EnablementServices will send the call to the destination specified in the SRV response.


15/102




c. Alternatively the Avaya Aura SIP EnablementServices can send the call to anOutbound Proxyif one has been provisioned on the Avaya Aura SIP EnablementServices (see Section 4.1). If no DNS server or Outbound has been provisioned, theAvaya Aura SIP EnablementServices will deny the call.

Note- Avayas Best Practice recommendation is to use Port 5060 for all configurations, and bydefault the Avaya Aura SIP EnablementServices will use port 5060 for outbound calls. If adifferent destination port is required, then Domain Based Routingshould notbe used and AvayaAura SIP EnablementServices Host Maps must be usedto specify this non-standard port. SeeAppendix Bfor more information on provisioning Avaya Aura CommunicationManager andthe Avaya Aura SIP EnablementServices to utilize Host Maps for outbound calls.

1.6. Call Flows

To better understand how calls are routed between the PSTN and the enterprise sites using SIP

trunks, two call flows are described in this section.

The first call scenario illustrated inFigure 5is an inbound call from PSTN to the enterprise siteterminating on a telephone supported by Avaya Aura CommunicationManager.

1. A user on the PSTN dials a Verizon Business Service provided DID number that isassigned to an Avaya Aura CommunicationManager telephone at the enterprise site.The PSTN routes the call to the Verizon Business Service network (as the local serviceprovider), which in turn routes the DID number to the assigned customer.

2. Based on the DID number, the Verizon Business Service offers the call to Avaya Aura

SIP Enablement Services using SIP signaling messages sent over the managed accessfacility. Note that the assignment of the DID number and the address of the Avaya AuraSIP Enablement Services server was previously established during the ordering andprovisioning of the service.

3. Avaya Aura SIP EnablementServices routes the call to the Avaya AuraCommunication Manager over a SIP trunk.

4. Avaya Aura CommunicationManager terminates the call to the Avaya telephone. Thesame process occurs for calls to any Avaya analog, digital and H.323 IP telephone.

- or

4a. Inbound calls destined for a SIP extension at the enterprise are routed to Avaya AuraCommunication Manager. Avaya Aura CommunicationManager, acting as a SIP back-to-back user agent, then transmits the appropriate SIP signaling via Avaya Aura SIPEnablement Services to the SIP telephone (as shown by the 4a arrow.)


16/102




Figure 5: Incoming PSTN Calls to Avaya Aura Communication Manager

The second call scenario illustrated in Figure 6 is an outgoing call from an Avaya telephone at theenterprise site to the PSTN via the SIP trunk to the Verizon Business Service.

1. An Avaya H.323, analog or digital telephone served by Avaya Aura Communication

Manager originates a call to a user on the PSTN.

- or-

1a. An Avaya SIP telephone originates a call that is routed via Avaya Aura SIP EnablementServices (as shown by the 1a arrow) to Avaya Aura CommunicationManager.

2. Avaya Aura CommunicationManager handles the call request where originationtreatment such as Class of Restrictions (COR) and Automatic Route Selection (ARS) isperformed. Avaya Aura CommunicationManager selects the SIP trunk and sends theSIP signaling messages to Avaya Aura SIP EnablementServices.

3. Avaya Aura SIP EnablementServices routes the call to the Verizon Business Service.

4. The Verizon Business Service completes the call to the PSTN.

Figure 6: Outgoing Calls from Avaya Aura CommunicationManager to the PSTN


17/102


18/102




Outbound calls will use the Automatic Route Selection route patterns with FRL screeningto prevent fax calls from using the G.729 trunk group.

Incoming calls will use the Avaya Aura SIP EnablementServices media server addressmaps to route fax designated DID numbers to the trunk group supporting the G.711 codec.

1.9. Known LimitationsThe following limitations are noted for the reference configuration described in these ApplicationNotes:

These Application Notes describe the Domain Based Routing method for directing outboundcalls from Avaya Aura SIP Enablement Services. In certain configurations this method will

result in the absence of a PAI header for INVITEs sent by Avaya Aura SIP EnablementServices. If the PAI header is required for network admission control, then the Avaya Aura

SIP Enablement Services Host Map method of Domain Based Routing described in [11] shouldbe used.

Avaya Aura Communication Manager sends SIP 180 RINGING messages with SDP.

Although this does not meet the Verizon Business Product Integration Requirements, noimpact to call processing was observed.

Verizon Business IPCC Services suite does notsupport History Info Headers.

Verizon Business IPCC Services suite does support Diversion Headers.

Verizon Business IP Trunking service does not support T.38 fax.

The use of an Audio Codes MP-202 Gateway between Avaya Aura CommunicationManager and the fax device is recommended for G.711 fax.

Verizon Business IP Trunking service does not support G.711a codec for domestic service(EMEA only).

Verizon Business IP Trunking service does not support G.729B codec.

1.10. History Info and Diversion Headers

The Verizon Business IP Trunk service does not support SIP History Info Headers. Instead theVerizon Business IP Trunk service requires that SIP Diversion Header be sent for any callredirection events. Avaya Aura Communication Manager version 5.2 SIP trunk form providesoptions for specifying whether History Info Headers or Diversion Headers are sent (see Section3.1.6).


19/102




2. Equipment and Software ValidatedThe following equipment and software were used for the sample configuration provided:

Equipment Firmware Software

Avaya S8300 Server H4 FW1 -Avaya Aura CommunicationManager R015x.02.0.947.3

Service Pack 1 - 02.0.947.3-17294

Avaya Aura SIP EnablementServices (SES) - ses-5.2.0.0-947.3b

Avaya G350 Media Gateway 29.22.3 -

Avaya 4621SW IP Telephones - 2.9.1 (H.323)

Avaya 9630 IP Telephones - 2.4.1.0 (SIP)

Table 2: Equipment and Software Used in the Tested Configuration

Note- The solution integration validated in these Application Notes should be considered valid for

deployment with Avaya Aura Communication Manager release 5.2.1 andAvaya Aura SIPEnablement Services release 5.2.1. Avaya agrees to provide service and support for the integrationof Avaya Aura Communication Manager release 5.2.1 and Avaya Aura SIP EnablementServices release 5.2.1 with Verizon Business IP Trunk service offer, in compliance with existingsupport agreements for Avaya Communication Manager release 5.2 and Avaya SIP EnablementServices release 5.2, and in conformance with the integration guidelines as specified in the body ofthis document.


20/102




3. Configure Avaya Aura CommunicationManager for SIPTrunking

This section describes the steps for configuring Avaya Aura CommunicationManager with thenecessary signaling and media characteristics for the SIP trunk connection with the VerizonBusiness IP Trunk service offer.

Note- The initial installation, configuration, and provisioning of the Avaya servers for AvayaAura CommunicationManager and Avaya Aura SIP EnablementServices, Avaya MediaGateways and their associated boards, as well as Avaya telephones, are presumed to have beenpreviously completed and are not discussed in these Application Notes.

As described in Section 1, two dialing environments were created for the reference architecture,Domestic and EMEA.

The EMEA site utilized Avaya Aura CommunicationManager on an S8300 server located in anAvaya G350 Media Gateway. This environment contained Avaya SIP, Avaya H.323, and analogfax endpoints.

The Domestic site utilized Avaya Aura CommunicationManager running on an Avaya S8500server. Collocated with these servers is an Avaya G650 Media Gateway containing a C-LANsignaling processor card, a MedPro media processor card, and an IPSI controller card forcommunicating to the Avaya S8500 server. The Domestic site also contained Avaya SIP, AvayaH.323, and analog fax endpoints.

Note- As the Domestic/S8500 configuration is more complex, these Application Notes will focuson the Domestic provisioning. Unless otherwise noted, the configuration of the EMEA AvayaAura CommunicationManager is similar. See Section 3.2 for EMEA/S8300 specificprovisioning of Avaya Aura CommunicationManager.

NoteThe Avaya Aura CommunicationManager commands described in these ApplicationNotes were administered using the System Access Terminal (SAT). SSH was used connect to SATvia the appropriate IP address, login and password.

NoteThe Avaya Aura CommunicationManager and Avaya Aura SIP EnablementServicesprovisioning described in these Application Notes are also applicable on non SIP Trunk Redundant

(2-CPE) architectures.


21/102




3.1. Domestic (S8500 environment) Provisioning for Avaya AuraCommunication Manager

3.1.1 Verify System Capacity and Features

The Avaya Aura CommunicationManager license file controls the customer capabilities.

Contact an authorized Avaya representative for assistance if a required feature needs to be enabled.

1. On Page 2of the display system-parameters customer-optionsform, verify that theMaximum AdministeredSIP Trunksis sufficient for the combination of trunks to theVerizon Business IP Trunk service offer, trunks for SIP endpoints and any other SIPtrunking applications. Be aware that for each call from a non-SIP endpoint to the VerizonBusiness IP Trunk service offer one SIP trunk is used for the duration of the call.However, due to Avaya SIP endpoint configuration, each Avaya SIP endpoint on a callwith the Verizon Business IP Trunk service offer requires two SIP trunks for the durationof the call.

NoteIf any changes are made to the system-parameters customer-optionsform, you must logout of SAT and log back in for the changes to take effect.

display system-parameters customer-options Page 2of 10OPTIONAL FEATURES

IP PORT CAPACITIES USEDMaximum Administered H.323 Trunks: 800 4

Maximum Concurrently Registered IP Stations: 2400 3Maximum Administered Remote Office Trunks: 800 0

Maximum Concurrently Registered Remote Office Stations: 2400 0Maximum Concurrently Registered IP eCons: 0 0

Max Concur Registered Unauthenticated H.323 Stations: 0 0Maximum Video Capable H.323 Stations: 0 0Maximum Video Capable IP Softphones: 0 0

Maximum Administered SIP Trunks: 75 66Maximum Administered Ad-hoc Video Conferencing Ports: 0 0Maximum Number of DS1 Boards with Echo Cancellation: 80 0

Maximum TN2501 VAL Boards: 10 1Maximum Media Gateway VAL Sources: 250 0

Maximum TN2602 Boards with 80 VoIP Channels: 128 0Maximum TN2602 Boards with 320 VoIP Channels: 128 0

Figure 7: System-Parameters Customer-Options FormPage 2

2. On Page 3of the System-Parameters Customer-Optionsform, verify that the Automatic

Route Selection (ARS) feature is enabled.


22/102





Abbreviated Dialing Enhanced List? y Audible Message Waiting? yAccess Security Gateway (ASG)? n Authorization Codes? yAnalog Trunk Incoming Call ID? y CAS Branch? n

A/D Grp/Sys List Dialing Start at 01? y CAS Main? nAnswer Supervision by Call Classifier? y Change COR by FAC? nARS? y Computer Telephony Adjunct Links? n

ARS/AAR Partitioning? y Cvg Of Calls Redirected Off-net? yARS/AAR Dialing without FAC? y DCS (Basic)? yASAI Link Core Capabilities? n DCS Call Coverage? yASAI Link Plus Capabilities? n DCS with Rerouting? y

Async. Transfer Mode (ATM) PNC? nAsync. Transfer Mode (ATM) Trunking? n Digital Loss Plan Modification? y

ATM WAN Spare Processor? n DS1 MSP? nATMS? y DS1 Echo Cancellation? y

Attendant Vectoring? y


3. On Page 4of the System-Parameters Customer-Optionsform, verify that the IP Trunksfeature is enabled.


Emergency Access to Attendant? y IP Stations? yEnable 'dadmin' Login? yEnhanced Conferencing? y ISDN Feature Plus? y

Enhanced EC500? y ISDN/SIP Network Call Redirection? nEnterprise Survivable Server? n ISDN-BRI Trunks? y

Enterprise Wide Licensing? n ISDN-PRI? yESS Administration? n Local Survivable Processor? n

Extended Cvg/Fwd Admin? y Malicious Call Trace? yExternal Device Alarm Admin? y Media Encryption Over IP? y

Five Port Networks Max Per MCC? n Mode Code for Centralized Voice Mail? nFlexible Billing? y

Forced Entry of Account Codes? y Multifrequency Signaling? yGlobal Call Classification? y Multimedia Call Handling (Basic)? y

Hospitality (Basic)? y Multimedia Call Handling (Enhanced)? yHospitality (G3V3 Enhancements)? y Multimedia IP SIP Trunking? n

IP Trunks? yIP Attendant Consoles? y

(NOTE: You must logoff & login to effect the permission changes.)


3.1.2 Domestic Dial Plan

In the reference configuration the Domestic environment uses local extensions four digits in lengthbeginning with 1, 2, 3, and 4. Trunk Access Codes (TAC) are 3 digits in length and begin with 6.The Feature Access Code (FAC) to access ARS is one digit in length (9).

The dial plan is modified with the change dialplan analysiscommand.


23/102




1. On Page 1of the form: Local extensions:

1. In the Dialed String field enter 12. In the Total Lengthfield enter 43. In theCall Typefield enter ext

4. Repeat forDialed String 2, 3, and4 TAC codes:

1. In the Dialed Stringfield enter 62. In the Total Lengthfield enter 33. In the Call Typefield enter dac

FAC codeARS access:1. In the Dialed String field enter 92. In the Total Lengthfield enter13. In the Call Type field enter fac

change dialplan analysis Page 1 of 12DIAL PLAN ANALYSIS TABLE

Location: all Percent Full: 0Dialed Total Call Dialed Total Call Dialed Total CallString Length Type String Length Type String Length Type

1 4 ext2 4 ext3 4 ext4 4 ext6 3 dac9 1 fac

Figure 10: Change Dialplan Analysis FormPage 1

3.1.3 Domestic Node Names

In the IP Node Namesform, verify (or assign) the node names to be used in this configurationusing the change node-names ipcommand. As described in Section 1, Domestic uses an AvayaS8500 Server as the Avaya Aura CommunicationManager Platform. When the display node-names IPcommand is issued, the NIC IP address of the server is displayed as procr.

Procrand 166.38.98.23are the Nameand IP Addressof the Avaya Aura CommunicationManager S8500 server.

C-LAN-1a03and 166.38.98.26are used below as the Nameand IP Addressof the C-LANsignaling processor in the G650 Media Gateway.

Med-1a04and 166.38.98.24are used below as the Nameand IP Addressof the Media

Processor in the G650 Media Gateway.

SBC and 166.34.76.196are used below as the Nameand IP Addressof the Verizon SessionBorder Controller (SBC). All traffic to and from the Verizon network passes through the SBC.

Primary-SESand 166.38.98.22are used below as the Nameand IP Addressof the PrimaryAvaya Aura SIP EnablementServices server used in the SIP Trunk Redundant (2-CPE)


24/102




configuration. NoteThis IP address only applies to the Domestic environment. A differentIP address is assigned for EMEA (see Section 3.2).

Secondary-SESand 166.38.98.17are used below as the Nameand IP Addressof theSecondary Avaya Aura SIP EnablementServices server used in the SIP Trunk Redundant(2-CPE) configuration.NoteThis IP address only applies to the Domestic environment. A

different IP address is assigned for EMEA (see Section 3.2).

list node-namesNODE NAMES

Type Name IP AddressIP SBC 166.34.76.196IP Primary-SES 166.38.98.22IP Secondary-SES 166.38.98.17IP clan-1a03 166.38.98.26IP default 0.0.0.0IP med-1a04 166.38.98.24IP procr 166.38.98.23

Figure 11: Domestic IP Node Names Form

3.1.4 Domestic IP-Network-Regions

Three network regions were defined in the reference configuration. Avaya equipment in theDomestic location is assigned to ip-network-region 1 as are the local SIP trunks. Voice trunks areassigned to ip-network-region 2. Fax trunks are assigned to ip-network-region 3.

Avaya Component IP_Network-Region

C-LAN 1

MedPro 1

Local SIP Trunks 10 & 11 1

Voice SIP Trunks 12, 13, 14, & 15 2Fax SIP Trunks 18, 19, 20, & 21 3

Table 3Domestic IP Network Regions

The SIP trunk ip-network-regions are defined in the SIP Signaling Group form Far-end regionparameter (see Section 3.1.6).

Network region assignments for ip-interfaces may be verified with the list ip-interface allcommand.

list ip-interface allIP INTERFACES

NetON Type Slot Code Sfx Node Name/ Subnet Mask Gateway Address Rgn VLAN

IP-Address-- ---- ---- ---- --- --------------- --------------- --------------- --- ----yC-LAN 01A03 TN799 D C-LAN-1a03 255.255.255.0 166.38.98.1 1 n

166.38.98.26yMEDPRO 01A04 TN2302 med-1a04 255.255.255.0 166.38.98.1 1 n

166.38.98.24

Figure 12: IP-Interface IP-Network-Region AssignmentsDomestic


25/102




The network-region for an ip-interface may be modified with the change ip-interface x commandwhere xis the board location (the C-LAN interface is shown in the example below).

change ip-interface 01a03IP INTERFACES

Type: C-LANSlot: 01A03

Code/Suffix: TN799 DNode Name: C-LAN-1a03IP Address: 166.38 .98 .26Subnet Mask: 255.255.255.0 Link: 1

Gateway Address: 166.38 .98 .1Enable Ethernet Port? y Allow H.323 Endpoints? y

Network Region: 1 Allow H.248 Gateways? yVLAN: n Gatekeeper Priority: 5

Target socket load and Warning level: 400Receive Buffer TCP Window Size: 8320

ETHERNET OPTIONSAuto? nSpeed: 100MbpsDuplex: Full

Figure 13: IP-Interface IP-Network-Region Assignment.

The IP-Network-Regionform specifies the parameters used by the Avaya AuraCommunication Manager components and how components defined to different regions interactwith each other. The following ip-network-region assignments were used in the referenceconfiguration. Other combinations are possible. In addition, specific codecs are used tocommunicate between these regions. See Section 3.1.5 for the Codec form configurations.

Inter Region Communication IP-Codec used

Region 1 to Region 1 Codec 1Region 1 to Region 2 Codec 1

Region 1 to Region 3 Codec 2

Region 2 to Region 3 Codec 2

Table 4: Inter Region Codec Assignments

NoteAvaya IP telephones inherit the ip-network-region of the C-LAN (or procr for an AvayaS8300 based system) they register to. So if an IP phone registers to a C-LAN, that phone willbecome part of region 1. If an IP phone needs to be defined to a different region regardless ofregistration, this may be performed with the ip-network-mapcommand.[1]

3.1.4.1 IP-Network-Region 1As described in Section 3.1.4, ip-network-region 1 is defined for local Avaya IP interfaces as wellas for local SIP trunks. The network regions are modified with the change ip-network-region xcommand, where x is the network region number (Figure 14).

1. On Page 1of the IP Network Regionform: Configure the Authoritative Domainfield to match the SIP Domainname

configured on the Avaya Aura SIP EnablementServices System Propertiesfield


26/102




(see Section 4.1). In this configuration, the Domestic domain name isavaya8500.icpiptrunksit2.gsiv.com (provided by Verizon).

NoteThe value placed in the Authoritative Domainfield is used to create the SIP Fromheader for outbound calls from stations in this region. In addition, inbound call Request URIs

to stations in this region must match the Authoritative Domain.

By default, IP-IP Direct Audio(media shuffling) is set to yesto allow audio trafficto be sent directly between SIP endpoints to reduce the use of media resources.

Set theCodec Setto 1for the corresponding calls within the IP Network Region.

change ip-network-region 1 Page 1of 19IP NETWORK REGION

Region: 1Location: Authoritative Domain: avaya8500.icpiptrunksit2.gsiv.com

Name: Local RegionMEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes

Codec Set: 1 Inter-region IP-IP Direct Audio: yes

UDP Port Min: 2048 IP Audio Hairpinning? nUDP Port Max: 3029

DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? yCall Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS

Audio PHB Value: 46 Use Default Server Parameters? yVideo PHB Value: 26

802.1P/Q PARAMETERSCall Control 802.1p Priority: 6

Audio 802.1p Priority: 6Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS

H.323 IP ENDPOINTS RSVP Enabled? nH.323 Link Bounce Recovery? y

Idle Traffic Interval (sec): 20

Keep-Alive Interval (sec): 5Figure 14: IP Network Region 1Page 1

2. On Page 3of the IP Network Regionform: Define the Codec Setused for inter-region communications. Codec Set2is entered

for communications with region 2. Codec Set3is used for inter-regioncommunication with region 3.

Set the direct WANfield toy,indicating that devices in each region can directlycommunicate with each other.

Set the WAN-BW-Limitsfields to NoLimitindicating that the Inter NetworkRegion Connections are not constrained by bandwidth limits.

Set theIGAR(Inter-Gateway-Alternate-Routing) field to nbecause this field is not

used in these Application Notes.


27/102




change ip-network-region 1 Page 3of 19Inter Network Region Connection Management

src dstcodecdirect WAN-BW-limits Video Intervening Dynrgn rgn set WAN Units Total Norm Prio Shr Regions CAC IGAR AGL1 1 1 all1 2 2 y NoLimit n

1 3 3 y NoLimit n

Figure 15: IP Network Region 1Page 3

3.1.4.2 IP-Network-Region 2

As described in Section 3.1.4, ip-network-region 2 is defined for Voice SIP trunks. Provisioning isthe same as for ip-network-region 1 except:

1. On Page 1of the IP Network Regionform: Set theCodec Setto IP Codec Set2to be used for the corresponding calls within

the IP Network Region.



Name: VoiceMEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes

Codec Set: 2 Inter-region IP-IP Direct Audio: yesUDP Port Min: 2048 IP Audio Hairpinning? yUDP Port Max: 3029


Audio PHB Value: 46 Use Default Server Parameters? yVideo PHB Value: 26

802.1P/Q PARAMETERSCall Control 802.1p Priority: 6



Idle Traffic Interval (sec): 20


2. On Page 3of the IP Network Regionform: Define the Codec Setused for inter-region communications. Codec Set2is

entered for communications with region 1. Codec Set3is used for inter-regioncommunication with region 3.

change ip-network-region 2 Page 3of 19Inter Network Region Connection Managementsrc dst codec direct WAN-BW-limits Video Intervening Dynrgn rgn set WAN Units Total Norm Prio Shr Regions CAC IGAR AGL2 1 2 y NoLimit n2 2 2 all2 3 3 y NoLimit n



28/102




3.1.4.3 IP-Network-Region 3

As described in Section 3.1.4, ip-network-region 3 is defined for fax SIP trunks. Provisioning isthe same as for ip-network-region 1 except:

1. On Page 1of the IP Network Regionform: Set theCodec Setto IP Codec Set2to be used for the corresponding calls within

the IP Network Region.



Name: FaxMEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes

Codec Set: 3 Inter-region IP-IP Direct Audio: yesUDP Port Min: 2048 IP Audio Hairpinning? yUDP Port Max: 3029


Audio PHB Value: 46 Use Default Server Parameters? yVideo PHB Value: 26802.1P/Q PARAMETERSCall Control 802.1p Priority: 6



Idle Traffic Interval (sec): 20Keep-Alive Interval (sec): 5

Keep-Alive Count: 5


2. On Page 3of the IP Network Regionform: Define the Codec Setused for inter-region communications. Codec Set3is entered for

communications with region 1. Codec Set3is used for inter-region communicationwith region2.

display ip-network-region 3 Page 3of 19Inter Network Region Connection Management

src dst codec direct WAN-BW-limits Video Intervening Dynrgn rgn set WAN Units Total Norm Prio Shr Regions CAC IGARAGL3 1 3 y NoLimit n

3 2 3 y NoLimit n3 3 3all



29/102




3.1.5 Domestic IP Codec Sets

Three codec sets are defined in the reference configuration. One for local intra customer locationcalls (ip-network-region 1), off network voice calls (ip-network-region 2), and off network G.711fax calls (ip-network-region 3). Table 5shows the codecs defined to each of these codec sets.

IP-Codec Form IP-Network-Region Codecs Defined

Codec Form 1 1 G.711MU / G.729A

Codec Form 2 2 G.729AB / G.729A / G.711MU

Codec Form 3 3 G.729MU / G.711A

Table 5: Codec Form Codec Assignments

3.1.5.1 Intra Customer LocationIP-Codec-Set 1

G.711MU is typically used within the same location and is often specified first. G.729A is alsospecified as an option. Other codecs could be specified as well depending on local requirements.This codec set is associated with ip-network-region 1.

The IP-Codec-Setform is modified with the change ip-codec xcommand, wherexis the codecform number.

1. On Page 1of the form: Configure the Audio Codecfield 1to G.711MU. Configure the Audio Codecfield 1to G.729A.

change ip-codec-set 1 Page 1 of 2IP Codec Set

Codec Set: 1Audio Silence Frames PacketCodec Suppression Per Pkt Size(ms)

1: G.711MU n 2 202: G.729A n 2 20

Figure 20: IP Codec Set 1

2. On Page 2of the form: Configure the Fax field to off. Configure the Fax Redundancy field to 0. Let all other fields default.

change ip-codec-set 1 Page 2of 2IP Codec Set

Allow Direct-IP Multimedia? nMode Redundancy

Fax off 0Modem off 0TDD/TTY off 3Clear-channel n 0

Figure 21: IP Codec Set 1Page 2


30/102




3.1.5.2 Voice CallsIP-Codec-Set 2

G.729AB was picked as the first option as it uses less bandwidth and is compatible with annexb(noise suppression). G.729A was used as the second choice, with G.711MU as the third choice.This codec set is associated with ip-network-region 2.

1. On Page 1of the form: Configure the Audio Codecfield 1to G.729AB. Configure the Audio Codecfield 1to G.729A. Configure the Audio Codecfield 2to G.711MU.

display ip-codec-set 2 Page 1 of 2IP Codec Set


1:G.729AB n 2 20

2: G.729A n 2 203: G.711MU n 2 20

Figure 22: Voice Call IP Codec Set 2

2. On Page 2of the form set the values shown in Figure 22 for codec set 1.

3.1.5.3 Fax CallsIP-Codec-Set 3

G.711Mu was picked as the first option with G.711A as the third choice. This codec set isassociated with ip-network-region 3.

1. On Page 1of the form:

Configure the Audio Codecfield 1to G.711MU. Configure the Audio Codecfield 2to G.711A.

change ip-codec-set 3 Page 1 of 2IP Codec Set


1: G.711MU n 2 202: G.711A n 2 20

Figure 23: Fax Call IP Codec Set 32. On Page 2of the form set the values shownfor codec set 1.

3.1.6 Domestic SIP Trunk Groups

As described in Section 1.2SIP trunks are defined for local SIP communication as well as for, offnetwork voice and G.711 fax calls. In addition, for each of these call types, SIP trunks areprovisioned to the Primary and Secondary Avaya Aura SIP EnablementServices servers. Table6lists the SIP trunks used in the reference configuration. A SIP trunk is created in Avaya AuraCommunication Manager by provisioning a SIP Trunk Group as well as a SIP Signaling Group.


31/102




SIP Trunk Function

Avaya Aura

Communication

Manager SIP Signaling

Group/Trunk Group

Avaya Aura Communication

Manager SIP Signaling Group

Far-End Domain

Avaya Aura

Communication

Manager IP Network

Region

Local - Primary Trunk 10 Avaya Aura SIP Enablement

Services SIP Domainavaya8500.icpiptrunksit2.gsiv.com

1

Local - Secondary Trunk 11 Avaya Aura SIP EnablementServices SIP Domain

avaya8500.icpiptrunksit2.gsiv.com

1

Inbound Voice - Primary Trunk 12 2

Inbound Voice - Secondary Trunk 13 2

Outbound Voice - Primary Trunk 14 Verizon network Fully QualifiedDomain Name (FQDN)

schsj1n0005.icpiptrunksit2.gsiv.com

2

Outbound Voice - Secondary Trunk 15 Verizon network Fully QualifiedDomain Name (FQDN)


2

Inbound Fax - Primary Trunk 20 3Inbound Fax - Secondary Trunk 21 3

Outbound Fax - Primary Trunk 18 Verizon network Fully QualifiedDomain Name (FQDN)


3

Outbound Fax - Secondary Trunk 19 Verizon network Fully QualifiedDomain Name (FQDN)


3

Table 6: Avaya SIP Trunk Configuration for SIP Trunk Redundant (2-CPE)

3.1.6.1 Configure Local SIP Trunks10 and 11

Create Primary and Secondary Signaling Groups and Trunk Groups 10 and 11 to support the localSIP phone registration and for voice calls between the local Avaya SIP stations and non-SIPphones (H.323/DCP/analog) defined on Avaya Aura CommunicationManager. Local SIP Trunk10 is defined to the Primary Avaya Aura SIP EnablementServices server and Local SIP Trunk11 is defined to the Secondary Avaya Aura SIP EnablementServices server.

a. Using the add signaling-group10 command, configure the PrimaryLocal SignalingGroup as follows:

Set theGroup Typefield to sip. The Transport Methodfield will default to tls(Transport Layer Security). Note that

this specifies the transport method used between Avaya Aura Communication

Manager and Avaya Aura SIP EnablementServices, not the transport method used tothe Verizon Business.

Specify the C-LAN used for SIP signaling (node name clan-1a03) and the PrimaryAvaya Aura SIP EnablementServices server (node name Primary-SES) as the twoends of the signaling group in the Near-end Node Nameand Far-end Node Namefields, respectively. These field values are taken from the IP Node Namesform showninSection 3.1.3.


32/102




Specify 5061in the Near-Endand Far-end Listen Portfields.

NoteSee Section 3.1.6regarding Near-End port values for inbound voice andG.711 fax calls.

Enter the value 1into the Far-end Network Regionfield. This value is for theIPNetwork Regiondefined in Section 3.1.5.

Enter the domestic Avaya Aura SIP EnablementServices server SIP Domain of thePrimary Avaya Aura SIP EnablementServices server (see Section 4.1) in the Far-endDomainfield. In the reference configuration, the Avaya Aura SIP EnablementServices domestic domain name (for both the Primary and Secondary Avaya Aura SIPEnablement Services servers) is avaya8500.icpiptrunksit2.gsiv.com .

The Direct IP-IP Audio Connectionsfield should be set to yto allow RTP voice pathsto be established directly between IP telephones and the Verizon Business IP Trunkservice offer. When compatible conditions exist, this allows the voice packets to followa direct path between the telephones and the network edge, potentially reducing mediaprocessor resources and network usage.

The DTMF over IPfield should remain set to the default value of rtp-payload. This

value enables Avaya Aura CommunicationManager to send DTMF tones using RFC2833.

The default values for the other fields may be used.

add signaling-group 10 Page 1 of 1SIGNALING GROUP

Group Number: 1 Group Type: sipTransport Method: tls

IMS Enabled? nNear-end Node Name: GW1-CLAN1 Far-end Node Name: Primary-SES

Near-end Listen Port: 5061 Far-end Listen Port: 5061Far-end Network Region: 1

Far-end Domain: avaya8500.icpiptrunksit2.gsiv.com

Bypass If IP Threshold Exceeded? nDTMF over IP: rtp-payload Direct IP-IP Audio Connections? y

Session Establishment Timer(min): 3 IP Audio Hairpinning? nEnable Layer 3 Test? y Direct IP-IP Early Media? n

H.323 Station Outgoing Direct Media? n Alternate Route Timer(sec): 6

Figure 24: Primary Signaling Group 10Primary Local SIP Trunk

b. Using the add signaling-group11 command, add the SecondaryLocal Signaling Group.Provisioning is the same as for Primary Local Signaling Group10 except: Specify the Secondary Avaya Aura SIP EnablementServices server (node name

Secondary-server) as the Far-end Node Name. This field value is taken from the IPNode Namesform shown inFigure 12.


33/102




add signaling-group 11 Page 1 of 1SIGNALING GROUP

Group Number: 1 Group Type: sipTransport Method: tls

IMS Enabled? n

Near-end Node Name: clan-1a03 Far-end Node Name: Secondary-SESNear-end Listen Port: 5061 Far-end Listen Port: 5061Far-end Network Region: 1

Far-end Domain: avaya8500.icpiptrunksit2.gsiv.comBypass If IP Threshold Exceeded? n

DTMF over IP: rtp-payload Direct IP-IP Audio Connections? ySession Establishment Timer(min): 3 IP Audio Hairpinning? n

Enable Layer 3 Test? y Direct IP-IP Early Media? nH.323 Station Outgoing Direct Media? n Alternate Route Timer(sec): 6

Figure 25: Secondary Local Signaling Group 11

c. Using the add trunk-group10command, add the PrimaryLocal Trunk group as follows:a. On Page 1 of the Trunk Group form:

Set the Group Typefield to sip. Choose a descriptive Group Namesuch as PrimaryLocal. Specify an available trunk access code (TAC) such as 610. Set the Service Typefield to tie. Enter 10as the Signaling Groupnumber. This value was previously

determined during the Signaling Groupconfiguration(Figure 25). Specify the Number of Membersused by this SIP trunk group (e.g. 5).

add trunk-group 10 Page 1of 21TRUNK GROUP

Group Number: 10 Group Type: sip CDR Reports: yGroup Name: Primary_Local COR: 1 TN: 1 TAC: 610

Direction: two-way Outgoing Display? nDial Access? n Night Service:Queue Length: 0Service Type: tie Auth Code? n

Signaling Group: 10Number of Members: 5

Figure 26: Primary Local Trunk Group 10Page 1

b. On Page 3 of the Trunk Group form: Set the Numbering Formatfield to public. This field specifies the format

of the calling party number sent to the far-end.

add trunk-group 10 Page 3of 21

TRUNK FEATURESACA Assignment? n Measured: noneMaintenance Tests? y

Numbering Format: publicUUI Treatment: service-providerReplace Restricted Numbers? nReplace Unavailable Numbers? n



34/102




c. On Page 4 of the Trunk Groupform: Set the Telephone Event Payload Typeto 101to match the configuration

on the Verizon Business IPCC Services suite offer. Set Support Request History? toN.

SetDiversion Header?to Y. Let all other values default

add trunk-group 10 Page 4of 21PROTOCOL VARIATIONS

Mark Users as Phone? nPrepend '+' to Calling Number? n

Send Transferring Party Information? nNetwork Call Redirection? n

Send Diversion Header? ySupport Request History? n

Telephone Event Payload Type: 101


d. Using the add trunk-group11 command, add the SecondaryLocal Trunk Group.Provisioning is the same as for Primary Local SIP Trunk 10 except on Page 1of the form: Specify a new name (e.g. Secondary_Local). Specify a new TAC code (e.g. 611) Specify Signaling Group 11.

add trunk-group 11 Page 1of 21TRUNK GROUP

Group Number: 11 Group Type: sip CDR Reports: yGroup Name: Secondary_Local COR: 1 TN: 1 TAC: 611Direction: two-way Outgoing Display? n

Dial Access? n Night Service:Queue Length: 0Service Type: tie Auth Code? n

Signaling Group: 11Number of Members: 5

Figure 29: Secondary Local Trunk Group 11Page 1

3.1.6.2 Configure Public Inbound SIP Trunks

Create Primary and Secondary signaling groups and trunk groups to support inbound voice andG.711 fax calls with the Verizon Business IP Trunk service offer. Following the proceduresdescribed in Section 3.1.6.1create the Signaling and Trunk groups indicated below using thevalues specified in Tables 6through 9. Note that the Far-End Domainfield is left blank to accept

incoming calls from any far end domain or IP address.

To discriminate between incoming voice and G.711 fax calls, the incoming voice calls will useport 5061 (default) and the G.711 fax call will use port 5062. These port values are set in theAvaya Aura SIP EnablementServices (see Section 4.1).

All other values should match those shown inSection 3.1.6.1.


35/102




3.1.6.2.1 Public Inbound Voice Signaling Groups

Signaling Group

Name

Group

Number

Far-end Node

Name

Near-end

listen-

port

Far-end

Network

Region

Far-end Domain

Primary_ Inbound_Voice 12 Primary-SES 5061 2

Secondary_Inbound_Voice 13 Secondary-SES 5061 2

Table 7: Public Inbound Voice Signaling Groups

3.1.6.2.2 Public Inbound Fax Signaling Groups

Signaling Group

Name

Group

Number

Far-end Node

Name

Near-end

listen-

port

Far-end

Network

Region

Far-end Domain

Primary_ Inbound_Fax 20 Primary-SES 5062 3

Secondary_Inbound_Fax 21 Secondary-SES 5062 3

Table 8: Public Inbound Fax Signaling Groups

3.1.6.2.3 Public Inbound Voice Trunk Groups

Trunk Group

Name

Group

Number

TAC Service Type Signaling

Group

Primary_ Inbound_Voice 12 612 public-ntwrk 12Secondary_Inbound_Voice 13 613 public-ntwrk 13

Table 9: Public Inbound Voice Signaling Groups

3.1.6.2.4 Public Inbound Fax Trunk Groups

Trunk Group

Name

Group

Number


GroupPrimary_ Inbound_Fax 20 620 public-ntwrk 20Secondary_Inbound_Fax 21 621 public-ntwrk 21

Table 10: Public Inbound Fax Signaling Groups

3.1.6.3 Configure Public Outbound Voice SIP Trunks

Create Primary and Secondary signaling groups and trunk groups to support outbound voice andG.711 fax calls with the Verizon Business IP Trunk service offer. Using the procedures describedin Section 3.1.6.1create the following Signaling and Trunk groups using the values specified inTables 10through 13below. Note that the Far-End Domainfield specifies the Fully QualifiedDomain Name (FQDN) of the Verizon network. All other values should match those shown in

Section 3.1.6.1.

3.1.6.3.1 Public Outbound Voice Signaling Groups

Signaling Group

Name

Group

Number

Far-end Node

Name

Far-end

Network

Region

Far-end Domain

Primary_ Outbound_Voice 14 Primary-SES 2 schsj1n0005.icpiptrunksit2.gsiv.com

Secondary_Outbound_Voice 15 Secondary-SES 2 schsj1n0005.icpiptrunksit2.gsiv.com


36/102




Table 11: Public Outbound Voice Signaling Groups

3.1.6.3.2 Public Outbound Fax Signaling Groups

Signaling Group

Name

Group

Number

Far-end Node

Name

Far-end

Network

Region

Far-end Domain

Primary_ Outbound_Fax 18 Primary-SES 3 schsj1n0005.icpiptrunksit2.gsiv.com

Secondary_Outbound_Fax 19 Secondary-SES 3 schsj1n0005.icpiptrunksit2.gsiv.com

Table 12: Public Outbound Fax Signaling Groups

3.1.6.3.3 Public Outbound Voice Trunk Groups

Trunk Group

Name

Group

Number


Group

Primary_ Outbound_Voice 14 614 public-ntwrk 14Secondary_Outbound_Voice 15 615 public-ntwrk 15

Table 13: Public Outbound Voice Trunk Groups

3.1.6.3.4 Public Outbound Fax Trunk Groups

Trunk Group

Name

Group

Number


Group

Primary_ Outbound_Fax 18 618 public-ntwrk 18Secondary_Outbound_Fax 19 619 public-ntwrk 19

Table 14: Public Outbound Fax Trunk Groups

3.1.7 Domestic Public Unknown Numbering

In the reference configuration, the extensions on Domestic Avaya Aura CommunicationManager use a 4 digit dialing plan using extensions 10xx, 20xx, and 40xx. The Public-Unknown-Numberingform allows Avaya Aura CommunicationManager to use these extensions as thecalling party number for outbound calls. OtherwiseAnonymousis displayed as the calling number.Each extension string is defined for theoutboundtrunk group that the extensions may use. Thesetrunks may be defined individually or in contiguous ranges.

Use the changepublic-unknown-numbering xcommand, wherexis the leading digit of the dialplan extensions (e.g. 1, 2, or 4). For example to define the extensions beginning with 1, enter thefollowing:

Set theExt Lenfield to 4.

Set the Ext Codefield to 1.This is the matching digit(s) of the extension. Setting this valueto 10would work as well.

Set the Trk Grp(s)field to 10-11 (local),12-15 (voice),and18-21 (fax).

Set the Total CPN Lenfield to 4. This is the total number of digits in the extension.

Repeat these steps for extensions beginning with 2and 4.

All provisioned public-unknown-numbering entries can be displayed by entering the commanddisplaypublic-unknown-numbering 0 as show in Figure 30.


37/102




display public-unknown-numbering 0 Page 1 of 2NUMBERING - PUBLIC/UNKNOWN FORMAT

TotalExt Ext Trk CPN CPNLen Code Grp(s) Prefix Len

Total Administered: 6Maximum Entries: 99994 1 10-15 44 1 18-21 44 2 10-15 44 2 18-21 44 4 10-15 44 4 18-21 4

Figure 30: Public-unknown-numbering Form

3.1.8 Domestic Call Routing

3.1.8.1 Outbound CallsAs described in Section 1.5, Domain Based Routing is used for outbound calls. Avaya AuraCommunication Manager has outbound SIP trunks (14, 15, 18, and 19) that specify a foreign Far-End Domain on their Signaling Group forms. Since the Avaya Aura SIP EnablementServices isnot authoritative for this foreign domain, the Avaya AuraSIP Enablement Services will do aDNS query on the foreign domain and route the call accordingly. Using this method, no Host Mapsneed to be defined in the Avaya Aura SIP EnablementServices.

The following sections describe additional Avaya Aura Communication Manager required foroutbound dialing. These include Automatic Route Selection (ARS) and Look Ahead Routing(LAR). ARS determines how an outbound call is processed and LAR allows for SIP trunk fail-over

from the Primary SIP trunks to the Secondary SIP trunks.

3.1.8.1.1 ARS

Automatic Route Selection feature is used to route calls via the SIP trunks to the Verizon BusinessIP Trunk service offer, which in turn completes the calls to the destination. In the referenceconfiguration ARS is triggered by dialing a 9 (feature access code or FAC) and then dialing thecalled number. ARS matches on the called number and sends the call to a specified route pattern.

1. Verify that the appropriate extensions are defined in the Public-Unknown-Numbering form (seeSection 3.1.7). This allows local extension to be used as the calling number.

2. Use the change dialplan analysiscommand to add 9as a feature access code (fac). Set Dialed Stringto 9. Set Total Lengthto 1. Set Call Typeto fac.


38/102




change dialplan analysis Page 1 of 12DIAL PLAN ANALYSIS TABLE

Location: all Percent Full: 1Dialed Total Call Dialed Total Call Dialed Total CallString Length Type String Length Type String Length Type

9 1 fac

Figure 31: Dialplan Analysis Form

3. Use thechange feature-access-codescommand to specify 9as the access code for externaldialing. Set Auto Route Selection (ARS)Access Code 1:to 9.

change feature-access-codes Page 1 of 8FEATURE ACCESS CODE (FAC)

Abbreviated Dialing List1 Access Code:Abbreviated Dialing List2 Access Code:Abbreviated Dialing List3 Access Code:

Abbreviated Dial - Prgm Group List Access Code:

Announcement Access Code:Answer Back Access Code:

Attendant Access Code:Auto Alternate Routing (AAR) Access Code:

Auto Route Selection (ARS) - Access Code 1: 9 Access Code 2:Automatic Callback Activation: Deactivation:

Call Forwarding Activation Busy/DA: All: Deactivation:Call Forwarding Enhanced Status: Act: Deactivation:

Call Park Access Code:Call Pickup Access Code:

CAS Remote Hold/Answer Hold-Unhold Access Code:CDR Account Code Access Code:

Change COR Access Code:Change Coverage Access Code:

Figure 32: Feature-Access-Codes FormPage 1

4. Use the change ars analysiscommand to configure the route pattern selection rule basedupon the number dialed following the ARS access digit 9. In the reference configuration,domestic outbound calls are placed to the following numbers (x represents any digit):

530352xxxx 1530352xxxx 1972728xxxx 18xxxxxxxxx 1xxx5551212 011 0

For example, to specify the 530352xxxx called number, enter the command change arsanalysis 530352and enter the following values:

Set theDialed Stringfield to 530352.


39/102




Set the Total Minfield to 10. Set the Total Maxfield to 10. Set the Route Patternfield to 16. Set the Typefield to fnpa.

Using the same procedure, specify the other called number patterns in the ARS table. Figure33shows the completed ARS table. Note that route pattern 16 was used for all outbound callsin the reference configuration.

display ars analysis 0 Page 1 of 2ARS DIGIT ANALYSIS TABLE

Location: all Percent Full: 0Dialed Total Route Call Node ANIString Min Max Pattern Type Num Reqd

0 1 1 16 op n011 11 20 16 intl n1xxx5551212 11 11 16 fnpa n1530352 11 11 16 fnpa n

18 11 11 16 fnpa n1972728 11 11 16 fnpa n530352 10 10 16 fnpa n

Figure 33: ARS Analysis Form

3.1.8.1.2 Route Patterns and LAR

Look Ahead Routing is a method for having a list of alternate trunks specified for the outboundcalls. If the outbound call attempt fails for the first trunk on the list, the subsequent trunks listedwill be tried in the order they appear on the list. LAR is specified on the route pattern form. Routepattern 16 was used in the reference configuration.

In addition to LAR, the reference configuration used Facility Restriction Level (FRL) to determinewhich outbound trunks could be used for voice and Verizon Business IP Trunk service offer G.711fax calls. Each outbound trunk is assigned an FRL on the route pattern form. In addition, all voiceextensions were provisioned with an FRL of 2 and all fax extensions were provisioned with anFRL of 1 (see Section 1.3.3). The higher the FRL, the higher the access level (e.g. an extensionwith an FRL of 1 cannot access a trunk specified with an FRL of 2. However an extension with anFRL of 2 can access trunks with FRLs of 2 and 1). In this manner G.711 fax calls are limited totrunks 18 and 19, while voice calls can use trunks 14, 15, 18, and 19.

Note- Route patterns may also be used to add or delete digits prior to sending them out thespecified trunk(s). This feature was not used in the reference configuration.

1. Use the change route-patterncommand to define the outbound SIP trunk groups includedin the route pattern that ARS selects (see Figure 34).

Primary voice trunk- This trunk will always be selected first for outbound voicecalls.

Set thefirst Grp Nofield to 14. Set the FRLfield to 2.


40/102




Set the LARfield to next. Secondary voice trunk- This trunk will be selected for voice calls only if the

voice call attempt fails over trunk 14. Set thesecond Grp Nofield to 15. Set the FRLfield to 2.

Set the LARfield to next. Primary Fax trunk- This trunk will always be selected first for outbound G.711

fax calls. It will also be used as the third choice for voice calls if attempts overtrunks 14 and 15 fail.

Set thethird Grp Nofield to 18. Set the FRLfield to 1. Set the LARfield to next.

Secondary Fax trunk- This trunk will be selected for G.711 fax calls only if theVerizon Business IP Trunk service offer G.711 fax call attempt over trunk 18 fails.It will also be used as the fourth choice for voice calls if attempts over trunks 14,15, and 18 fail.

Set thefourth Grp Nofield to 19. Set the FRLfield to 1. Leave the LARfield at none(default).

change route-pattern 16 Page 1 of 3Pattern Number: 16 Pattern Name: Outbound

SCCAN? n Secure SIP? nGrp FRLNPA Pfx Hop Toll No. Inserted DCS/ IXC

No Mrk Lmt List Del Digits QSIGDgts Intw

1: 14 2 n user2: 15 2 n user3: 18 1 n user4: 19 1 n user

5: n user6: n userBCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR0 1 2 M 4 W Request Dgts Format

Subaddress1: y y y y y n n rest next2: y y y y y n n rest next3: y y y y y n n rest next4: y y y y y n n rest none5: y y y y y n n rest none

Figure 34: Route Pattern 16Outbound Calls with LAR

3.1.8.1.3 Locations Form

One of the parameters on the locations form specifies the default outbound route pattern thatAvaya Aura CommunicationManager will use if no other route criteria are matched.

1. Use the change locationscommand to designate the default outbound SIP trunk routepattern (route pattern 16below) in the Proxy Sel Rte Patfield.


41/102




change locationsLOCATIONS

ARS Prefix 1 Required For 10-Digit NANP Calls? yLoc Name Timezone Rule NPA Proxy SelNo Offset Rte Pat1: Main + 00:00 0 16

Figure 35: Locations Form Administration

3.1.8.2 Incoming Calls

As described in Section 3.1.6.2, SIP trunks 12 and 13 are used for inbound voice calls and SIPtrunks 20 and 21 are used for inbound G.711 fax calls.

In the reference configuration the Verizon network used the voice and fax extensions defined onAvaya Aura CommunicationManager as the called number for inbound calls. Therefore noincoming digit manipulation was required. However if an incoming called number needed to bechanged to match a provisioned extension, this can be performed with the change inc-call-handling-trmt trunk-group x command, where xis the receiving trunk. For example if a called

number 8001234567 need to be mapped to extension 1001, and the call came into trunk 10, thenthe following provisioning would be used:

Use the change inc-call-handling-trmt trunk-group10command to administer thisassignment.

Leavepublic-ntwrk (default) in the Service/Featurefield.

Enter 10into the Called Lenfield to match the length of the incoming digits.

Enter 8001234567into the Called Numberfield as the digit pattern to be matched.

Enter 10into the Delfield as the number of digits that should be deleted from the end of

the incoming digits.

Enter 1001into the Insertfield.

change inc-call-handling-trmt trunk-group 10 Page 1 of 30INCOMING CALL HANDLING TREATMENT

Service/ Called Called Del InsertFeature Len Numberpublic-ntwrk 10 8001234567 10 1001

Figure 36: Example - Change Incoming Call Handling Treatm

Documents

SES and Comunication Manager