Configuring Enterprise Mobility User (EMU) for Avaya Communication Manager Systems Networked with a QSIG Trunk Issue 1.3

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring Enterprise Mobility User (EMU) for Avaya Communication Manager Systems Networked with a QSIG Trunk Issue 1.3 Abstract Within a network consisting of independent Avaya Communication Manager systems interconnected with a QSIG Trunk and Uniform Dial Plan, Enterprise Mobility User (EMU) provides users a wired roaming capability in the enterprise voice network. It allows users to log into an Avaya IP Telephone or Avaya Digital Telephone controlled by any of the networked systems. When a user logs into a visited switch, the user can get the same call appearance, feature button, and message-waiting status the user would typically receive from the user s home switch. Incoming calls to the user s home extension are redirected to the visited switch. From the perspective of the called party, outgoing calls from the visiting user can appear to have been originated from the user s extension at the home switch. These Application Notes describe the administrative steps required to configure the Enterprise Mobility User feature in Avaya Communication Manager. 1 of 30

2 1. Introduction Enterprise Mobility User (EMU) is a software-only feature that provides users the ability to associate the buttons and features of their primary telephones to telephones of the same type anywhere within the enterprise network. This feature supplements previously available mobility, wired roaming, and hot-desking features. In this sample configuration, Avaya 1600, 4600, and 9600 series of IP Telephones, and Avaya 2420 Digital Telephones are illustrated EMU Operational Overview This section is intended as a brief EMU functional overview. For additional information, refer to Reference [1]. The EMU feature requires two or more separate Avaya Communication Manager systems interconnected with QSIG trunks and a Uniform Dial Plan. QSIG Manufacturer Specific Information (MSI) is used to transport signaling necessary for EMU feature operation. All systems must be running the same version of Avaya Communication Manager if the systems are running Release 3.1. For systems running Communication Manager 4.0 and later, releases are interoperable. Assume a user Alan has a telephone extension on System A. Alan will be traveling to a location whose telephone service is provided by System B. When visiting, Alan will be using a telephone either physically (i.e., 2420 digital telephone) or logically (i.e., IP Telephones) associated with System B. The System B extension associated with Alan s visited telephone must have been configured to allow use of the EMU feature. Upon arrival, Alan can dial the EMU activation access code, followed by the extension and station security code for Alan s extension on System A. Assuming proper credentials are entered, System B, the visited system, contacts System A, the home system in this example. System A transports information about Alan s telephone extension on System A to System B, which then downloads button information to the telephone Alan is using in the visited office. An example set of feature buttons that are capable of being downloaded to Alan s visited telephone are listed in Section 1.2. If Alan uses a different telephone type in the visited office, Alan will have his call appearances and message waiting state indication from System A, but not the telephone features programmed for his extension on System A. When the telephone at System B is associated with Alan s telephone extension on System A, Alan s home telephone at System A displays text that indicates the EMU feature is active for the extension of the visited telephone at System B. Alan s home telephone at System A can be used to make emergency calls while Alan is visiting the telephone at System B, or that phone itself can be used as a visited station for a user with a telephone extension in System B if the systems are running Communication Manager 4.0 or later. 2 of 30

3 Alan can make calls using the visited telephone at System B using either the dial-pad of the telephone, or using stored number buttons that have been downloaded from System A. When using a call appearance, if an extension is dialed via the dial pad, or if the ARS access code and number are dialed via the dial-pad, the dial plan of the visited system (System B in this example) is consulted for routing the call. In general, when stored number buttons are used, the digits are processed according to the dial-plan of the home system (System A in this example). For example, calls made using an abbreviated dial (AD) feature button are processed by and routed through the user s home switch using the number stored in the AD list on the home switch. In general, the called user can see the name and number associated with Alan s extension at System A, provided the Avaya Communication Manager trunk group in the visited system has been configured to allow this. Other types of feature button presses (e.g., Send All Calls) are also processed by the user s home switch (Switch A in this example). When an incoming call arrives for Alan at his home switch (System A), the home switch redirects the call to the visited switch (System B) over the QSIG trunks so that the visiting user has an opportunity to answer the call at the visited telephone. However, the home switch also maintains control of the call in that call coverage or diversion into voice messaging is managed at the user s home switch. An emergency call made by the visiting user from the dial pad is a special case. When an emergency call (e.g., 911) is dialed, the digits are processed at the visited switch and routed to the appropriate agency. An emergency call dialed by the visiting user also terminates the visited registration, allowing the emergency response agency the opportunity to call the user back at the telephone number normally associated with the visited set EMU Supported Feature Assuming the visiting EMU user registers using the same telephone type used at the user s home switch, the following button features are eligible to be downloaded and used at the visited telephone: Analog bridged appearance (abrdg-appr) Abbreviated dial (abrv-dial) Automatic Message Waiting (aut-msg-wt) Automatic Call Back (auto-cback) Automatic Intercom (auto-icom) Bridged Appearance (brdg-appr) Busy Indication (busy-ind) for another extension or trunk Call appearance(s) (call-appr) Call Forwarding (call-fwd) Call Forward Busy / Don t Answer (cfwd-bsyda) Dial Intercom (dial-icom) Extension To Cellular (EC500) Exclusion (exclusion) 3 of 30

4 Personal CO-line (per-coline) Send All Calls (send-calls) 2. Configuration The network configuration consists of two locations, System A and System B. System A has a pair of Avaya S8710 Servers controlling two SCC1 Cabinets (Multi-Connect) and System B has a pair of Avaya S8710 Servers controlling a G650 Gateway (IP connect). An H.323 (QSIG) trunk is established between these two locations. Avaya Modular Messaging system provides centralized messaging service to both systems. Avaya CMS is configured for both high reliability and survivability in System B. A Wireless 3626 telephone will be used for EC500 support with EMU. Figure 1 is the network configuration used for these Application Notes. System A utilizes an 11- digit dial plan. System B utilizes a 7-digit dial plan. System A Ext xxxx System B Ext 432-xxxx Avaya S8710 Server Pair Multi-Connect Avaya 4620SW IP Telephone X Avaya 9630 IP Telephone X Avaya 4620 IP Telephone X Avaya S8710 Server Pair IP Connect Control Network Ethernet Ethernet CORP LAN IP Wide Area Network Ethernet C-LAN MEDPRO IPSI C-LAN(s) MEDPRO(s) Avaya Modular Messaging Avaya 9630 IP Telephone X Avaya G650 Media Gateway Avaya SCC1 Media Gateway Avaya Wireless Avaya CMS Avaya Telephone Digital Telephone Avaya 1608 X X IP Telephone X Avaya 2420 Digital Telephone X Avaya 1608 IP Telephone X Figure 1: Network Configuration for Enterprise Mobility User 4 of 30

5 These Application Notes will not cover the Avaya S8710 Server, Avaya Modular Messaging, and Avaya CMS basic system configurations. For documentation regarding these configurations, refer to user documentation listed in Section Equipment and Software Validated Table 1 illustrates the equipment and software used in the sample configuration: Equipment Software/Firmware Avaya S8710 Servers in System A Avaya Communication Manager 5.0 (R014x ) with Update 1004 Avaya SCC1 Gateway in System A TN2312BP IP Server Interface TN799DP C-LAN Interface TN2302AP IP Media Processor Avaya 8710 Servers in System B Avaya G650 Gateway in System B TN2312BP IP Server Interface TN799DP C-LAN Interface TN2602AP IP Media Processor HW12 FW058 HW01 FW024 HW20 FW116 Avaya Communication Manager (R014x ) HW11 FW021 HW01 FW012 HW02 FW007 Avaya Modular Messaging Release 3.1 Avaya 4620SW/4610SW IP Telephone (H.323) Release 2.8 Avaya 1608 IP telephone (H.323) Release 1.0 Avaya 2420 Digital Telephone N/A Avaya CMS Release 14 Avaya Wireless 3626 IP Telephone Version Avaya 9630 (H.323) Release 1.5 Table 1: Equipment and Software Version The dial plan and extension range used for both systems are shown in Table 2 below. Dialed Number Format Call Type xxxx System A telephones 432-xxxx System B telephones Modular Messaging Pilot # *77 EMU Activation Code on both systems *78 EMU Deactivation Code on both systems Table 2: Dial Plan for System A and System B 5 of 30

6 4. Assumptions and Limitations It is assumed that the appropriate license files and authentication files have been installed, and appropriate system parameter configurations have been performed. Table 3 shows the supported releases of Avaya Communication Manager in regards to EMU. The table is based on the Avaya Communication Manager software running in the Home Configuration and the supported releases the Visited Configuration may run in order for EMU to work properly. Home Configuration Visited Configuration R 3.1 R3.1, R3.1.2 R3.1.2 R3.1, R3.1.2 R 4.0 R4.0, R 4.0.1, R5.0 R R4.0, R4.0.1, R5.0 R 5.0 R4.0, R4.0.1, R5.0 Table 3: Avaya Communication Managers Supporting EMU The following is a list of other requirements for the EMU feature: QSIG must be the private networking protocol in the network of Avaya Communication Manager Systems. This requirement also includes QSIG MWI. EMU does not replace normal dial plan / UDP programming. EMU users rely on the dial plan and UDP of the visited configuration to route calls back to the home switch. Therefore it is necessary that the visited configuration include all VDNs, messaging pilot numbers, and any other needed extensions in its dial plan. For Visited Configurations where Avaya Call Management System is configured for both high reliability and survivability, and the Home Configuration utilizes an expanded dial plan, use the call type udp instead of ext when changing the dial plan of the visited configuration. The udp call type is used specifically for situations, where it is not desirable to use true long extensions on the CMS-connected switch, but necessary to permit users on that visited switch to reach longer extensions on other home switches via UDP. The visited telephone must be the same model type as the primary telephone to enable an optimal transfer of the image of the primary telephone. If the visited telephone is not the same type, only the call appearance (call-appr) buttons and the message waiting light are transferred. See section 4.1 for an exception to this rule when using the 1600 series of IP telephones. The PSA permission for the primary telephone must be set to y in Class of Service (COS). 6 of 30

7 4.1. Supported Telephones The EMU feature has been designed for the newer type of self-designating telephones that have downloadable button configuration. These include Avaya 4600 and Avaya 9600 series IP telephones and 2400 series digital telephones. SIP endpoints are not supported. Table 4 below lists the telephones supported for EMU. IP Telephones Digital Telephones 4610, 4610SW 2410 and , 4620SW 4621SW 4622SW 4625SW 1603, 1608, , 9630, 9640, 9650 Table 4: Telephones Supporting EMU For Avaya 2410 and 2420 digital telephones, the Messages button can not be utilized by the Visited Configuration. When the Messages button is pressed, a busy tone will be delivered. However, a speed dial button containing the pilot number of the messaging system will work Series The Avaya 1600 series is a family of cost-effective IP Telephones, which are administered as described in Table 5 within Avaya Communication Manager. Since the 1600 series is aliased as a different phone type, it is possible to activate EMU across different phone types, and still download MWI and all supported buttons (as listed in Section 1.2). For example, a user with a 1608 home station in System A can successfully get all MWI and supported buttons transferred to a 4610 set in System B upon EMU activation. Unlike the 4600 and 9600 series of IP telephones, the 1600 does not support the self-designation of button assignments. Paper designations strips are utilized for button labels. It s very likely that downloaded button assignments on a visited 1600 series telephone will not match any predesignated paper strips. The visiting user can press the Feature button on the visited 1600 set to scroll through and display button information Series Administered As Table 5: 1600 Series IP Telephones 7 of 30

8 5. Configure Avaya Communication Manager This section illustrates the aspects of Avaya Communication Manager EMU configuration for Figure 1. Note that both System A and System B are running separate Avaya Communication Manager Releases. An IP QSIG trunk is established between the C-LANs of the two systems. Avaya Modular Messaging is connected to the SCC1 at System A using an IP H.323 trunk with QSIG enabled providing voice message service for both systems. A uniform dial plan is configured at both System A and B Verify Required Features Use the command display system-parameters customer-options to verify required features are licensed in Avaya Communication Manager for both System A and System B. On page 3, ensure that ARS? is set to y. Ensure that ARS/AAR Dialing without FAC? is also set to y, as the dial plan used in both System A and System B use AAR to route calls between locations within a private network. display system-parameters customer-options Page 3 of 11 OPTIONAL FEATURES Abbreviated Dialing Enhanced List? y Audible Message Waiting? y Access Security Gateway (ASG)? y Authorization Codes? y 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)? n ASAI Link Core Capabilities? y DCS Call Coverage? n ASAI Link Plus Capabilities? y DCS with Rerouting? n Async. Transfer Mode (ATM) PNC? n Async. Transfer Mode (ATM) Trunking? y Digital Loss Plan Modification? n ATM WAN Spare Processor? n DS1 MSP? n ATMS? y DS1 Echo Cancellation? y Attendant Vectoring? y 8 of 30

9 On page 4, ensure that both IP Trunks? and ISDN-PRI? are set to y. display system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y Enable 'dadmin' Login? y Enhanced Conferencing? y Enhanced EC500? y Enterprise Survivable Server? n Enterprise Wide Licensing? n ESS Administration? y Extended Cvg/Fwd Admin? y External Device Alarm Admin? n Five Port Networks Max Per MCC? n Flexible Billing? n Forced Entry of Account Codes? n Global Call Classification? n Hospitality (Basic)? y Hospitality (G3V3 Enhancements)? n IP Trunks? y IP Stations? y ISDN Feature Plus? y ISDN Network Call Redirection? y ISDN-BRI Trunks? y ISDN-PRI? y Local Survivable Processor? n Malicious Call Trace? y Media Encryption Over IP? y Mode Code for Centralized Voice Mail? n Multifrequency Signaling? y Multimedia Call Handling (Basic)? y Multimedia Call Handling (Enhanced)? y IP Attendant Consoles? y On page 5, ensure that both Personal Station Access (PSA)? and Uniform Dialing Plan? are set to y. display system-parameters customer-options Page 5 of 11 OPTIONAL FEATURES Multinational Locations? n Multiple Level Precedence & Preemption? n Multiple Locations? n Personal Station Access (PSA)? y Posted Messages? n PNC Duplication? n Port Network Support? y Processor and System MSP? n Private Networking? y Processor Ethernet? y Remote Office? y Restrict Call Forward Off Net? y Secondary Data Module? y Station and Trunk MSP? n Station as Virtual Extension? n System Management Data Transfer? n Tenant Partitioning? n Terminal Trans. Init. (TTI)? y Time of Day Routing? y Uniform Dialing Plan? y Usage Allocation Enhancements? y TN2501 VAL Maximum Capacity? y Wideband Switching? y Wireless? y 9 of 30

10 5.2. System Features Showing QSIG Parameters Use the command display system-parameters features to verify that the QSIG/ETSI TSC Extension is configured for both System A and System B on page 8. display system-parameters features Page 8 of 17 FEATURE-RELATED SYSTEM PARAMETERS ISDN PARAMETERS PARAMETERS FOR CREATING Send Non-ISDN Trunk Group Name as Connected Name? n QSIG SELECTION NUMBERS Display Connected Name/Number for ISDN DCS Calls? y Network Level: 1 Send ISDN Trunk Group Name on Tandem Calls? n Level 2 Code: Level 1 Code: 22 QSIG/ETSI TSC Extension: MWI - Number of Digits Per Voice Mail Subscriber: 11 Feature Plus Ext: National CPN Prefix: International CPN Prefix: Pass Prefixed CPN to ASAI? n Unknown Numbers Considered Internal for AUDIX? n USNI Calling Name for Outgoing Calls? n Path Replacement with Measurements? y QSIG Path Replacement Extension: Path Replace While in Queue/Vectoring? n 5.3. System Features Showing EMU Timeout Parameters Use the command change system-parameters features to modify the EMU Inactivity Interval for Deactivation (hours) field. This is performed in both System A and System B configurations. The default value for this field is null. These Application Notes will use a deactivation timer of one hour. When a visited phone in System B is inactive (no use of the telephone) for one hour, the system will automatically log the user out of EMU. change system-parameters features Page 3 of 17 TTI/PSA PARAMETERS FEATURE-RELATED SYSTEM PARAMETERS WARNING! SEE USER DOCUMENTATION BEFORE CHANGING TTI STATE Terminal Translation Initialization (TTI) Enabled? n Customer Telephone Activation(CTA) Enabled? n Don't Answer Criteria For Logged Off IP/PSA/TTI Stations? y EMU PARAMETERS EMU Inactivity Interval for Deactivation(hours):1 CALL PROCESSING OVERLOAD MITIGATION Restrict Calls: stations-first 10 of 30

11 5.4. Node Names The following screen shows the node names used in this configuration. These node names will appear in other screens depicting the configuration and verification. Use the command change node-name-ip to add node names and corresponding IP addresses. This configuration is required on both switches. System A: change node-name-ip Page 1 of 1 CALL CENTER OPTIONAL FEATURES IP NODE NAMES Name IP Address Name IP Address C-LAN-A C-LAN-System-B System B: change node-name-ip Page 1 of 1 CALL CENTER OPTIONAL FEATURES IP NODE NAMES Name IP Address Name IP Address C-LAN-B C-LAN-System-A Configure Dial Plan The following screens illustrate the dial plan used as part of the configuration on both systems. EMU does not replace normal dial plan / UDP programming. EMU relies on the dial plan and UDP to route calls. Therefore, all numbers (extensions, VDN s, etc.) for both configurations should be configured in both dial plans. To verify these entries, type display dialplan analysis. In both dial plans, the first digit * with length 3 is also defined as a feature access code (fac). The dial plan on System B is slightly different than the dial plan in System A. Since Avaya CMS is configured for survivability in System B, and System A uses an expanded dial plan, a Call Type of udp is used when changing the dial plan of System B. The udp Call Type is used specifically for situations where it is not desirable to use true long extensions on the Avaya CMS-connected switch, but necessary to permit users on that visited switch to reach longer extensions on other home switches via udp. If CMS is not configured on a visited system, then a Call Type of ext can be used to define the dial plan. 11 of 30

12 System A: display dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Percent Full: 1 System B: Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type ext ext 3 5 ext 8 1 fac 9 1 fac * 3 fac display dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Percent Full: 1 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type udp ext 3 5 ext 8 1 fac 9 1 fac * 3 fac 5.6. Configure Feature Access Codes Use the command display feature-access-codes to verify that the EMU feature access code has been configured properly on both systems. On page 1, the digit 8 is used for the Auto Alternate Routing (AAR) Access Code to allow dialing between remote locations. display feature-access-codes Page 1 of 8 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: *20 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: On page 2, the feature access codes for both Enterprise Mobility User Activation and Deactivation must be set on all servers using EMU. Users must enter the FAC of the server in 12 of 30

13 the location from which they are dialing. To avoid confusion, Avaya recommends that all the servers in the network have the same EMU feature access codes. These configurations use *77 to activate EMU and *78 to deactivate EMU. display feature-access-codes Page 2 of 8 FEATURE ACCESS CODE (FAC) Data Origination Access Code: Data Privacy Access Code: Directed Call Pickup Access Code: Emergency Access to Attendant Access Code: EC500 Self-Administration Access Code: Enhanced EC500 Activation: Deactivation: Enterprise Mobility User Activation: *77 Deactivation: * Set Class of Service Since all stations are using Class of Service (COS) 1, use the command display cos to verify that Personal Station Access (PSA) is set to y on all systems. PSA allows a user to associate the preferences and permissions assigned to a home extension with any other compatible telephone. display cos Page 1 of 2 CLASS OF SERVICE 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 n n n n n n n n n n n n n n n Off-hook Alert n y 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 y y y y y y y y y y y y y y y y Call Forwarding Busy/DA n n n n n n n n n n n n n n n n Personal Station Access (PSA) n y n n n n n n n n n n n n n n Extended Forwarding All n n n n n n n n n n n n n n n n Extended Forwarding B/DA n n 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 y 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 Automatic Exclusion n n n n n n n n n n n n n n n n 13 of 30

14 5.8. Configure H.323 Signaling Group on System A The following screen shows the signaling group used in this configuration on System A. Use the command display signaling-group to view this information. Signaling group 3 uses a Group Type of h.323. Set Max number of NCA TSC and Max number of CA TSC to 10. The Trunk Group for NCA TSC and Trunk Group for Channel Selection are both set to 3. Trunk group 3 will be created in Section A Supplementary Service Protocol of b is selected for QSIG features. The Near-end Node Name of C-LAN-A represents the C-LAN of the SCC1 Gateway in System A. The Far-end Node Name of C-LAN-System-B located in Far-end Network Region 8 is the C-LAN of the G650 Gateway in System B. It is recommended that Calls Share IP Signaling Connection be set to y for performance reasons. display signaling-group 3 SIGNALING GROUP Group Number: 3 Group Type: h.323 Remote Office? n Max number of NCA TSC: 10 SBS? n Max number of CA TSC: 10 IP Video? n Trunk Group for NCA TSC: 3 Trunk Group for Channel Selection: 3 Supplementary Service Protocol: b Network Call Transfer? y T303 Timer(sec): 10 Near-end Node Name: C-LAN-A Far-end Node Name: C-LAN-System-B Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 8 LRQ Required? n Calls Share IP Signaling Connection? y RRQ Required? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress DCP/Analog Bearer Capability: 3.1kHz 14 of 30

15 5.9. Configure COR on System A The following screen shows the COR values used in this configuration. Use the command change cor to update the EMU login or logoff at this phone field. In this configuration, COR 1 is used. The default for this field is none. Set this field to all to allow full login and logoff privileges for 2400 series telephones. change cor 1 Page 2 of 21 CLASS OF RESTRICTION MF Incoming Call Trace? n Brazil Collect Call Blocking? n Block Transfer Display? n Block Enhanced Conference/Transfer Displays? y Remote Logout of Agent? n Station Lock COR: 1 Outgoing Trunk Disconnect Timer (minutes): Station-Button Display of UUI IE Data? n Service Observing by Recording Device? n ERASE 24XX USER DATA UPON Dissociate or unmerge this phone: none EMU login or logoff at this phone: all Mask CPN/NAME for Internal Calls? n Configure H.323 Trunk Group on System A The following screens show the trunk group used in this configuration on System A. Use the command display trunk-group to view this information. On page 1, the Group Type is isdn and the Carrier Medium is H.323. Direction is set as twoway, Service Type is tie, and COR is 1. display trunk-group 3 Page 1 of 21 TRUNK GROUP Group Number: 3 Group Type: isdn CDR Reports: y Group Name: to System B COR: 1 TN: 1 TAC: 103 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: manual 15 of 30

16 On page 2, the Supplementary Service Protocol is b and Digit Handling (in/out) is enbloc/enbloc, which is the default value for this field. display trunk-group 3 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: unk-unk Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 On page 3, the NCA-TSC Trunk Member is 3, which identifies the trunk member whose D- channel will be used to route NCA-TSCs. The Format is unknown, which indicates the numbering plan indicator is unknown and that the type of number is unknown. Set Send EMU Visitor CPN to y to send calling party identification of the home station. The Send EMU Visitor CPN field controls which calling party identification (extension of the primary telephone or extension of the visited telephone) is used when a call is made from a visited telephone. Please note there are areas where public network trunks disallow a call if the calling party information is invalid. In this case, there can be instances where the extension of the primary telephone is considered invalid and the extension of the visited telephone must be used. If this occurs, set Send EMU Visitor CPN to n. display trunk-group 3 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: 3 Send Name: y Send Calling Number: y Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? y Suppress # Outpulsing? n Format: unknown UUI IE Treatment: service-provider Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Called/Busy/Connected Number: n Hold/Unhold Notifications? y Modify Tandem Calling Number? n For testing purposes, only 5 voice channels are added on page 5. Sig Grp is set to of 30

17 display trunk-group 3 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/5 GROUP MEMBER ASSIGNMENTS Total Administered Members: 5 Port Name Night Sig Grp 1: T : T : T : T : T : Configure Codec Set on System A Codec set 1 is used for inter-region connectivity between these two systems. Use the command change ip-codec-set to configure the codec. In this configuration, G.729 is used in codec set 1. change ip-codec-set 1 Page 1 of 2 Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.729 n : 3: 17 of 30

18 5.12. Configure IP Network Region on System A Network Region 8 is used as the far end network region between System A and System B. Note that Codec Set is set to 1 and Intra-region IP-IP Direct Audio and Inter-region IP-IP Direct Audio are set to y. change ip-network-region 8 Page 1 of 19 IP NETWORK REGION Region: 8 Location: Authoritative Domain: Name: To System B MEDIA 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? y UDP Port Max: 3029 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: On Page 3, choose codec 1 for network region 8 between the two Systems. change ip-network-region 8 Page 3 of 19 IP NETWORK REGION Inter Network Region Connection Management src dst codec direct Dynamic CAC rgn rgn set WAN WAN-BW-limits Intervening-regions Gateway IGAR y :NoLimit n of 30

19 5.13. Configure AAR on System A There are many ways to manipulate digits before the call leaves the switch. In this configuration, since System A and System B are using different digit ranges, there is no need to manipulate digits between the two systems. The following screen illustrates the AAR analysis form, showing how digits 432-xxxx (extension range used in System B) is routed. Calls to System B will use Route Pattern 3. display aar analysis 4 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n Configure Route Pattern on System A The following screen shows the configuration of route pattern 3 to System B. Note the field TSC (Temporary Signaling Connection) is set to y, CA-TSC is set to as-needed and Numbering Format is set to unk-unk. display route-pattern 3 Page 1 of 3 Pattern Number: 3 Pattern Name: to System B 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: 3 0 n user 2: n user 3: n user 4: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR W Request Dgts Format Subaddress 1: y y y y y n y as-needed rest unk-unk none 2: y y y y y n n rest none 19 of 30

20 5.15. Configure H.323 Signaling Group on System B The following screen shows the signaling group used in this configuration on System B. Use the command display signaling-group to view this information. Signaling group 2 uses a Group Type of h.323. Set Max number of NCA TSC and Max number of CA TSC to 10. The Trunk Group for NCA TSC and Trunk Group for Channel Selection are both set to 2. Trunk group 2 will be created in Section A Supplementary Service Protocol of b is selected for QSIG features. The Near-end Node Name of C-LAN-B represents the C-LAN in the G650 Gateway in System B. The Far-end Node Name of C-LAN-System-A located in Far-end Network Region 8 is the C-LAN of the SCC1 Gateway in System A. It is recommended that Calls Share IP Signaling Connection? be set to y for performance reasons display signaling-group 2 SIGNALING GROUP Group Number: 2 Group Type: h.323 Remote Office? n Max number of NCA TSC: 10 SBS? n Max number of CA TSC: 10 IP Video? n Trunk Group for NCA TSC: 2 Trunk Group for Channel Selection: 2 Supplementary Service Protocol: b Network Call Transfer? y T303 Timer(sec): 10 Near-end Node Name: C-LAN-B Far-end Node Name: C-LAN-System-A Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 8 LRQ Required? n Calls Share IP Signaling Connection? y RRQ Required? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress DCP/Analog Bearer Capability: 3.1kHz 20 of 30

21 5.16. Configure COR on System B The following screen shows the COR values used in this configuration. Use the command change cor to update the EMU login or logoff at this phone field. In this configuration COR 1 is used. The default for this field is none. Set this field to all to allow full login and logoff privileges for 2400 series telephones. change cor 1 Page 2 of 21 CLASS OF RESTRICTION MF Incoming Call Trace? n Brazil Collect Call Blocking? n Block Transfer Display? n Block Enhanced Conference/Transfer Displays? y Remote Logout of Agent? n Station Lock COR: 1 Outgoing Trunk Disconnect Timer (minutes): Station-Button Display of UUI IE Data? n Service Observing by Recording Device? n ERASE 24XX USER DATA UPON Dissociate or unmerge this phone: none EMU login or logoff at this phone: all Mask CPN/NAME for Internal Calls? n Configure H.323 Trunk Group on System B The following screens show the trunk group used in this configuration on System B. Use the command display trunk-group to view this information. On page 1, the Group Type is isdn and the Carrier Medium is H.323. Direction is set as twoway, Service Type is tie, and COR is 1. display trunk-group 2 Page 1 of 21 TRUNK GROUP Group Number: 2 Group Type: isdn CDR Reports: y Group Name: to System A COR: 1 TN: 1 TAC: 1001 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? y Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: manual 21 of 30

22 On page 2, the Supplementary Service Protocol is b and Digit Handling (in/out) is enbloc/enbloc, which is the default value for this field. display trunk-group 2 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc QSIG Value-Added? y Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: unk-unk Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 On page 3, the NCA-TSC Trunk Member is 2, which identifies the trunk member whose D- channel will be used to route NCA-TSCs. The Format is unknown, which indicates the numbering plan indicator is unknown and that the type of number is unknown. Set Send EMU Visitor CPN to y to send calling party identification of the home station. The Send EMU Visitor CPN field controls which calling party identification (extension of the primary telephone or extension of the visited telephone) is used when a call is made from a visited telephone. Please note there are areas where public network trunks disallow a call if the calling party information is invalid. In this case, there can be instances where the extension of the primary telephone is considered invalid and the extension of the visited telephone must be used. In this occurs, set Send EMU Visitor CPN to n. display trunk-group 2 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: 2 Send Name: y Send Calling Number: y Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? y Suppress # Outpulsing? n Format: unknown UUI IE Treatment: service-provider Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Called/Busy/Connected Number: n Hold/Unhold Notifications? y Modify Tandem Calling Number? n For testing purposes, only 5 voice channels are added on page 5. Sig Grp is set to of 30

23 display trunk-group 2 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/5 GROUP MEMBER ASSIGNMENTS Total Administered Members: 5 Port Name Night Sig Grp 1: T : T : T : T : T : Configure Codec Set on System B Codec set 1 is used for inter-region connectivity between these two systems. Use the command change ip-codec-set to configure the codec. In this configuration, G.729 is used in codec set 1. change ip-codec-set 1 Page 1 of 2 Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.729 n : 23 of 30

24 5.19. Configure IP Network Region on System B Network Region 8 is used as the far end network region between System A and System B. Note that Codec Set is set to 1 and Intra-region IP-IP Direct Audio and Inter-region IP-IP Direct Audio are set to y. change ip-network-region 8 Page 1 of 19 IP NETWORK REGION Region: 8 Location: Authoritative Domain: Name: To System A MEDIA 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? y UDP Port Max: 3029 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: Choose codec 1 for network region 8 between the two systems. change ip-network-region 8 Page 3 of 19 IP NETWORK REGION Inter Network Region Connection Management src dst codec direct Dynamic CAC rgn rgn set WAN WAN-BW-limits Intervening-regions Gateway IGAR y :NoLimit n of 30

25 5.20. Configure AAR on System B There are many ways to manipulate digits before the call leaves the switch. In this configuration, since System A and System B are using different digit ranges, there is no need to manipulate digits between the two systems. The following screen illustrates the AAR analysis form, showing how digits xxxx (extension range used in System A) is routed. Calls to System A will use Route Pattern 2. display aar analysis 17 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n Configure Route Pattern on System B The following screen shows the configuration of route pattern 2 to System B. Note the field TSC (Temporary Signaling Connection) is set to y, CA-TSC is set to as-needed and Numbering Format is set to unk-unk. display route-pattern 2 Page 1 of 3 Pattern Number: 2 Pattern Name: to System A 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: 2 0 n user 2: n user 3: n user 4: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR W Request Dgts Format Subaddress 1: y y y y y n y as-needed rest unk-unk none 2: y y y y y n n rest none 25 of 30

26 5.22. Enable EMU on Stations The following steps describe the procedure to enable the EMU feature on IP station in System A. The configuration is same for Digital stations. Use the command change station to verify station information. On page 1, verify that COR and COS are set to 1. This should be repeated for any station in System B that utilizes the EMU feature. change station Page 1 of 4 STATION Extension: Lock Messages? n BCC: 0 Type: 4620 Security Code: 1234 TN: 1 Port: S00000 Coverage Path 1: 1 COR: 1 Name: IP-Main Coverage Path 2: COS: 1 Hunt-to Station: STATION OPTIONS Loss Group: 19 Personalized Ringing Pattern: 1 Message Lamp Ext: Speakerphone: 2-way Mute Button Enabled? y Display Language: english Expansion Module? n Survivable GK Node Name: Survivable COR: internal Survivable Trunk Dest? y Media Complex Ext: IP SoftPhone? n Customizable Labels? y On page 2, verify that EMU Login Allowed? is set to y. change station Page 2 of 4 STATION FEATURE OPTIONS LWC Reception: none Auto Select Any Idle Appearance? n LWC Activation? y Coverage Msg Retrieval? y LWC Log External Calls? n Auto Answer: all CDR Privacy? n Data Restriction? n Redirect Notification? y Idle Appearance Preference? n Per Button Ring Control? n Bridged Idle Line Preference? n Bridged Call Alerting? n Restrict Last Appearance? y Active Station Ringing: single Conf/Trans on Primary Appearance? n EMU Login Allowed? y H.320 Conversion? n Per Station CPN - Send Calling Number? y Service Link Mode: as-needed Multimedia Mode: enhanced Audible Message Waiting? y MWI Served User Type: qsig-mwi Display Client Redirection? N 26 of 30

27 6. Verification Steps The following steps can be used to verify simple EMU operations. Network connectivity: 1. Use commands status signaling group and status trunk group to show the h.323 signaling group and QSIG trunk group are in service between the two systems. The following screen captures are from Avaya Communication Manager at System A. Status signaling-group 3 STATUS SIGNALING GROUP Group ID: 3 Active NCA-TSC Count: 0 Group Type: h.323 Active CA-TSC Count: 0 Signaling Type: facility associated signaling Group State: in-service Status trunk 3 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0003/001 T00021 in-service/idle no 0003/002 T00022 in-service/idle no 0003/003 T00023 in-service/idle no 0003/004 T00024 in-service/idle no 0003/005 T00025 in-service/idle no 2. Dial the Avaya Modular Messaging pilot number from station and verify that the station can access its mailbox. Repeat this step for stations , , , , and Make a call from station to station Verify the call is successful. Repeat this step between all stations and verify that all calls are successful. 4. Program Abbreviated dial (abrv-dial) and Automatic Call Back (auto-cback) buttons on station Enable EC500 on this station as well. EC500 is an Extension to Cellular solution where calls to or from an office phone can be answered via a cell or wireless phone. For more info on EC500, refer to Reference [3]. EMU Feature: 1. From System B, on station dial *77 (EMU Activation FAC) followed by home station number and station security code. Verify that audible confirmation tone is played on the station Verify the call appearance and feature button labels are received from System A. 2. Verify that the message Visited Registration Active: is displayed on station screen. 27 of 30

28 3. From System B, use the command list off-pbx-telephone station-mapping to show that station is in Visitor EMU (VEMU) mode. list off-pbx-telephone station-mapping STATION TO OFF-PBX TELEPHONE MAPPING Station Appl Phone Number Config Trunk Mapping Calls Extension Set Selection Mode Allowed VEMU / udp both all 4. From System A, use the command list off-pbx-telephone station-mapping to show that station is in Home EMU (HEMU) mode. list off-pbx-telephone station-mapping STATION TO OFF-PBX TELEPHONE MAPPING Station Appl Phone Number Config Trunk Mapping Calls Extension Set Selection Mode Allowed HEMU / udp both all 5. Use an abrv-dial button to make a call and verify that it works from the visited station. 6. Make a call from station to station Verify that the visited station (home station in System B) rings, as well as the EC500 station. Answer the call and verify that the call is successful. 7. Repeat step 6 and do not answer the call. Verify that Modular Messaging plays the greeting for station and the user can leave a message for that station. 8. Verify that MWI on visited station is turned on for new voice mail for extension Use the EMU deactivation FAC to logoff station and verify that MWI reverts back to the status of the home station and all station call appearances are changed back to its native setting. 10. Verify MWI is turned on station and the message Visited Registration Active: is no longer displayed. 11. Repeat step 1. Do not make any calls or press any buttons on the visited station ( ) 12. Verify that after the EMU deactivation timer interval is reached, the Visited Configuration logs the EMU station off. 13. From System B, on station dial *77 (EMU Activation FAC) followed by home station number and station security code. Verify that audible confirmation tone is played on the station Verify the call appearance and feature button labels are received from System A. 28 of 30

29 14. Verify that message Visited Registration Active: is displayed on station screen. 15. From System A, on station dial *77 (EMU Activation FAC) followed by home station number and station security code. Verify that audible confirmation tone is played on the station Verify the call appearance and feature button labels are received from System B. 16. Verify that message Visited Registration Active: is displayed on station screen. 17. Make a call from station to station Verify that the visited station (home station in System B) rings. Answer the call and verify that the call is successful. 18. Make a call from station to station Verify that the visited station (home station in System A) rings. Answer the call and verify that the call is successful. 19. Do not make any calls or press any buttons from either of the visited stations. 20. Verify that after the EMU timer interval is reached on both configurations, the visited configurations log the EMU stations off. 7. Conclusion These Application Notes have provided the administrative details on configuring the EMU feature for two independent systems running Avaya Communication Manager. As illustrated in these Application Notes, Avaya Communications Manager can provide users mobility to work at any location within the enterprise network as long as the EMU feature is enabled, with an H.323 QSIG trunk and a properly configured dial plan. 8. Additional References Use this URL to access this document. [1] Administrator Guide for Avaya Communication Manager Issue 3.1: February [2] Modular Messaging Release 3.1 Messaging Application Server Administration Guide for Avaya Modular Messaging with the Avaya MAS and MSS, February [3] Avaya Extension to Cellular User Guide Issue 9: February [4] Avaya Call Management System Release 14 Administration :July of 30

30 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 30 of 30