Dialogic Media Gateway Installation and Configuration Integration Note. 1. Scope. 2. Configuration Details. 2.1 Dialogic Gateway

Transcription

1 Dialogic Media Gateway Installation and Configuration Integration Note 1. Scope This document is intended to detail a typical installation and configuration of Dialogic 1000 Media Gateway Series (DMG1000) when used with an Analog Telephone Adapter (Grandstream HandyTone HT-502). 2. Configuration Details Listed below are the specific details of the Dialogic gateway and Analog Telephone Adapter used in the testing to construct the following documentation. 2.1 Dialogic Gateway Gateway Model Software Version Protocol PBX/Integration Dialogic 1000 Media Gateway Series (DMG1008LSW) Version 6.0 SU3 or later Analog Avaya G3V9/In-band 2.2 Analog Telephone Adapter Vendor Model Grandstream HandyTone HT-502 V1.1C Software Program Bootloader Core Base Information Link 1

2 2.3 System Diagram The diagram below details the setup used in the testing and creation of the technical document. Public Fax PBX Stations ATA Station ATA Fax IP LAN or ATA Station 8 Analog Station Lines HandyTone HT-502 PBX Dialogic 1000 Media Gateway Series (DMG1008LSW) IP Application Server 3. Prerequisites 3.1 PBX Prerequisites This document assumes that PBX programming or Direct PSTN connectivity has been established by using other published PBX specific configuration guides. 3.2 Gateway Prerequisites The gateway used in this document is a Dialogic 1000 Media Gateway Series (DMG1008LSW) model, but this configuration can apply to other Dialogic 1000 Media Gateway Series (DMG1000) models. 4. Summary of Limitations Known limitation when transferring or conferencing between the two IP endpoints as SIP-to-SIP is unsupported on the DMG1000 series - see Section 8: Testing Validation Matrix for more details. 5. Network Configuration This document assumes that the following IP addresses and subnet masks were assigned: ATA Ethernet: IP: (Device Default) Used for configuration Subnet: ATA WAN: IP: Subnet: Gateway: IP: Subnet:

3 6. HandyTone HT-502 Setup The HandyTone HT-502 Quick Installation Guide is posted at: Alternatively, you can follow the steps below: 6.1 Configuration Via Web Access - Connect your PC to the HandyTone HT-502 LAN port - Set your PC IP address to Type (The HandyTone HT-502 default LAN port IP Address) in a web browser and hit Enter - Login using the default password admin 3

4 6.2 HandyTone HT-502 WAN Port Configuration - Click on: Basic Settings tab - Click on: statically configured as radio button - Set IP Address: Set Subnet Mask: Set WAN side HTTP/Telnet access: Yes (If Device WAN configuration Access is desired) -Click on Update -Click Reboot for the changes to take effect 4

5 6.3 Telephone Line Configuration After logging back in: FXS Port 1: - Click on FXS Port 1 tab - Complete the following fields: - Primary SIP Server: (Gateway IP Address) - SIP transport: TCP - SIP User ID: User ID is phone number: Yes - SIP Registration: No - Click on Update - Click Reboot for the changes to take effect 5

6 FXS Port 2: - Click on FXS Port 2 tab - Complete the following fields: - Primary SIP Server: (Gateway IP Address) - SIP transport: TCP - SIP User ID: User ID is phone number: Yes - SIP Registration: No - Click on Update - Click Reboot for the changes to take effect 6

7 7. Gateway Setup Notes Steps for setting up the gateway: Connection Parameter Configuration Routing Engine Configuration o VoIP Host Group o Inbound TDM Rules o Inbound VoIP Rules 7.1 Connection Set your computer to the following network settings: IP: Subnet Mask: Login to the gateway via web browser at: Set the Gateway IP and Subnet to: IP: Subnet Mask: Reboot the gateway Set your computer back to the following network settings: IP: Subnet Mask: Login to the gateway via web browser at: 7

8 7.2 Parameter Configuration Refer to other published configuration guides depending on your IP application. For Microsoft Office Communications Server 2007, refer to: Routing Engine Configuration In this example, we will assume that the two HandyTone HT-502 ATA extension numbers are 3201 and Their corresponding IP addresses on the ATA side are: :5060 and : VoIP Host Groups First, create two VoIP host groups (ATA Port 1 and ATA Port 2). ATA Port 1 = :5060 ATA Port 2 = :5062 When inbound TDM calls are targeted to ATA extensions 3201 or 3202, the gateway will use inbound TDM rules in order to route these calls to the two VoIP host group destinations. 8

9 7.2.2 Inbound TDM Rules Create two Inbound TDM rules in order to route TDM calls targeted for the two ATA extensions (3201 and 3202) to their respective destinations. Inbound Rule #1: Create an inbound TDM rule that matches a called number of 3201 and routes it to ATA Port 1 VoIP host group created in the previous step. Important Note: Ensure that this rule is listed prior to the general inbound TDM rule. 9

10 Inbound Rule #2: Create an inbound TDM rule that matches a called number of 3202 and routes it to ATA Port 2 VoIP host group created in the previous step. Important Note: Ensure that this rule is listed prior to the general inbound TDM rule. 10

11 7.2.3 Inbound VoIP Rules Create two inbound VoIP rules which deal with routing IP calls to 3201 and 3202 including calls from on ATA port to the other. Inbound IP Called Party = 3201 then Route to Host Group ATA Port 1 11

12 Inbound IP Called Party = 3202 then Route to Host Group ATA Port 2 Note: Calls between the ATA Extensions are processed through the gateway and utilize these two rules. 12

13 8. Testing Validation Matrix The table below shows various test scenarios that were executed in this configuration and their results - ATA Port 1 is connected to an analog telephone - ATA Port 2 is connected to an analog telephone Test Number Call Scenario Description Notes Inbound TDM calls 1 Inbound Call to PBX destination Inbound Call to PBX destination 3202 Outbound to VOIP (From one ATA port to the other) 1 Outbound from 3201 to Outbound from 3202 to 3201 Outbound to TDM 1 Outbound from 3201 to PBX Extension 2 Outbound from 3202 to PBX Extension 3 Outbound from 3201 to External Number 4 Outbound from 3202 to External Number Blind Call Transfer 1 Inbound to 3201, 3201 transfer to Inbound to 3201, 3201 transfers to PBX Extension 3 Inbound to 3201, 3201 transfers to External Number Fail (SIP-to-SIP is unsupported on the DMG1000 series) 13

14 Attended Call Transfer 1 Inbound to 3201, 3201 transfers to Inbound to 3201, 3201 transfers to PBX Extension 3 Inbound to 3201, 3201 transfers to External Number Fail (SIP-to-SIP is unsupported on the DMG1000 series) (Uses 2 Gateway Ports) (Uses 2 gateway ports) Bellcore Style 3-Way Conference 1 Inbound to 3201, 3201 initiates 3 way conference to 3202, 3202 answers, 3201 completes the conference. 2 Inbound to 3201, 3201 initiates 3 way conference to PBX #, PBX # answers, 3201 completes the conference. 3 Inbound to 3201, 3201 initiates 3 way conference to external #, external # answers, 3201 completes the conference. (Uses 2 Gateway Ports) (Uses 2 Gateway Ports) Fax 1 Inbound to 3201 and 3202 HP LaserJet Outbound from 3201 and 3202 HP LaserJet 3100 Notes: Blind Transfer Assume that call Caller A and B are in conversation. A wants to Blind Transfer B to C: 1. Caller A presses FLASH on the analog phone to hear the dial tone. 2. Caller A dials *87 then dials caller C s number, and then # (or wait for 4 seconds) 3. Caller A will hear the confirm tone. Then, A can hang up. Attended Transfer Assume that Caller A and B are in conversation. Caller A wants to Attend Transfer B to C: 1. Caller A presses FLASH on the analog phone for dial tone. 2. Caller A then dials Caller C s number followed by # (or wait for 4 seconds). 3. If Caller C answers the call, Caller A and Caller C are in conversation. Then A can hang up to complete transfer. 4. If Caller C does not answer the call, Caller A can press flash to resume call with Caller B. 14

15 Bellcore Style 3-Way Conferencing Assume that call party A and B are in conversation. Caller A (HandyTone HT-502) wants to bring third Caller C into conference: 1. A presses FLASH (on the analog phone, or Hook Flash for old model phones) to get a dial tone. 2. A dials C s number then # (or wait for 4 seconds). 3. If C answers the call, then A presses FLASH to bring B, C in the conference. 4. If C does not answer the call, A can press FLASH back to talk to B. 5. If A presses FLASH during conference, C will be dropped out. 6. If A hangs up, the conference will be terminated for all three parties when configuration Transfer on Conference Hangup is set to No. If the configuration is set to Yes, A will transfer B to C so that B and C can continue the conversation. For more details, please consult the HandyTone HT-502 documentation at: 15

16 9. Troubleshooting 9.1 Important Debugging Tools Ethereal/Wireshark Used to view and analyze the network captures provided by the Dialogic gateway diagnostic firmware. Adobe Audition Used to review and analyze the audio extracted from the network captures to troubleshoot any audio-related issues. 9.2 Important Gateway Trace Masks These keys are helpful during all troubleshooting scenarios and should be considered keys to activate by default fro all troubleshooting cases. voip prot and voip code this allows the collection of all SIP-related messages as they are sent from and received by the gateway. This data is important in cases where you feel that the gateway is not able to communicate properly with the messaging server. tel event and tel code This allows the collection of all circuit-side activity of the emulated station set such as display updates, key presses, light transitions and hook state changes. This data is very important in the following scenarios: o Call control problems (dropped calls, failing transfers, etc ) o Integration problems (incorrect mailbox placement, missed auto-attendant greetings etc ) teldrv prot This allows the collection of all ISDN messages both transmitted and received on the gateways front-end interface. This data is very important in the following scenarios: o Call control problems (dropped calls, failing transfers, etc ) o Integration problems (incorrect mailbox placement, missed auto-attendant greetings etc ) Routingtable (all keys) This allows you to look inside the routing table engine and see how matching rules and CPID manipulation rules work with respect to your call. This data is very important in the following scenarios: o Call routing problem (reaching the incorrect Microsoft Office Communications Server 2007 client or no client at all, etc ) Note: Turning on all traces is not recommended. Doing this floods the debug stream with significant amounts of information that can cause delays in determining the root cause of a problem. 16

17 Copyright and Legal Notice Copyright 2009 Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation at the address provided below. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Corporation or its subsidiaries ( Dialogic ). Reasonable effort is made to ensure the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY. Dialogic products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries, and thus may not function properly in other countries. You are responsible for ensuring that your use of such products occurs only in the countries where such use is suitable. For information on specific products, contact Dialogic Corporation at the address indicated below or on the web at It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing collateral produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by third parties. Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such product in accordance with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a signed agreement with Dialogic. More detailed information about such intellectual property is available from Dialogic s legal department at 9800 Cavendish Blvd., 5 th Floor, Montreal, Quebec, Canada H4M 2V9. Dialogic encourages all users of its products to procure all necessary intellectual property licenses required to implement any concepts or applications and does not condone or encourage any intellectual property infringement and disclaims any responsibility related thereto. These intellectual property licenses may differ from country to country and it is the responsibility of those who develop the concepts or applications to be aware of and comply with different national license requirements. Dialogic, Dialogic Pro, Brooktrout, Diva, Cantata, SnowShore, Eicon, Eicon Networks, NMS Communications, NMS (stylized), Eiconcard, SIPcontrol, Diva ISDN, TruFax, Exnet, EXS, SwitchKit, N20, Making Innovation Thrive, Connecting to Growth, Video is the New Voice, Fusion, Vision, PacketMedia, NaturalAccess, NaturalCallControl, NaturalConference, NaturalFax and Shiva, among others as well as related logos, are either registered trademarks or trademarks of Dialogic Corporation or its subsidiaries. Dialogic s trademarks may be used publicly only with permission from Dialogic. Such permission may only be granted by Dialogic s legal department at 9800 Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada H4M 2V9. Any authorized use of Dialogic s trademarks will be subject to full respect of the trademark guidelines published by Dialogic from time to time and any use of Dialogic s trademarks requires proper acknowledgement. Microsoft is a registered trademark of Microsoft Corporation in the United States and/or other countries. Other names of actual companies and products mentioned herein are the trademarks of their respective owners. This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property rights November