T Mobile Extension and ISDN-PRI Trunks

To view this page ensure that Adobe Flash Player version 9.0.124 or greater is installed.

Please login or register to make a comment!

Avaya Solution & Interoperability Test Lab Application Notes for Configuring Avaya one-X" Mobile and Avaya Communication Manager with AT&T Mobile Extension and ISDN-PRI Trunks 3 Issue 1.0 Abstract These Application Notes describe the steps for configuring Avaya one-X" Mobile and Avaya Communication Manager with AT&T Mobile Extension and ISDN-PRI trunks. Avaya one- X" Mobile is an enterprise mobility solution that allows users roaming or otherwise located away from the office to access enterprise telephony and unified communications services. More specifically, users can utilize the Avaya one-X" Mobile Unified Communication (UC) client application running on their mobile phones to manage the routing of inbound business calls, place outbound business calls, manage corporate voice messages, and search the corporate directory.

The AT&T Mobile Extension offer is an integrated solution that provides all the necessary components to enable wireless-PBX integration at the enterprise, including a cost control capability for enterprise wireless usage. The AT&T Mobile Extension offer is based on the combination of enterprise communications products, AT&T wireless handsets, and AT&T wireless enterprise rate plans. AT&T is a member of the Avaya DevConnect Service Provider program.

Information in these Application Notes has been obtained through compliance testing and additional technical discussions. Testing was conducted via ... more. less.

the DevConnect Program at the Avaya Solution and Interoperability Test Lab. RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 1 of 79 AV1XM_ATTME RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 2 of 79 AV1XM_ATTME TABLE OF CONTENTS 1. Introduction................................................................................................................ .............4 1.1. Sample Configuration.....................................................................................................5 1.2. Call Flows................................................................................................................ .......7 2. Equipment and Software Validated......................................................................................14 3. Avaya Communication Manager..........................................................................................15 3.1. System Parameters........................................................................................................1 5 3.2. Dial Plan and Feature Access Codes............................................................................19 3.3. Class of Restriction and Class of Service.....................................................................21 3.4. ISDN-PRI Trunk...........................................................................................................2 3 3.5. PSTN Call Routing.......................................................................................................24 3.5.1. Outbound Calls.....................................................................................................24 3.5.2. Inbound Calls........................................................................................................27 3.6. CTI Connection with Avaya AE Services....................................................................28 3.7. Voicemail................................................................................................................. .....29 3.8. Configuration Set......................................................................................................... .29 3.9. Configuration for Avaya one-X" Mobile Users.........................................................30 3.10. Allow SAT Access for Avaya one-X" Mobile.......................................................32 4. Avaya Application Enablement (AE) Services.....................................................................35 4.1. Licensed Features......................................................................................................... .35 4.2. DMCC and JTAPI Users..............................................................................................38 4.3. Enabling DMCC Ports..................................................................................................40 4.4. Switch Connections and CTI Connections...................................................................41 4.5. Security Database......................................................................................................... .44 4.6. [Optional] Dial Plan Settings........................................................................................46 4.7. SMS....................................................................................................................... ........48 4.8. Restart Avaya AE Services Server...............................................................................48 5. Avaya Modular Messaging with MSS..................................................................................50 6. Microsoft Active Directory.................................................................................................. .53 7. Avaya one-X" Mobile......................................................................................................... 55 7.1. Licenses.................................................................................................................. .......55 7.2. Profiles.................................................................................................................. ........55 7.2.1. Provisioning Profile..............................................................................................55 7.2.2. CTI Profile............................................................................................................5 7 7.2.3. Voicemail Profile..................................................................................................59 7.2.4. Corporate Directory Profile..................................................................................61 7.2.5. Class of Service.....................................................................................................63 7.3. CTI Ports................................................................................................................. ......68 7.4. Import Users.............................................................................................................. ....69 7.5. Direct Call PBX Numbers............................................................................................70 8. Interoperability Compliance Testing....................................................................................72 8.1. General Test Approach.................................................................................................72 8.2. Test Results.............................................................................................................. .....73 9. Verification Steps.......................................................................................................... ........73 9.1. Verification Tests........................................................................................................ ..73 RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 3 of 79 AV1XM_ATTME 9.2. Troubleshooting Tools..................................................................................................77 10. Support.................................................................................................................... ..........77 11. Conclusion................................................................................................................. .......77 12. References................................................................................................................. ........78 RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 4 of 79 AV1XM_ATTME 1. Introduction These Application Notes describe the steps for configuring Avaya one-X" Mobile and Avaya Communication Manager with AT&T Mobile Extension and ISDN-PRI trunks. Avaya one-X" Mobile is an enterprise mobility solution that allows users roaming or otherwise located away from the office to access enterprise telephony and unified communications services. More specifically, users can: " Manage the routing of inbound business calls 1 3 Using the Avaya one-X" Mobile UC client application (running on the mobile phone), users can select the destinations, e.g., office phone, mobile phone, home phone, other landline phones, etc., to which inbound business calls are routed. The users can then answer inbound business calls at any of the selected destinations. " Place outbound business calls 3 Using the Avaya one-X" Mobile UC client application, users can place outbound business calls from any phone, e.g., mobile phone, home phone, other landline phones, etc. Since these business calls are placed through the Avaya Communication Manager, the user 9s business number is presented as the calling party number. " Switch between using the office phone and mobile phone on active calls 3 Users can move active calls from the office phone to the mobile phone, and vice versa. Note: SIP phones are not supported in the Avaya one-X" Mobile solution. " Manage corporate voice messages 3 users can view, listen to, save, and delete corporate voice messages from the Avaya one-X" Mobile UC client application. " Search the corporate directory 3 Using the Avaya one-X" Mobile UC client application, users can search the corporate directory for the contact information of other enterprise users. The AT&T Mobile Extension offer is an integrated solution that provides all the necessary components to enable wireless-PBX integration at the enterprise, including a cost control capability for enterprise wireless usage. The AT&T Mobile Extension offer is based on the combination of enterprise communications products, AT&T wireless handsets, and AT&T wireless enterprise rate plans, as follows: " Enterprise PBX 3 namely, Avaya Communication Manager. " Enterprise Fixed Mobility Convergence (FMC) components 3 namely, Avaya one-X" Mobile and supporting components. " AT&T certified wireless handset(s). 1 The term cbusiness call d is referred to as a call established through the enterprise voice communications system, i.e., Avaya Communication Manager, as opposed to a direct inbound call to the user 9s mobile phone number or an outbound call dialed directly from the user 9s mobile phone native dialer. RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 5 of 79 AV1XM_ATTME " Wireless handset software clients 3 namely, Avaya one-X" Mobile UC client applications. " AT&T Value-Added Feature for special FMC wireless usage billing. 1.1. Sample Configuration The sample configuration used in these Application Notes is shown in Figure 1 . The Avaya one-X" Mobile solution consists of several components: " Avaya Communication Manager provides the enterprise voice communications services. In this configuration, Avaya Communication Manager runs on an Avaya S8710 Media Server. This solution is extensible to other Avaya S8xxx Media Servers. " The Avaya Media Gateway provides the physical interfaces and resources for enterprise voice communications. In this configuration, an Avaya G650 Media Gateway is used. This solution is extensible to other Avaya Media Gateways. " Avaya Application Enablement (AE) Services provides the Computer Telephony Integration (CTI) interfaces to allow CTI applications such as Avaya one-X" Mobile to monitor and invoke voice communications services on Avaya Communication Manager. " Avaya Modular Messaging provides the corporate voice messaging capabilities for enterprise users. " Avaya one-X" Mobile interacts with Avaya AE Services to access enterprise voice communications services on Avaya Communication Manager, with Avaya Modular Messaging to access corporate voice messaging services, and with Microsoft Active Directory to access the corporate directory. Avaya one-X" Mobile may be implemented on a single server or, as in Figure 1 , a pair of servers (one internal server inside the corporate firewall, one external server outside the corporate firewall). Consult [1] for further details on the various Avaya one-X" Mobile topology configurations. " The Avaya Communication Manager phones are the coffice d / cdesk d phones used by enterprise users in the office. " The AT&T mobile phones are the enterprise users 9 mobile phones, typically used away the office. " The external PSTN phones are typically landline phones located away from the office, e.g., home phones, other landline phones, etc. With the Avaya one-X" Mobile solution, enterprise users may elect to receive their business calls at such phones, as well as use such phones in making outbound business calls. " Microsoft Active Directory contains the enterprise corporate directory. " A PSTN trunk is used for voice communications between the enterprise and the PSTN. In this configuration, an ISDN-PRI trunk is used. 123 456 789 * 0# ABCDEF MNO JKL GHI PQRSWXYZ TUV SpeakerMuteHold RedialTransferRing 6416D+M MenuExitPrevNext OK PHONE MESSAGE CONTACTSMENUCALL LOG VOLUME ABCDEF JKLMNO GHI 123 456 TUVWXYZ PQRS 789 * [ 0# .,@ MUTE SPEAKER HEADSET FORWARD COMPACT COMPACT COMPACT COMPACT COMPACT COMPACT COMPACT Figure 1: Sample Avaya one-X" Mobile with AT&T Mobile Extension Solution Configuration RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 6 of 79 AV1XM_ATTME 1.2. Call Flows To understand how the Avaya one-X" Mobile solution manages outbound and inbound calls, several call flows are described in this section. The first call scenario illustrated in Figure 2 is an inbound PSTN call to an enterprise user enabled with Avaya one-X" Mobile. The call arrives via a public trunk at Avaya Communication Manager, and due to the Avaya one-X" Mobile integration, rings all of the endpoints, e.g., office phone, mobile phone, home phone, other landline phones, etc., selected by the user as receive ( cSend Calls d) destinations. 1. The inbound PSTN call arrives on Avaya Communication Manager and is routed to an Avaya Communication Manager extension. 2. Since Avaya one-X" Mobile is monitoring calls (via Avaya AE Services) on the called extension, Avaya one-X" Mobile is aware of the inbound call and looks up the receive destinations that the Avaya one-X" Mobile user associated with the called extension has selected for receiving inbound calls. Avaya one-X" Mobile then instructs Avaya Communication Manager (via Avaya AE Services) to route the call to those receive destinations. In these Application Notes, the calls routed to those receive destinations are referred to as simultaneous ring, or cSimulring d, calls. The called user may then answer the call at a) the office phone; b) the mobile phone; or c) other selected receive destinations. Once the user answers at any one of those destinations, the user is connected to the caller and ringing stops on the other receive destinations. PSTN Avaya Communication Manager Avaya one-X Mobile AT&T Mobile Network AT&T Mobile Phone (Called Party Receive Destination) 2b 1 PSTN Phone (Calling Party) Internet 2 OK PHONE MESSAGE CONTACTSMENUCALL LOG VOLUME ABCDEF JKLMNO GHI 123 456 TUVWXYZ PQRS 789 * [ 0# .,@ MUTE SPEAKER HEADSET FORWARD 2a Office Phone (Called Party Receive Destination ) PSTN Phone (Called Party Receive Destination) 2c Figure 2: Inbound PSTN Call Scenario RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 7 of 79 AV1XM_ATTME The second call scenario illustrated in Figure 3 is similar to the first call scenario, except that the call is an internal call from another Avaya Communication Manager phone, e.g., an intra-office call. 1. An Avaya Communication Manager phone calls the office extension of an enterprise user enabled with Avaya one-X" Mobile. 2. Since Avaya one-X" Mobile is monitoring calls (via Avaya AE Services) on the called extension, Avaya one-X" Mobile is aware of the inbound call and looks up the receive destinations that the Avaya one-X" Mobile user associated with the called extension has selected for receiving inbound calls. Avaya one-X" Mobile then instructs Avaya Communication Manager (via Avaya AE Services) to route the call to those receive destinations. In these Application Notes, the calls routed to those receive destinations are referred to as simultaneous ring, or cSimulring d, calls. The called user may then answer the call at a) the office phone; b) the mobile phone; or c) other selected receive destinations. Once the user answers at any one of those destinations, the user is connected to the caller and ringing stops on the other receive destinations. OK PHONE MESSAGE CONTACTSMENUCALL LOG VOLUME ABCDEF JKLMNO GHI 123 456 TUVWXYZ PQRS 789 * [ 0# .,@ MUTE SPEAKER HEADSET FORWARD OK PHONE MESSAGE CONTACTSMENUCALL LOG VOLUME ABCDEF JKLMNO GHI 123 456 TUVWXYZ PQRS 789 * [ 0# .,@ MUTE SPEAKER HEADSET FORWARD Figure 3: Inbound Internal Call Scenario RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 8 of 79 AV1XM_ATTME The third call scenario illustrated in Figure 4 is a business call from a user 9s mobile phone to a PSTN number, where the call is initiated from the Avaya one-X" Mobile UC client application running on the user 9s mobile phone. 1. Using the Avaya one-X" Mobile UC client application, the user enters a request to make a business call between the mobile phone and a PSTN number, e.g., a customer 9s number. The request is delivered over the Internet via HTTP/HTTPS to Avaya one-X" Mobile. 2. Avaya one-X" Mobile decomposes the request into parts. First, Avaya one-X" Mobile instructs Avaya Communication Manager (via Avaya AE Services) to place a call to the calling user 9s mobile phone number. In these Application Notes, this leg of the overall business call is referred to as the cCallback d call. The calling user answers the cCallback d call. 3. Avaya one-X" Mobile then instructs Avaya Communication Manager (via Avaya AE Services) to place a call to the destination PSTN number. The destination PSTN phone answers. 4. Avaya one-X" Mobile instructs Avaya Communication Manager to merge the two call legs, thereby connecting the calling user (on the mobile phone) to the destination PSTN phone. Figure 4: Outbound PSTN Call From Mobile Phone Call Scenario RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 9 of 79 AV1XM_ATTME The fourth call scenario illustrated in Figure 5 is similar to the third call scenario, except that the destination number is another Avaya Communication Manager extension, e.g., another office extension. 1. Using the Avaya one-X" Mobile UC client application, the user enters a request to make a business call between the mobile phone and another Avaya Communication Manager extension. The request is delivered over the Internet via HTTP/HTTPS to Avaya one- X" Mobile. 2. Avaya one-X" Mobile decomposes the request into parts. First, Avaya one-X" Mobile instructs Avaya Communication Manager (via Avaya AE Services) to place a call to the calling user 9s mobile phone number. As in the third call scenario, this leg of the overall business call is referred to as the cCallback d call. The calling user answers the cCallback d call. 3. Avaya one-X" Mobile then instructs Avaya Communication Manager (via Avaya AE Services) to place a call to the destination extension. The destination extension answers. 4. Avaya one-X" Mobile instructs Avaya Communication Manager to merge the two call legs, thereby connecting the calling user (on the mobile phone) to the destination extension Note that if the destination extension is also that of another Avaya one-X" Mobile user, then as in the first call scenario, the called user 9s selected receive destinations will simultaneously ring, and the called user may answer the call at his/her office phone, mobile phone, or other selected receive destinations. OK PHONE MESSAGE CONTACTSMENUCALL LOG VOLUME ABCDEF JKLMNO GHI 123 456 TUVWXYZ PQRS 789 * [ 0# .,@ MUTE SPEAKER HEADSET FORWARD Figure 5: Outbound Internal Call From Mobile Phone Call Scenario RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 10 of 79 AV1XM_ATTME The fifth call scenario illustrated in Figure 6 is a business call from a user 9s landline phone, i.e., not the user 9s office or mobile phone, to another PSTN number, where the call is initiated from the Avaya one-X" Mobile UC client application running on the user 9s mobile phone. 1. Using the Avaya one-X" Mobile UC client application, the user enters a request to make a business call between the user 9s landline phone, e.g., home phone, hotel phone, phones in conference rooms, etc., and another PSTN number, e.g., a customer 9s number. The request is delivered over the Internet via HTTP/HTTPS to Avaya one-X" Mobile. 2. Avaya one-X" Mobile decomposes the request into parts. First, Avaya one-X" Mobile instructs Avaya Communication Manager (via Avaya AE Services) to place a call to the calling user 9s landline phone number. As in the third call scenario, this leg of the overall business call is referred to as the cCallback d call. The calling user answers the cCallback d call. 3. Avaya one-X" Mobile then instructs Avaya Communication Manager (via Avaya AE Services) to place a call to the destination PSTN number. The destination PSTN phone answers. 4. Avaya one-X" Mobile instructs Avaya Communication Manager to merge the two call legs, thereby connecting the calling user (on the landline phone) to the destination PSTN phone. 1 PSTN Avaya Communication Manager Avaya one-X Mobile AT&T Mobile Network Avaya one-X Mobile UC Client on AT&T Mobile Phone 3 PSTN Phone (Called Party) Internet 4 2 3 4 2 PSTN Phone (Calling Party) Figure 6: Outbound Call From Landline Phone Call Scenario RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 11 of 79 AV1XM_ATTME The sixth call scenario illustrated in Figure 7 is one where an active business call on a user 9s office phone is moved to the user 9s mobile phone. 1. The user is on an active business call on his/her desk phone. 2. The user then decides to move the call to his/her mobile phone by pressing the cextend call d button on his/her office phone. Avaya Communication Manager places a call to the user 9s mobile phone number. The user answers at the mobile phone. 3. Avaya Communication Manager connects the user to the other party on the call, and the user on-hooks the office phone. The call appearance on the office phone is still available should the user decide to return to the office phone (see seventh call scenario below). OK PHONE MESSAGE CONTACTSMENUCALL LOG VOLUME ABCDEF JKLMNO GHI 123 456 TUVWXYZ PQRS 789 * [ 0# .,@ MUTE SPEAKER HEADSET FORWARD Figure 7: Move Call From Office Phone to Mobile Phone Call Scenario RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 12 of 79 AV1XM_ATTME The seventh call scenario illustrated in Figure 8 is one where an active business call on a user 9s mobile phone is moved to the user 9s office phone. 1. The user is on an active business call on his/her mobile phone. 2. The user then returns to his/her office, and sees that the call is also available on the office phone. The user presses the corresponding call appearance on his/her office phone, and the office phone is connected to the other party on the call. 3. The user disconnects the mobile phone. If the user decides to move the call back to his/her mobile phone, then the user would have to carry out the sixth call scenario above. OK PHONE MESSAGE CONTACTSMENUCALL LOG VOLUME ABCDEF JKLMNO GHI 123 456 TUVWXYZ PQRS 789 * [ 0# .,@ MUTE SPEAKER HEADSET FORWARD Figure 8: Move Active Call From Mobile Phone to Office Phone Call Scenario RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 13 of 79 AV1XM_ATTME RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 14 of 79 AV1XM_ATTME 2. Equipment and Software Validated The following equipment and software was used for the sample configuration described in these Application Notes. Component Version Avaya Avaya one-X" Mobile (run on Microsoft Windows Server 2003 R2 Enterprise Edition Service Pack 2) 1.1.1 (1.0.0.0.242) Avaya one-X" Mobile UC Client Application Apple iPhone 3G (Safari web browser client) N/A BlackBerry 8700c 1.1.22 BlackBerry 8800 1.1.22 Samsung BlackJack II (i617) 1.1.2 Avaya S8710 Server Avaya Communication Manager 5.1.1 (R015x.01.1.415.1 with update 16732) Avaya G650 Media Gateway TN2312BP IP Server Interface (IPSI) HW03 FW044 TN799DP Control-LAN (C-LAN) HW01 FW026 TN464GP DS1 Interface HW06 FW022 TN2224CP Digital Line HW08 FW015 TN2602AP IP Media Resource 320 (MedPro) HW02 FW041 Avaya 9630 IP Telephone Avaya one-X" Deskphone Edition H.323 Release 2.0 Avaya 9640 IP Telephone Avaya one-X" Deskphone Edition H.323 Release 2.0 Avaya 4610SW IP Telephone 2.9 Avaya 6416D+M Digital Telephone - Avaya S8500B Server Avaya Application Enablement Services 4.2.1 Patch 1 (r4-2-1-20-5-0) with G3PD Hot Fix (libg3pd.so.4.2.1_Build_418) Avaya Modular Messaging on Avaya S3500 Messaging Servers (MAS and MSS) 4.0 with Service Pack 1 (7.2.642.4) Microsoft Active Directory on Microsoft Windows Server 2003 R2 Enterprise Edition Service Pack 2 5.2.3790.3959 Table 1: Equipment and Software Versions RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 15 of 79 AV1XM_ATTME 3. Avaya Communication Manager This section describes the administration steps for Avaya Communication Manager in support of integration with Avaya one-X" Mobile. The steps are performed from the Avaya Communication Manager System Access Terminal (SAT) interface. These Application Notes assume that basic Avaya Communication Manager administration has already been performed. Consult [3] for further details if necessary. 3.1. System Parameters This section reviews the Avaya Communication Manager licenses and features that are required for the sample configuration described in these Application Notes. For required licenses that are not enabled in the steps that follow, contact an authorized Avaya account representative to obtain the licenses. 1. Enter the display system-parameters customer-options command. On Page 4 of the system-parameters special-applications form, verify that (SA8481) 3 Replace Calling Party Number with ASAI ANI is set to c y d. display system-parameters special-applications Page 4 of 8 SPECIAL APPLICATIONS (SA8481) - Replace Calling Party Number with ASAI ANI? y (SA8500) - Expanded UUI Display Information? n (SA8506) - Altura Interoperability (FIPN)? n (SA8507) - H245 Support With Other Vendors? y (SA8508) - Multiple Emergency Access Codes? n (SA8510) - NTT Mapping of ISDN Called-Party Subaddress IE? n (SA8517) - Authorization Code By COR? n (SA8518) - Automatic Callback with Called Party Queuing? n (SA8520) - Hoteling Application for IP Terminals? n (SA8558) - Increase Automatic MWI & VuStats (S8700 only)? n (SA8567) - PHS X-Station Mobility over IP? n (SA8569) - No Service Observing Tone Heard by Agent? n (SA8573) - Call xfer via ASAI on CAS Main? n (SA8582) - PSA Location and Display Enhancements? n (SA8587) - Networked PSA via QSIG Diversion? n (SA8589) - Background BSR Polling? n (SA8608) - Increase Crisis Alert Buttons (S8700 only)? n (SA8621) - SCH Feature Enhancements? N Figure 9: System-Parameters Special-Applications Form 3 Page 4 RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 16 of 79 AV1XM_ATTME 2. On Page 7 of the system-parameters special-applications form, verify that (SA8931) 3 Send IE with EC500 Extension Number is set to c y d. change system-parameters special-applications Page 7 of 8 SPECIAL APPLICATIONS (SA8888) - Per Station Music On Hold? n (SA8889) - Verizon VoiceGenie SIP MIME Message Bodies? n (SA8891) - Verizon VoiceGenie SIP Headers? n (SA8896) - IP Softphone Lamp Control? n (SA8900) - Support for NTT Call Screening? n (SA8904) - Location Based Call Type Analysis? n (SA8911) - Expanded Public Unknown Table? n (SA8917) - LSP Redirect using special coverage point? n (SA8927) - Increase Paging Groups? n (SA8928) - Display Names on Bridged Appearance Labels? n (SA8931) - Send IE with EC500 Extension Number? y (SA8942) - Multiple Unicode Message File Support? n (SA8944) - Multiple Logins for Single IP Address? n (SA8946) - Site Data Expansion? n (SA8957) - PIN Checking for Private Calls? n (SA8958) - Increase BSR Polling/Interflow Pairs to 40000? n (SA8965) - SIP Shuffling with SDP? n (SA8967) - Mask CLI and Station Name for QSIG/ISDN Calls? n (SA8972) - Overwrite Calling Identity? n Figure 10: System-Parameters Special Applications Form 3 Page 7 3. Enter the display system-parameters customer-options command. On Page 1 of the system-parameters customer-options form, verify that the Maximum Off-PBX Telephones 3 EC500 number is sufficient for the number of expected Avaya one-X" Mobile users (one EC500 license per Avaya one-X" Mobile user). display system-parameters customer-options Page 1 of 11 OPTIONAL FEATURES G3 Version: V15 Software Package: Standard Location: 1 RFA System ID (SID): 1 Platform: 6 RFA Module ID (MID): 1 USED Platform Maximum Ports: 44000 286 Maximum Stations: 36000 101 Maximum XMOBILE Stations: 0 0 Maximum Off-PBX Telephones - EC500: 1000 0 Maximum Off-PBX Telephones - OPS: 36000 15 Maximum Off-PBX Telephones - PBFMC: 0 0 Maximum Off-PBX Telephones - PVFMC: 0 0 Maximum Off-PBX Telephones - SCCAN: 0 0 Figure 11: System-Parameters Customer-Options Form 3 Page 1 RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 17 of 79 AV1XM_ATTME 4. On Pages 3, 4, and 9 of the system-parameters customer-options form, verify that the bolded fields in the following screenshots are set to c y d. display system-parameters customer-options Page 3 of 11 OPTIONAL FEATURES Abbreviated Dialing Enhanced List? y Audible Message Waiting? n Access Security Gateway (ASG)? n Authorization Codes? n Analog Trunk Incoming Call ID? y CAS Branch? n A/D Grp/Sys List Dialing Start at 01? y CAS Main? n Answer Supervision by Call Classifier? y Change COR by FAC? n ARS? y Computer Telephony Adjunct Links? y ARS/AAR Partitioning? y Cvg Of Calls Redirected Off-net? y ARS/AAR Dialing without FAC? y DCS (Basic)? y ASAI Link Core Capabilities? y DCS Call Coverage? y ASAI Link Plus Capabilities? y DCS with Rerouting? y Async. Transfer Mode (ATM) PNC? n Async. Transfer Mode (ATM) Trunking? n Digital Loss Plan Modification? y ATM WAN Spare Processor? n DS1 MSP? n ATMS? n DS1 Echo Cancellation? y Attendant Vectoring? y Figure 12: System-Parameters Customer-Options Form 3 Page 3 display system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable 'dadmin' Login? y Enhanced Conferencing? y ISDN Feature Plus? y Enhanced EC500? y ISDN/SIP Network Call Redirection? y Enterprise Survivable Server? n ISDN-BRI Trunks? y Enterprise Wide Licensing? n ISDN-PRI? y ESS Administration? n Local Survivable Processor? n Extended Cvg/Fwd Admin? y Malicious Call Trace? n External Device Alarm Admin? n Media Encryption Over IP? n Five Port Networks Max Per MCC? n ode Code for Centralized Voice Mail? n Flexible Billing? n Forced Entry of Account Codes? n Multifrequency Signaling? y Global Call Classification? n Multimedia Call Handling (Basic)? y Hospitality (Basic)? y Multimedia Call Handling (Enhanced)? y Hospitality (G3V3 Enhancements)? n Multimedia IP SIP Trunking? n IP Trunks? y IP Attendant Consoles? n Figure 13: System-Parameters Customer-Options Form 3 Page 4 RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 18 of 79 AV1XM_ATTME display system-parameters customer-options Page 9 of 11 ASAI ENHANCED FEATURES Adjunct Routing? y CTI Stations? y Increased Adjunct Route Capacity? n Phantom Calls? y ASAI PROPRIETARY FEATURES Agent States? n Figure 14: System-Parameters Customer-Options Form 3 Page 9 5. On Page 10 of the system-parameters customer-options form, verify that there are sufficient IP_API_A licenses. display system-parameters customer-options Page 10 of 11 MAXIMUM IP REGISTRATIONS BY PRODUCT ID Product ID Rel. Limit Used IP_API_A : 1000 0 IP_API_B : 1000 0 IP_API_C : 1000 0 Figure 15: System-Parameters Customer-Options Form 3 Page 10 6. Enter the change system-parameters features command. On Page 4 of the system- parameters features form, set Trunk-to-Trunk Transfer to c all d. change system-parameters features Page 1 of 17 FEATURE-RELATED SYSTEM PARAMETERS Self Station Display Enabled? n Trunk-to-Trunk Transfer: all Automatic Callback - No Answer Timeout Interval (rings): 3 Call Park Timeout Interval (minutes): 10 Off-Premises Tone Detect Timeout Interval (seconds): 20 AAR/ARS Dial Tone Required? y Music/Tone on Hold: none Music (or Silence) on Transferred Trunk Calls? no DID/Tie/ISDN/SIP Intercept Treatment: attd Internal Auto-Answer of Attd-Extended/Transferred Calls: transferred Automatic Circuit Assurance (ACA) Enabled? n Abbreviated Dial Programming by Assigned Lists? n Auto Abbreviated/Delayed Transition Interval (rings): 2 Protocol for Caller ID Analog Terminals: Bellcore Display Calling Number for Room to Room Caller ID Calls? n Figure 16: System-Parameters Features Form 3 Page 1 RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 19 of 79 AV1XM_ATTME 3.2. Dial Plan and Feature Access Codes This section briefly describes the dial plan requirements and feature access codes for the configuration described in these Application Notes. 1. Enter the change dialplan analysis command to provision the dial plan. Note the following dialed strings administered in Figure 17 : " 3-digit dial access codes (indicated with a Call Type of c dac d) beginning with the digits c1 d 3 Trunk Access Codes (TACs) defined for trunk groups in this configuration conform to this format. " 5-digit extensions (indicated with a Call Type of c ext d) beginning with the digit c2 d 3 extensions for stations, CTI ports, CTI links, voicemail access, etc. in this configuration conform to this format. " Single-digit ( c9 d) and 3-digit ( c* d and c# d) feature access codes (indicated with a Call Type of c fac d) 3 These dialed strings will be interpreted as Feature Access Codes (FACs). In this configuration, c9 d is used as the user-dialed prefix for outbound calls to the PSTN, and 3-digit codes beginning with c* d and c# d are used by Avaya one-X" Mobile to invoke features described in the next step. display dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Location: all Percent Full: 2 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 1 3 dac 2 5 ext 8 1 fac 9 1 fac * 3 fac # 3 fac Figure 17: Dialplan Analysis Form 2. Enter the change feature-access-codes command. On Pages 1, 2, and 3 of the feature- access-codes form, provision access codes that are valid under the administered dial plan in Step 1 for the following features: " Auto Route Selection (ARS) - Access Code 1 3 In this configuration, ARS is used for routing calls to the PSTN, and the access code ( c 9 d in Figure 18 ) entered here is used as the user-dialed prefix for outbound calls. See Section 3.5.1 for further details on outbound call routing administration. " EC500 Self-Administration Access Code 3 Avaya one-X" Mobile uses this FAC to provision a mapping in Avaya Communication Manager between a user 9s office extension and the user 9s mobile phone number. " Enhanced EC500 Activation and Deactivation - Avaya one-X" Mobile uses this FAC on a per call basis to activate/deactivate cSimulring d calls to a user 9s mobile phone number. RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 20 of 79 AV1XM_ATTME " Send All Calls Activation and Deactivation - Avaya one-X" Mobile uses this FAC to activate/deactivate the sending of a user 9s inbound calls to call coverage, i.e., to the user 9s corporate voice mailbox. change feature-access-codes Page 1 of 9 FEATURE 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: 8 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: Contact Closure Open Code: Close Code: Figure 18: Feature-Access-Codes Form 3 Page 1 change feature-access-codes Page 2 of 9 FEATURE ACCESS CODE (FAC) Contact Closure Pulse Code: Data Origination Access Code: Data Privacy Access Code: Directed Call Pickup Access Code: Directed Group Call Pickup Access Code: Emergency Access to Attendant Access Code: EC500 Self-Administration Access Codes: *70 Enhanced EC500 Activation: *71 Deactivation: #71 Enterprise Mobility User Activation: Deactivation: Extended Call Fwd Activate Busy D/A All: Deactivation: Extended Group Call Pickup Access Code: Facility Test Calls Access Code: Flash Access Code: Group Control Restrict Activation: Deactivation: Hunt Group Busy Activation: Deactivation: ISDN Access Code: Last Number Dialed Access Code: Leave Word Calling Message Retrieval Lock: Leave Word Calling Message Retrieval Unlock: Figure 19: Feature-Access-Codes Form 3 Page 2 RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 21 of 79 AV1XM_ATTME change feature-access-codes Page 3 of 9 FEATURE ACCESS CODE (FAC) Leave Word Calling Send A Message: Leave Word Calling Cancel A Message: Limit Number of Concurrent Calls Activation: Deactivation: Malicious Call Trace Activation: Deactivation: Meet-me Conference Access Code Change: PASTE (Display PBX data on Phone) Access Code: Personal Station Access (PSA) Associate Code: Dissociate Code: Per Call CPN Blocking Code Access Code: Per Call CPN Unblocking Code Access Code: Priority Calling Access Code: Program Access Code: Refresh Terminal Parameters Access Code: Remote Send All Calls Activation: Deactivation: Self Station Display Activation: Send All Calls Activation: *80 Deactivation: #80 Station Firmware Download Access Code: Figure 20: Feature-Access-Codes Form 3 Page 3 3.3. Class of Restriction and Class of Service This section briefly discusses the Class of Restriction (COR) and Class of Service (COS) used in this configuration. In general, COR and COS are used to define and restrict call and feature privileges. Note that there can be different customer reasons and strategies in administering and assigning various Classes of Restriction and Classes of Service in actual deployments, but that is beyond the scope of these Application Notes. Consult [4] for further details. For simplicity, a single COR and single COS is used throughout this configuration. Enter the change cor r command, where r is the number of an unused Class of Restriction. On Page 1 of the cor form, assign an FRL (Facility Restriction Level) between 0 and 7, with 0 being the least restrictive, and set Calling Party Restriction and Called Party Restriction to c none d. For simplicity, an FRL of 0 is used in this configuration. RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 22 of 79 AV1XM_ATTME change cor 1 Page 1 of 23 CLASS OF RESTRICTION COR Number: 1 COR Description: FRL: 0 APLT? y Can Be Service Observed? y Calling Party Restriction: none Can Be A Service Observer? y Called Party Restriction: none Partitioned Group Number: 1 Forced Entry of Account Codes? n Priority Queuing? n Direct Agent Calling? y Restriction Override: none Facility Access Trunk Test? n Restricted Call List? n Can Change Coverage? n Access to MCT? y Fully Restricted Service? n Group II Category For MFC: 7 Hear VDN of Origin Annc.? y Send ANI for MFE? n Add/Remove Agent Skills? n MF ANI Prefix: Automatic Charge Display? n Hear System Music on Hold? y PASTE (Display PBX Data on Phone)? n Can Be Picked Up By Directed Call Pickup? y Can Use Directed Call Pickup? y Group Controlled Restriction: inactive Figure 21: COR Form 3 Page 1 COS 1 is used in this configuration (may vary according to customer requirements). Consult [3] for descriptions of the COS feature permissions. change cos Page 1 of 2 CLASS OF SERVICE 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Auto Callback n y y n y n y n y n y n y n y n Call Fwd-All Calls n y n y y n n y y n n y y n n y Data Privacy n y n n n y y y y n n n n y y y Priority Calling n y n n n n n n n y y y y y y y Console Permissions n y n n n n n n n n n n n n n n Off-hook Alert n n n n n n n n n n n n n n n n Client Room n n n n n n n n n n n n n n n n Restrict Call Fwd-Off Net n n y y y y y y y y y y y y y y Call Forwarding Busy/DA n y n n n n n n n n n n n n n n Personal Station Access (PSA) n n n n n n n n n n n n n n n n Extended Forwarding All n y n n n n n n n n n n n n n n Extended Forwarding B/DA n y n n n n n n n n n n n n n n Trk-to-Trk Transfer Override n y n n n n n n n n n n n n n n QSIG Call Offer Originations n n n n n n n n n n n n n n n n Contact Closure Activation n n n n n n n n n n n n n n n n Figure 22: COS Form RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 23 of 79 AV1XM_ATTME 3.4. ISDN-PRI Trunk In this configuration, an ISDN-PRI trunk is used for both inbound Direct Inward Dialing (DID) calls from, and outbound calls to, the PSTN. Since the ISDN-PRI trunk administration can vary according to customer needs and the ISDN-PRI trunk service offered in a given locale, consult [3] for details on ISDN-PRI trunk administration options. This section briefly describes the administration options relevant to this configuration. Enter the change trunk-group t command, where t is the number of an ISDN-PRI trunk group. On Pages 2 and 3 of the trunk-group form, set the bolded fields in Figure 23 and Figure 24 to the values shown. change trunk-group 99 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical Digital Loss Group: 13 Incoming Calling Number - Delete: Insert: Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? y Answer Supervision Timeout: 0 Administer Timers? n CONNECT Reliable When Call Leaves ISDN? n Figure 23: Trunk-Group Form 3 Page 2 change trunk-group 99 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: public Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y Network Call Redirection: none Hold/Unhold Notifications? y Send UUI IE? y Modify Tandem Calling Number? n Send UCID? n Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n Apply Local Ringback? n US NI Delayed Calling Name Update? n Show ANSWERED BY on Display? y Network (Japan) Needs Connect Before Disconnect? n Figure 24: Trunk-Group Form 3 Page 3 RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 24 of 79 AV1XM_ATTME 3.5. PSTN Call Routing This section describes the steps for administering outbound and inbound PSTN call routing on Avaya Communication Manager. In this configuration, each user is assigned a DID number as shown in Table 2 . Note that these Application Notes uses North American (10-digit numbers with a leading c1 d as the country code where necessary) numbering in all calling and called number examples that follow. User Extension User DID (Business Number) 20001 732-552-2747 20002 732-552-2748 20003 732-552-2749 20004 732-552-2948 Table 2: User Extension and User DID Association 3.5.1. Outbound Calls This section describes the steps for administering the routing of outbound calls to the PSTN. In this configuration, ARS is used to route outbound calls via the ISDN-PRI trunk described in Section 3.4 to the PSTN. Outbound call routing is used in the following situations: " Calls placed by an Avaya Communication Manager phone (e.g., an office phone) to PSTN phone numbers. " cSimulring d calls to receive ( cSend Calls d) destinations, e.g., mobile phone, home phone, other landline phones, etc., selected by an Avaya one-X" Mobile user for inbound business calls. " cCallback d calls from Avaya Communication Manager to the phone, e.g., mobile phone, home phone, other landline phone, etc., selected by an Avaya one-X" Mobile user for originating a call. 1. Enter the change ars digit-conversion x command. In the ars digit-conversion form, provision entries as shown in bold in Figure 25 . The first entry matches dialed 10-digit numbers that are in the chome d area code of the enterprise office, i.e., same area code as the DID / business numbers assigned to the enterprise office, and directs such calls to be then handled by ARS routing without any modification to the dialed 10-digit numbers. Note that this entry varies according to the customer location. The second entry prefixes a leading c 1 d to all other dialed 10-digit numbers and directs such calls to be then handled by ARS routing. change ars digit-conversion x Page 1 of 2 ARS DIGIT CONVERSION TABLE Location: all Percent Full: 1 Matching Pattern Min Max Del Replacement String Net Conv ANI Req 732 10 10 0 ars n n x 10 10 0 1 ars n n Figure 25: ARS Digit-Conversion Form RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 25 of 79 AV1XM_ATTME 2. Enter the change ars analysis d command, where d is any digit(s). In the ars digit- conversion form, provision an entry for each PSTN destination as follows: " Dialed String 3 Enter the leading digits of a dialed PSTN destination, e.g., 1 followed by the destination area code. " Total Min and Max 3 Enter c 11 d. " Route Pattern 3 Enter the number of an unused route pattern. " Call Type 3 Enter c fnpa d. Note: Enterprise users, by habit, accident, or other reasons, might still dial a leading c1 d to all PSTN destinations, even destination numbers in the chome d area code of the enterprise office. For that reason, an entry to cover this case should also be provisioned as above. In addition, provision another entry to cover the case where enterprise users dial PSTN destinations in the chome d area code of the enterprise office without a leading c1 d. For this entry, set Dialed String to the leading digits of the dialed PSTN destination, e.g., the chome d area code, Total Min and Max to c 10 d, Route Pattern to the same route pattern as above, and Call Type to c hnpa d. change ars analysis 1732 Page 2 of 2 ARS DIGIT ANALYSIS TABLE Location: all Percent Full: 2 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd 1732 11 11 99 hnpa n 1908 11 11 99 fnpa n 1404 11 11 99 fnpa n 732 10 10 99 hnpa n Figure 26: ARS Analysis Form In Figure 26 , entries are shown for outbound calls to 732-xxx-xxxx, 1-732-xxx-xxxx, 1- 908-xxx-xxxx and 1-404-xxx-xxxxx. Typical deployments generally require additional entries, or the use of less exact or wildcard matching strings, to cover all permitted PSTN destination numbers, but that is beyond the scope of these Application Notes. Ensure that there are entries to cover all permitted PSTN destination numbers, including those of the mobile phones and other receive destinations. Consult [3] and [4] for further information on ARS administration. 3. Enter the change route-pattern r command, where r is the route pattern entered in Step 2. Provision an entry as follows: " Grp No - Enter the number of the ISDN-PRI trunk group described in Section 3.4. " FRL - Enter the minimum Facility Restriction Level necessary to use this trunk group, with 0 being the least restrictive. Set this FRL to a value less than or equal to the FRL of the COR administered in Section 3.3 and assigned to the stations in Section 3.9 Step 1. " Pfx Mrk 3 Enter c 1 d. RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 26 of 79 AV1XM_ATTME change route-pattern 99 Page 1 of 3 Pattern Number: 99 Pattern Name: Out to PSTN SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 99 0 1 n user 2: n user 3: n user 4: n user 5: n user 6: n user Figure 27: Route-Pattern Form 4. Enter the change public-unknown numbering 0 command to specify the calling party numbers sent on outbound calls on the ISDN-PRI trunk. In the public-unknown numbering form, provision an entry as follows: " Ext Len - enter the extension length, e.g., c 5 d since 5-digit extensions are used in this configuration. " For deployments where users 9 extensions and users 9 business numbers share a common suffix 2 , enter enough leading digits to identify a user extension range for Ext Code . In addition, enter enough prefix digits for CPN Prefix to form the business numbers, i.e., the CPN Prefix will be prefixed to the extension to form the complete business number. Note that this entry would then be valid for multiple users, i.e., those in the same extension range. For example, if a deployment uses extensions 31xxx and business numbers 212-553-1xxx, then set Ext Code to c31 d and CPN Prefix to c21255 d or c121255 d (depending on whether 10- or 11-digit calling party numbers are to be sent). As another example, if a deployment uses extensions 31xxx and business numbers 212- 550-1xxx, then set Ext Code to c31 d and CPN Prefix to c212550 d or c1212550 d (the c0 d overwrites the c3 d). " For deployments where users 9 extensions and users 9 business numbers do not share a common suffix, as in Figure 28 , enter a user 9s entire extension for Ext Code , and enter the user 9s business number for CPN Prefix . Note that this entry would then be valid for a single user, and as such, additional similar entries must be configured for all other users. " Trk Grp(s) - Enter the number of the ISDN-PRI trunk group described in Section 3.4. " Total CPN Len - Enter the total length of the calling party number to be sent. Provision as many entries as necessary to cover all user extensions / extension ranges. 2 For example: " Extensions 31xxx and business number 732-553-1xxx share a common suffix 31xxx. " Extensions 31xxx and business number 732-550-1xxx share a common suffix 1xxx. " Extensions 31xxx and business number 732-531-xxx0 do NOT share a common suffix. RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Avaya Inc. All Rights Reserved. 27 of 79 AV1XM_ATTME change public-unknown-numbering 0 Page 1 of 2 NUMBERING - PUBLIC/UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Len Code Grp(s) Prefix Len Total Administered: 63 5 20001 99 7325522747 10 Maximum Entries: 9999 5 20002 99 7325522748 10 5 20003 99 7325522749 10 5 20004 99 7325522948 10 Figure 28: Public-Unknown Numbering Form 3.5.2. Inbound Calls This section describes the steps for administering the routing of inbound DID calls to Avaya Communication Manager extensions. Once a DID call is routed to an extension, if that extension is also that of an Avaya one-X" Mobile user, then Avaya one-X" Mobile instructs Avaya Communication Manager to route the call to all of the receive ( cSend Calls d) destinations selected by the user. For the receive destinations that are in the PSTN (e.g., mobile and/or landlines), those calls are routed according to the outbound call routing described in Section 3.5.1. The procedures for which a user specifies and selects receive destinations is described in the one-X" Mobile User Guides [7], [8], and [9]. In this configuration, inbound calls from the PSTN arrive via the ISDN-PRI trunk described in Section 3.4. Enter the change inc-call-handling-trmt trunk-group t command, where t is the number of the trunk group described in Section 3.4, to specify how the called party numbers on inbound calls on the ISDN-PRI trunk are to be interpreted. In the inc-call-handling-trmt trunk-group form, provision an entry as follows: " Called Len 3 Enter the total number of digits in the called party number. " For deployments where users 9 extensions and users 9 business numbers share a common suffix, enter enough leading digits to uniquely match a business number range for Called Number . In addition, for Del , enter the total number of leading business number digits that need to be deleted in order to arrive at the common suffix, and for Insert , if necessary enter the leading digit(s) to be prefixed to the suffix in order to arrive at the extension. Note that this entry would then be valid for multiple business numbers, i.e., those in the same business number range. For example, if a deployment uses business numbers 212-553-1xxx and extensions 31xxx, then set Called Number to c2125531 d and Del to c5 d. As another example, if a deployment uses business numbers 212-550-1xxx and extensions 31xxx, then set Called Number to c2125501 d, Del to c6 d, and Insert to c3 d. " For deployments where users 9 extensions and users 9 business numbers do not share a common suffix, as in Figure 29 , enter a user 9s business number for Called Number , the total number of digits in the business number for Del , and the user 9s extension for Insert . Note that this entry would then be valid for a single business number, and as such, additional similar entries must be configured for every other business number. Provision as many entries as necessary to cover all users 9 business numbers / number ranges. RL; Reviewed SPOC 3/3/2009 Solution & Interoperability Test Lab Application Notes ©2009 Av

less