1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Gateway
  5. QuesCom 400
  6. Application notes

Avaya QuesCom 400 Application Notes

Ip/gsm gateway with avaya communication manager using h.323
Hide thumbs Also See for QuesCom 400:
Table of Contents

Advertisement

Quick Links

Avaya Solution & Interoperability Test Lab
Application Notes for Configuring QuesCom 400 IP/GSM
Gateway with Avaya Communication Manager using H.323
Trunks – Issue 1.0
These Application Notes describe the configuration steps required for the QuesCom IP/GSM
400 to successfully interoperate with Avaya Communication Manager using H.323 trunks.
The QuesCom 400 IP/GSM is an IP-GSM-gateway, supporting outgoing and incoming GSM
calls. All GSM calls made from Avaya Communications Manager will be routed to the
QuesCom 400 IP/GSM gateway to the GSM network. The QuesCom 400 IP/GSM can also
receive calls from the GSM network and route the calls to Avaya Communications Manager.
The QuesCom 400 IP/GSM can provide a backup route for the PSTN and also be backed up
by the PSTN.
Information in these Application Notes has been obtained through compliance testing and
additional technical discussions.
Program at the Avaya Solution and Interoperability Test Lab.
HJP; Reviewed:
SPOC 9/14/2006
Abstract
Testing was conducted via the DeveloperConnection
Solution & Interoperability Test Lab Application Notes
©2006 Avaya Inc. All Rights Reserved.
1 of 27
QuescomACM_H323

Advertisement

Table of Contents
loading

Related Manuals for Avaya QuesCom 400

Summary of Contents for Avaya QuesCom 400

  • Page 1 QuesCom 400 IP/GSM gateway to the GSM network. The QuesCom 400 IP/GSM can also receive calls from the GSM network and route the calls to Avaya Communications Manager. The QuesCom 400 IP/GSM can provide a backup route for the PSTN and also be backed up by the PSTN.
  • Page 2 GSM network and route the calls to Avaya Communications Manager. The QuesCom 400 IP/GSM can provide a backup route for the PSTN and also be backed up by the PSTN. This can be configured in Avaya Communication Manager using Automatic Route Selection (ARS).

  • Page 3: Equipment And Software Validated

    Display the system-parameters special-applications command and ensure that (SA8507) - H245 Support With Other Vendors? is set to “y”. If not, contact your Avaya authorized sales representative to enable this feature. Note: This feature only needs to be enabled if FastStart is enabled on the QuesCom 400 IP/GSM.

  • Page 4: Pstn E1 Isdn-Pri

    3.2. PSTN E1 ISDN-PRI This section displays the PSTN E1 ISDN-PRI configuration on Avaya Communication Manager in the sample configuration of Figure 1. See Section 9 for Avaya documentation references. Step Description Enter the display ds1 <board location> to display the PSTN DS1 Circuit Pack configuration.
  • Page 5 Trunk Group for NCA TSC: 19 Trunk Group for Channel Selection: 19 X-Mobility/Wireless Type: NONE Supplementary Service Protocol: a HJP; Reviewed: Solution & Interoperability Test Lab Application Notes 5 of 27 SPOC 9/14/2006 ©2006 Avaya Inc. All Rights Reserved. QuescomACM_H323...
  • Page 6 3.3. H.323 Trunks and Signaling Groups The steps in this section create an H.323 IP trunk group to the QuesCom 400 IP/GSM. Step Description Enter the change node-names ip command. Specify the node name and IP address for the QuesCom 400. Observe the node name of the C-LAN card shown in bold. These node names will be used in the configuration of the H.323 signalling group in Step 4.

  • Page 7: Trunk Features

    H.235 Annex H Required? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? n IP Audio Hairpinning? n Interworking Message: PROGress HJP; Reviewed: Solution & Interoperability Test Lab Application Notes 7 of 27 SPOC 9/14/2006 ©2006 Avaya Inc. All Rights Reserved. QuescomACM_H323...

  • Page 8: Ars Tables And Route Patterns

    In the sample configuration described in these Application Notes, when placing outbound calls to the public network, stations on Avaya Communication Manager must first dial the ARS Feature Access Code (FAC) before dialing an external number. The single digit “9” was used as the ARS FAC in the compliance-tested configuration (configuration step not shown).
  • Page 9 Step 1. Add two routing preference entries as follows: 1) First Routing Preference – H.323 IP trunk to QuesCom 400 • Grp No – enter the trunk group number routed to the QuesCom 400 gateway (see Section 3.3, Step 2) •...

  • Page 10: Avaya Extension To Cellular(Ec500) Configuration

    3.5. Avaya Extension to Cellular(EC500) Configuration Avaya Extension to Cellular allows a cell phone to be treated as if it were an extension defined in Avaya Communication Manager. This is accomplished by mapping the user’s main office phone to the cellular telephone number. All other types of calls, such as direct calls to and from the published cell phone number, are unaffected by Extension to Cellular.
  • Page 11 Outside callers may use the QuesCom 400 to reach Avaya Communication Manager extensions by first calling a SIM card number on the QuesCom 400. The QuesCom 400 may be configured to directly route incoming calls from the SIM card to a specific extension on Avaya Communication Manager.
  • Page 12 Enter the change off-pbx-telephone feature-name-extensions and enter extensions to be associated with Avaya Communication Manager features. For example, Idle Appearance Select can be used by an EC500 cell phone to make a call from an idle call appearance on the mapped office extension.

  • Page 13: Configure The Quescom 400 Ip/Gsm

    4. Configure the QuesCom 400 IP/GSM This section describes the steps for configuring the QuesCom 400 gateway. The steps are provided for illustration only; users should consult with Quescom for specific instructions. 4.1. QuesCom Server Configuration Step Description After the initial installation of the QuesCom server, telnet into the QuesCom server from the management PC shown in figure 1, using the default IP address “192.168.1.1.”.
  • Page 14 0 H.323 1 SIP > 0 VoIP Protocol: H.323 Enter “N” as the QuesCom 400 IP/GSM does not need to register to a GateKeeper in this configuration. Does the QuesCom IP/GSM need to register to a GateKeeper [Y/N]: N HJP; Reviewed: Solution &...
  • Page 15 0 No (to exit, and GWconfig /setup command can be re-entered) 1 Yes(to continue the setup and restart the QuesCom Q400) > 1 Setup is confirmed Wait for 3 minutes for the QuesCom 400 gateway to reboot. Setting up SmartIAD System Configuration... Setting up Gateway Application... Please wait...

  • Page 16: Quescom Routing Configuration

    IPaddress:8000>. For this configuration “http://10.1.10.55:8000” was entered. Log in using the appropriate user name and password. On the left hand side of the screen under the QuesCom 400 menu. Click on Licenses and Profiles VoIP Profile. A default entry is created with Name “NO_RAS_H323” due to the initial configuration in Section 4.1.
  • Page 17 The following screen is presented for illustration. Default values may be retained on the VoIP Profile screen below. On the left hand side of the screen under the QuesCom 400 menu, click on Objects Foreign Gatekeeper. An entry with the ID “CM” and the IP address of Avaya Communication Manager C-LAN board is created due to the initial configuration in Section 4.1.
  • Page 18 Service. Four entries are present by default. ID “3” is created by default and is routing for calls from Avaya Communication Manager to the QuesCom 400 gateway. ID “4” is routing of outbound calls from the QuesCom 400 gateway to the GSM network. Click on the pencil (edit) button next to ID “3”...
  • Page 19 Type is set to “VoIP Outgoing”. No other changes need to be made to the default values for the record ID 4 on the Service screen below. HJP; Reviewed: Solution & Interoperability Test Lab Application Notes 19 of 27 SPOC 9/14/2006 ©2006 Avaya Inc. All Rights Reserved. QuescomACM_H323...
  • Page 20 Step Description Routing of inbound calls to the QuesCom 400 gateway from the GSM network is created by clicking on the ADD RECORD button on the main Service screen shown in Step 6. On the Service screen, configure the following as shown below.
  • Page 21 Step Description 11. From the management PC shown in Figure 1, launch the QuesCom 400 QWA management console by clicking Start Programs QuesCom QuesCom Management Console. Right click on Management Console and click New Call Server. 12. In the Connection dialog, configure the following, and click OK: •...
  • Page 22 Q400 and click on Stop. Right click Q400 and click on Start and wait for the SIM cards to register. HJP; Reviewed: Solution & Interoperability Test Lab Application Notes 22 of 27 SPOC 9/14/2006 ©2006 Avaya Inc. All Rights Reserved. QuescomACM_H323...

  • Page 23: Interoperability Compliance Testing

    The main objectives were to verify that: • When internal extensions place outbound calls to GSM numbers, the calls are routed to the QuesCom 400, and the QuesCom 400 decides on the least cost routing and routes the call to the GSM network.

  • Page 24: Verification Steps

    6. Verification Steps This section provides the tests that can be performed to verify proper configuration of Avaya Communication Manager and QuesCom 400. Step Description From the SAT, enter the command status signaling-group s, where s is the number of a signaling group configured in Section 3.3,...
  • Page 25 8. Conclusion These Application Notes describe the configuration steps required for QuesCom IP/GSM 400 to successfully interoperate with Avaya Communication Manager 3.1 using H.323 trunks. All feature functionality, performance and serviceability test cases were completed successfully. HJP; Reviewed: Solution & Interoperability Test Lab Application Notes...

  • Page 26: Additional References

    9. Additional References This section references the Avaya and QuesCom IP/GSM 400 product documentation that are relevant to these Application Notes. The following Avaya Documents are available at http://support.avaya.com Administrator Guide for Avaya Communication Manager, Document ID 03-300509, Issue 2, Feb 2006.
  • Page 27 2006 Avaya Inc. All Rights Reserved. © 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.

Table of Contents