Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring Enterprise Mobility User (EMU) Feature for Avaya Communication Manager 3.1 Systems Running at Two Systems Networked with A QSIG Trunk Issue 1.0 Abstract Avaya Communication Manager 3.1 has introduced a new feature called Enterprise Mobility User (EMU). Within a network consisting of independent Avaya Communication Manager systems interconnected with a QSIG Trunk and Uniform Dial Plan, this new feature 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. As a user logs into a visiting 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. Feature buttons assigned to the user s extension at the home switch can be automatically downloaded and used at the visiting set. These Application Notes describe the administrative steps required to configure the Enterprise Mobility User feature in Avaya Communication Manager of 25

2 1. Introduction Avaya Communication Manager 3.1 has introduced a new feature called Enterprise Mobility User (EMU). Enterprise Mobility User (EMU) is a software-only feature that gives 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 new feature supplements previously available mobility, wired roaming, and hot-desking features. Capabilities available prior to the introduction of the EMU feature include: Avaya 4600 Series IP Telephone users can log-out and log-in to any Avaya Communication Manager system accessible to the telephone over the IP network. The IP Telephone can obtain and maintain a list of alternate points of registration that can include H.323 gatekeeper addresses associated with one or more Avaya Communication Manager systems. This enables Avaya Communication Manager to provide the same physical telephone with the personalized features and permissions of different users upon log-in to the telephone. Additional personalization outside the scope of Avaya Communication Manager, such as telephone speed-dials, ringing patterns, and customized text labels can also be automatically retrieved by the IP Telephone upon login, so that a visiting user could have all the familiar features of the user s home office environment. A Special Application is available that enables programmatic re-association of Avaya 4600 Series IP Telephones, without requiring end-user action. Special Application SA8520, Hoteling Application for IP Terminals, allows an application to automatically re-associate a physical 4600 Series IP Telephone upon check-in of a visiting user with the hoteling application. The Un-Named Registrations feature, introduced in Avaya Communication Manager in Release 3.0.1, is loosely related to wired roaming. The feature allows Avaya 4600 Series IP Terminals to have basic phone service and configurable permissions; even before a telephone extension is associated with the telephone. For example, a pool of IP Telephones used for hoteling could by default be in the Un-named registered state, until a specific user logged in, or until the telephone was automatically associated with a user via SA8520. The Avaya IP Softphone enables a mobile user access to the features and permissions of the office telephone (and more), whether the user s primary office telephone is an IP Telephone or a Digital Telephone. The Avaya IP Softphone can be used in conjunction with any telephone type at the remote office. The Personal Station Access (PSA) feature allows the disassociation and re-association of telephone features and permissions among telephones controlled by the same Avaya Communication Manager system. The PSA feature applies to Avaya Digital Telephones as well as Avaya IP Telephones. The EMU feature is somewhat similar to the PSA feature, except that the disassociation and reassociation of telephone features and permissions can occur within a network of independent Avaya Communication Manager systems networked with QSIG trunks. That is, the visited telephone is a telephone physically or logically associated with a different Avaya Communication Manager system than the user s home system. Like the PSA feature, the EMU 2 of 25

3 feature allows use of either Avaya Digital Telephones or Avaya IP Telephones. However, whereas the PSA feature allowed older digital telephones (e.g., 6400 Series) to be used, the EMU feature requires the class of newer self-designating telephones with downloadable button configuration. In this sample configuration, Avaya 4610 and 4620 IP Telephones, and Avaya 2410 and 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] in Section 11. The EMU feature requires two or more 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. 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 physical telephone either physically (i.e., 24XX digital telephone) or logically (i.e., 46XX IP Telephone) associated with System B. The system B extension associated with Alan s visiting 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. Assuming Alan is using the same physical telephone type at the visiting office that he uses at his home system, System B downloads button information to the telephone Alan is using in the visiting office. An example set of feature buttons that are capable of being downloaded to Alan s visiting telephone are listed in the Section 1.2. If Alan uses a different telephone type in the visiting office, Alan will have his call appearances and message waiting state indication from System A, but no additional telephone features programmed for his extension on System A. When the telephone at System B is associated to 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 visiting telephone at System B. Alan s home telephone at System A can only be used to make emergency calls while Alan is visiting the telephone at System B. Alan can make calls using the visiting 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-pan, or if the ARS access code and number are dialed via the dial-pad, the dial plan of the visiting 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 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 has been configured to allow this. Other types 3 of 25

4 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. Normally, the call will still be accessible at the user s home telephone or bridged appearances of that extension. Emergency calls made by the visiting user from the dial pad are a special case. When an emergency call (e.g., 911) is dialed, the digits are processed at the visiting switch and routed to the appropriate agency. An emergency call dialed by the visiting user also terminates the visiting 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 visiting 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) Personal CO-line (per-coline) Send All Calls (send-calls) These Application Notes detail the administrative steps needed to configure the Avaya Communication Manager Enterprise Mobility User feature. The network configuration consists of two locations; System A and System B. System A has a pair of Avaya S8710 Media Servers controlling two SCC1 Cabinets (Multi-connect) and System B has a pair of Avaya S8710 Media Servers controlling a G650 Media Gateway (IP connect). An H.323 (QSIG) trunk is established between these two locations. Avaya Modular Messaging system provides centralized messaging 4 of 25

5 service to both Systems. Figure 1 is the network configuration used for these Application Notes. Both Systems have a 5-digit dial plan. System A 3xxxx Avaya S8710 Media Server Pair Multi-Connect Server 1: Server 2: Avaya 4620SW IP Telephone x30000 Avaya 4610SW IP Telephone x xxxx System B Avaya 4620 IP Telephone x20002 Avaya S8710 Media Server Pair IP Connect Control Network Server 1: Server 2: IPSI(s) Ethernet Ethernet IP Wide Area Network C-LAN MEDPRO IPSI Ethernet CORP LAN Avaya SCC1 Media Gateway C-LAN(s) MEDPRO(s) Avaya Modular Messaging Avaya 2420 Digital Telephone x20010 Avaya G650 Media Gateway Avaya 2420 Digital Telephone x30010 Figure 1: Network Configuration for Enterprise Mobility User These Application Notes will not cover the Avaya S8710 Media Server and Avaya Modular Messaging system configuration. For documentation regarding these configurations, refer to user documentation listed in Section 11. In these Application Notes, any telephone that is not the home telephone is referred to as the visited telephone and any server that is not the home server of the home telephone is referred to as the visited server. 5 of 25

6 2. Equipment and Software Validated The following equipment and software were used for the sample configuration: Equipment Avaya S8710 Media Servers in System A Avaya TN2312BP IPSI in SCC1 Avaya TN799DP C-LAN in SCC1 Avaya TN2302AP MEDPRO in SCC1 Avaya S8710 Media Servers in System B Avaya TN2312BP IPSI in G650 Media Gateway Avaya TN799DP C-LAN in G650 Media Gateway Avaya TN2302AP MEDPRO in G650 Media Gateway Software Communication Manager 3.1 Load R013x FW030 FW015 FW102 Communication Manager 3.1 Load R013x FW030 FW017 FW102 Avaya Modular Messaging 3.0 (Beta Version, build ) Avaya 4620SW/4610SW Load 2.3 Avaya 2420 Digital Telephone NA 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 3xxxx System A telephones 2xxxx 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 6 of 25

7 3. 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. The following is a list of 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. Avaya Communication Manager Release 3.1 or later software must be running on the home server and all visited servers. A Uniform Dial Plan directs calls to the QSIG trunks. 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. All endpoints must be terminals capable of paperless button label display. Define PSA permission for primary telephone must be set to y in Class of Service (COS). Supplementary services b (QSIG) must be used in trunk group between two Systems. The EMU feature has been designed for the newer type of self-designating telephones that have downloadable button configuration. These include Avaya 46xx series IP telephones and 24xx series digital telephones. SIP endpoints are not supported. Table 3 below lists the telephones supported for EMU. IP Telephones Digital Telephones 4610, 4610SW 2410 and , 4620SW Table 3: Telephones Supporting EMU 7 of 25

8 3.1. Verify Required Feature The following screens show Communication Manager licensed options for System A. Note that those required fields (bolded fields) have been set to y. Use the command display system-parameters customer-options to verify the required features are licensed. On Page 3, ensure that ARS is enabled. display system-parameters customer-options Page 3 of 11 OPTIONAL FEATURES Abbreviated Dialing Enhanced List? y Audible Message Waiting? y Access Security Gateway (ASG)? n Authorization Codes? n Analog Trunk Incoming Call ID? n Backup Cluster Automatic Takeover? n A/D Grp/Sys List Dialing Start at 01? n CAS Branch? n Answer Supervision by Call Classifier? y CAS Main? n ARS? y Change COR by FAC? n ARS/AAR Partitioning? y Computer Telephony Adjunct Links? n ARS/AAR Dialing without FAC? n Co-Res DEFINITY LAN Gateway? n ASAI Link Core Capabilities? y Cvg Of Calls Redirected Off-net? y ASAI Link Plus Capabilities? y DCS (Basic)? y Async. Transfer Mode (ATM) PNC? n DCS Call Coverage? y Async. Transfer Mode (ATM) Trunking? y DCS with Rerouting? y ATM WAN Spare Processor? n ATMS? y Digital Loss Plan Modification? y Attendant Vectoring? y DS1 MSP? y DS1 Echo Cancellation? Y On Page 4, ensure that IP Trunks and ISDN-PRI are enabled. In these Application Notes, IP Stations and Media Encryption over IP are used, but these are not required in general. display system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y IP Stations? y Enable 'dadmin' Login? y Internet Protocol (IP) PNC? n Enhanced Conferencing? y ISDN Feature Plus? y Enhanced EC500? y ISDN Network Call Redirection? y Enterprise Survivable Server? n ISDN-BRI Trunks? n Enterprise Wide Licensing? n ISDN-PRI? y ESS Administration? y Local Survivable Processor? n Extended Cvg/Fwd Admin? y Malicious Call Trace? y External Device Alarm Admin? n Media Encryption Over IP? y Five Port Networks Max Per MCC? n Mode Code for Centralized Voice Mail? n Flexible Billing? n Forced Entry of Account Codes? y Multifrequency Signaling? y Global Call Classification? n Multimedia Appl. Server Interface (MASI)? n Hospitality (Basic)? y Multimedia Call Handling (Basic)? n Hospitality (G3V3 Enhancements)? y Multimedia Call Handling (Enhanced)? n IP Trunks? y IP Attendant Consoles? Y 8 of 25

9 On Page 5, ensure that 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 3.2. System Features Showing QSIG Parameters Use the command display system-parameters features to verify that the QSIG TSC extension is configured on Page 8. display system-parameters features Page 8 of 17 FEATURE-RELATED SYSTEM PARAMETERS ISDN PARAMETERS Send Non-ISDN Trunk Group Name as Connected Name? n Display Connected Name/Number for ISDN DCS Calls? n Send ISDN Trunk Group Name on Tandem Calls? n Send Custom Messages Through QSIG? y QSIG TSC Extension: MWI - Number of Digits Per Voice Mail Subscriber: 5 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? y Path Replacement with Measurements? n QSIG Path Replacement Extension: Path Replace While in Queue/Vectoring? N 9 of 25

10 4. Configure Avaya Communication Manager EMU Feature This section illustrates foundational aspects of the Avaya Communication Manager EMU configuration for Figure 1. Note that both System A and System B are running its own Avaya Communication Manager 3.1 systems. An IP QSIG trunk is established between two C-LANs from two Systems. An Avaya Messaging Application Server (MAS) is connected to the SCC1 at System A using an IP H.323 with QSIG enabled. Uniform dial plan is configured at both System A and B and the Modular Messaging system provides voice message service for both Systems 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. 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-B MAS MedPro-A MedPro-B C-LAN-System-B Configure Avaya Communication Manager on System A 5.1. Configure H.323 Signaling Group and Trunk Group to System B The following screen shows that signaling group 3 is an H.323 signaling group using the C-LAN with node name C-LAN-A. Supplementary Service Protocol b is selected for QSIG features. The Far-end Node Name is the C-LAN in the G650 Media Gateway in System B. 10 of 25

11 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? n 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 The following screens describe trunk group 3, the trunk group associated with signaling group 3. 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 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 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 11 of 25

12 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. 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 : 5.2. Configure Codec Set and IP Network Region Codec set 1 is used for inter-region connectivity between these two Systems. Use the command change ip-codec-set to configure Codec. In this configuration, the G.729 is used in the 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: 12 of 25

13 Network Region 8 is used 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? n 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 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 25

14 5.3. Configure the Route Pattern to System B There are many ways to manipulate digits before the call leaves switch. In this configuration, since System A and System B are using different digit range, there is no need to manipulate digits between two Systems. The following screen illustrates the AAR analysis form, showing how the digits 2xxxx (Extension range used in System B) are routed. Calls to System B will use the route pattern 3. display aar analysis 2 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 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 bank 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 14 of 25

15 6. Configure Avaya Communication Manager on System B 6.1. Configure H.323 Signaling Group and Trunk Group to System A The following screen shows that signaling group 2 is an H.323 signaling group using the C-LAN with node name C-LAN-B. Supplementary Service Protocol b is selected for QSIG features. The Far-end Node Name is the C-LAN-System-A in the SCC1 Cabinet in System A. 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? n 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 The following screens describe trunk group 2, the trunk group associated with signaling group 2. 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 15 of 25

16 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 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. 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 : 16 of 25

17 6.2. Configure Codec Set and IP Network Region Codec set 1 is used for inter-region connectivity between these two Systems. Use the command change ip-codec-set to configure Codec. In this configuration, the G.729 is used in the 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: Network Region 8 is used 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? n 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: 17 of 25

18 Choose codec 1 for network region 8 between 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 Configure the Route Pattern to System A The route pattern configuration is similar to the configuration on System A. The following screen illustrates the AAR analysis form, showing how the digits 3xxxx (Extension range used in System A) are routed. Calls to System A will use the route pattern 2. display aar analysis 2 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 The following screen shows the configuration of route pattern 2 to System A. 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: 3 Pattern Name: to bank 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 18 of 25

19 7. Configure Dial Plan and Feature Access Code The following screen illustrates the dial plan and feature access codes used as part of the configuration on both Systems. In this dial plan analysis form, the digit 8 is the AAR access code, and the digit 9 is the ARS access code. The first digit * with length 3 is also defined as a feature access code (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 1 3 dac 2 5 ext 3 5 ext 8 1 fac 9 1 fac * 3 fac Use command display feature-access-codes to verify that EMU feature access code has been configured properly. 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 (FACs) for both EMU activation and EMU deactivation must be set on all servers using EMU. Users must enter the FAC of the server in 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. 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: *78 19 of 25

20 8. Enable EMU on Stations 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. 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 The following steps describe the procedure to enable EMU feature on IP station The configuration is same for Digital stations. 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 Media Complex Ext: Survivable Trunk Dest? y IP SoftPhone? n Customizable Labels? y 20 of 25

21 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 MWI Served User Type: qsig-mwi Emergency Location Ext: Always Use? n IP Audio Hairpinning? y Audible Message Waiting? y Display Client Redirection? n Select Last Used Appearance? n Coverage After Forwarding? s Multimedia Early Answer? n Direct IP-IP Audio Connections? y 9. Verification Steps The following steps can be used to verify EMU operation. 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 two Systems. The following captures are displays 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 21 of 25

22 2. Dial Modular Messaging pilot number from station and verify that station can access its mailbox. Repeat this step for stations 30001, 30010, and Make a call from station to station Verify that call is successful. Repeat this step between stations and and verify that call is successful. 4. Make a call from station to station Do not answer the call and wait for the voice mail prompt. Leave message for station and verify that station has its MWI turned on. 5. Repeat step 4 for call from station to Verify that MWI is turned on for station EMU Feature: 1. On station dial the *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. 2. Verify that message Visited Registration Active: is displayed on station screen. 3. From System A switch, 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 B switch, 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. Program Abbreviated dial (abrv-dial) and Automatic Call Back (auto-cback) buttons on station On station dial the *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 changed to and feature button labels are received. 22 of 25

23 6. Use an abrv-dial button to make a call and verify that it works from the visiting station. 7. Make a call from station to station Verify that the visiting station (home station in System B) rings. Answer the call and verify that the call is successful. 8. Repeat step 7 and do not answer the call. Verify that Modular Messaging plays the greeting for station and user can leave message for station Verify that MWI on visited station is turned on for new voice mail for extension Use deactivation FAC to logoff station and verify that MWI goes off on station and station call appearance changed back to its native setting. 11. Make a call from station to station Verify that the visiting station (home station in System A) rings. Answer the call and verify that the call is successful. 12. Use the command status station to verify that signaling and audio paths are correct. status station Page 1 of 6 GENERAL STATUS Administered Type: 4620 Service State: in-service/off-hook Connected Type: 4620 TCP Signal Status: connected Extension: Port: S00000 Parameter Download: complete Call Parked? no SAC Activated? no Ring Cut Off Act? no CF Destination Ext: Active Coverage Option: 1 EC500 Status: N/A Message Waiting: Connected Ports: T00021 Off-PBX Service State: in-service/idle status station Page 3 of 6 CALL CONTROL SIGNALING Port: S00000 Switch IP IP Port Switch-end IP Addr:Port Set-end IP Addr:Port IP Signaling: 01A : :5143 H.245: Node Name: C-LAN-A Network Region: of 25

24 status station Page 4 of 6 AUDIO CHANNEL Port: S00000 Switch IP IP Port Other-end IP Addr :Port Set-end IP Addr:Port G.729 Audio: : :53902 Node Name: MedPro-B Network Region: 8 1 Audio Connection Type: ip-direct Port: S00000 Product ID and Release: IP_Phone 2.30 H.245 Tunneled in Q.931? does not apply Registration Status: registered-authenticated MAC Address: 00:04:0d:9b:7d:af Native NAT Address: not applicable ALG - NAT WAN IP address: not applicable Authentication Type: DES-56-plus Shared Port: 13. On station 30000, transfer the existing call to station and verify the call transfer successful. 14. Hang up the call. On station dial the *78 (EMU Deactivation FAC) followed by home station number and station security code. Verify that audible conformation tone is played on the station Verify that station can logoff from the station The call appearance and feature button labels are restored to its native mode. 10. Conclusion These Application Notes have provided the administrative details on configuring EMU feature for two independent Systems running Avaya Communication Manager 3.1. As illustrated in these Application Notes, the Avaya Communications Manager 3.1 can provide users mobility to work at any location within enterprise network as long as the EMU feature is enabled, and QSIG and dial plan are properly configured. 11. Additional References Use this URL to access this document. [1] Administrator Guide for Avaya Communication Manager 3.1/3.1.1 Issue: Feb-06, Document ID: of 25

25 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 25 of 25