How to Configure an Avaya TM IP600 Server With MultiTECH Systems MVP200 Gateway - Issue 1.0

Transcription

1 How to Configure an Avaya TM IP600 Server With MultiTECH Systems MVP200 Gateway - Issue 1.0 Abstract These Application notes describe the configurations that enable the Avaya IP600 Internet Protocol Communications Server to successfully interoperate with the MultiVOIP MVP200 Gateway from MultiTECH Systems for networking a main location with small or satellite offices. Each channel on the MVP200 Gateway can be set for FXS, FXO or E&M operation. Interoperability caveats and limitations are discussed within the Observations section. 1 of 16

2 1. Introduction The MultiVOIP MVP200 Gateway from MultiTECH Systems allows traditional analog voice transmission systems such as FXS (Foreign Exchange Station), FXO (Foreign Exchange Office), and analog E&M (Ear and Mouth) tie line connectivity over an IP network. The MVP200 Gateway converts the speech in each direction, allowing dissimilar networks to communicate with each other. These Application Notes are the result of a number of inquiries of the interoperability capabilities between Avaya and MultiTECH. The configuration in Figure 1 shows how the various Avaya components are interconnected to the MVP200 Gateway. In this configuration, the MVP200 Gateway translates the FXS telephone and analog E&M data formats to IP protocol procedures and vice versa. The MVP200 can also support FXO and is FAX capable. These application notes shall describe the configurations necessary to interconnect these devices. Avaya IP SoftPhone X 7716 To DHCP Server TFTP Server CLAN.4 Avaya IP600 Fax X-7707 Prowler Avaya IP Phone X H S 1 H S 2 OK 1 O K 2 PS CO L - A C T - S TA - P333T IP CON S O L E / 24 (subnet).85 DCP X-7704 FXS Channel 1 E & M Channel 2 Fax X-7374 FXS Telephone X-6350 Management Console MultiVOIP MVP200 Gateway Phone X-7399 Avaya DEFINITY or Other Vendor's PBX Figure 1: Avaya device connectivity through the MVP200 Gateway with E&M E&M operation on Avaya DEFINITY requires TN760 modules with the Trunk Group Type set to tie. 2 of 16

3 The configuration in Figure 2 illustrates MVP200 s FXO interface to the remote or vendor s PBX. Avaya IP SoftPhone X 7716 To DHCP Server TFTP Server Avaya IP Phone X-7712 CLAN Prowler TM Avaya IP CO L- H S 1 HS 2 O K 1 O K2 P S A C T- S T A - P333T IP / 24 (subnet) CONSOLE DCP X-7704 FXS Channel 1 FXO Channel 2 FXS Telephone X-6350 Management Console MultiVOIP Gatewa Phone X-7399 Avaya PBX or Vendor's Figure 2: FXO connectivity through the MVP200 Gateway FXO operation on the Avaya DEFINITY server is set up as a 2500 analog station type. 3 of 16

4 The configuration in Figure 3 illustrates an FXS channel on the MVP200 box being used as a FAX interface. Avaya IP SoftPhone X 7716 To DHCP Server TFTP Server CLAN TM Avaya IP600.4 Prowler Avaya IP Phone X H S 1 HS 2 O K 1 O K 2 P S C OL - A CT - S T A- C ONSOLE P333T IP / 24 (subnet) Fax X FXS Channel 1 Fax X-6350 Management Console MultiVOIP GW Figure 3: FAX Configuration 2. Equipment and Software Validated Avaya Product Version Avaya IP600 Server Version R010c Avaya IP Telephone (models 4612, Version ) Avaya IP Softphone Version MultiTECH Product Version MultiVOIP MVP200 Gateway Version 2.52 FAX Machine Model OKIFAX Internet Fax Observations The following observations are presented to reveal the conditions that produce optimal functionality between the MultiVOIP MVP200 Gateway and the Avaya communications server. 4 of 16

5 If the Avaya IP600 Server version is not R010c or later, an Avaya IP Telephone will not receive a ring back tone when a call to a MVP200 gateway using FXS, FXO or E&M is made. Although ring back tone is not heard on the Avaya IP Telephone, the FXS, FXO or E&M telephone endpoint connected to the MVP200 Gateway should ring properly, and normal voice is heard in both directions when calls are answered. The Avaya solution should be administered so IP Shuffling is disabled. With IP shuffling set to y, only one-way conversation is heard when an Avaya IP Telephone calls a FXS, FXO or E&M telephone endpoint connected to the MVP200 Gateway. If a call is initiated from the MVP200 Gateway, the MVP200 Gateway generates a Buserror and the box resets. IF fax operation is intended between the two sites and the connection is through a MultiVOIP MVP200, the best way to set it up is as an FXS Connection using G.711 codec. Referring to Figure 1, FAX operation from X-7374 to X-7707 functions correctly. FAX operation did not function when attempting to FAX from X-7707 to X FAX Note: MVP200 s FAX Enable configurable flag was not enabled on either channel 1 or channel 2 (See Figure 8). If MVP200 s FAX Enable switch was enabled, when faxing from X7707 to X-7374 a Buserror would occur and the box would reset. Referring to Figure 2, FAX operation through an FXO interface does not function. Attempting to FAX through an FXO interface causes a Buserror if MVP200 s FAX Enable switch is enabled. IP Hairpinning functions at G.711 and G.729. Note: When multiple codecs are configured on the Avaya IP600 Server (IP-codec), the codec at the top of the list must match the codec that is set on the MVP200 Gateway box. If not, IP Hairpinning will not occur because the station status command results in an ip_tdm status. When operating properly, the station status command results in an ip_hairpin status. In the telephone directory, a leading colon (:) is required with a telephone number when communicating to an E&M or FXO channel. This procedure is not in the MultiTECH Users Guide Manual ( Rev C). Currently there is a problem with a leading character other than numeric. Therefore, the colon needs to be preceded by a number or a group of numbers. See section 4.8 for details on how to overcome this obstacle. Pin 7 on Multitech s E&M RJ45 connector should be grounded at the Avaya DEFINITY or other Vendor s PBX Summarization of Interoperability Effort The following table summarizes the interoperability between Avaya and MVP200: 5 of 16

6 MuiltiTECH VOICE Operation IP FXS IP FXO IP E&M FAX Operation IP FXS IP FXO IP E&M Functionality Works correctly for VoIP calls using both G.711 and G.729. Works correctly for VoIP calls using both G.711 and G.729. Works correctly for VoIP calls using both G.711 and G.729. Works correctly for FAX calls using G.711. Does not work correctly for FAX calls Does not work correctly for FAX calls. FAX calls from E&M to IP work correctly using G.711. FAX calls from IP to E&M fail. 4. MultiTECH MVP200 Gateway Configuration The MVP200 Gateway configuration interface requires software to be loaded on a local PC. It also requires a serial connection between the PC and the MVP200 gateway (provided), an RJ45 connection to an Ethernet 10Base-T network, and connections to end-point devices, such as in this case, the FXS, FXO and E&M interfaces. Details of configuring the MultiVOIP MVP200 can be found at the MultiTECH WEB site: The MVP200 Gateway configuration below is an overview of what is presented in the manual Software Loading Prior to installing the MVP200 Gateway software, all cabling and network connections must be in place. During the software setup process, the user will be prompted for configuration information. The installation configuration screens below are displayed in the sequence they appear during the setup process, and show the information used in this example configuration Port Setup Figure 4 is a screen shot of the Port Setup screen. Choose the appropriate Communication Type, where COM Port is default, then choose Select Port, where COM1 is default. Port Setup allows PC connectivity to the MVP200, where administration is performed. 6 of 16

7 Figure 4: MVP200 Gateway COM Port Setup screen The Init String and Hangup String are predefined values IP Setup Figure 5 is a screen shot of the IP Protocol Default Setup screen. Here, place the IP address assigned to the MVP200 Gateway, the appropriate mask, and the IP address of the network gateway. Figure 5: IP Protocol Default Setup screen 4.4. Channel 1 Setup -- FXS Channel 1 is set up for FXS (Loop Start) and is the channel s default. Figure 6 displays the Channel Setup screen. 7 of 16

8 Figure 6: Channel 1: FXS Setup 4.5. Channel 2 Setup -- E&M To administer another Channel, click on the Select Channel down arrow and select Channel 2. Channel 2 in this configuration is the setup for E&M. Figure 7 displays Setup screen for Channel 2. Figure 1 illustrates Channel 2 being set up as E&M. Figure 7: Channel 2: E&M Setup 8 of 16

9 4.6. Channel 2 Setup -- FXO To administer channel 2 as an FXO, click on the Select Channel down arrow and select Channel 2. Select the FXO Interface button. Configuring an FXO on the MVP200 side requires an FXS (or an analog station) interface on the PBX side. Referring to Figure 2, a phone call from a device on the Avaya IP600 Server to an Avaya or other Vendor s PBX is handled in the same manner as an E&M connection. In the other direction however, when a user wishes to call from an Avaya or other Vendor s PBX to a device on an Avaya IP600 Server, the user must first dial extension The MVP200 box will then respond with a secondary dial tone. When the user hears the secondary dial tone, the desired end-point extension is entered and that phone should ring Codec Setup The Codec for each channel is set within the Voice/Fax tab. Figure 8: Manual Codec Setup 4.8. Phone Directory Telephone extensions, associated with IP addresses and Channel numbers, allows the MVP200 the capability of routing calls to the appropriate end-point. Telephone extensions associated with the different end-points are added into the database on this screen. To enter an extension and other information, click the Add button. 9 of 16

10 Figure 9: Phone Directory screen When an extension is added to the Phone Directory, the IP address and channel number (1 or 2) are also indicated here. The 9: (in this example, we have chosen a 9 ) in front of extension 73XX (where XX indicates wild characters), is required by the MVP200 Gateway to allow communication to an E&M or FXO channel (Note: See section for more information). Since channel 1 is set as FXS (Figure 1 and Figure 2) and channel 2 as E&M (Figure 1) or FXO (Figure 2), telephone calls to an E&M or FXO interface require this prefix colon (9:) convention. Calls to the FXS or default interface (63xx or 77xx) do not require this convention MultiVOIP Configuration Figure 10 displays the MultiVOIP Configuration screen. When the Voice Channels, Phone Book, or IP icon is clicked, the administrative interfaces previously discussed are displayed. 10 of 16

11 Figure 10: MVP200 Gateway Main Configuration Screen NOTE: Each time a change is made to the configuration, the Download Setup icon must be clicked so that the new setting are downloaded to the MVP200 Gateway Normal FAX Operation Normal FAX operation in both directions was achieved with the MVP200 configured as shown in Figure 3. The FAX machine is plugged directly into the MVP200 FXS port Avaya Configuration Signaling Group The following screen shots show the pertinent aspects of the Avaya IP600 Server configuration. The Far-end Node Name: within this Signaling group is pointed at MVP200 (MultiTECH) utilizing port The more important aspects are highlighted. Display or change the signaling group entries by entering: change signaling-group of 16

12 SIGNALING GROUP Group Number: 15 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 15 Supplementary Service Protocol: a Network Call Transfer? n Near-end Node Name: clan-ip600 Far-end Node Name: MultiTECH Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 1 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Bypass If IP Threshold Exceeded? n Direct IP-IP Audio Connections? n IP Audio Hairpinning? y Interworking Message: PROGress Trunk Group In this example, Trunk Group 15 is associated with Signaling Group 15. In addition, it includes trunk member assignment. Display or change the trunk group entries by entering: change trunk-group 15. TRUNK GROUP Group Number: 15 Group Type: isdn CDR Reports: y Group Name: Alternate IP600 Test Networ COR: 1 TN: 1 TAC: 106 Direction: two-way Outgoing Display? y Carrier Medium: IP Dial Access? n Busy Threshold: 99 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 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 QSIG Value-Added? n Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 Trunk Group 15 Port Members TRUNK GROUP Administered Members (min/max): 1/7 GROUP MEMBER ASSIGNMENTS Total Administered Members: 7 12 of 16

13 Port Code Sfx Name Night Sig Grp 1: T : T : T : T : T : T : T : Node Names-IP The Node Names-IP form configures C-LANs, Prowlers, Gateways and their associated IP addresses. Display or change the IP node names entries by entering: change node-name ip. IP NODE NAMES Name IP Address Name IP Address clan-ip MultiTECH default prowler IP Interfaces The IP Interfaces form defines gateway router IP addresses for C-LANs and Prowlers. Display or change the IP interface by entering: change ip-interface. IP INTERFACES Enable Net Eth Pt Type Slot Code Sfx Node Name Subnet Mask Gateway Addr Rgn y C-LAN 01A04 TN799 C clan-ip y MEDPRO 01A05 TN2302 prowler n IP Network Regions Display or change the IP network region by entering: change ip-interfaces 1 Region: 1 Name: main Audio Parameters Codec Set: 1 UDP Port Range Min: 2048 Max: DiffServ PHB Value: 40 IP Network Region 13 of 16

14 802.1p/Q Enabled? n DiffServ PHB Value: 40 Direct IP-IP Audio Connections? y IP Audio Hairpinning? y IP Codec Display or change the IP codec definition(s) by entering: change ip-codec IP Codec Set Codec Set: 1 Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n : G.729 n Route Pattern This Route pattern is used when an Avaya IP600 Server user dials extension 73XX. Note that the digit 9 (i.e. the chosen number for this test) is inserted. When extension 7399 is dialed, the digits are sent out. The inserted digit 9 is required by the MVP200 Gateway E&M channel interface as shown in Section 4.8. change route-pattern 73 Pattern Number: 73 Grp. FRL NPA Pfx Hop Toll No. Inserted No. Mrk Lmt List Del Digits Dgts 1: : 3: FAX Configuration On both the Avaya IP600 Server and the Avaya DEFINITY, the FAX machine is plugged directly into an analog phone port configured as a 2500 phone set. 5. Conclusion After these configuration steps are completed, the Avaya IP600 Server will be able to successfully interoperate with the MultiVOIP MVP200 Gateway from MultiTECH Systems with the caveats and limitations indicated. This facilitates interoffice communications via the IP network, thus avoiding the additional cost of dedicated FXO/FXS or E&M Tie Trunks between sites. With this solution any office that has an IP Connection can now exploit the data network for the voice traffic between Avaya voice systems and those of different manufacturers. Enterprises with more than two locations gain the added benefit of only requiring each location to have only one MultiVOIP 200 Gateway connecting to the IP network. In legacy voice 14 of 16

15 networks multiple dedicated facilities and hardware would be required to support communications between more than two locations. Traffic volumes would dictate the appropriateness of this solution, but for small volume communications between satellite offices this solution can have many valuable applications. 15 of 16

16 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 and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 16 of 16