User`s manual

ManualsBrandsAudioCodes ManualsNetworkingMediant 1000

™ Mediant™ Media Gateways

H.323 Mediant 1000

Document #: LTRT-83401 December 2006

User’s Manual Version 5.0

Summary of content (462 pages)

PAGE 1
™ Mediant™ Media Gateways H.323 Mediant 1000 User’s Manual Version 5.
PAGE 2
PAGE 3
H.323 User's Manual Contents Table of Contents 1 Overview ............................................................................................................21 1.1 Mediant 1000 Features .......................................................................................... 22 1.1.1 1.1.2 1.1.3 2 Mediant Physical Description ..........................................................................27 2.1 Mediant 1000 Front Panel..............................................................
PAGE 4
Mediant 1000 5 Web Management..............................................................................................55 5.1 5.2 Computer Requirements ........................................................................................ 55 Protection and Security Mechanisms..................................................................... 55 5.2.1 5.2.2 5.2.3 5.3 Accessing the Embedded Web Server .................................................................. 57 5.3.1 5.
PAGE 5
H.323 User's Manual 5.6.2 5.6.3 5.6.4 5.6.5 5.6.6 5.6.7 5.6.8 5.7 5.7.2 5.7.3 Gateway Statistics ................................................................................................ 177 5.7.1.1 IP Connectivity ...................................................................................... 177 5.7.1.2 Call Counters......................................................................................... 179 5.7.1.3 Call Routing Status....................................................
PAGE 6
Mediant 1000 6.4 The ini File Structure ............................................................................................ 210 6.4.1 6.4.2 6.5 The ini File Parameter Reference ........................................................................ 212 6.5.1 6.5.2 6.5.3 6.5.4 6.5.5 6.5.6 6.5.7 6.5.8 6.5.9 6.5.10 6.5.11 6.5.12 6.5.13 7 Networking Parameters ........................................................................................ 212 System Parameters ..........................
PAGE 7
H.323 User's Manual 8.9 8.10 8.11 8.12 Contents Call Termination on Mediant 1000 FXO............................................................... 268 Mapping PSTN Release Cause to H.323 Response ........................................... 269 Call Detail Report ................................................................................................. 269 Supported RADIUS Attributes.............................................................................. 271 8.12.1 RADIUS Server Messages ...
PAGE 8
Mediant 1000 11.5 Using Parameter Tables ...................................................................................... 303 11.5.1 11.5.2 11.5.3 11.5.4 11.5.5 Table Indices ........................................................................................................ 303 Table Permissions ................................................................................................ 304 Dynamic Tables vs. Static Tables ....................................................................
PAGE 9
H.323 User's Manual Contents 14.3 Syslog Support..................................................................................................... 342 14.3.1 Syslog Servers...................................................................................................... 343 14.3.2 Operation .............................................................................................................. 343 15 SNMP-Based Management ......................................................................
PAGE 10
Mediant 1000 C BootP/TFTP Configuration Utility ..................................................................381 C.1 C.2 C.3 C.4 C.5 C.6 C.7 C.8 C.9 C.10 When to Use the BootP/TFTP.............................................................................. 381 An Overview of BootP .......................................................................................... 381 Key Features........................................................................................................
PAGE 11
H.323 User's Manual Contents G Installation and Configuration of Apache HTTP Server...............................421 G.1 Windows 2000/XP Operation Systems ................................................................ 421 G.2 Linux Operation Systems ..................................................................................... 422 H OSN Server Hardware Installation .................................................................425 H.1 H.2 I Required Working Tools...........................
PAGE 12
Mediant 1000 List of Figures Figure 2-1: Mediant 1000 Front View and CPU Enlargement................................................................27 Figure 2-2: Mediant 1000 Front Layout ..................................................................................................28 Figure 2-3: Location of Front Panel LEDs ..............................................................................................31 Figure 2-4: Mediant 1000 Rear Connectors ..........................................
PAGE 13
H.323 User's Manual Contents Figure 5-42: General Media Settings Screen ...................................................................................... 148 Figure 5-43: E1/T1 Trunk Settings Screen.......................................................................................... 150 Figure 5-44: TDM Bus Settings Screen............................................................................................... 157 Figure 5-45: Configuration File Screen .....................................
PAGE 14
Mediant 1000 Figure 11-9: Software Upgrade Key Screen ....................................................................................... 313 Figure 11-10: Example of a Software Upgrade Key File Containing Multiple S/N Lines .................... 314 Figure 12-1: Metering Tone Relay Architecture .................................................................................. 317 Figure 12-2: ini File Example for TDM Tunneling (Originating Side) ..................................................
PAGE 15
H.323 User's Manual Contents Figure I-5: Selecting Extract Option .................................................................................................... 435 Figure I-6: Extract Files ....................................................................................................................... 435 Figure I-7: ISO-Extract screen............................................................................................................. 436 Figure I-8: Text Edit screen ................
PAGE 16
Mediant 1000 List of Tables Table 2-1: Mediant 1000 Front View Component Descriptions (continues on pages 27 to 28).............27 Table 2-2: CPU Module LEDs Description .............................................................................................31 Table 2-3: Analog I/O Modules LEDs Description..................................................................................31 Table 2-4: Digital I/O Modules LED Description....................................................................
PAGE 17
H.323 User's Manual Contents Table 5-46: Trunk Channel Status Color Indicators continues on pages 201 to 201) ........................ 201 Table 5-47: Description of the Module Status Indicators .................................................................... 201 Table 5-48: Description of Ethernet Ports, Dry Contacts, Power Supply, and Fan Tray Indicators.... 202 Table 5-49: Ethernet Port Information Parameters .............................................................................
PAGE 18
Mediant 1000 Table F-14: acBoardEthernetLinkAlarm Alarm Trap ........................................................................... 417 Table F-15: acKeepAlive Log Trap...................................................................................................... 418 Table F-16: acPerformanceMonitoringThresholdCrossing Log Trap.................................................. 418 Table F-17: acHTTPDownloadResult Log Trap ..........................................................................
PAGE 19
H.323 User's Manual Notices Notices Notice This document describes the AudioCodes Mediant 1000 Voice-over-IP (VoIP) H.323 media gateway. Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions.
PAGE 20
Mediant 1000 Related Documentation Document # Manual Name LTRT-832xx (e.g., LTRT-83201) Mediant 1000 H.323 Release Notes LTRT-835xx Mediant 1000 MEGACO-H.323-SIP Fast Track Guide Warning: Ensure that you connect FXS ports to analog telephone or to PBX-trunk lines only and FXO ports to CO/PBX lines only. Warning: Disconnect the Mediant 1000 from the mains and from the Telephone Network Voltage (TNV) before servicing.
PAGE 21
H.323 User's Manual 1 1. Overview Overview The AudioCodes Mediant 1000 is a best-of-breed Voice-over-IP (VoIP) H.323 media gateway, using field-proven, market-leading technology, implementing analog and digital cutting-edge technology. The Mediant 1000 is designed to seamlessly interface between TDM and IP networks, providing superior voice quality and optimized packet voice streaming (voice, fax, and data traffic) over IP networks.
PAGE 22
Mediant 1000 The Mediant 1000 supports various ISDN PRI protocols such as EuroISDN, North American NI2, Lucent™ 4/5ESS, Nortel™ DMS100 and others. In addition, it supports different variants of CAS protocols for E1 and T1 spans, including MFC R2, E&M immediate start, E&M delay dial / start, loop start and ground start.
PAGE 23
H.323 User's Manual 1.1.2 1. Overview Supports a configurable channel select mode per trunk group. Supports various number manipulation rules for IPÆTel and TelÆIP, called and calling numbers. Interworking of ISDN Progress message and Progress Cause. Supports transfer of User-to-User Information Element between H.323 and PRI. Interworking of Calling Name, Calling Name Presentation, and Redirect Number in QSIG-to-H.323 and H.323-to-QSIG calls.
PAGE 24
Mediant 1000 1.1.3 H.323 Features The Mediant 1000 H.323 gateway is built on and implements the RadVision™ H.323 version 4.2 protocol stack. The gateway complies with H.323 Version 4.0 ITU standard, H.245 Version 10 and H.225 Version 4. 1.1.3.1 1.1.3.2 Gatekeeper Registers to known Gatekeeper. Supports Gatekeeper registration with prefixes. Supports sending of Unregister request before reset. Uses routed or direct mode calls.
PAGE 25
H.323 User's Manual 1.1.3.3 1. Overview Supports collecting Digits from POTS (Plain Old Telephone Service) (for FXS gateways) or from PBX/PSTN (for FXO gateways) using predefined digit map. Supports one or two stage dialing for network to PBX/PSTN calls, using MP-10x/FXO gateway. Supports answer supervision (FXO) using detection of either polarity reversal or human voice.
PAGE 26
Mediant 1000 Reader's Notes H.
PAGE 27
H.323 User's Manual 2 2. Mediant Physical Description Mediant Physical Description Designed to meet Network Equipment Building System (NEBS) Level 3, the Mediant 1000 is a 19-inch industrial platform chassis, 1U high and 13.8 inch deep. The Mediant 1000 supports a scalable, modular architecture that includes up to six analog modules, up to four digital modules, a single CPU module, a power supply module and an optional fan tray module (the extractable modules are shown in Section 2.3 on page 33).
PAGE 28
Mediant 1000 Table 2-1: Mediant 1000 Front View Component Descriptions (continues on pages 27 to 28) Item # Label Component Description 4 CPU Spare CPU module slot and also used for OSN server where slot hosts connection module (for OSN Server installation, refer to Appendix H on page 425). 5 CPU Main CPU module. 6 Power 1 Spare power supply slot. 7 Power 2 Main power supply. 8 Schematic Extractable fan tray. Enlarged View of CPU 9 - Locking screws (2).
PAGE 29
H.323 User's Manual 2.1.1 2. Mediant Physical Description I/O Modules The Mediant 1000 can house both analog and or digital modules: Analog modules: the gateway supports up to six replaceable analog FXO and/or FXS modules. Each module contains four analog RJ-11 ports. Therefore, the gateway can support up to 24 analog ports (6 modules x 4 ports). Digital modules: the gateway supports up to four digital trunks (fully flexible, from a single up to four trunks per module).
PAGE 30
Mediant 1000 2.1.2.5 Reset Button (Labeled //) The Mediant 1000 Reset button is located directly above the RS-232 port. To reset the system, take a pointed object and press in the Reset button. You can also use the Reset button to restore the Mediant 1000 networking parameters to their factory default values (refer to Section 11.1 on page 297). 2.1.
PAGE 31
H.323 User's Manual 2.1.5 2. Mediant Physical Description Front Panel LEDs Figure 2-3 below, shows the location of the front panel LEDs on the Mediant 1000. They are described below in Table 2-2, Table 2-3, Table 2-4, and Table 2-5. Figure 2-3: Location of Front Panel LEDs Table 2-2: CPU Module LEDs Description LED Color State Ethernet 3 (Left LED) Orange Ports I & II 3 (Right LED) Green Blinking Activity. On Link OK.
PAGE 32
Mediant 1000 Table 2-4: Digital I/O Modules LED Description LED Location Color State LED Indication RJ-48c (Only for digital interfaces) 2 Green On Trunk is synchronized (normal operation) Red On Loss due to any of the following 4 signals: LOS - Loss of Signal LOF - Loss of Frame AIS - Alarm Indication Signal (the Blue Alarm) RAI - Remote Alarm Indication (the Yellow Alarm) - Off Either there is a failure / disruption in the AC power supply or the power is currently not being supplie
PAGE 33
H.323 User's Manual 2.3 2. Mediant Physical Description Mediant 1000 Modules The extractable Mediant 1000 modules are shown in Table 2-7 below. Table 2-7: Extractable Mediant 1000 Modules (continues on pages 33 to 34) Module Description CPU module Digital I/O module (e.g., 2 spans) 4-port FXS Analog I/O module 4-port FXO Analog I/O module 4-port FXO G Analog I/O module (for ground start support) Version 5.
PAGE 34
Mediant 1000 Table 2-7: Extractable Mediant 1000 Modules (continues on pages 33 to 34) Module Description Fan tray module with six fans and an air filter Power supply module H.
PAGE 35
H.323 User's Manual 3 3. Installing the Mediant 1000 Installing the Mediant 1000 This section provides information on the hardware installation procedure for the Mediant 1000. Caution Electrical Shock The equipment must only be installed or serviced by qualified service personnel. ¾ To install your Mediant 1000, take these 4 steps: 1. Unpack the Mediant 1000 (refer to Section 3.1 below). 2. Check the package contents (refer to Section 3.2 below). 3. Mount the Mediant 1000 (refer to Section 3.
PAGE 36
Mediant 1000 3.3 Mounting the Mediant 1000 The Mediant 1000 can be mounted on a desktop, or installed in a standard 19-inch rack. For detailed information on cabling the Mediant 1000, refer to Section 3.4 on page 37. 3.3.1 Mounting the Mediant 1000 on a Desktop The integral front brackets are not required for a desktop installation. Optionally, attach the four (supplied) anti-slide bumpers to the base of the Mediant 1000 and place it on the desktop in the position you require. 3.3.
PAGE 37
H.323 User's Manual 3. Installing the Mediant 1000 ¾ To place the Mediant 1000 on a 19-inch rack’s shelf, take these 2 steps: 1. Place the Mediant 1000 on a preinstalled shelf. 2. It is recommended to attach the Mediant 1000 integral front brackets to the frame of the rack to prevent it from sliding off the shelf during cabling. Use standard 19-inch rack bolts (not provided) to fasten the front of the Mediant 1000 to the frame of the rack.
PAGE 38
Mediant 1000 • Digital interfaces: Connect the E1/T1 trunk cables to the ports on the digital I/O module/s. Connect the other ends of the trunk cables to your PBX/PSTN switch. For a 1+1 or 2+2 fallback option, connect trunks 1 and 3 to your PBX, and trunks 2 and 4 to the PSTN. If the power fails, a relay connects trunks 1 to 2 and 3 to 4 (in the same module) acting as a fallback for PSTN trunks. RJ-48c trunk connectors are wired according to the figure below.
PAGE 39
H.323 User's Manual 3.4.2 3. Installing the Mediant 1000 Setting up a Dry Contact Relay Alarm System The dry contact ports I and II located on the gateway's CPU module (refer to Figure 2-1 on page 27), allows you to connect the gateway to an external audible or visual alarm system. The table below describes the operational status of these dry contact ports. Table 3-1: Dry Contact Operational Description Port Normal State Alarm Severity State I During normal operation, the dry contact is open.
PAGE 40
Mediant 1000 ¾ To set up a dry contact system, take these 2 steps: 1. Insert two wires into the mate’s spring-cage wire connectors in position 4 and 3 for the gateway's dry contact port I, and two wires in position 2 and 1 (for the gateway's dry contact port II), by performing the following: a. b. 2. 3.4.3 With a sharp, pointed object, press the position's corresponding orange button; the cage of the connection opens.
PAGE 41
H.323 User's Manual 3. Installing the Mediant 1000 The Lifeline provides a wired analog POTS phone connection to any PSTN or PBX FXS port when there is no power, or when the network connection fails. You can therefore, use the Lifeline phone even when the Mediant 1000 is not powered on or not connected to the network. The Lifeline splitter connects pins 1 and 4 to another source of an FXS port, and pins 2 and 3 to the POTS phone (refer to the Lifeline pinout in Figure 3-7 on page 41).
PAGE 42
Mediant 1000 3.5 Maintenance This section describes the following maintenance operations: 3.5.1 Replacing modules (refer to Section 3.5.1 on page 42) Inserting additional modules (refer to Section 3.5.2 on page 43) Replacing the Fan Tray unit (refer to Section 3.5.3 on page 43) Replacing Modules The Mediant 1000 I/O modules are hot-swappable (except for the OSN Server modules -refer to Appendix H on page 425). The replacement of Mediant 1000 communication modules (i.e.
PAGE 43
H.323 User's Manual 3.5.2 3. Installing the Mediant 1000 Inserting Modules to Previously Empty Slots The procedure below describes how to add additional modules (i.e., digital, and FXS and FXO analog) to previously empty module slots in the gateway. Warning: Adding a module to a previously empty slot must only be performed when the power to the gateway is switched off. Note: The standard FXO module supports outdoor and indoor (lightning protection) loop start signaling.
PAGE 44
Mediant 1000 ¾ To clean / replace the air filter, take these 7 steps: 1. Release the two screws on the top right-hand corner and the bottom right-hand corner of the front panel of the fan tray unit. 2. Pull the fan tray unit outward. Figure 3-9 below shows the fan tray unit slightly extracted. Figure 3-9: Slightly Extracted Fan Tray Unit 3. With your fingertips, grasp the steel frame of the air filter and separate it from the fan tray unit; you should be able to remove it relatively easily.
PAGE 45
H.323 User's Manual 3. Installing the Mediant 1000 5. Attach the (new / cleaned) air filter to the fan tray module; position the two holes on the filter over the pins on the fan tray (refer to Figure 3-10). 6. Insert the fan tray unit into its slot, until the front panel is flush with the chassis plate. 7. Fasten the two screws on the top right-hand corner and the bottom right-hand corner of the front panel of the fan tray unit. Version 5.
PAGE 46
Mediant 1000 Reader's Note H.
PAGE 47
H.323 User's Manual 4 4. Getting Started Getting Started The Mediant 1000 is supplied with default networking parameters (show in Table 4-1 below) and with an application software already resident in its flash memory (with factory default parameters). Before you begin configuring the gateway, change its default IP address to correspond with your network environment (refer to Section 4.2) and learn about the configuration methods available on the Mediant 1000 (refer to Section 4.1 below).
PAGE 48
Mediant 1000 4.2.1 Assigning an IP Address Using HTTP ¾ To assign an IP address using HTTP, take these 8 steps: 1. Disconnect the Mediant 1000 from the network and reconnect it to your PC using one of the following two methods: • Use a standard Ethernet cable to connect the network interface on your PC to a port on a network hub / switch. Use a second standard Ethernet cable to connect the Mediant 1000 to another port on the same network hub / switch.
PAGE 49
H.323 User's Manual 4. Getting Started ¾ To assign an IP address using BootP, take these 3 steps: 4.2.3 1. Open the BootP application (supplied with the Mediant 1000 software package). 2. Add client configuration for the Mediant 1000, refer to Section C.11.1 on page 387. 3. Use the reset button to physically reset the gateway causing it to use BootP; the Mediant 1000 changes its network parameters to the values provided by the BootP.
PAGE 50
Mediant 1000 The following configuration parameters can be queried or modified via the voice menu: Table 4-2: Configuration Parameters Available via the Voice Menu Item Number at Menu Prompt 4.2.4 Description 1 IP address 2 Subnet mask 3 Default gateway IP address 4 Primary DNS server IP address 7 DHCP enable / disable 11 MGCP call agent IP address (N/A) 12 MGCP call agent port number (N/A) 99 Voice menu password (initially 12345).
PAGE 51
H.323 User's Manual 2. 4. Getting Started To access the CLI using the RS-232 port, perform the following: Connect the RS-232 port to your PC (refer to Section 3.4.1 on page 38). Use serial communication software (e.g., HyperTerminalTM) to connect to the Mediant 1000. Set your serial communication software to the following communications port settings: ♦ Baud Rate: 115,200 bps ♦ Data bits: 8 ♦ Parity: None ♦ Stop bits: 1 ♦ Flow control: None The CLI prompt becomes available. a. b. 3.
PAGE 52
Mediant 1000 4.3 Configure the Mediant 1000 Basic Parameters To configure the Mediant 1000 basic parameters use the Embedded Web Server’s ‘Quick Setup’ screen (shown in Figure 4-1 below). Refer to Section 5.3 on page 57 for information on accessing the ‘Quick Setup’ screen. Figure 4-1: Quick Setup Screen ¾ To configure basic H.323 parameters, take these 6 steps: 1. If the Mediant 1000 is connected to a router with Network Address Translation (NAT) enabled, perform the following procedure.
PAGE 53
H.323 User's Manual 4. Getting Started 5. To configure the Tel to IP Routing Table, click the arrow button next to ‘Tel to IP Routing Table’. For information on how to configure the Tel to IP Routing Table, refer to Section 5.5.4.2 on page 98. 6. Click the Reset button, and then at the prompt, click OK; the Mediant 1000 applies the changes and restarts. You are now ready to start using the VoIP gateway.
PAGE 54
Mediant 1000 Reader's Notes H.
PAGE 55
H.323 User's Manual 5 5. Web Management Web Management The Embedded Web Server is used both for gateway configuration, including loading of configuration files, and for run-time monitoring. The Embedded Web Server can be accessed from a standard Web browser, such as Microsoft™ Internet Explorer, Netscape™ Navigator, etc. Specifically, users can employ this facility to set up the gateway configuration parameters.
PAGE 56
Mediant 1000 Table 5-1: Available Access Levels and their Privileges Access Level Numeric Representation* Security Administrator 200 Read / write privileges for all screens Administrator 100 Read-only privilege for security-related screens and read / write privileges for the others User Monitor 50 No access to security-related and file-loading screens and read-only access to the others No Access 0 No access to any screen Privileges * The numeric representation of the access level is used onl
PAGE 57
H.323 User's Manual 5.2.2 5. Web Management Limiting the Embedded Web Server to Read-Only Mode Users can limit access to the Embedded Web Server to read-only mode by changing the ini file parameter ‘DisableWebConfig’ to 1. In this mode all Web screens, regardless of the access level used, are read-only and cannot be modified. In addition, the following screens cannot be accessed: ‘Quick Setup’, ‘Web User Accounts’, ‘Maintenance Actions‘ and all file-loading screens.
PAGE 58
Mediant 1000 5.3.1 Using Internet Explorer to Access the Embedded Web Server Internet explorer’s security settings may block access to the gateway’s Web browser if they’re configured incorrectly. In this case, the following message is displayed: Unauthorized Correct authorization is required for this area. Either your browser does not perform authorization or your authorization has failed. RomPager server. ¾ To troubleshoot blocked access to Internet Explorer™, take these 3 steps 1.
PAGE 59
H.323 User's Manual 5.4.1 5. Web Management Submenu bar: appears on the top of screens and contains submenu options. Main action frame: the main area of the screen in which information is viewed and configured. Home icon: when clicked it opens the Home page screen (refer to Section 5.10 on page 197). Corporate logo: AudioCodes’ corporate logo. For information on how to remove this logo Section 11.5 on page 303.
PAGE 60
Mediant 1000 5.4.4 Searching for Configuration Parameters The Embedded Web Server provides a search engine that allows you to search any ini file parameter that is configurable by the Web server. The Search button, located near the bottom of the Main menu bar is used to perform parameter searches. You can search for a specific parameter (e.g., "EnableIPSec") or a sub-string of that parameter (e.g., "sec").
PAGE 61
H.323 User's Manual 3. 5. Web Management In the searched result list, click the required parameter to open the screen in which the parameter appears. The relevant parameter is highlighted in green in the screen for easy viewing. Figure 5-4: Searched Parameter Highlighted in Screen Note: If the searched parameter is not located, the "No Matches Found For This String" message is displayed. Version 5.
PAGE 62
Mediant 1000 5.5 Protocol Management The Protocol Management menu is used to configure the gateway’s H.323 parameters and tables. Note: Throughout this chapter, parameters contained within square brackets are the names used to configure the parameters via the ini file. 5.5.1 Protocol Definition Parameters Use this submenu to configure the following gateway’s specific H.323 protocol parameters: General parameters (refer to Section 5.5.1.1 on page 63) Gatekeeper parameters (refer to Section 5.5.1.
PAGE 63
H.323 User's Manual 5.5.1.1 5. Web Management General Parameters The General Parameters option is used to configure general H.323 parameters. ¾ To configure the general parameters under Protocol Definition, take these 4 steps: 1. Open the ‘General Parameters’ screen (Protocol Management menu > Protocol Definition submenu > General Parameters option); the ‘General Parameters’ screen is displayed. Figure 5-5: Protocol Definition, General Parameters Screen 2.
PAGE 64
Mediant 1000 Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description Connection Mode [IsFastConnectUsed, IsTunnelingUsed] Gateway’s connection modes: Normal [IsFastConnectUsed=0, IsTunnelingUsed=0] (default). Tunneling [IsFastConnectUsed=0, IsTunnelingUsed=1]. Fast Start [IsFastConnectUsed=1, IsTunnelingUsed=0]. Fast Start + Tunneling [IsFastConnectUsed=1, IsTunnelingUsed=1]. The Fast Start connection mode allows a media path to be established using H.
PAGE 65
H.323 User's Manual 5. Web Management Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description No [0] = Voice channel is opened after an Alert message is sent (default). Open Media on Connect [IsFSOpenMediaOnConne Yes [1] = Voice channel is opened after the call is answered and a Connect ct] message is sent.
PAGE 66
Mediant 1000 Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description Source Number Encoding Type [SourceEncodeType] Source number encoding type. This defines the encoding type of the calling phone number in H.225 Setup messages. You can select: E.164 [0] (default). H.323-ID [1]. E.164 & H.323-ID [2]. NPI/TON from Table [3]. NPI/TON & H323-ID [4]. Note 1: The values of NPI/TON in the Q.931 part of the H.
PAGE 67
H.323 User's Manual 5. Web Management Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description H.225 Dial Port [H225DialPort] TCP port number on which the gateway sends H.225/Setup messages. The valid range is 0 to 65534. The default value is 1720. Send Channel Non Standard Info [SendChannelNonStandar d] 0 = Don't send (default) 1 = Send If enabled the trunk and B-channel information is sent in Setup and Proceeding messages, in the non-standard part.
PAGE 68
Mediant 1000 Table 5-3: Protocol Definition, General Parameters (continues on pages 64 to 68) Parameter Description UseSourceNumberAsDisp layName [Use Source Number as Display Name] Applicable to TelÆIP calls. 0 = The Tel Source Number is used as the IP Source Number and the Tel Display Name is used as the IP Display Name (if Tel Display Name is received). If no Display Name is received from the Tel side, the IP Display Name remains empty (default).
PAGE 69
H.323 User's Manual 5.5.1.2 5. Web Management Gatekeeper Parameters Use this screen to configure parameters that are associated with Gatekeepers. ¾ To configure the Gatekeeper parameters, take these 4 steps: 1. Open the ‘Gatekeeper’ parameters screen (Protocol Management menu > Protocol Definition submenu > Gatekeeper option); the ‘Gatekeeper’ parameters screen is displayed. Figure 5-6: Gatekeeper Parameters Screen 2. Configure the Gatekeepers parameters according to Table 5-4. 3.
PAGE 70
Mediant 1000 Table 5-4: Gatekeeper Parameters (continues on pages 70 to 73) Parameter Description General Working with Gatekeeper [IsGatekeeperUsed] No [0] = Gatekeeper isn’t used. Yes [1] = Gatekeeper is used (default). If you are using a Gatekeeper, enter the IP address of the primary Gatekeeper in the ‘Gatekeeper IP address’ field. If you are not using a Gatekeeper, you must configure the Tel to IP Routing table on the gateway (described in Section 5.5.4.2 on page 98).
PAGE 71
H.323 User's Manual 5. Web Management Table 5-4: Gatekeeper Parameters (continues on pages 70 to 73) Parameter Description Second Gatekeeper ID [GatekeeperIP] String used to identify the first redundant Gatekeeper. Used in Registration Request (RRQ messages). The default value is an empty string. Note: This parameter is available only if you select Yes in the Gatekeeper Redundancy field.
PAGE 72
Mediant 1000 Table 5-4: Gatekeeper Parameters (continues on pages 70 to 73) Parameter Description RAI High Threshold [RAIHighThreshold] High Threshold (in percentage) that defines the gateway‘s busy endpoints. The range is 0 to 100. The default value is 90%. When the percentage of the gateway‘s busy endpoints exceeds the value configured in High Threshold, the gateway sends RAI message with ‘almostOutOfResources = TRUE’ and an SNMP ‘acBoardCallResourcesAlarm’ Alarm Trap with a ‘major’ Alarm Status.
PAGE 73
H.323 User's Manual 5. Web Management Table 5-4: Gatekeeper Parameters (continues on pages 70 to 73) Parameter Description RAS Response Timeout [sec] [ResponseTimeOut] Time in seconds that the gateway waits for a RAS response from the Gatekeeper. When this time expires, the gateway retransmits the RAS message. The range is 0 to 2 0. The default time is 1 second.
PAGE 74
Mediant 1000 3. From the Packetization Time drop-down list, select the packetization time (in msec) for the coder you selected. The packetization time determines how many coder payloads are combined into a single RTP packet. Note 1: If not specified, the ptime gets a default value. Note 2: The ptime specifies the packetization time the gateway expects to receive. The gateway always uses the ptime requested by the remote side for sending RTP packets. 4.
PAGE 75
H.323 User's Manual 5.5.1.4 5. Web Management DTMF & Dialing Parameters Use this screen to configure parameters that are associated with DTMF and dialing. ¾ To configure the dialing parameters, take these 4 steps: 1. Open the ‘DTMF & Dialing’ screen (Protocol Management menu > Protocol Definition submenu > DTMF & Dialing option); the ‘DTMF & Dialing’ screen is displayed. Figure 5-8: DTMF & Dialing Screen 2. Configure the DTMF & Dialing parameters according to Table 5-6. 3.
PAGE 76
Mediant 1000 Table 5-6: DTMF & Dialing Parameters (continues on pages 75 to 77) Parameter st th 1 to 5 Tx DTMF Option [TxDTMFOption] Description One or more preferred Transmit DTMF negotiation methods. You can select: Not Supported [0] = DTMF is sent according to the ‘DTMFTransportType’ parameter (default). H.245 User Input [1]. H.245 Signal Method [2]. Q.931 Info Message [3]. RFC 2833 [4]. Note 1: DTMF negotiation methods are prioritized according to the order of their appearance.
PAGE 77
H.323 User's Manual 5. Web Management Table 5-6: DTMF & Dialing Parameters (continues on pages 75 to 77) Parameter Description Digit Mapping Rules [DigitMapping] Digit map pattern. If the digit string (dialed number) has matched one of the patterns in the digit map, the gateway stops collecting digits and starts to establish a call with the collected number The digit map pattern contains up to 52 options separated by a vertical bar (|) and enclosed in parenthesis.
PAGE 78
Mediant 1000 5.5.2 Configuring the Advanced Parameters Use this submenu to configure the following gateway’s advanced control protocol parameters: 5.5.2.1 General Parameters (refer to Section 5.5.2.1 on page 78) Supplementary Services (refer to Section 5.5.2.2 on page 85) Metering Tones (refer to Section 5.5.2.3 on page 88) Keypad Features (refer to Section 5.5.2.4 on page 90) General Parameters Use this screen to configure general control protocol parameters.
PAGE 79
H.323 User's Manual 5. Web Management Figure 5-9: Advanced Parameters, General Parameters Screen 2. Configure the general parameters under ‘Advanced Parameters’ according to Table 5-7. 3. Click the Submit button to save your changes. 4. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 193. Version 5.
PAGE 80
Mediant 1000 Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84) Parameter Description IP Security [SecureCallsFromIP] No [0] = Gateway accepts all H.323 calls (default). Yes [1] = Gateway accepts H.323 calls only from IP addresses defined in the Tel to IP routing table. The gateway rejects all calls from unknown IP addresses. For detailed information on the Tel to IP Routing table, refer to Section 5.5.4.2 on page 98.
PAGE 81
H.323 User's Manual 5. Web Management Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84) Parameter Description Enable Digit Delivery to IP [EnableDigitDelivery2IP] Disable [0] = Disabled (default). Enable [1] = Enable digit delivery to IP. The digit delivery feature enables sending of DTMF digits to the destination IP address after the TelÆIP call was answered. To enable this feature, modify the called number to include at least one ’p’ character.
PAGE 82
Mediant 1000 Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84) Parameter Description No [0] = Don’t release the call. Disconnect on Broken Yes [1] = Call is released if RTP packets are not received for a predefined Connection [DisconnectOnBrokenConnec timeout (default). tion] Note 1: If enabled, the timeout is set by the parameter ‘BrokenConnectionEventTimeout’, in 100 msec resolution. The default timeout is 10 seconds: (BrokenConnectionEventTimeout =100).
PAGE 83
H.323 User's Manual 5. Web Management Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84) Parameter Description Debug Level [GwDebugLevel] Syslog logging level.
PAGE 84
Mediant 1000 Table 5-7: Advanced Parameters, General Parameters (continues on pages 80 to 84) Parameter Description Delay After Reset [sec] [GWAppDelayTime] Defines the amount of time (in seconds) the gateway’s operation is delayed after a reset cycle. The valid range is 0 to 45. The default value is 7 seconds. Note: This feature helps to overcome connection problems caused by some LAN routers or IP configuration parameters change by a DHCP Server.
PAGE 85
H.323 User's Manual 5.5.2.2 5. Web Management Supplementary Services Use this screen to configure parameters that are associated with supplementary services. For detailed information on the supplementary services, refer to Section 8.1 on page 257. ¾ To configure the supplementary services’ parameters, take these 4 steps: 1. Open the ‘Supplementary Services’ screen (Protocol Management menu > Advanced Parameters submenu > Supplementary Services option); the ‘Supplementary Services’ screen is displayed.
PAGE 86
Mediant 1000 Table 5-8: Supplementary Services Parameters (continues on pages 86 to 88) Parameter Description Enable Hold [EnableHold] Disable [0] = Disable the Hold service. Enable [1] = Enable the Hold service (H.450.4) (default). If the Hold service is enabled, a user can activate Hold (or Unhold) using the hookflash. On receiving a Hold request, the remote party is put on-hold and hears the hold tone. Note: To use the H.
PAGE 87
H.323 User's Manual 5. Web Management Table 5-8: Supplementary Services Parameters (continues on pages 86 to 88) Parameter Description Number of Call Waiting Number of waiting indications that are played to the receiving side of the call (FXS Indications only) for Call Waiting. [NumberOfWaitingIndicati The default value is 2. ons] Time Between Call Waiting Difference (in seconds) between call waiting indications (FXS only) for Call Indications Waiting.
PAGE 88
Mediant 1000 Table 5-8: Supplementary Services Parameters (continues on pages 86 to 88) Parameter Description MWI Display [MWIDisplay] Disable [0] = Disabled (default). Enable [1] = Enable digital MWI using Caller ID Interface. If enabled, the gateway generates an MWI FSK message that is displayed on the MWI display. This parameter is applicable only to FXS modules. Stutter Tone Duration [StutterToneDuration] Duration (in msec) of the played stutter dial tone that indicates waiting message(s).
PAGE 89
H.323 User's Manual 4. 5. Web Management In the Tel to IP Routing table (Section 5.5.4.2 on page 98) assign a charge code rule to the routing rules you require. When a new call is established, the Tel to IP Routing table is searched for the destination IP addresses. Once a route is found, the Charge Code (configured for that route) is used to associate the route with an entry in the Charge Codes table. 5. Click the Submit button to save your changes. 6.
PAGE 90
Mediant 1000 3. 5.5.2.4 Use the table to define up to 25 different charge codes (each charge code is defined in a single row). Each code can include from a single and up to four different time periods in a day (24 hours). Each time period is composed of: • The end (in a 24 rounded-hour’s format) of the time period. • The time interval between pulses (in seconds). • The number of pulses sent on answer. 4. The first time period always starts at midnight (00).
PAGE 91
H.323 User's Manual 5. Web Management To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 193. 4. Notes: • The method used by the gateway to collect dialed numbers is identical to the method used during a regular call (i.e., max digits, interdigit timeout, digit map, etc.). • The activation of each feature remains in effect until it is deactivated (i.e., it is not per call).
PAGE 92
Mediant 1000 5.5.3 Configuring the Number Manipulation Tables The VoIP gateway provides four Number Manipulation tables for incoming and outgoing calls. These tables are used to modify the destination and source telephone numbers so that the calls can be routed correctly.
PAGE 93
H.323 User's Manual 5. Web Management ¾ To configure the Number Manipulation tables, take these 5 steps: 1. Open the Number Manipulation screen you want to configure (Protocol Management menu > Manipulation Tables submenu); the relevant Manipulation table screen is displayed. Figure 5-14 shows the ‘Source Phone Number Manipulation Table for TelÆIP calls’. Figure 5-14: Source Phone Number Manipulation Table for TelÆIP calls 2.
PAGE 94
Mediant 1000 Table 5-11: Number Manipulation Parameters (continues on pages 93 to 94) Parameter Description Prefix / Suffix to add Prefix - Enter the number / string you want to add to the front of the phone number. For example, if you enter 9 and the phone number is 1234, the new number is 91234. Suffix - Enter the number / string (in brackets) you want to add to the end of the phone number. For example, if you enter (00) and the phone number is 1234, the new number is 123400.
PAGE 95
H.323 User's Manual 5.5.3.1 5. Web Management Dialing Plan Notation The dialing plan notation applies, in addition to the four Manipulation tables, also to TelÆIP Routing table and to IPÆTrunk Group Routing table. When entering a number in the destination and source ‘Prefix’ columns, you can create an entry that represents multiple numbers using the following notation: [n-m] represents a range of numbers [n,m] represents multiple numbers. Note that this notation only supports single digit numbers.
PAGE 96
Mediant 1000 For NI-2 and DMS-100 ISDN variants the valid combinations of TON and NPI for calling and called numbers are (Plan/Type): 5.5.
PAGE 97
H.323 User's Manual 5. Web Management Table 5-13: Routing Tables, General Parameters (continues on pages 97 to 98) Parameter Description No [0] = Don’t add trunk group ID as prefix (default). Add Trunk Group ID as Yes [1] = Add trunk group ID as prefix to called number. Prefix [AddTrunkGroupAsPrefix] If enabled, then the trunk group ID is added as a prefix to the destination phone number for TelÆIP calls. Note 1: This option can be used to define various routing rules.
PAGE 98
Mediant 1000 Table 5-13: Routing Tables, General Parameters (continues on pages 97 to 98) Parameter Description Max Allowed Packet Loss Packet loss percentage at which the IP connection is considered a failure. for Alt Routing [%] The range is 1% to 20%. The default value is 20%. [IPConnQoSMaxAllowedP L] Transmission delay (in msec) at which the IP connection is considered a failure. Max Allowed Delay for Alt The range is 100 to 1000. The default value is 250 msec.
PAGE 99
H.323 User's Manual 5. Web Management Alternative Routing – (When Gatekeeper isn’t used) an alternative IP destination for telephone number prefixes is available. To associate an alternative IP address to called telephone number prefix, assign it with an additional entry (with a different IP address), or use an FQDN that resolves to two IP addresses.
PAGE 100
Mediant 1000 Table 5-14: Tel to IP Routing Table (continues on pages 100 to 100) Parameter Description Tel to IP Routing Mode [RouteModeTel2IP] Route calls before manipulation [0] = TelÆIP calls are routed before the number manipulation rules are applied (default). Route calls after manipulation [1] = TelÆIP calls are routed after the number manipulation rules are applied. Note: Not applicable if Gatekeeper is used.
PAGE 101
H.323 User's Manual 5. Web Management The call is then sent to the VoIP gateway channels assigned to that trunk group. The specific channel, within a trunk group that is assigned to accept the call is determined according to the trunk group’s channel selection mode which is defined in the Trunk Group Settings screen (Section 5.5.10 on page 124) or according to the global parameter ‘ChannelSelectMode’ (refer to Table 5-7 on page 80).
PAGE 102
Mediant 1000 ¾ To configure the IP to Trunk Group Routing table, take these 6 steps: 1. Open the ‘IP to Trunk Group Routing’ screen (Protocol Management menu > Routing Tables submenu > IP to Trunk Group Routing option); the ‘IP to Trunk Group Routing’ table screen is displayed (shown in Figure 5-17). Figure 5-17: IP to Trunk Group Routing Table Screen 2. In the ‘IP to Tel Routing Mode’ field, select the IP to Tel routing mode (refer to Table 5-15). 3.
PAGE 103
H.323 User's Manual 5. Web Management Table 5-15: IP to Trunk Group Routing Table Parameter Description Any H.323 incoming call whose destination number matches the prefix defined in the ‘Destination Phone Prefix’ field and its source number matches the prefix defined in the adjacent ‘Source Phone Prefix‘ field and its source IP address matches the address defined in the ‘Source IP Address’ field, is assigned to the trunk group entered in the field to the right of these fields.
PAGE 104
Mediant 1000 ¾ To configure the internal DNS table, take these 7 steps: 1. Open the ‘Internal DNS Table’ screen (Protocol Management menu > Routing Tables submenu > Internal DNS Table option); the ‘Internal DNS Table’ screen is displayed. Figure 5-18: Internal DNS Table Screen 5.5.4.5 2. In the ‘Domain Name' field, enter the host name to be translated. You can enter a string up to 31 characters long. 3.
PAGE 105
H.323 User's Manual 5. Web Management For configuring this table, you can also use the ini file parameters AltRouteCauseTel2IP and AltRouteCauseIP2Tel (refer to Section 6.5.9 on page 236). ¾ To configure the reasons for alternative routing, take these 5 steps: 1. Open the ‘Reasons for Alternative Routing’ screen (Protocol Management menu > Routing Tables submenu > Reasons for Alternative Routing option); the ‘Reasons for Alternative Routing’ screen is displayed.
PAGE 106
Mediant 1000 5.5.5 Configuring the Profile Definitions Utilizing the Profiles feature, the Mediant 1000 provides high-level adaptation when connected to a variety of equipment (from both Tel and IP sides) and protocols, each of which requires a different system behavior.
PAGE 107
H.323 User's Manual 5. Web Management ¾ To configure the coder group settings, take these 11 steps: 1. Open the ‘Coder Group Settings’ screen (Protocol Management menu > Profile Definitions submenu > Coder Group Settings option); the ‘Coder Group Settings’ screen is displayed. Figure 5-20: Coder Group Settings Screen 2. From the Coder Group ID drop-down list, select the coder group you want to edit (up to four coder groups can be configured). 3.
PAGE 108
Mediant 1000 5.5.5.2 Tel Profile Settings Use the Tel Profile Settings screen to define up to four different Tel Profiles. These Profiles are used in the ‘Trunk Group’ table to associate different Profiles to the gateway’s channels, thereby applying different behavior to different channels. You can also configure Tel Profiles using the ini file parameter TelProfile_ID (refer to Section 6.5.7 on page 226). ¾ To configure the Tel Profile settings, take these 9 steps: 1.
PAGE 109
H.323 User's Manual 5. Web Management 3. In the ‘Profile Name’ field, enter a name that enables you to identify the Profile intuitively and easily. 4. In the ‘Profile Preference’ drop-down list, select the preference (1-20) of the current Profile. The preference option is used to determine the priority of the Profile. Where ‘20’ is the highest preference value.
PAGE 110
Mediant 1000 5.5.5.3 IP Profile Settings Use the IP Profile Settings screen to define up to four different IP Profiles. These Profiles are used in the Tel to IP and IP to Trunk Group Routing tables to associate different Profiles to routing rules. You can also configure the IP Profiles using the ini file parameter IPProfile_ID (refer to Section 6.5.7 on page 226). ¾ To configure the IP Profile settings, take these 9 steps: 1.
PAGE 111
H.323 User's Manual 5. Web Management 4. From the ‘Profile Preference’ drop-down list, select the preference (1-20) of the current Profile. The preference option is used to determine the priority of the Profile. Where ‘20’ is the highest preference value. If both IP and Tel profiles apply to the same call, the coders and other common parameters (noted by an asterisk in the description of the parameter IPProfile_ID) of the preferred Profile are applied to that call.
PAGE 112
Mediant 1000 5.5.6 Configuring the Registration Prefixes The Gatekeeper Registration Prefixes Table enables the Mediant 1000 to register with a Gatekeeper by associating dialing plan information with specific digit prefixes. The Gatekeeper Registration Prefixes Table data is sent when the gateway requests permission to register with the Gatekeeper. This registration request is triggered by a gateway reset, or by the user from the Web Interface.
PAGE 113
H.323 User's Manual 5. Web Management Table 5-16: Registration Prefixes Table Parameter Description Gatekeeper Registration Prefixes Enter the Gatekeeper Registration prefixes. These prefixes are used by the VoIP gateway to register to a Gatekeeper. When entering a prefix, you can create an entry that represents multiple prefixes using the following notation: n-m represents a range of numbers. For example, enter ‘250-279’ to specify all prefixes from 250 to 279. NPI Select the H.225/Q.
PAGE 114
Mediant 1000 5.5.7 Configuring the Endpoint Settings The Endpoint Settings screens enable you to configure port-specific parameters. Note: The Endpoint Settings screens are only applicable to the analog modules. 5.5.7.1 H.323 Port ID The H.323 Port ID table enables you to assign a specific ID to each FXS or FXO port. These IDs are used for registration to the Gatekeeper (RRQ) when ‘GWRegistrType’ = 1 or 2 and for Gatekeeper admission (ARQ) and call initialization when ‘SourceEncodeType’ = 1 or 2.
PAGE 115
H.323 User's Manual 5.5.7.2 5. Web Management Automatic Dialing Use the Automatic Dialing Table to define telephone numbers that are automatically dialed when a specific port is used. You can also configure the Automatic Dialing table using the ini file parameter TargetOfChannelX (refer to Section 6.5.9 on page 236). ¾ To configure the Automatic Dialing table, take these 6 steps: 1.
PAGE 116
Mediant 1000 5.5.7.3 Caller ID Use the Caller Display Information screen to send (to IP) Caller ID information when a call is made using the VoIP gateway (relevant to both FXS and FXO). The person receiving the call can use this information for caller identification. The information on this table is sent in the H.225 Setup message sent to the remote party. For information on Caller ID restriction according to destination / source prefixes, refer to Section 5.5.3 on page 92.
PAGE 117
H.323 User's Manual 5.5.7.4 5. Web Management Call Forward The VoIP gateway allows you to forward incoming IPÆTel calls based on the VoIP gateway port to which the call is routed (applicable only to FXS modules). The Call Forwarding Table is applicable only if the Call Forward feature is enabled. To enable Call Forward set ‘Enable Call Forward’ to ‘Enable’ in the ‘Supplementary Services’ screen, or ‘EnableForward = 1’ in the ini file (refer to Table 5-8 on page 86).
PAGE 118
Mediant 1000 5.5.7.5 Caller ID Permissions The Caller ID Permissions table is used to enable or disable (per port) the Caller ID generation (for FXS modules) and detection (for FXO modules). If a port isn’t configured, its Caller ID generation / detection are determined according to the global parameter ‘EnableCallerID’ (described in Table 5-8 on page 86). You can also configure the Caller ID Permissions table using the ini file parameter EnableCallerID_X (refer to Section 6.5.9 on page 236).
PAGE 119
H.323 User's Manual 5.5.8 5. Web Management Configuring the FXO Parameters Use this screen to configure the gateway’s specific FXO parameters. ¾ To configure the FXO parameters, take these 4 steps: 1. Open the ‘FXO Settings’ screen (Protocol Management menu > FXO Settings > FXO Settings option); the ‘FXO Settings’ screen is displayed. Figure 5-29: FXO Settings Screen 2. Configure the FXO parameters according to Table 5-18 on page 119. 3. Click the Submit button to save your changes. 4.
PAGE 120
Mediant 1000 Table 5-18: FXO Parameters (continues on pages 119 to 121) Parameter Description Waiting For Dial Tone [IsWaitForDialTone] No [0] = Don’t wait for dial tone. Yes [1] = Wait for dial tone (default). Used for IPÆMediant 1000/FXO modules, when ‘One Stage Dialing’ is enabled. If ‘wait for dial tone’ is enabled, the FXO module dials the phone number (to the PSTN/PBX line) only after it detects a dial tone.
PAGE 121
H.323 User's Manual 5. Web Management Table 5-18: FXO Parameters (continues on pages 119 to 121) Parameter Description Answer Supervision [EnableVoiceDetection] Yes [1] = FXO module sends Connect message when speech/fax/modem is detected. No [0] = Connect is sent immediately after the FXO module finishes dialing (default). Usually this feature is used only with Fast Connect to establish voice path before the call is answered. Note: This feature is applicable only to ‘One Stage’ dialing.
PAGE 122
Mediant 1000 5.5.9 Configuring the Trunk Group Table Use the Trunk Group table to assign trunk groups, profiles and logical telephone numbers to the gateway's channels. Trunk Groups are used for routing IPÆTel calls with common rules. Channels that are not defined are disabled. You can also use the ini file parameter TrunkGroup_x to configure the Trunk Groups (refer to Section 6.5.9 on page 236). ¾ To configure the Trunk Group table, take these 4 steps: 1.
PAGE 123
H.323 User's Manual 5. Web Management Table 5-19: Trunk Group Table (continues on pages 122 to 123) Parameter Description Phone Number In each of the Phone Number fields, enter the first number in an ordered sequence that is assigned to the range of channels defined in the adjacent ‘Channels’ field. Note: This field is optional.
PAGE 124
Mediant 1000 5.5.10 Configuring the Trunk Group Settings The Trunk Group Settings Table is used to determine the method in which new calls are assigned to channels within each trunk group. If such a rule doesn’t exist (for a specific Trunk group), the global rule, defined by the Channel Select Mode parameter (Protocol Definition > General Parameters), applies. You can also configure the Trunk Group Settings table using the ini file parameter TrunkGroupSettings (refer to Section 6.5.9 on page 236).
PAGE 125
H.323 User's Manual 5. Web Management Table 5-20: Channel Select Modes Mode Description By Dest Phone Number Select the gateway port according to the called number (refer to the note below). Cyclic Ascending Select the next available channel in an ascending cycle order. Always select the next higher channel number in the Trunk Group.
PAGE 126
Mediant 1000 5.5.11 Configuring the Digital Gateway Parameters The 'Digital Gateway' screen is used to configure miscellaneous digital parameters. ¾ To configure the digital gateway parameters, take these 4 steps: 1. Open the ‘Digital Gateway Parameters' screen (Protocol Management menu > Digital Gateway Parameters); the ‘Digital Gateway Parameters' screen is displayed. Figure 5-32: Digital Gateway Parameters Screen 2. Configure the Digital Gateway parameters according to Table 5-21. 3.
PAGE 127
H.323 User's Manual 5. Web Management Table 5-21: Digital Gateway Parameters (continues on pages 126 to 128) Parameter Description Swap Redirect and Called Numbers [SwapRedirectNumber] 0 = Don't change numbers (default) 1 = Incoming ISDN call that includes redirect number (sometimes referred as ‘original called number’) uses this number instead of the called number. Enable Transfer Capability [EnableTransferCap] 0 = Disable (default) 1 = Enable. When disabled, Transfer Capability field sent in Q.
PAGE 128
Mediant 1000 Table 5-21: Digital Gateway Parameters (continues on pages 126 to 128) Parameter Description Trunk Groups to Send IE [SendIEonTG] A list of Trunk Group IDs (up to 50 characters) from where the optional ISDN IE, defined by the parameter ‘AddIEinSetup’, is sent. For example: ‘SendIEonTG = 1,2,4,10,12,6’. Enable User-to-User IE for Tel to IP [EnableUUITel2IP] 0 = Disabled (default). 1 = Enable transfer of User-to-User Information Element (UUIE) from PRI Setup message to H.323 Setup message.
PAGE 129
H.323 User's Manual 5.6 5. Web Management Advanced Configuration Use this menu to set the gateway’s advanced configuration parameters. Note: Parameters contained within square brackets are the names used to configure the parameters via the ini file. 5.6.1 Configuring the Network Settings From the Network Settings you can: 5.6.1.1 Configure the IP Settings (refer to Section 5.6.1.1 below) Configure the Application Settings (refer to Section 5.6.1.
PAGE 130
Mediant 1000 2. Configure the IP Settings according to Table 5-22. 3. Click the Submit button to save your changes. 4. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 193. Table 5-22: Network Settings, IP Settings Parameters (continues on pages 130 to 132) Parameter Description IP Networking Mode [EnableMultipleIPs] Enables / disables the Multiple IPs mechanism. Single IP Network [0] (default). Multiple IP Network [1].
PAGE 131
H.323 User's Manual 5. Web Management Table 5-22: Network Settings, IP Settings Parameters (continues on pages 130 to 132) Parameter Description IP Address [LocalMediaIPAddress] The gateway’s source IP address in the Media network. The default value is 0.0.0.0. Subnet Mask [LocalMediaSubnetMask] The gateway’s subnet mask in the Media network. The default subnet mask is 0.0.0.0. Default Gateway Address [LocalMediaDefaultGW] The gateway’s default gateway IP address in the Media network.
PAGE 132
Mediant 1000 Table 5-22: Network Settings, IP Settings Parameters (continues on pages 130 to 132) Parameter Description Media Premium QoS [PremiumServiceClassMediaDiffServ] Sets the DiffServ value for Premium Media service class content (only if IPDiffServ is not set in the selected IP Profile). The valid range is 0 to 56. The default value is 46. Note: The value for the Premium Control DiffServ is determined by (according to priority): (1) IPDiffServ value in the selected IP Profile.
PAGE 133
H.323 User's Manual 5. Web Management 2. Configure the Application Settings according to Table 5-23. 3. Click the Submit button to save your changes. 4. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 193. Table 5-23: Network Settings, Application Settings Parameters Parameter Description NTP Settings For detailed information on NTP, refer to Section 9.8 on page 285.
PAGE 134
Mediant 1000 ¾ To configure the NFS Settings parameters, take these 7 steps: 1. Open the ‘Application Settings’ screen (Advanced Configuration menu > Network Settings > Application Settings option); the ‘Application Settings’ screen is displayed (Figure 5-34). 2. Open the NFS Table screen by clicking the arrow sign (-->) to the right of the NFS label; the NFS Table screen is displayed (Figure 5-35). Figure 5-35: NFS Settings Table Screen 3.
PAGE 135
H.323 User's Manual 5. Web Management Table 5-24: Network Settings, NFS Settings Parameters Parameter Description Line Number [NFSServers_Index] The row index of the remote file system. The valid range is 0 to 4. Host / IP [NFSServers_HostOrIP] The domain name or IP address of the NFS server. If a domain name is provided, a DNS server must be configured. Root Path [NFSServers_RootPath] Path to the root of the remote file system.
PAGE 136
Mediant 1000 5.6.1.4 Configuring the IP Routing Table The IP routing table is used by the gateway to determine IP routing rules. It can be used, for example, to define static routing rules for the OAM and Control networks since a default gateway isn’t supported for these networks (refer to Section 9.10.1 on page 286). Before sending an IP packet, the gateway searches this table for an entry that matches the requested destination host / network.
PAGE 137
H.323 User's Manual 5. Web Management Table 5-25: IP Routing Table Column Description Column Name [ini File Parameter Name] Description The address of the host / network you want to reach is determined by an AND operation that is applied on the fields ‘Destination IP Address’ and ‘Destination Mask’. For example: To reach the network 10.8.x.x, enter 10.8.0.0 in the field ‘Destination IP Address’ and 255.255.0.0 in the field ‘Destination Mask’.
PAGE 138
Mediant 1000 5.6.1.5 Configuring the VLAN Settings For detailed information on the Mediant 1000 VLAN implementation, refer to Section 9.9 on page 285. ¾ To configure the VLAN Settings parameters, take these 4 steps: 1. Open the ‘VLAN Settings’ screen (Advanced Configuration menu > Network Settings > VLAN Settings option); the ‘VLAN Settings’ screen is displayed. Figure 5-37: VLAN Settings Screen 2. Configure the VLAN Settings according to Table 5-26. 3. Click the Submit button to save your changes.
PAGE 139
H.323 User's Manual 5. Web Management Table 5-26: Network Settings, VLAN Settings Parameters Parameter Description Control VLAN ID [VlanControlVlanID] Sets the control VLAN identifier. The valid range is 1 to 4094. The default value is 2. Media VLAN ID [VlanMediaVlanID] Sets the media VLAN identifier. The valid range is 1 to 4094. The default value is 3. Priority Settings Network Priority [VlanNetworkServiceClassPriority] Sets the priority for Network service class content.
PAGE 140
Mediant 1000 5.6.2 Configuring the Media Settings Use these menus to set the gateway’s channel parameters. These parameters are applied to all Mediant 1000 channels. From the Media Settings page you can define: Voice Settings (refer to Section 5.6.2.1). Fax / Modem / CID Settings (refer to Section 5.6.2.2 on page 142). RTP/RTCP Settings (refer to Section 5.6.2.3 on page 145). Hook-Flash Settings (refer to Section 5.6.2.4 on page 147). General Media Settings (refer to Section 5.6.2.
PAGE 141
H.323 User's Manual 5. Web Management 3. Click the Submit button to save your changes. 4. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 193. Table 5-27: Media Settings, Voice Settings Parameters Parameter Description Voice Volume [VoiceVolume] Voice gain control in dB. This parameter sets the level for the transmitted (IPÆPSTN/Tel) signal. The valid range is -32 to 31 dB. The default value is 0 dB. Input Gain [InputGain] PCM input gain control in dB.
PAGE 142
Mediant 1000 5.6.2.2 Configuring the Fax / Modem / CID Settings ¾ To configure the Fax / Modem / CID Settings parameters, take these 4 steps: 1. Open the ‘Fax / Modem / CID Settings’ screen (Advanced Configuration menu > Media Settings > Fax / Modem / CID Settings option); the ‘Fax / Modem / CID Settings’ screen is displayed. Figure 5-39: Fax / Modem / CID Settings Screen 2. Configure the Fax / Modem / CID Settings according to Table 5-28. 3. Click the Submit button to save your changes. 4.
PAGE 143
H.323 User's Manual 5. Web Management Table 5-28: Media Settings, Fax/Modem/CID Parameters (continues on pages 142 to 144) Parameter Description Caller ID Type [CallerIDType] Defines one of the following standards for detection (FXO) and generation (FXS) of Caller ID and detection (FXO) of MWI (when specified) signals. Bellcore [0] (Caller ID and MWI) (default).
PAGE 144
Mediant 1000 Table 5-28: Media Settings, Fax/Modem/CID Parameters (continues on pages 142 to 144) Parameter Description Fax Relay ECM Enable [FaxRelayECMEnable] Disable [0] = Error Correction Mode (ECM) mode is not used during fax relay. Enable [1] = ECM mode is used during fax relay (default). Fax Relay Max Rate (bps) [FaxRelayMaxRate] Maximum rate, in bps, at which fax relay messages are transmitted. You can select: 2400 [0] = 2.4 kbps. 4800 [1] = 4.8 kbps. 7200 [2] = 7.2 kbps. 9600 [3] = 9.6 kbps.
PAGE 145
H.323 User's Manual 5.6.2.3 5. Web Management Configuring the RTP / RTCP Settings ¾ To configure the RTP / RTCP Settings parameters, take these 4 steps: 1. Open the ‘RTP / RTCP Settings’ screen (Advanced Configuration menu > Media Settings > RTP / RTCP Settings option); the ‘RTP / RTCP Settings’ screen is displayed. Figure 5-40: RTP / RTCP Settings Screen 2. Configure the RTP / RTCP Settings according to Table 5-29. 3. Click the Submit button to save your changes. 4.
PAGE 146
Mediant 1000 Table 5-29: Media Settings, RTP / RTCP Parameters Parameter Description Dynamic Jitter Buffer Minimum Delay [DJBufMinDelay] Minimum delay for the Dynamic Jitter Buffer. The valid range is 0 to 150 milliseconds. The default delay is 10 milliseconds. Note: For more information on the Jitter Buffer, refer to Section 8.7 on page 266. Dynamic Jitter Buffer Optimization Factor [DJBufOptFactor] Dynamic Jitter Buffer frame error / delay optimization factor. The valid range is 0 to 13.
PAGE 147
H.323 User's Manual 5. Web Management Table 5-29: Media Settings, RTP / RTCP Parameters Parameter Description Remote RTP Base UDP Port [RemoteBaseUDPPort] Determines the lower boundary of UDP ports used for RTP, RTCP and T.38 by a remote gateway. If this parameter is set to a non-zero value, ThroughPacket™ is enabled. Note that the value of ‘RemoteBaseUDPPort’ on the local gateway must equal the value of ‘BaseUDPPort’ of the remote gateway.
PAGE 148
Mediant 1000 Table 5-30: Media Settings, Hook-Flash Settings Parameters Parameter Description Min. Flash-Hook Detection Period [msec] [MinFlashHookTime] Sets the minimal time (in msec) for detection of a flash-hook event (for FXS only). The valid range is 25 to 300. The default value is 300 msec. Detection is guaranteed for flash hook periods of at least 60 msec (when setting the minimal time to 25). Flash-hook signals that last a shorter period of time are ignored.
PAGE 149
H.323 User's Manual 5. Web Management Table 5-31: Media Settings, General Media Settings Parameters Parameter Description DSP Version Template Number N/A. Max Echo Canceller Length [MaxEchoCancellerLength] Maximum Echo Canceler Length in msec: 0 = based on various internal gateway settings -- 64 msec (default) 4 = 32 msec 11 = 64 msec Note 1: The gateway must be reset after the value of ‘MaxEchoCancellerLength’ is changed.
PAGE 150
Mediant 1000 5.6.3 Configuring the Trunk Settings ¾ To configure the Trunk Settings, take these 9 steps: 1. Open the ‘Trunk Settings’ screen (Advanced Configuration menu > Trunk Settings); the ‘Trunk Settings’ screen is displayed. Initially, the screen appears with the parameters fields grayed (i.e., read-only). The Stop Trunk button appears at the bottom of the screen. The Trunk Status indicators appear colored. Table 5-45 on page 199 shows the possible indicators and their descriptions.
PAGE 151
H.323 User's Manual 4. 5. Web Management Select the ‘Protocol Type’ you use. Note that different trunks can be defined with different protocols (CAS or ISDN variants) on the same gateway (subject to the constraints in the Mediant 1000 H.323 Release Notes). Note: When modifying the ‘Protocol Type’ field, the menu is automatically updated according to the selected protocol (ISDN, CAS or Transparent). Additional parameters are appropriate to the selected protocol type. 5.
PAGE 152
Mediant 1000 Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Web Parameter Name Valid Range and Description ProtocolType [Protocol Type] Sets the PSTN protocol to be used for this trunk.
PAGE 153
H.323 User's Manual 5. Web Management Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Web Parameter Name Valid Range and Description TraceLevel [Trace Level] Defines the trace level. Valid options include: 0 = No trace (default) 1= Full ISDN trace 2 = Layer 3 ISDN trace 3 = Only ISDN Q.931 messages trace 4 = Layer 3 ISDN no duplication trace FramingMethod [Framing Method] Selects the framing method to be used for E1/T1 spans.
PAGE 154
Mediant 1000 Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Web Parameter Name ISDNRxOverlap_x [Enable Receiving of Overlap Dialing] Valid Range and Description Enable / disable Rx ISDN overlap per trunk ID. 0 = Disabled (default). 1 = Enabled. Note 1: If enabled, the gateway receives ISDN called number that is sent in the ‘Overlap’ mode.
PAGE 155
H.323 User's Manual 5. Web Management Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Web Parameter Name Valid Range and Description ISDN Flexible Behavior Parameters ISDN protocol is implemented in different Switches / PBXs by different vendors. Several implementations vary a little from the specification. Therefore, to provide a flexible interface that supports these ISDN variants, the ISDN behavior parameters are used. 1 = Q.
PAGE 156
Mediant 1000 Table 5-32: E1/T1/J1 Configuration Parameters (continues on pages 152 to 156) ini File Field Name Web Parameter Name ISDNGeneralCCBehavior [General Call Control Behavior] Valid Range and Description 16 = The gateway clears down the call if it receives a NOTIFY message specifying ‘User-Suspended’. A NOTIFY (User-Suspended) message is used by some networks (e.g., in Italy or Denmark) to indicate that the remote user has cleared the call, especially in the case of a long distance voice call.
PAGE 157
H.323 User's Manual 5.6.4 5. Web Management Configuring the TDM Bus Settings ¾ To configure the TDM Bus Settings parameters, take these 5 steps: 1. Open the ‘TDM Bus Settings’ screen (Advanced Configuration menu > TDM Bus Settings); the ‘TDM Bus Settings’ screen is displayed. Figure 5-44: TDM Bus Settings Screen 2. Configure the TDM Bus Settings parameters. 3. Click the Submit button to save your changes. 4. To save the changes so they are available after a power fail, refer to Section 5.9.
PAGE 158
Mediant 1000 Table 5-33: TDM Bus Settings Parameters (continues on pages 157 to 158) Parameter Description Idle ABCD Pattern [IdleABCDPattern] ABCD (CAS) Pattern to be applied to CAS signaling bus when the channel is idle. Range 0x0 to 0xF Default = -1 (default, pattern = 0000) Note: This is only relevant when using PSTN interface with CAS protocols. TDM Bus Local Reference [TDMBusLocalReference] 0 to 4 (default = 0) Physical Trunk ID from which the gateway recovers its clock.
PAGE 159
H.323 User's Manual 5.6.5 5. Web Management Restoring and Backing up the Gateway Configuration The Configuration File screen enables you to restore (load a new ini file to the gateway) or to back up (make a copy of the VoIP gateway ini file and store it in a directory on your computer) the current configuration the gateway is using. Back up your configuration if you want to protect your VoIP gateway programming.
PAGE 160
Mediant 1000 5.6.6 Regional Settings The ‘Regional Settings’ screen allows you to define and view the gateway’s internal date and time as well as to load configuration files (Call Progress Tones, FXS/FXO coefficient, and CAS) to the gateway. For detailed information on the configuration files, refer to Section 5.8.2 on page 189. ¾ To configure the date and time of the Mediant 1000, take these 3 steps: 1.
PAGE 161
H.323 User's Manual 5. Web Management ¾ To load a configuration file to the VoIP gateway, take these 8 steps: 1. Open the ‘Regional Settings’ screen (Advanced Configuration menu > Regional Settings); the ‘Regional Settings’ screen is displayed (shown in Figure 5-46). 2. Click the Browse button adjacent to the file you want to load. 3. Navigate to the folder that contains the file you want to load. 4.
PAGE 162
Mediant 1000 5.6.7 Security Settings From the Security Settings you can: 5.6.7.1 Configure the Web User Accounts (refer to Section 5.6.7.1 below) Configure the Web & Telnet Access List (refer to Section 5.6.7.2 on page 163) Configure the Firewall Settings (refer to Section 5.6.7.3 on page 164) Configure the Certificates (refer to Section 5.6.7.4 on page 167) Configure the General Security Settings (refer to Section 5.6.7.
PAGE 163
H.323 User's Manual 5. Web Management 2. To change the access level of the secondary account (the access level of the primary account cannot be changed), from the ‘Access Level’ drop-down list, select the new access level, and then click the button Change Access Level; the new access level is applied immediately. 3.
PAGE 164
Mediant 1000 2. To add a new authorized IP address, in the ‘New Authorized IP Address’ field, enter the required IP address (refer to Note 1 below) and click the button Add New Address; the IP address you entered is added as a new entry to the Web & Telnet Access List table. 3.
PAGE 165
H.323 User's Manual 5. Web Management ¾ To edit a rule, take these 5 steps: 1. Select the radio button of the entry you want to edit. 2. Click the Make Rule Editable button; the rule’s fields can now be modified. 3. Modify the fields according to your requirements. 4. Click the Apply Rule Settings button to save the changes. 5. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 193. ¾ To activate a de-activated rule, take these 2 steps: 1.
PAGE 166
Mediant 1000 Table 5-34: Internal Firewall Fields Parameter Description Is Rule Active A read-only field that indicates whether the rule is active or not. Note: After reset all rules are active. Source IP [AccessList_Source_IP] IP address (or DNS name) of source network, or a specific host. Mask [AccessList_Net_Mask] IP network mask. 255.255.255.255 for a single host or the appropriate value for the source IP addresses.
PAGE 167
H.323 User's Manual 5.6.7.4 5. Web Management Configuring the Certificates Use the Certificates screen to replace the server (refer to Section 13.2.3 on page 331) and client (refer to Section 13.2.4 on page 332) certificates and to update the private key (HTTPSPkeyFileName, described in Section 6.5.4 on page 223). 5.6.7.5 Configuring the General Security Settings ¾ To configure the General Security Settings parameters, take these 4 steps: 1.
PAGE 168
Mediant 1000 Table 5-35: General Security Settings Parameters (continues on pages 168 to 169) Parameter Description Secured Web Connection [HTTPSOnly] Determines the protocol types used to access the Embedded Web Server. HTTP and HTTPS [0] (default). HTTPS only [1] (unencrypted HTTP packets are blocked). HTTP Authentication Mode [WebAuthMode] Determines the authentication mode for the Embedded Web Server. Basic [0] = Basic authentication (clear text) is used (default).
PAGE 169
H.323 User's Manual 5. Web Management Table 5-35: General Security Settings Parameters (continues on pages 168 to 169) Parameter Description Local RADIUS Password Cache Mode [RadiusLocalCacheMode] Defines the gateway’s mode of operation regarding the timer (configured by the parameter RadiusLocalCacheTimeout) that determines the validity of the username and password (verified by the RADIUS server).
PAGE 170
Mediant 1000 5.6.8 Configuring the Management Settings ¾ To configure the Management Settings parameters, take these 4 steps: 1. Open the ‘Management Settings’ screen (Advanced Configuration menu > Management Settings); the ‘Management Settings’ screen is displayed. Figure 5-51: Management Settings Screen 2. Configure the Management Settings according to Table 5-36. 3. Click the Submit button to save your changes. 4. To save the changes so they are available after a power fail, refer to Section 5.
PAGE 171
H.323 User's Manual 5. Web Management Table 5-36: Management Settings Parameters (continues on pages 171 to 172) Parameter Description Syslog Settings Syslog Server IP address [SyslogServerIP] IP address (in dotted format notation) of the computer you are using to run the Syslog Server. The Syslog Server is an application designed to collect the logs and error messages generated by the VoIP gateway. Note: Use the SyslogServerPort parameter to define the Syslog server's port.
PAGE 172
Mediant 1000 Table 5-36: Management Settings Parameters (continues on pages 171 to 172) Parameter Description Device Software Update [ActivityListToLog = SWU] cmp loading via the Software Upgrade Wizard. Access to Restricted Domains [ActivityListToLog = ARD] Access to Restricted Domains. The following screens are restricted: (1) ini parameters (AdminPage) (2) General Security Settings (3) Configuration File (4) IPSec/IKE tables (5) Software Upgrade Key (6) Internal Firewall (7) Web Access List.
PAGE 173
H.323 User's Manual 5. Web Management Note: If you clear a checkbox and then click Submit, all settings in the same row revert to their defaults. Table 5-37: SNMP Managers Table Parameters Parameter Description Checkbox [SNMPManagerIsUsed_x] Up to five parameters, each determines the validity of the parameters (IP address and port number) of the corresponding SNMP Manager used to receive SNMP traps.
PAGE 174
Mediant 1000 5.6.8.2 Configuring the SNMP Community Strings Use the SNMP Community Strings table to configure up to five read-only and up to five read / write SNMP community strings, and to configure the community string that is used for sending traps. For detailed information on SNMP community strings, refer to section 15.7.1 on page 354. ¾ To configure the SNMP Community Strings, take these 5 steps: 1.
PAGE 175
H.323 User's Manual 5.6.8.3 5. Web Management Configuring SNMP V3 Users Use the SNMP V3 Table to configure authentication and privacy for up to 10 SNMP v3 users. ¾ To configure the SNMP v3 users, take the following 6 steps: 1. Access the ‘Management Settings’ screen (Advanced Configuration menu > Management Settings); the ‘Management Settings’ screen is displayed. 2.
PAGE 176
Mediant 1000 Table 5-39: SNMP V3 Users Parameters (continues on pages 175 to 176) Parameter Description [SNMPUsers_PrivProtocol] [PrivProtocol] Privacy protocol to be used for the SNMP v3 user. 0 = none (default) 1 = DES 2 = 3DES 3 = AES128 4 = AES192 5 = AES256 [SNMPUsers_AuthKey] [AuthKey] Authentication key. Keys can be entered in the form of a text password or long hex string. Keys are always persisted as long hex strings and keys are localized. [SNMPUsers_PrivKey] [PrivKey] Privacy key.
PAGE 177
H.323 User's Manual 5.7 5. Web Management Status & Diagnostics Use this menu to view and monitor the gateway’s channels, Syslog messages, hardware / software product information, and to assess the gateway’s statistics and IP connectivity information. 5.7.1 Gateway Statistics Use the screens under Gateway Statistics to monitor real-time activity such as IP Connectivity information, call details and call statistics, including the number of call attempts, failed calls, fax calls, etc.
PAGE 178
Mediant 1000 Figure 5-55: IP Connectivity Screen Table 5-40: IP Connectivity Parameters Column Name Description IP Address IP address defined in the destination IP address field in the Tel to IP Routing table. or IP address that is resolved from the host name defined in the destination IP address field in the Tel to IP Routing table. Host Name Host name (or IP address) defined in the destination IP address field in the Tel to IP Routing table.
PAGE 179
H.323 User's Manual 5.7.1.2 5. Web Management Call Counters The Call Counters screens provide you with statistic information on incoming (IPÆTel) and outgoing (TelÆIP) calls. The statistic information is updated according to the release reason that is received after a call is terminated (during the same time as the end-of-call CDR message is sent). The release reason can be viewed in the Termination Reason field in the CDR message.
PAGE 180
Mediant 1000 Table 5-41: Call Counters Description (continues on pages 179 to 180) Counter Description Number of Established This counter indicates the number of established calls.
PAGE 181
H.323 User's Manual 5.7.1.3 5. Web Management Call Routing Status The Call Routing Status screen provides you with information on the current routing method used by the gateway. This information includes the IP address and FQDN (if used) of the Proxy server with which the gateway currently operates.
PAGE 182
Mediant 1000 5.7.2 Activating the Internal Syslog Viewer The Message Log screen displays Syslog debug messages sent by the gateway. You can simply select the messages, and then copy and paste them into a text editor such as Notepad. This text file (txt) can then be sent to our Technical Support for diagnosis and troubleshooting. Note: It's not recommended to keep a ‘Message Log’ session open (even if the window is minimized) for a prolonged period (refer to the Note below).
PAGE 183
H.323 User's Manual 5.7.3 5. Web Management Device Information The Device Information screen displays specific hardware and software product information. This information can help you to expedite any troubleshooting process. Capture the screen and email it to ‘our’ Technical Support personnel to ensure quick diagnosis and effective corrective action. From this screen you can also view and remove any loaded files used by the Mediant 1000 (stored in the RAM).
PAGE 184
Mediant 1000 5.8 Software Update The Software Update menu enables users to upgrade the Mediant 1000 software by loading a new cmp file along with the ini and a suite of auxiliary files, or to update the existing auxiliary files. The ‘Software Update’ menu comprises the following submenus: Software Upgrade Wizard (refer to Section 5.8.1 below) Load Auxiliary Files (refer to Section 5.8.2 on page 189) Software Upgrade Key (refer to section 5.8.
PAGE 185
H.323 User's Manual 5. Web Management Figure 5-60: Start Software Upgrade Screen Note: At this point, the process can be canceled with no consequence to the Mediant 1000 (click the Cancel button). If you continue the process (by clicking the Start Software Upgrade button, the process must be followed through and completed with a Mediant 1000 reset at the end.
PAGE 186
Mediant 1000 5. Click the Browse button, navigate to the cmp file and click the button Send File; the cmp file is loaded to the Mediant 1000 and you’re notified as to a successful loading (refer to Figure 5-62). Figure 5-62: cmp File Successfully Loaded 6. Note that the four action buttons (Cancel, Reset, Back, and Next) are now activated (following cmp file loading).
PAGE 187
H.323 User's Manual 7. 8. 5. Web Management In the ‘Load an ini File’ screen, you can now choose to either: • Click Browse and navigate to the ini file; the check box ‘Use existing configuration’, by default checked, becomes unchecked. Click Send File; the ini file is loaded to the Mediant 1000 and you’re notified as to a successful loading. • Ignore the Browse button (its field remains undefined and the check box ‘Use existing configuration’ remains checked by default).
PAGE 188
Mediant 1000 Figure 5-65: FINISH Screen Figure 5-66: ‘End Process’ Screen 11. Click the End Process button; the ‘Quick Setup’ screen appears and the full Web application is reactivated. H.
PAGE 189
H.323 User's Manual 5.8.2 5. Web Management Auxiliary Files The ‘Auxiliary Files’ screen enables you to load various files to the gateway, as described in Table 5-43. For detailed information on these files, refer to Chapter 16 on page 367. For information on deleting these files from the Mediant 1000, refer to Section 5.7.3 on page 183. The table presents a brief description of each auxiliary file.
PAGE 190
Mediant 1000 5.8.2.1 Loading the Auxiliary Files via the Embedded Web Server ¾ To load an auxiliary file to the gateway using the embedded Web server, take these 7 steps: 1. Open the ‘Auxiliary Files’ screen (Software Upgrade menu > Load Auxiliary Files); the ‘Auxiliary Files’ screen is displayed. Figure 5-67: Auxiliary Files Screen 2. Click the Browse button corresponding to the type of file that you want to load, and then navigate to the folder that contains the file you want to load. 3.
PAGE 191
H.323 User's Manual 5.8.2.2 5. Web Management Loading the Auxiliary Files via the ini File Before you load the configuration files (Call Progress Tones, Prerecorded Tones, FXS/FXO Coefficient, and CAS) to the gateway, in the ini file you need to define certain ini file parameters associated with these files. These ini file parameters specify the files that you want loaded and whether they must be stored in the non-volatile memory.
PAGE 192
Mediant 1000 5.9 Maintenance The Maintenance menu is used for the following operations: 5.9.1 Locking and unlocking the gateway (refer to Section 5.9.1 on page 192) Saving the gateway's configuration (refer to Section 5.9.2 on page 193) Resetting the gateway (refer to Section 5.9.3 on page 195) Locking and Unlocking the Gateway The Lock and Unlock options allow you to lock the gateway so that it does not accept any new incoming calls.
PAGE 193
H.323 User's Manual 5. Web Management 3. In the 'Lock Timeout' field (relevant only if the 'Graceful Option' in the previous step is set to 'Yes'), enter the time (in seconds) after which the gateway locks. Note that if no traffic exists and the time has not expired, the gateway locks. 4. Click the LOCK button; If 'Graceful Option' is set to 'Yes', the lock is delayed and a screen displaying the number of remaining calls and time is displayed. Otherwise, the lock process begins immediately.
PAGE 194
Mediant 1000 ¾ To save the changes to the non-volatile, take these 2 steps: 1. Open the ‘Maintenance Actions' screen (Maintenance menu); the ‘Maintenance Actions' screen is displayed. Figure 5-69: Maintenance Actions Screen 2. Click the BURN button; a confirmation message appears when the save is completed successfully. H.
PAGE 195
H.323 User's Manual 5.9.3 5. Web Management Resetting the Mediant 1000 The 'Maintenance Actions' screen enables you to remotely reset the gateway. Before you reset the gateway, you can choose the following options: Save the gateway's current configuration to the flash memory (non-volatile). Perform a graceful shutdown. Reset starts only after a user-defined time expires or no more active traffic exists (the earliest thereof). ¾ To reset the gateway, take these 6 steps: 1.
PAGE 196
Mediant 1000 5. In the 'Shutdown Timeout' field (relevant only if the 'Graceful Option' in the previous step is set to 'Yes'), enter the time after which the gateway resets. Note that if no traffic exists and the time has not expired, the gateway resets. 6. Click the RESET button; If 'Graceful Option' is set to 'Yes', the reset is delayed and a screen displaying the number of remaining calls and time is displayed. When the device resets, a message is displayed informing of the waiting period. H.
PAGE 197
H.323 User's Manual 5.10 5. Web Management Monitoring the Gateway (Home Page) The Home icon, located above the main menu bar, opens the Home page. This page allows you to perform the following: Monitor trunks and channels (refer to Section 5.10.1 on page 199) Monitor analog and digital modules (refer to Section 5.10.2 on page 201) Monitor Ethernet ports, Dry Contacts, power supply units, and fan tray unit (refer to Section 5.10.
PAGE 198
Mediant 1000 Table 5-44: Description of the Areas of the Home Page Item# Description 1 ALARMS button for viewing the Active Alarms table. For a detailed description, refer to Section 5.10.4 on page 202. 2 Module slot number (1 to 6). 3 Module type (digital, FXO, or FXS). 4 Module status indicator. For a detailed description, refer to Section 5.10.2 on page 201. 5 Module's port (trunk or channel) status indicator. For a detailed description, refer to Section 5.10.1 on page 199.
PAGE 199
H.323 User's Manual 5. Web Management 5.10.1 Monitoring the Mediant 1000 Trunks and Channels The Home page provides real-time monitoring of the trunks and channels. ¾ To monitor the status of the Mediant 1000 trunks and channel ports, take this step: Open the Home page by clicking the Home icon; the Home page is displayed. The number of trunks and channels that appear in the screen depends on the system configuration.
PAGE 200
Mediant 1000 ¾ To view a detailed status of a channel, take these 3 steps: 1. In the Home page, click the trunk or analog port of whose status you want to view; a shortcut menu appears. 2. From the shortcut menu, choose Port Settings; the following appears, depending on whether you clicked a trunk or FXO/FXS port: • Trunk: the 'Trunk & Channel Status' screen pertaining to the specific trunk appears.
PAGE 201
H.323 User's Manual 5. Web Management Table 5-46: Trunk Channel Status Color Indicators continues on pages 201 to 201) Indicator Color Label Description Grey Inactive Configured, but currently no call Green Active Call in progress (RTP traffic) Pink SS7 Configured for SS7 (Currently not supported) Dark blue Non Voice Not configured Blue ISDN Signaling Configured as a D-channel 5.10.
PAGE 202
Mediant 1000 5.10.3 Monitoring Ethernet Ports, Dry Contacts, Power Supply Units, and Fan Tray Unit The Home page also displays the status of the Ethernet ports, Dry Contacts, power supply units, and fan tray unit.
PAGE 203
H.323 User's Manual 5. Web Management 5.10.5 Viewing Trunk Settings The Home page provides an alternative path (Advanced Configuration menu > Trunk Settings) for accessing the 'Trunk Settings' screen (refer to Section 5.6.3 on page 150), in which the trunk settings are viewed and configured. ¾ To view the trunk settings, take these 3 steps: 1. In the Home page, click the required trunk port; a shortcut menu appears. 2.
PAGE 204
Mediant 1000 5.10.6 Viewing Ethernet Port Settings The 'Ethernet Port Information' screen provides read-only information on the Ethernet connection used by the Mediant 1000. The Ethernet Port Information parameters are displayed in Table 5-49. For detailed information on the Ethernet interface configuration, refer to Section 9.1 on page 279. ¾ To view Ethernet port settings, take this step: In the Home page, click the Ethernet port status icon Information' screen opens.
PAGE 205
H.323 User's Manual 5. Web Management 5.10.8 Releasing an Analog Channel The Home page allows you to inactivate (release) an FXO or FXS analog channel. This is sometimes useful in scenarios, for example, when the gateway (FXO) is connected to a PBX and the communication between the two can't be disconnected (e.g., when using reverse polarity). ¾ To release a channel, take these 2 steps: 1. Open the Home page by clicking the Home icon. 2.
PAGE 206
Mediant 1000 b. Click the Remove Module button; a message box appears requesting you to confirm module removal. Figure 5-81: Confirmation Message Box after Clicking Remove Module Button c. Click OK to confirm module removal; after a few seconds, the module is "removed" and the module status indicator is grayed. The name of the module is suffixed with the word 'Reserved'. Figure 5-82: Module Removed Indicated by "Reserved" d. 2. You can now physically remove the module (refer to Section 3.5.
PAGE 207
H.323 User's Manual 5.11 5. Web Management Logging Off the Embedded Web Server The Log Off button enables you to log off the Embedded Web Server and to re-access it with a different account. For detailed information on the Web User Accounts, refer to Section 5.2.1 on page 55. ¾ To log off the Embedded Web Server, take these 2 steps: 1. Click the Log Off button on the main menu bar; the 'Log Off' prompt screen is displayed. Figure 5-84: Log off Prompt 2. Version 5.
PAGE 208
Mediant 1000 Reader's Notes H.
PAGE 209
H.323 User's Manual 6 6. ini File Configuration of the Mediant 1000 ini File Configuration of the Mediant 1000 As an alternative to configuring the VoIP gateway using the Web interface (refer to Section 5 on page 55), it can be configured by loading the ini file containing Customer-configured parameters. The ini file is loaded via the BootP/TFTP utility (refer to Appendix C on page 381) or via any standard TFTP server. It can also be loaded through the Web Interface (refer to Section 5.6.5 on page 159).
PAGE 210
Mediant 1000 6.3 The ini File Content The ini file contains the following gateway information: 6.4 Networking parameters (refer to Section 6.5.1 on page 212) System parameters (refer to Section 6.5.2 on page 217) Web and Telnet parameters (refer to Section 6.5.3 on page 222) Security parameters (refer to Section 6.5.4 on page 223) RADIUS parameters (refer to Section 6.5.5 on page 224) SNMP parameters (refer to Section 6.5.6 on page 225) H.
PAGE 211
H.323 User's Manual 6.4.2 6. ini File Configuration of the Mediant 1000 The ini File Example Figure 6-2 shows an example of an ini file for the VoIP gateway. Figure 6-2: H.323 ini File Example PCMLawSelect = 1 ProtocolType = 1 TerminationSide = 0 FramingMethod = 0 LineCode = 2 TDMBusClockSource = 4 ClockMaster = 0 ;Channel Params DJBufMinDelay = 75 RTPRedundancyDepth = 1 IsGatekeeperUsed = 1 GatekeeperIp = 192.168.122.
PAGE 212
Mediant 1000 6.5 The ini File Parameter Reference The table below lists all the ini file parameters. References to their descriptions in the Web interface are provided, except for those ini file parameters that don't have corresponding Web interface parameters. 6.5.
PAGE 213
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Web Parameter Name Valid Range and Description EnableIPAddrTranslation 0 = Disable IP address translation. 1 = Enable IP address translation for RTP, RTCP and T.38 packets (default). 2 = Enable IP address translation for ThroughPacket™. 3 = Enable IP address translation for all protocols (RTP, RTCP, T38 and ThroughPacket™).
PAGE 214
Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Web Parameter Name Valid Range and Description BaseUDPport For a description of this parameter, refer to Table 5-29 on page 146. RemoteBaseUDPPort For a description of this parameter, refer to Table 5-29 on page 146. L1L1ComplexTxUDPPort For a description of this parameter, refer to Table 5-29 on page 146. L1L1ComplexRxUDPPort For a description of this parameter, refer to Table 5-29 on page 146.
PAGE 215
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Web Parameter Name Valid Range and Description EnableNTPasOAM This parameter applies to both Multiple IPs and VLAN mechanisms. Multiple IPs: Determines the network type for NTP services. VLAN: Determines the traffic type for NTP services. 1 = OAM (default) 0 = Control.
PAGE 216
Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Web Parameter Name Valid Range and Description PPPoEUserName User Name for PAP or Host Name for CHAP authentication. The valid range is a string of up to 47 characters. The default value is 0. PPPoEPassword Password for PAP or Secret for CHAP authentication. The valid range is a string of up to 47 characters. The default value is 0. PPPoEServerName Server Name for CHAP authentication.
PAGE 217
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-1: Networking Parameters (continues on pages 212 to 217) ini File Field Name Web Parameter Name Valid Range and Description The combination of Host / IP and Root Path must be unique for each row in the table. For example, there must be only one row in the table with a Host / IP of 192.168.1.1 and Root Path of /audio. NFSServers_NfsVersion For a description of this parameter, refer to Table 5-24 on page 135.
PAGE 218
Mediant 1000 Table 6-2: System Parameters (continues on pages 217 to 221) ini File Field Name Web Parameter Name Valid Range and Description ActivityListToLog The Activity Log mechanism enables the gateway to send log messages (to a Syslog server) that report certain types of web actions according to a predefined filter. The following filters are available: PVC (Parameters Value Change) - Changes made on-the-fly to parameters. AFL (Auxiliary Files Loading) - Loading of auxiliary files (e.g.
PAGE 219
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-2: System Parameters (continues on pages 217 to 221) ini File Field Name Web Parameter Name Valid Range and Description RAILowThreshold For a description of this parameter, refer to Table 5-4 on page 70. RAILoopTime For a description of this parameter, refer to Table 5-4 on page 70. Disconnect Supervision Parameters DisconnectOnBrokenConn ection For a description of this parameter, refer to Table 5-7 on page 80.
PAGE 220
Mediant 1000 Table 6-2: System Parameters (continues on pages 217 to 221) ini File Field Name Web Parameter Name Valid Range and Description FXOCoeffFileURL Specifies the name of the FXO coefficients file and the location of the server (IP address or FQDN) from which it is loaded. http://server_name/file, https://server_name/file. Note: The maximum length of the URL addres is 99 characters.
PAGE 221
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-2: System Parameters (continues on pages 217 to 221) ini File Field Name Web Parameter Name Valid Range and Description BootPDelay The interval between the device’s startup and the first BootP/DHCP request that is issued by the device. 1 = 1 second (default). 2 = 3 second. 3 = 6 second. 4 = 30 second. 5 = 60 second. Note: This parameter only takes effect from the next reset of the device.
PAGE 222
Mediant 1000 6.5.3 Web and Telnet Parameters Table 6-3: Web and Telnet Parameters (continues on pages 222 to 223) ini File Field Name Web Parameter Name Valid Range and Description WebAccessList_x Defines up to ten IP addresses that are permitted to access the gateway’s Web and Telnet interfaces. Access from an undefined IP address is denied. This security feature is inactive (the gateway can be accessed from any IP address) when the table is empty. For example: WebAccessList_0 = 10.13.2.
PAGE 223
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-3: Web and Telnet Parameters (continues on pages 222 to 223) ini File Field Name Web Parameter Name Valid Range and Description LogoFileName Name of the image file containing the user’s logo. File name can be up to 47 characters. The logo file name can be used to replace AudioCodes’ default Web logo with a user defined logo. Use a gif, jpeg or jpg image file.
PAGE 224
Mediant 1000 Table 6-4: Security Parameters (continues on pages 223 to 224) ini File Field Name Web Parameter Name Valid Range and Description AccessList_Start_Port AccessList_End_Port For a description of this parameter, refer to Table 5-34 on page 166. AccessList_Protocol For a description of this parameter, refer to Table 5-34 on page 166. AccessList_Packet_Size For a description of this parameter, refer to Table 5-34 on page 166.
PAGE 225
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-5: RADIUS Parameter (continues on pages 224 to 225) ini File Field Name Web Parameter Name Valid Range and Description RadiusLocalCacheTimeout For a description of this parameter, refer to Table 5-35 on page 168. RadiusVSAVendorID For a description of this parameter, refer to Table 5-35 on page 168. RadiusVSAAccessAttribute For a description of this parameter, refer to Table 5-35 on page 168. 6.5.
PAGE 226
Mediant 1000 Table 6-6: SNMP Parameters (continues on pages 225 to 226) ini File Field Name Web Parameter Name Valid Range and Description SNMPUsers_AuthKey For a description of this parameter, refer to Table 5-39 on page 175. SNMPUsers_PrivKey For a description of this parameter, refer to Table 5-39 on page 175. SNMPUsers_Group For a description of this parameter, refer to Table 5-39 on page 175. 6.5.7 H.323 Configuration Parameters Table 6-7: H.
PAGE 227
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name * Web Parameter Name CoderName Valid Range and Description Defines the gateway’s coder list (up to five coders can be configured). Enter coders in the following format: CoderName=,,,,. Coder Name Templat e Packetizatio n Time Rate Payloa d Type Silence Suppressio n G.
PAGE 228
Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name * Web Parameter Name Valid Range and Description Note 1: The coder name is case-sensitive. Note 2: If silence suppression is not defined (for a specific coder), the value defined by the parameter EnableSilenceCompression is used. Note 3: The value of several fields is hard-coded according to well-known standards (e.g., the payload type of G.711 U-law is always 0). Other values can be set dynamically.
PAGE 229
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name * Web Parameter Name Valid Range and Description H323IDString For a description of this parameter, refer to Table 5-3 on page 64. SourceEncodeMode For a description of this parameter, refer to Table 5-3 on page 64. DestEncodeMode For a description of this parameter, refer to Table 5-3 on page 64.
PAGE 230
Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name * Web Parameter Name Valid Range and Description EnableHold For a description of this parameter, refer to Table 5-8 on page 86. EnableTransfer For a description of this parameter, refer to Table 5-8 on page 86. XferPrefix For a description of this parameter, refer to Table 5-8 on page 86. EnableForward For a description of this parameter, refer to Table 5-8 on page 86.
PAGE 231
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-7: H.323 Configuration Parameters (continues on pages 226 to 232) ini File Field Name * Web Parameter Name Valid Range and Description EnableDigitDelivery2IP For a description of this parameter, refer to Table 5-7 on page 80. EnableDigitDelivery For a description of this parameter, refer to Table 5-7 on page 80.
PAGE 232
Mediant 1000 Table 6-7: H.
PAGE 233
H.323 User's Manual 6.5.8 6. ini File Configuration of the Mediant 1000 ISDN and CAS Interworking-Related Parameters Table 6-8: ISDN and CAS Interworking-Related Parameters (continues on pages 233 to 236) ini File Field Name Web Parameter Name Valid Range and Description EnableTDMoverIP For a description of this parameter, refer to Table 5-21 on page 126. EnableISDNTunnelingTel 2IP For a description of this parameter, refer to Table 5-21 on page 126.
PAGE 234
Mediant 1000 Table 6-8: ISDN and CAS Interworking-Related Parameters (continues on pages 233 to 236) ini File Field Name Web Parameter Name Valid Range and Description DefaultCauseMapISDN2I P Defines a single default ISDN Release Cause that is used (in ISDN to IP calls) instead of all received release causes except when the following Q.931 cause values are received: Normal Call Clearing (16), User Busy (17), No User Responding (18) or No Answer from User (19). The range is valid Q.
PAGE 235
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-8: ISDN and CAS Interworking-Related Parameters (continues on pages 233 to 236) ini File Field Name Web Parameter Name Valid Range and Description EnableUUIIP2Tel For a description of this parameter, refer to Table 5-21 on page 126. ScreeningInd2IP For a description of this parameter, refer to Table 5-21 on page 126. SupportRedirectInFacility 0 = Not Supported (default).
PAGE 236
Mediant 1000 Table 6-8: ISDN and CAS Interworking-Related Parameters (continues on pages 233 to 236) ini File Field Name Web Parameter Name Valid Range and Description EnablePatternDetector Enables or disables activation of the Pattern Detector (PD). Valid options include: 0 = Disable (default). 1 = Enable. PDPattern Defines the patterns that can be detected by the Pattern Detector. The valid range is 0 to 0xFF.
PAGE 237
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-9: Analog Telephony Parameters (continues on pages 236 to 239) ini File Field Name Web Parameter Name [Module n] CallerDisplayInfoX n = 0 or 5 (module serial number) Valid Range and Description CallerDisplayInfo = , Port = 0 to 3. 0 = Not restricted (default). 1 = Restricted. For example: [Module 0] CallerDisplayInfo0 = Susan C.,0 CallerDisplayInfo2 = Mark M.
PAGE 238
Mediant 1000 Table 6-9: Analog Telephony Parameters (continues on pages 236 to 239) ini File Field Name Web Parameter Name Valid Range and Description MWIDisplay For a description of this parameter, refer to Table 5-8 on page 86. StutterToneDuration For a description of this parameter, refer to Table 5-8 on page 86. PayPhoneMeteringMode For a description of this parameter, refer to Table 5-9 on page 89. MeteringType For a description of this parameter, refer to Table 5-9 on page 89.
PAGE 239
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-9: Analog Telephony Parameters (continues on pages 236 to 239) ini File Field Name Web Parameter Name PolarityReversalType Valid Range and Description Defines the voltage change slope during polarity reversal or wink. 0 = Soft (default). 1 = Hard. Note 1: Some Caller ID signals use reversal polarity and/or wink signals. In these cases it is recommended to set PolarityReversalType to 1 (Hard). Note 2: Applicable only to FXS modules.
PAGE 240
Mediant 1000 6.5.10 Number Manipulation and Routing Parameters Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Web Parameter Name TrunkGroup_x Valid Range and Description For digital interfaces: Defines the Trunk Group table. TrunkGroup_x = T-U/a-b,c,d x = Trunk group ID (1 to 99). T = Starting physical trunk number. U = Ending physical trunk number. a = Starting B-channel (from 1). b = Ending B-channel (up to 31).
PAGE 241
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Web Parameter Name Valid Range and Description ReplaceEmptyDstWithPort Number For a description of this parameter, refer to Table 5-13 on page 97. CopyDestOnEmptySource 0 = Leave Source Number empty (default). 1 = If the Source Number of an incoming Tel to IP call is empty, the Destination Number is copied to the Source Number.
PAGE 242
Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Web Parameter Name PSTNPrefix Valid Range and Description PSTNPrefix = a,b,c,d,e a = Destination Number Prefix b = Trunk group ID (1 to 99) c = Source Number Prefix d = Source IP address (obtained from the Setup message) e = IP Profile ID (1 to 4) Selection of trunk groups (for IP to Tel calls) is according to destination number, source number and source IP address.
PAGE 243
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Web Parameter Name NumberMapTel2IP Valid Range and Description Manipulates the destination number for Tel to IP calls (Destination Phone Number Manipulation Table for TelÆIP calls). NumberMapTel2IP = a,b,c,d,e,f,g a = Destination number prefix b = Number of stripped digits from the left, or (if brackets are used) from the right.
PAGE 244
Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Web Parameter Name SourceNumberMapTel2IP Valid Range and Description Configures the Source Phone Number Manipulation Table for TelÆIP calls. SourceNumberMapTel2IP = a,b,c,d,e,f,g,h a = Source number prefix b = Number of stripped digits from the left, or (if in brackets are used) from right. A combination of both options is allowed.
PAGE 245
H.323 User's Manual 6.
PAGE 246
Mediant 1000 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 240 to 246) ini File Field Name Web Parameter Name EnableETSIDiversion Valid Range and Description Defines the method in which the Redirect Number is passed towards the Tel side. Valid options include: [0] = Q.
PAGE 247
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 246 to 248) ini File Field Name Web Parameter Name Valid Range and Description DChConfig_x For a description of this parameter, refer to Table 5-32 on page 152. ISDNNFASInterfaceID_x For a description of this parameter, refer to Table 5-32 on page 152. CASTableIndex_x For a description of this parameter, refer to Table 5-32 on page 152.
PAGE 248
Mediant 1000 Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 246 to 248) ini File Field Name Web Parameter Name Valid Range and Description ISDNIBehavior_x Same as the description for parameter ISDNIBehavior, but for a specific trunk ID. ISDNInCallsBehavior_x Same as the description for parameter ISDNInCallsBehavior, for a specific trunk ID. ISDNOutCallsBehavior_x Same as the description for parameter ISDNOutCallsBehavior, but for a specific trunk ID. 6.5.
PAGE 249
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 Table 6-12: Channel Parameters (continues on pages 248 to 250) ini File Field Name Web Parameter Name NSEMode Valid Range and Description Cisco compatible fax and modem bypass mode 0 = NSE disabled (default) 1 = NSE enabled Note 1: This feature can be used only if VxxModemTransportType=2 (Bypass) Note 2: To use this feature: The Cisco gateway must include the following definition: ‘modem passthrough nse payload-type 100 codec g711alaw’.
PAGE 250
Mediant 1000 Table 6-12: Channel Parameters (continues on pages 248 to 250) ini File Field Name Web Parameter Name Valid Range and Description EnableStandardSIDPayloadType For a description of this parameter, refer to Table 5-29 on page 146. RTPSIDCoeffNum Determines the number of spectral coefficients added to an SID packet being sent according to RFC 3389. Valid only if ‘EnableStandardSIDPayloadType’ is set to 1. The valid values are 0 (default), 4, 6, 8 and 10.
PAGE 251
H.323 User's Manual 6. ini File Configuration of the Mediant 1000 6.5.13 Configuration Files Parameters The configuration files (Call Progress Tones, Prerecorded Tones, User Information, FXS/FXO Coefficient, and CAS) can be loaded to the Mediant 1000 using the Embedded Web Server or a TFTP session (refer to Section 5.8.2 on page 189). Before you load them to the gateway, in the ini file, you need to specify the files that you want loaded and whether they must be stored in the non-volatile memory.
PAGE 252
Mediant 1000 Reader's Notes H.
PAGE 253
H.323 User's Manual 7 7. Using BootP / DHCP Using BootP / DHCP The Mediant 1000 uses the Bootstrap Protocol (BootP) and the Dynamic Host Configuration Protocol (DHCP) to obtain its networking parameters and configuration automatically after it is reset. BootP and DHCP are also used to provide the IP address of a TFTP server on the network, and files (cmp and ini) to be loaded into memory. DHCP is a communication protocol that automatically assigns IP addresses from a central point.
PAGE 254
Mediant 1000 7.2 Using DHCP When the gateway is configured to use DHCP (DHCPEnable = 1), it attempts to contact the local DHCP server to obtain the networking parameters (IP address, subnet mask, default gateway and primary/secondary DNS server). These network parameters have a ‘time limit’. After the time limit expires, the gateway must ‘renew’ its lease from the DHCP server.
PAGE 255
H.323 User's Manual 7. Using BootP / DHCP 7.3 Using BootP 7.3.1 Upgrading the Mediant 1000 When upgrading the Mediant 1000 (loading new software onto the gateway) using the BootP/TFTP configuration utility: From version 4.4 to version 4.4 or to any higher version, the device retains its configuration (ini file). However, the auxiliary files (CPT, logo, etc.) may be erased. From version 4.6 to version 4.
PAGE 256
Mediant 1000 Table 7-1 details the vendor specific information field according to device types: Table 7-1: Vendor Specific Information Field Tag # Description Value Length 220 Gateway Type #09 = Mediant 1000 1 221 Current IP Address XXX.XXX.XXX.XXX 4 222 Burned Boot Software Version X.XX 4 223 Burned cmp Software Version XXXXXXXXXXXX 12 224 Geographical Address 0 – 31 1 225 Chassis Geographical Address 0 – 31 1 228 Indoor / Outdoor (Indoor is valid only for FXS.
PAGE 257
H.323 User's Manual 8. Telephony Capabilities 8 Telephony Capabilities 8.1 Working with Supplementary Services The Mediant 1000 gateway supports the following supplementary services: Call Hold and Retrieve; refer to Section 8.1.1 on page 257 Consultation / Alternate; refer to Section 8.1.2 on page 257 Call Transfer (H.450.2); refer to Section 8.1.3 on page 258 Call Forward (H.450.3); refer to Section 8.1.4 on page 258 Call Waiting (H.450.6); refer to Section 8.1.
PAGE 258
Mediant 1000 8.1.3 Call Transfer There are two types of call transfers: Consultation Transfer (REFER and REPLACES) Blind Transfer (REFER) The common way to perform a consultation transfer is as follows: In the transfer scenario there are three parties: Party A = transferring, Party B = transferred, Party C = transferred to. A Calls B. B answers. A presses the hook-flash and puts B on-hold (party B hears a hold tone) A dials C.
PAGE 259
H.323 User's Manual 8.1.5 8. Telephony Capabilities Call Waiting The Call Waiting feature enables FXS modules to accept an additional (second) call on busy endpoints. If an incoming IP call is designated to a busy port, the called party hears a call waiting tone (several configurable short beeps) and (for Bellcore and ETSI Caller IDs) can view the Caller ID string of the incoming call. The calling party hears a Call Waiting Ringback Tone.
PAGE 260
Mediant 1000 8.2 Configuring the DTMF Transport Types The Mediant 1000 gateway supports several methods of conveying DTMF digits over the IP network. Three methods are controlled by H.245 protocol and therefore use its capability exchange mechanism to ensure coordination with the remote side. A fourth method uses Q.931 Info messages. If neither of these methods is selected, DTMF is transferred inside the audio stream.
PAGE 261
H.323 User's Manual 8.2.1 8. Telephony Capabilities Overview of In-Band DTMF Transport Types The Mediant 1000 gateway controls the way DTMF digits are transferred in-band (as part of the audio stream) using the DTMFTransport configuration parameter. Note that this parameter is automatically updated in the first four methods described in the previous section and therefore shouldn’t be changed, while, for the fifth method (in-band DTMF) it should normally be set to Transparent.
PAGE 262
Mediant 1000 8.3.3 Configuring Fax/Modem Bypass Mode When VxxTransportType= 2 (FaxModemBypass, Vxx can be one of the following: V32/V22/Bell/V34/Fax), then on detection of fax/modem, the channel automatically switches from the current voice coder to a high bit-rate coder (G.711 or G.726), as defined by the user, with the FaxModemBypassCoderType configuration parameter.
PAGE 263
H.323 User's Manual 8.4 8. Telephony Capabilities Redundant Gatekeeper Implementation The redundant Gatekeeper mechanism (IsRedundantGKUsed=1), similar to the Alternate Gatekeeper procedure (described in para. 7.2.6 in the H.323 standard), provides Mediant 1000 gateways with Gatekeeper redundancy options. This mechanism allows the gateway to use up to two additional Gatekeepers as a backup in the event of a primary Gatekeeper failure.
PAGE 264
Mediant 1000 8.5 Mediant 1000 Registration with a Gatekeeper The Mediant 1000 supports three different methods of registration with a Gatekeeper: 8.5.1 Registration with Prefixes The gateway registers with a Gatekeeper using prefixes (range of numbers). ¾ To register with prefixes, take these 2 steps: 1. Configure the Registration Prefixes Table (refer to Section 5.5.6 on page 112). 2. Set the GWRegistrType parameter (Table 5-4) according to your requirements: • E.
PAGE 265
H.323 User's Manual 8.5.3 8. Telephony Capabilities Registration with Endpoints The gateway registers with the Gatekeeper using the numbers defined in the ‘Trunk Group Table' screen (normally used with FXS modules). ¾ To register with endpoints, take these 2 steps: 1. Don’t configure the Registration Prefixes Table. 2. Set the GWRegistrType parameter according to your requirements: • E.164 [0] = The gateway registers the endpoints using E.164 format.
PAGE 266
Mediant 1000 8.7 Dynamic Jitter Buffer Operation Voice frames are transmitted at a fixed rate. If the frames arrive at the other end at the same rate, voice quality is perceived as good. In many cases, however, some frames can arrive slightly faster or slower than the other frames. This is called jitter (delay variation), and degrades the perceived voice quality. To minimize this problem, the gateway uses a jitter buffer.
PAGE 267
H.323 User's Manual 8.8 8. Telephony Capabilities Configuring the Gateway’s Alternative Routing (Based on Connectivity and QoS) The Alternative Routing feature enables reliable routing of Tel to IP calls when a Proxy isn’t used. The Mediant 1000 gateway periodically checks the availability of connectivity and suitable Quality of Service (QoS) before routing. If the expected quality cannot be achieved, an alternative IP route for the prefix (phone number) is selected.
PAGE 268
Mediant 1000 8.8.4 Relevant Parameters The following parameters (described in Table 5-13) are used to configure the Alternative Routing mechanism: 8.9 AltRoutingTel2IPEnable AltRoutingTel2IPMode IPConnQoSMaxAllowedPL IPConnQoSMaxAllowedDelay Call Termination on Mediant 1000 FXO The following six methods for call termination are supported by the Mediant 1000/FXO. Note that the used disconnection methods must be supported by the CO or PBX.
PAGE 269
H.323 User's Manual 8.10 8. Telephony Capabilities Mapping PSTN Release Cause to H.323 Response The Mediant 1000 FXO module is used to interoperate between the H.323 network and the PSTN/PBX. This interoperability includes the mapping of PSTN/PBX Call Progress Tones to H.323 Release Causes for IPÆTel calls. The converse is also true: For TelÆIP calls, the H.323 Release Causes are mapped to tones played to the PSTN/PBX.
PAGE 270
Mediant 1000 Table 8-1: Supported CDR Fields Field Name Cid Description Port Number CallId H.323/SIP Call Identifier Trunk Physical Trunk Number (digital only) BChan Selected B-Channel (digital only) ConId H.
PAGE 271
H.323 User's Manual 8.12 8. Telephony Capabilities Supported RADIUS Attributes Use Table 8-2 below for explanations on the RADIUS attributes contained in the communication packets transmitted between the Mediant 1000 and a RADIUS Server. Table 8-2: Supported RADIUS Attributes (continues on pages 271 to 272) Attribute Number Attribute Name VSA No.
PAGE 272
Mediant 1000 Table 8-2: Supported RADIUS Attributes (continues on pages 271 to 272) Attribute Number Attribute Name VSA No. Purpose Value Format Sample 2 AAA 41 Acct-DelayTime No.
PAGE 273
H.323 User's Manual 8.13 8. Telephony Capabilities Configuration Examples 8.13.1 Trunk-to-Trunk Routing Example This example describes two Mediant 1000 gateways, each interfacing with the PSTN through four E1 spans. Gateway ‘A’ is configured to route all incoming TelÆIP calls to gateway ‘B’. Gateway ‘B’ generates calls to PSTN on the same E1 Trunk as the call was originally received (in gateway ‘A’). Gateway ‘A’ IP address: 192.168.3.50 Gateway ‘B’ IP address: 192.168.3.
PAGE 274
Mediant 1000 8.13.2 Establishing a Call between Two Gateways After you’ve installed and set up the Mediant 1000, you can ensure that it functions as expected by establishing a call between it and another gateway. This section exemplifies how to configure two 8-port Mediant 1000 FXS H.323 gateways in order to establish a call. After configuration, you can make calls between telephones connected to a single Mediant 1000 gateway or between the two Mediant 1000 gateways.
PAGE 275
H.323 User's Manual 8. Telephony Capabilities 8.13.3 Using Two Gateways with Gatekeeper In this demo, a call can be made from an endpoint in one gateway to an endpoint in another. ¾ To configure the ini file parameters, take these 8 steps: 1. Use Gatekeeper. 2. 3. 4. 5. 6. 7. In ‘GatekeeperIP’, insert the IP of the PC that runs the Gatekeeper. Endpoint numbers of the first gateway: 101...108. Endpoint numbers of the second gateway: 201...208. Run Gatekeeper on the PC.
PAGE 276
Mediant 1000 8.13.5.1 Dialing from Remote Extension (Phone Connected to FXS) ¾ To configure the call, take these 3 steps: 1. Lift the handset to hear the dial tone coming from PBX, as if the phone was connected directly to PBX. The FXS and FXO Mediant 1000 gateways establish a voice path connection from the phone to the PBX immediately after the phone handset is raised. 2. Dial the destination number (the DTMF digits are sent, over IP, directly to the PBX).
PAGE 277
H.323 User's Manual 3. 8. Telephony Capabilities In the ‘Tel to IP Routing’ screen, enter 20 in the ‘Destination Phone Prefix’ field, and the IP address of the FXO Mediant 1000 gateway (10.1.10.2) in the field ‘IP Address’. Note: In remote extensions, for the transfer to function, hold must be disabled on the FXS (i.e., Enable Hold = 0). 8.13.5.4 FXO Mediant 1000 Configuration (using the Embedded Web Server) ¾ To configure the FXO Mediant 1000, take these 4 steps: 1.
PAGE 278
Mediant 1000 Reader's Notes H.
PAGE 279
H.323 User's Manual 9. Networking Capabilities 9 Networking Capabilities 9.1 Ethernet Interface Configuration Using the parameter ‘EthernetPhyConfiguration‘, users can control the Ethernet connection mode. Either the manual modes (10 Base-T Half-Duplex, 10 Base-T Full-Duplex, 100 Base-TX Half-Duplex, 100 Base-TX Full-Duplex) or Auto-Negotiate mode can be used.
PAGE 280
Mediant 1000 2. After start-up has completed and the operational software is running, the gateway continues to use the Ethernet port used for program load. The gateway switches over from one Ethernet port to the other every time an Ethernet link carrier loss is detected on the active Ethernet port and if the Ethernet link of the other port is operational.
PAGE 281
H.323 User's Manual 9. Networking Capabilities To solve these problems the following mechanisms are available: 9.3.1 First Incoming Packet Mechanism (refer to Section 9.3.1 on page 281) RTP / T.38 No-Op packets according to the avt-rtp-noop draft (refer to Section 9.3.2 on page 281). For SNMP NAT traversal, refer to Section 15.10 on page 364. First Incoming Packet Mechanism If the remote gateway resides behind a NAT device, it’s possible that the Mediant 1000 can activate the RTP/RTCP/T.
PAGE 282
Mediant 1000 9.4 Point-to-Point Protocol over Ethernet (PPPoE) PPPoE is a method of sending the Point-to-Point Protocol over Ethernet network. 9.4.1 Point-to-Point Protocol (PPP) Overview Point-to-Point Protocol (PPP) provides a method of transmitting data over serial point-topoint links. The protocol defines establishing, configuring and testing the data link connection and the network protocol.
PAGE 283
H.323 User's Manual 9.4.2 9. Networking Capabilities PPPoE Overview PPPoE is a method of sending the Point-to-Point Protocol over Ethernet network. PPPoE provides the ability to connect a network of hosts over a simple bridging access device to a remote Access Concentrator. Access control, billing and type of service can be done on a per-user, rather than a per-site, basis.
PAGE 284
Mediant 1000 When working in a PPPoE environment, the gateway negotiates for its IP address (as described above). However, if the user desires to disable the PPPoE client, the gateway can be configured to use default values for IP address, subnet mask and default gateway. This can be done using ini file parameters PPPoERecoverIPAddress, PPPoERecoverSubnetMask and PPPoERecoverDfgwAddress.
PAGE 285
H.323 User's Manual 9.8 9. Networking Capabilities Simple Network Time Protocol Support Simple Network Time Protocol (SNTP) client functionality generates requests and reacts to the resulting responses using the NTP version 3 protocol definitions (according to RFC 1305). Through these requests and responses, the NTP client is able to synchronize the system time to a time source within the network, thereby eliminating any potential issues should the local system clock 'drift' during operation.
PAGE 286
Mediant 1000 9.10 VLANS and Multiple IPs 9.10.1 Multiple IPs Media, Control, and Management (OAM) traffic in the gateway can be assigned one of the following IP addressing schemes: Single IP address for all traffic (i.e., Media, Control, and OAM). Separate IP address for each traffic type. For separate IP addresses, the different traffic types are separated into three dedicated networks.
PAGE 287
H.323 User's Manual 9. Networking Capabilities For the mapping of an application to its class-of-service and traffic type, refer to Table 9-1 on page 287. Media traffic type is assigned ‘Premium media’ class of service, Management traffic type is assigned ‘Bronze’ class of service, and Control traffic type is assigned ‘Premium control’ class of service.
PAGE 288
Mediant 1000 9.10.2.1 Operation Outgoing packets (from the gateway to the switch): All outgoing packets are tagged, each according to its interface (control, media or OAM). If the gateway’s native ID is identical to one of the other IDs (usually to the OAM ID), this ID (e.g., OAM) is set to zero on outgoing packets (VlanSendNonTaggedOnNative = 0). This method is called Priority Tagging (p tag without Q tag).
PAGE 289
H.323 User's Manual 9. Networking Capabilities 9.10.3.1 Integrating Using the Embedded Web Server ¾ To integrate the Mediant 1000 into a VLAN and multiple IPs network using the Embedded Web Server, take these 7 steps: 1. Access the Embedded Web Server (Section 5.3 on page 57). 2. Use the Software Upgrade Wizard (Section 5.8.1 on page 184) to load and burn the firmware version to the Mediant 1000 (VLANs and multiple IPs support is available only when the firmware is burned to flash). 3.
PAGE 290
Mediant 1000 Figure 9-3: Example of the IP Settings Screen • 5. Click the Submit button to save your changes. Configure the IP Routing table by completing the following steps (the IP Routing table is required to define static routing rules for the OAM and Control networks since a default gateway isn’t supported for these networks): • Open the ‘IP Routing Table’ screen (Advanced Configuration menu > Network Settings > IP Routing Table option); the ‘IP Routing Table’ screen is displayed.
PAGE 291
H.323 User's Manual 9. Networking Capabilities 9.10.3.2 Integrating using the ini File ¾ To integrate the Mediant 1000 into a VLAN and multiple IPs network using the ini file, take these 3 steps: 1.
PAGE 292
Mediant 1000 Reader's Notes H.
PAGE 293
H.323 User's Manual 10. Advanced PSTN Configuration 10 Advanced PSTN Configuration 10.1 Mediant 1000 Clock Settings The gateway can either generate its own timing signals, using an internal clock, or recover them from one of the E1/T1 trunks.
PAGE 294
Mediant 1000 Relevant parameters (described in Table 5-32 on page 152): 10.3 ISDNRxOverlap ISDNRxOverlap_x TimeBetweenDigits MaxDigits ISDNInCallsBehavior DigitMapping Using ISDN NFAS In regular (non-NFAS) T1 ISDN trunks, a single 64 kbps channel carries signaling for the other 23 B-channels of that particular T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24.
PAGE 295
H.323 User's Manual 10. Advanced PSTN Configuration 10.3.1 NFAS Interface ID Several ISDN switches require an additional configuration parameter per T1 trunk that is called ‘Interface Identifier’. In NFAS T1 trunks the Interface Identifier is sent explicitly in Q.931 Setup / Channel Identification IE for all NFAS trunks, except for the B-channels of the Primary trunk (refer to note 1 below).
PAGE 296
Mediant 1000 If there is no NFAS Backup trunk, the following configuration should be used: ISDNNFASInterfaceID_0 = 0 ISDNNFASInterfaceID_1 = 2 ISDNNFASInterfaceID_2 = 3 ISDNNFASInterfaceID_3 = 4 ISDNIBehavior = 512 ;This parameter should be added because of ;ISDNNFASInterfaceID coniguration above NFASGroupNumber_0 NFASGroupNumber_1 NFASGroupNumber_2 NFASGroupNumber_3 DchConfig_0 DchConfig_1 DchConfig_2 DchConfig_3 10.
PAGE 297
H.323 User's Manual 11. Advanced System Capabilities 11 Advanced System Capabilities 11.1 Restoring Networking Parameters to their Initial State You can use the ‘Reset’ button to restore the Mediant 1000 networking parameters to their factory default values (described in Table 4-1) and to reset the username and password. Note that the Mediant 1000 returns to the software version burned in flash. This process also restores the Mediant 1000 parameters to their factory settings.
PAGE 298
Mediant 1000 Note that after resetting the gateway, the information, shown in Figure 11-1, appears on the terminal screen. This information can be used to determine possible Mediant initialization problems, such as incorrectly defined (or undefined) local IP address, subnet mask, etc. Figure 11-1: RS-232 Status and Error Messages MAC address = 00-90-8F-01-00-9E Local IP address = 10.1.37.6 Subnet mask = 255.255.0.0 Default gateway IP address = 10.1.1.5 TFTP server IP address = 10.1.1.
PAGE 299
H.323 User's Manual 11. Advanced System Capabilities The following ini file example can be used to activate the Automatic Update mechanism. Figure 11-2: Example of an ini File Activating the Automatic Update Mechanism # DNS is required for specifying domain names in URLs DnsPriServerIP = 10.1.1.11 # Load an extra configuration ini file using HTTP IniFileURL = 'http://webserver.corp.com/AudioCodes/inifile.ini' # Load Call Progress Tones file using HTTPS CptFileUrl = 'https://10.31.2.17/usa_tones.
PAGE 300
Mediant 1000 The following example illustrates how to utilize Automatic Updates for deploying devices with minimum manual configuration. ¾ To utilize Automatic Updates for deploying the Mediant 1000 with minimum manual configuration, take these 5 steps: 1. Set up a Web server (in the following example it is http://www.corp.com/) where all configuration files are to be stored. 2. To each device, pre-configure the following parameter (DHCP / DNS are assumed): IniFileURL = 'http://www.corp.
PAGE 301
H.323 User's Manual 11.4 11. Advanced System Capabilities Startup Process The startup process (illustrated in Figure 11-3 on page 302) begins when the gateway is reset (physically or from the Web / SNMP) and ends when the operational software is running. In the startup process, the network parameters, software and configuration files are obtained. After the gateway powers up or after it is physically reset, it broadcasts a BootRequest message to the network.
PAGE 302
Mediant 1000 Figure 11-3: Mediant 1000 Startup Process Reset from the Web Interface or SNMP Physical Reset BootP x times No Response DHCP x times No Response Update network BootP Response parameters from DHCP Response BootP/DHCP reply BootP/DHCP reply contains firmware file name? No Yes Download firmware via TFTP BootP/DHCP reply contains ini file name? BootP/DHCP reply contains ini file name? No Preconfigured firmware URL? Yes Yes Download firmware via TFTP Yes No Device Reset No Pre
PAGE 303
H.323 User's Manual 11.5 11. Advanced System Capabilities Using Parameter Tables The Mediant 1000 uses parameter tables to group related parameters of specific entities and manage them together. These tables, similar to regular parameters, can be configured via the ini file, Embedded Web Server, SNMP, etc. Tables are composed of lines and columns. Columns represent parameters’ types. Lines represent specific entities. The instances in each line are called line attributes.
PAGE 304
Mediant 1000 11.5.2 Table Permissions Each column has a 'permission' attribute that is applied to all instances in the column. This permission determines if and when a field can be modified. Several permissions can be applied to each column. The following permissions are available: Read: The value of the field can be read. Write: The value of the field can be modified.
PAGE 305
H.323 User's Manual 11. Advanced System Capabilities 11.5.5 Using the ini File to Configure Parameter Tables You can use the ini file to add / modify parameter tables. When using tables, Read-Only parameters are not loaded, as they cause an error when trying to reload the loaded file. Therefore, Read-Only parameters mustn’t be included in tables in the ini file. Consequently, tables are loaded with all parameters having at least one of the following permissions: Write, Create or Maintenance Write.
PAGE 306
Mediant 1000 Refer to the following notes: Indices (in both the Format and the Data lines) must appear in the same order determined by the specific table's documentation. The Index field must never be omitted. The Format line can include a sub-set of the configurable fields in a table. In this case, all other fields are assigned with the pre-defined default values for each configured line. The order of the fields in the Format line isn’t significant (as opposed to the Indexfields).
PAGE 307
H.323 User's Manual 11.6 11. Advanced System Capabilities Customizing the Mediant 1000 Web Interface Customers incorporating the Mediant 1000 into their portfolios can customize the Web Interface to suit their specific corporate logo and product naming conventions. Customers can customize the Web Interface’s title bar (AudioCodes’ title bar is shown in Figure 11-5; a customized title bar is shown in Figure 11-7).
PAGE 308
Mediant 1000 Figure 11-7: Image Download Screen 4. Click the Browse button in the Send Logo Image File from your computer to the device box. Navigate to the folder that contains the logo image file you want to load. 5. Click the Send File button; the file is sent to the device. When loading is complete, the screen is automatically refreshed and the new logo image is displayed. 6. Note the appearance of the logo.
PAGE 309
H.323 User's Manual 11. Advanced System Capabilities Table 11-3: Customizable Logo ini File Parameters Parameter Description LogoFileName The name of the image file containing your corporate logo. Use a gif, jpg or jpeg image file. The default is AudioCodes’ logo file. Note: The length of the name of the image file is limited to 47 characters. LogoWidth Width (in pixels) of the logo image. Note: The optimal setting depends on the resolution settings.
PAGE 310
Mediant 1000 5. Click the Send File button; the file is sent to the device. When loading is complete, the screen is automatically refreshed and the new background image is displayed. 6. To save the image to flash memory so it is available after a power fail, refer to Section 5.9.2 on page 193. The new background appears on all Web Interface screens. Tip 1: If you encounter any problem during the loading of the files, or you want to restore the default images, click the Restore Default Images button.
PAGE 311
H.323 User's Manual 11. Advanced System Capabilities 11.6.4 Modifying ini File Parameters via the Web AdminPage ¾ To modify ini file parameters via the AdminPage, take these 6 steps: 1. Access the Mediant 1000 Embedded Web Server (refer to Section 5.3 on page 57). 2. In the URL field, append the suffix ‘AdminPage’ (note that it’s case-sensitive) to the IP address, e.g., http://10.1.229.17/AdminPage. 3. Click the INI Parameters option; the INI Parameters screen is displayed (shown in Figure 11-8).
PAGE 312
Mediant 1000 11.7 Software Upgrade Key Mediant 1000 gateways are supplied with a Software Upgrade Key already pre-configured for the gateway. Users can later upgrade their Mediant 1000 features, capabilities and quantity of available resources by specifying what upgrades they require, and purchasing a new key to match their specification. The Software Upgrade Key is sent as a string in a text file, to be loaded into the Mediant 1000.
PAGE 313
H.323 User's Manual 11. Advanced System Capabilities 11.7.3 Loading the Software Upgrade Key Using the Embedded Web Server ¾ To load a Software Upgrade Key using the Web Server, take these 6 steps: 1. 2. 3. Access the devices Embedded Web Server (refer to Section 5.3 on page 57). Click the Software Update button. Click the Software Upgrade Key tab; the Software Upgrade Key screen is displayed (shown in Figure 11-9). Figure 11-9: Software Upgrade Key Screen 4. 5. Version 5.
PAGE 314
Mediant 1000 6. After verifying that the Software Upgrade Key was successfully loaded, reset the device; the new capabilities and resources are active. Figure 11-10: Example of a Software Upgrade Key File Containing Multiple S/N Lines 11.7.4 Loading the Software Upgrade Key using BootP/TFTP ¾ To load the Software Upgrade Key file using BootP/TFTP, take these 5 steps: 1. 2. 3. 4. 5. Place the file in the same location you’ve saved the device’s cmp file.
PAGE 315
H.323 User's Manual 11. Advanced System Capabilities 11.7.6 Troubleshooting an Unsuccessful Loading of a Key If the Syslog server indicates that a Software Upgrade Key file was unsuccessfully loaded (the SN_ line is blank), take the following preliminary actions to troubleshoot the issue: Open the Software Upgrade Key file and check that the S/N line of the specific device whose key you want to update is listed in it. If it isn’t, contact AudioCodes.
PAGE 316
Mediant 1000 Reader's Notes H.
PAGE 317
H.323 User's Manual 12. Special Applications 12 Special Applications 12.1 Metering Tones Relay The Mediant 1000 FXS and FXO modules can be used to relay standard 12 or 16 kHz metering tones over the IP network as illustrated in Figure 12-1 below. Figure 12-1: Metering Tone Relay Architecture After a call is established between the FXS and FXO modules, the PSTN generates 12 or 16 kHz metering tones towards the FXO module.
PAGE 318
Mediant 1000 12.2 TDM Tunneling The Mediant 1000 TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network.
PAGE 319
H.323 User's Manual 12. Special Applications Figure 12-2: ini File Example for TDM Tunneling (Originating Side) EnableTDMOverIP = 1 ;E1_TRANSPARENT_31 ProtocolType_0 = 5 ProtocolType_1 = 5 ProtocolType_2 = 5 ProtocolType_3 = 5 prefix = '*,10.8.24.
PAGE 320
Mediant 1000 Reader's Notes H.
PAGE 321
H.323 User's Manual 13 13. Security Security This section describes the security mechanisms and protocols implemented on the Mediant 1000. The following list specifies the available security protocols and their objectives: 13.1 IPSec and IKE protocols are part of the IETF standards for establishing a secured IP connection between two applications. IPSec and IKE are used in conjunction to provide security for control and management protocols but not for media (refer to Section 13.1 below).
PAGE 322
Mediant 1000 13.1.1 IKE IKE is used to obtain the Security Associations (SA) between peers (the gateway and the application it’s trying to contact). The SA contains the encryption keys and profile used by the IPSec to encrypt the IP stream. The IKE table lists the IKE peers with which the gateway performs the IKE negotiation (up to 20 peers are available). The IKE negotiation is separated into two phases: main mode and quick mode.
PAGE 323
H.323 User's Manual 13. Security IPSec Specifications: Transport mode only Encapsulation Security Payload (ESP) only Support for Cipher Block Chaining (CBC) Supported IPSec SA encryption algorithms: DES, 3DES, and AES Hash types for IPSec SA include SHA1 and MD5 13.1.3 Configuring IPSec and IKE To enable IPSec and IKE on the gateway set the ini file parameter ‘EnableIPSec’ to 1. 13.1.3.
PAGE 324
Mediant 1000 Table 13-1: IKE Table Configuration Parameters (continues on pages 323 to 324) Parameter Name Description Authentication Method Determines the authentication method for IKE. [IkePolicyAuthenticationMeth The valid authentication method values include: od] 0 = Pre-shared Key (default) 1 = RSA Signiture Note 1: For pre-shared key based authentication, peers participating in an IKE exchange must have a prior (out-of-band) knowledge of the common key (see IKEPolicySharedKey parameter).
PAGE 325
H.323 User's Manual 13.
PAGE 326
Mediant 1000 4. Configure the IKE parameters according to Table 13-1 on page 323. 5. Click the button Create; a row is create in the IKE table 6. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 193. To delete a peer from the IKE table, select it in the ‘Policy Index’ drop-down list, click the button Delete and click OK at the prompt. 13.1.3.2 IPSec Configuration The parameters described in the table below are used to configure the SPD table.
PAGE 327
H.323 User's Manual 13. Security Table 13-3: SPD Table Configuration Parameters Parameter Name Description First to Fourth Proposal Encryption Type [IPSecPolicyProposalEncrypt ion_X] Determines the encryption type used in the quick mode negotiation for up to four proposals. X stands for the proposal number (0 to 3).
PAGE 328
Mediant 1000 In the SPD example, all packets designated to IP address 10.11.2.21 that originates from the OAM interface (regardless to their destination and source ports) and whose protocol is UDP are encrypted, the SPD also defines an SA lifetime of 900 seconds and two security proposals: DES/SHA1 and 3DES/SHA1. ¾ To configure the SPD table using the Embedded Web Server, take these 6 steps: 1. Access the Embedded Web Server (refer to Section 5.3 on page 57). 2.
PAGE 329
H.323 User's Manual 13. Security 13.1.3.3 IPSec and IKE Configuration Table’s Confidentiality Since the pre-shared key parameter of the IKE table must remain undisclosed, measures are taken by the ini file, Embedded Web Server and SNMP agent to maintain this parameter’s confidentiality. On the Embedded Web Server a list of asterisks is displayed instead of the pre-shared key. On SNMP, the pre-shared key parameter is a write-only parameter and cannot be read.
PAGE 330
Mediant 1000 13.2 SSL/TLS SSL, also known as TLS, is the method used to secure the Mediant 1000 Embedded Web Server and Telnet server. The SSL protocol provides confidentiality, integrity and authenticity between two communicating applications over TCP/IP. Specifications for the SSL/TLS implementation include the following: Supports transports: SSL 2.0, SSL 3.0, TLS 1.0 Supports ciphers: DES, RC4 compatible Authentication: X.509 certificates; CRLs are not supported 13.2.
PAGE 331
H.323 User's Manual 13. Security If the Telnet server is set to SSL mode, a special Telnet client is required on your PC to connect to the Telnet interface over a secured connection; examples include C-Kermit for UNIX, Kermit-95 for Windows, and AudioCodes' acSSLTelnet utility for Windows (that requires prior installation of the free OpenSSL toolkit). Contact AudioCodes to obtain the acSSLTelnet utility. 13.2.
PAGE 332
Mediant 1000 4. Copy this text and send it to your security provider; the security provider (also known as Certification Authority or CA) signs this request and send you a server certificate for the device. 5. Save the certificate in a file (e.g., cert.txt). Ensure the file is a plain-text file with the ‘BEGIN CERTIFICATE’ header. The figure below is an example of a Base64-Encoded X.509 Certificate. Figure 13-10: Example of a Base64-Encoded X.
PAGE 333
H.323 User's Manual 13. Security ¾ To install a client certificate, take these 6 steps: 1. Before continuing, set HTTPSOnly = 0 to ensure you have a method of accessing the device in case the client certificate doesn’t work. Restore the previous setting after testing the configuration. 2. Open the ‘Certificates’ screen (Advanced Configuration menu > Security Settings submenu > Certificates option); the ‘Certificates’ screen is displayed (Figure 13-9). 3.
PAGE 334
Mediant 1000 13.3 RADIUS Login Authentication Users can enhance the security and capabilities of logging to the gateway’s Web and Telnet embedded servers by using a Remote Authentication Dial-In User Service (RADIUS) to store numerous usernames, passwords and access level attributes (Web only), allowing multiple user management on a centralized platform.
PAGE 335
H.323 User's Manual 2. 13. Security If access levels are required, set up a VSA dictionary for the RADIUS server and select an attribute ID that represents each user's access level. The following example shows a dictionary file for FreeRADIUS that defines the attribute ‘ACL-Auth-Level’ with ID=35.
PAGE 336
Mediant 1000 6. Under section ‘RADIUS Authentication Settings’, in the field ‘Device Behavior Upon RADIUS Timeout’, select the gateway’s operation if a response isn’t received from the RADIUS server after the 5 seconds timeout expires: • • Deny Access – the gateway denies access to the Web and Telnet embedded servers. Verify Access Locally – the gateway checks the local username and password. 7.
PAGE 337
H.323 User's Manual 13.4 13. Security Internal Firewall The Mediant 1000 accommodates an internal access list facility, allowing the security administrator to define network traffic filtering rules.
PAGE 338
Mediant 1000 Figure 13-15 shows an advanced example of an access list definition via ini file: Figure 13-15: Advanced Example of an Access List Definition via ini File [ ACCESSLIST ] FORMAT AccessList_Index = AccessList_Source_IP, AccessList_Net_Mask, AccessList_Start_Port, AccessList_End_Port, AccessList_Protocol, AccessList_Packet_Size, AccessList_Byte_Rate, AccessList_Byte_Burst, AccessList_Allow_Type; AccessList 10 = 10.0.0.0, 255.0.0.0, 0, 65535, any, 0, 40000, 50000, allow ; AccessList 15 = 10.31.4.
PAGE 339
H.323 User's Manual 13.5 13. Security Network Port Usage The following table lists the default TCP/UDP network port numbers used by the Mediant 1000. Where relevant, the table lists the ini file parameters that control the port usage and provide source IP address filtering capabilities. Table 13-5: Default TCP/UDP Network Port Numbers Port Number Peer Port Application Notes 2 2 Debugging interface Always ignored 23 - Telnet Disabled by default (TelnetServerEnable).
PAGE 340
Mediant 1000 13.6 Recommended Practices To improve network security, the following guidelines are recommended when configuring the Mediant 1000: 13.7 Set the password of the primary web user account (refer to 5.6.7.1 on page 162) to a unique, hard-to-hack string. Do not use the same password for several devices as a single compromise may lead to others. Keep this password safe at all times and change it frequently. If possible, use a RADIUS server for authentication.
PAGE 341
H.323 User's Manual 14 14. Diagnostics Diagnostics Several diagnostic tools are provided, enabling you to identify correct functioning of the Mediant 1000, or an error condition with a probable cause and a solution or workaround. 14.1 Front and rear-panel LEDs on the Mediant 1000. The location and functionality of the Mediant 1000 front panel LEDs is shown in Section 2.1.5 on page 31. Self-Testing on hardware initialization (refer to Section 14.1 below). Line testing (refer to Section 14.
PAGE 342
Mediant 1000 14.2 Mediant 1000 Line Testing The Mediant 1000 features a mechanism that performs tests on the telephone lines connected to FXS and FXO ports. These tests provide various line measurements. Line testing is executed via SNMP only (using the acAnalogFxoLineTestTable SNMP table for FXO and the acAnalogFxsLineTestTable SNMP table for FXS). Note: The line testing mechanism must only be used for monitoring and never when there are calls in progress.
PAGE 343
H.323 User's Manual 14. Diagnostics 14.3.1 Syslog Servers Users can use the provided Syslog server (ACSyslog) or other third-party Syslog servers. Examples of Syslog servers available as shareware on the Internet: Kiwi Enterprises: http://www.kiwisyslog.com/ The US CMS Server: http://uscms.fnal.gov/hanlon/uscms_server/ TriAction Software: http://www.triaction.nl/Products/SyslogDaemon.asp Netal SL4NT 2.1 Syslog Daemon: http://www.netal.
PAGE 344
Mediant 1000 Reader's Notes H.
PAGE 345
H.323 User's Manual 15 15. SNMP-Based Management SNMP-Based Management Simple Network Management Protocol (SNMP) is a standards-based network control protocol for managing elements in a network. The SNMP Manager (usually implemented by a Network Management System (NMS) or an Element Management System (EMS)) connects to an SNMP Agent (embedded on a remote Network Element (NE)) to perform network element Operation, Administration and Maintenance (OAM).
PAGE 346
Mediant 1000 Set Request: The SNMP standard provides a method of effecting an action associated with a device (via the ‘set’ request) to accomplish activities such as disabling interfaces, disconnecting users, clearing registers, etc. This provides a way of configuring and controlling network devices via SNMP.
PAGE 347
H.323 User's Manual 15. SNMP-Based Management Typically, when a MIB is compiled into the system, the manager creates new folders or directories that correspond to the objects. These folders or directories can typically be viewed with a MIB Browser, which is a traditional SNMP management tool incorporated into virtually all Network Management Systems.
PAGE 348
Mediant 1000 15.3 Cold Start Trap Mediant 1000 technology supports a cold start trap to indicate that the device is starting. This allows the manager to synchronize its view of the device's active alarms. Two different traps are sent at start-up: 15.4 The standard coldStart trap - iso(1).org(3).dod(6).internet(1). snmpV2(6). snmpModules(3). snmpMIB(1). snmpMIBObjects(1). snmpTraps(5). coldStart(1) - sent at system initialization.
PAGE 349
H.323 User's Manual 15. SNMP-Based Management • acPMPSTN: for PSTN related monitoring such as channel use, trunk utilization. Note that the acPMTrunkUtilizationTable is not supported. • acPMSystem: for general (system related) monitoring. • The log trap, acPerformanceMonitoringThresholdCrossing (non-alarm) is sent every time the threshold of a Performance Monitored object is crossed.
PAGE 350
Mediant 1000 RTCP-XR: This MIB (RFC) implements the following partial support: • • • The rtcpXrCallQualityTable is fully supported. In the rtcpXrHistoryTable, support of the RCQ objects is provided only with no more than 3 intervals, 15 minutes long each. Supports the rtcpXrVoipThresholdViolation trap.
PAGE 351
H.323 User's Manual 15. SNMP-Based Management acAlarm: This is AudioCodes' proprietary carrier-grade alarm MIB. It is a simpler implementation of the notificationLogMIB and the IETF suggested alarmMIB (both also supported in all AudioCodes’ devices). The acAlarm MIB has the following groups: • ActiveAlarm: straightforward (single-indexed) table, listing all currently active alarms, together with their bindings (the alarm bindings are defined in acAlarm. acAlarmVarbinds and also in acBoard.acTrap.
PAGE 352
Mediant 1000 15.6 Traps Note: All traps are sent from the SNMP port (default 161). This is part of the NAT traversal solution. Full proprietary trap definitions and trap Varbinds are found in the acBoard MIB and acAlarm MIB. Table 15-1 lists the supported proprietary traps. For detailed information on these traps, refer to Appendix F on page 411. Table 15-1: Proprietary Traps Description (continues on pages 352 to 353) Trap Description acBoardFatalError Sent whenever a fatal device error occurs.
PAGE 353
H.323 User's Manual 15. SNMP-Based Management Table 15-1: Proprietary Traps Description (continues on pages 352 to 353) Trap Description acHTTPDownloadResult Sent at the success or failure of HTTP download. acDChannelStatus Non-alarm trap sent at the establishment, re-establishment, or release of LAPD link with its peer connection.
PAGE 354
Mediant 1000 15.7.1 SNMP Community Names By default, the device uses a single, read-only community string of ‘public’ and a single read-write community string of ‘private’.
PAGE 355
H.323 User's Manual 15. SNMP-Based Management ¾ To add a read-write community string (v2admin), take these 2 steps: 1. Add a new row to the snmpCommunityTable with CommunityName v2admin. 2. Add a row to the vacmSecurityToGroupTable for SecurityName v2admin, GroupName ReadWriteGroup and SecurityModel snmpv2c. ¾ To delete the read-write community string (v2admin), take these 2 steps: 1. If v2admin is being used as the trap community string, follow the procedure for changing the trap community string.
PAGE 356
Mediant 1000 15.7.2 SNMP v3 USM Users You can define up to 10 User-based Security Model (USM) users (USM users are referred to as “v3 users”). Each v3 user can be associated with an authentication type (none, MD5, or SHA-1) and a privacy type (none, DES, 3DES, or AES).
PAGE 357
H.323 User's Manual 15. SNMP-Based Management 15.7.2.1 Configuring SNMP v3 users via the ini File Use the SNMPUsers ini table to add, modify, and delete SNMPv3 users. For a description of the SNMPUsers table ini file parameters, refer to Section 6.5.6 on page 225. Note: The SNMPUsers ini table is a hidden parameter. Therefore, when you perform a “Get ini File” operation using the Web interface, the table will not be included in the generated file.
PAGE 358
Mediant 1000 ¾ To delete the read-only, noAuthNoPriv SNMPv3 user (v3user), take these 3 steps: 1. If v3 user is associated with a trap destination, follow the procedure for associating a different user to that trap destination. (See below.) 2. Delete the vacmSecurityToGroupTable row for SecurityName v3user, GroupName ReadGroup1, and SecurityModel usm. 3. Delete the row in the usmUserTable for v3user. ¾ To add a read-write, authPriv SNMPv3 user (v3user), take these 4 steps: 1.
PAGE 359
H.323 User's Manual 15. SNMP-Based Management 15.7.3 Trusted Managers By default, the agent accepts ‘get’ and ‘set’ requests from any IP address, as long as the correct community string is used in the request. Security can be enhanced via the use of Trusted Managers. A Trusted Manager is an IP address from which the SNMP Agent accepts and processes ‘get’ and ‘set’ requests. An EM can be used to configure up to five Trusted Managers.
PAGE 360
Mediant 1000 The following procedure assumes that there is at least one configured read-write community, are currently one or more Trusted Managers, and the TransportTag for columns for all rows in the snmpCommunityTable are currently set to MGR. This procedure must be done from one of the existing Trusted Managers. ¾ To add a subsequent Trusted Manager, take these 2 steps: 1.
PAGE 361
H.323 User's Manual 15. SNMP-Based Management 15.7.5 Multiple SNMP Trap Destinations An agent can send traps to up to five managers. For each manager, set the manager’s IP address, receiving port number, and enable sending traps to that manager. The user also has the option of associating a trap destination with a specific SNMPv3 USM user. Traps are then sent to that trap destination using the SNMPv3 format and the authentication and privacy protocol configured for that user..
PAGE 362
Mediant 1000 Figure 15-1: Example of Entries in a Device ini file Regarding SNMP ; SNMP trap destinations ; The board maintains a table of trap destinations containing 5 ;rows. The rows are numbered 0..4. Each block of 4 items below ;apply to a row in the table. ; To configure one of the rows, uncomment all 4 lines in that ;block. Supply an IP address and if necessary, change the port ;number. ; To delete a trap destination, set ISUSED to 0.
PAGE 363
H.323 User's Manual 15. SNMP-Based Management ¾ To add an SNMPv2 trap destination, take this step: Add a row to the snmpTargetAddrTable with these values: • Name=trapN (where N is an unused number between 0 and 4) • TagList=AC_TRAP • Params=v2cparams All changes to the trap destination configuration take effect immediately. ¾ To add an SNMPv3 trap destination, take these 2 steps: 1. 2.
PAGE 364
Mediant 1000 15.8 SNMP Manager Backward Compatibility With support for the Multi Manager Trapping feature, the older acSNMPManagerIP MIB object, which is synchronized with the first index in the snmpManagers MIB table is also supported. This is translated in two features: 15.9 SET/GET to either of the two MIB objects is identical. In other words, as far as the SET/GET are concerned, OID 1.3.6.1.4.1.5003.9.10.1.1.2.7 is identical to OID 1.3.6.1.4.1.5003.9.10.1.1.2.21.1.1.3.
PAGE 365
H.323 User's Manual 15. SNMP-Based Management The manger also has access to the STUN client configuration: audioCodes(5003).acProducts(9).acBoardMibs(10).acSystem(10).acSystemConfigura tion(1).acSysNetworkConfig(3).acSysNATTraversal(6).acSysSTUN(21). acNATTraversalAlarm: When the NAT is placed in front a device that is identified as a symmetric NAT, this alarm is raised. It is cleared when a non-symmetric NAT or no NAT replace the symmetric one. 15.11 SNMP Administrative State Control 15.11.
PAGE 366
Mediant 1000 15.12 AudioCodes’ Element Management System Using AudioCodes’ Element Management System (EMS) is recommended to Customers requiring large deployments (multiple media gateways in globally distributed enterprise offices, for example), that need to be managed by central personnel. The EMS is not included in the device’s supplied package. Contact AudioCodes for detailed information on AudioCodes’ EMS and on AudioCodes’ EVN - Enterprise VoIP Network – solution for large VoIP deployments. H.
PAGE 367
H.323 User's Manual 16 16. Configuration Files Configuration Files This section describes the configuration dat files that are loaded (in addition to the ini file) to the gateway. The configuration files include the following: Call Progress Tones file (refer to Section 16.1 on page 367) Prerecorded Tones file (refer to Section 16.2 on page 371) CAS protocol configuration files (refer to Section 16.3 on page 372) FXS/FXO Coefficient file (refer to Section 16.
PAGE 368
Mediant 1000 Cadence: A repeating sequence of on and off sounds. Up to four different sets of on / off periods can be specified. Burst: A single sound followed by silence. Only the ‘First Signal On time’ and ‘First Signal Off time’ should be specified. All other on and off periods must be set to zero. The burst tone is detected after the off time is completed. Users can specify several tones of the same type. These additional tones are used only for tone detection.
PAGE 369
H.323 User's Manual 16. Configuration Files • Second Signal Off Time [10 msec]: ‘Signal Off’ period (in 10 msec units) for the second cadence on-off cycle. Can be omitted if there isn’t a second cadence. • Third Signal On Time [10 msec]: ‘Signal On’ period (in 10 msec units) for the third cadence ON-OFF cycle. Can be omitted if there isn’t a third cadence. • Third Signal Off Time [10 msec]: ‘Signal Off’ period (in 10 msec units) for the third cadence ON-OFF cycle.
PAGE 370
Mediant 1000 16.1.2 Format of the Distinctive Ringing Section in the ini File Distinctive Ringing is only applicable to Mediant 1000/FXS modules. Using the distinctive ringing section of this configuration file, the user can create up to 16 distinctive ringing patterns. Each ringing pattern configures the ringing tone frequency and up to 4 ringing cadences. The same ringing frequency is used for all the ringing pattern cadences.
PAGE 371
H.323 User's Manual 16. Configuration Files 16.1.2.
PAGE 372
Mediant 1000 16.2.1 PRT File Format The PRT dat file contains a set of prerecorded tones to be played by the Mediant 1000 during operation. Up to 40 tones (totaling approximately one minute) can be stored in a single file in flash memory. The prerecorded tones (raw data PCM or L8 files) are prepared offline using standard recording utilities (such as CoolEditTM) and combined into a single file using the TrunkPack Downloadable Conversion utility (refer to Section E.1.4 on page 399).
PAGE 373
H.323 User's Manual 16. Configuration Files Hybrid balance Frequency response in transmit and receive direction Hook thresholds Ringing generation and detection parameters This means, for example, that changing impedance matching or hybrid balance doesn’t require hardware modifications, so that a single device is able to meet requirements for different markets.
PAGE 374
Mediant 1000 Reader's Notes H.
PAGE 375
H.323 User's Manual A A. Selected Technical Specifications Selected Technical Specifications Table A-1: Mediant 1000 Functional Specifications (continues on pages 375 to 377) 3 Modularity and Capacity Six slots for analog modules.Up to 24 FXS/FXO analog ports. Up to four digital trunks (fully flexible, from a single and up to four trunks per module) Interface I/O Modules FXS Telephony Interface Up to 6 modules with 4 FXS RJ-11 ports on each module (for a total of up to 24 analog FXS RJ-11 ports).
PAGE 376
Mediant 1000 Table A-1: Mediant 1000 Functional Specifications (continues on pages 375 to 377) Voice & Tone Characteristics Voice Compression G.711 PCM at 64 kbps µ-law/A-law (10, 20, 30, 40, 50, 60, 80, 100, 120 msec) G.723.1 MP-MLQ at 5.3 or 6.3 kbps (30, 60, 90 msec) G.726 at 32 kbps ADPCM (10, 20, 30, 40, 50, 60, 80, 100, 120 msec) G.729 CS-ACELP 8 Kbps Annex A / B (10, 20, 30, 40, 50, 60 msec) NetCoder at 6.4, 7.2, 8.0 and 8.8 kbps (20, 40, 60, 80, 100, 120 msec).
PAGE 377
H.323 User's Manual A. Selected Technical Specifications Table A-1: Mediant 1000 Functional Specifications (continues on pages 375 to 377) CPU Network Interface Two Ethernet RJ-45 connectors, 10/100 Base-TX RS-232 Interface RS-232 terminal interface. Non-standard RS-232 connector on the device’s CPU. Reset Resets the device. Dry Contact NB (Night Bell) and paging Audio I/O MOH (Music on Hold) and paging Physical Dimensions 19” (width) by 1U (height) by 13.
PAGE 378
Mediant 1000 Reader's Notes H.
PAGE 379
H.323 User's Manual B B. Supplied H.323 Software Kit Supplied H.323 Software Kit The table below describes the standard supplied software kit for Mediant 1000. The supplied documentation includes this User’s Manual, the Mediant 1000 Analog & Digital Fast Track Guide and the Mediant 1000 H.323 Release Notes. Table B-1: Supplied Software Kit File Name Description Ram.cmp file Mediant_H323_xxx.cmp Image file containing the software for both FXS and FXO modules. M1000_Digital_H323_xxx.
PAGE 380
Mediant 1000 Reader’s Notes H.
PAGE 381
H.323 User's Manual C C. BootP/TFTP Configuration Utility BootP/TFTP Configuration Utility The BootP/TFTP utility enables you to easily configure and provision our boards and media gateways. Similar to third-party BootP/TFTP utilities (which are also supported) but with added functionality; our BootP/TFTP utility can be installed on Windows™ 98 or Windows™ NT/2000/XP. The BootP/TFTP utility enables remote reset of the device to trigger the initialization procedure (BootP and TFTP).
PAGE 382
Mediant 1000 C.4 C.5 Unicast BootP response. User-initiated BootP respond, for remote provisioning over WAN. Filtered display of BootP requests. Location of other BootP utilities that contain the same MAC entity. Common log window for both BootP and TFTP sessions. Works with Windows™ 98, Windows™ NT, Windows™ 2000 and Windows™ XP.
PAGE 383
H.323 User's Manual C.7 C. BootP/TFTP Configuration Utility BootP/TFTP Application User Interface Figure C-1 shows the main application screen for the BootP/TFTP utility. Figure C-1: Main Screen Log Window C.8 Function Buttons on the Main Screen Pause: Click this button to pause the BootP Tool so that no replies are sent to BootP requests. Click the button again to restart the BootP Tool so that it responds to all BootP requests.
PAGE 384
Mediant 1000 Figure C-2: Reset Screen When a gateway resets, it first sends a BootRequest. Therefore, Reset can be used to force a BootP session with a gateway without needing to power cycle the gateway. As with any BootP session, the computer running the BootP Tool must be located on the same subnet as the controlled VoIP gateway. C.9 Log Window The log window (refer to Figure C-1 on the previous page) records all BootP request and BootP reply transactions, as well as TFTP transactions.
PAGE 385
H.323 User's Manual C. BootP/TFTP Configuration Utility Use right-click on a line in the Log Window to open a pop-up window with the following options: Reset: Selecting this option results in a reset command being sent to the client VoIP gateway. The program searches its database for the MAC address indicated in the line. If the client is found in that database, the program adds the client MAC address to the Address Resolution Protocol (ARP) table for the computer.
PAGE 386
Mediant 1000 C.10.1 BootP Preferences ARP is a common acronym for Address Resolution Protocol, and is the method used by all Internet devices to determine the link layer address, such as the Ethernet MAC address, in order to route Datagrams to devices that are on the same subnet. When ARP Manipulation is enabled on this screen, the BootP Tool creates an ARP cache entry on your computer when it receives a BootP BootRequest from the VoIP gateway.
PAGE 387
H.323 User's Manual C. BootP/TFTP Configuration Utility Timeout: This specifies the number of seconds that the TFTP utility waits before retransmitting TFTP messages. This can be left at the default value of 5 (the more congested your network, the higher the value you should define in these fields). Maximum Retransmissions: This specifies the number of times that the TFTP utility tries to resend messages after timing out.
PAGE 388
Mediant 1000 3. Click Apply to save this entry to the list of clients, or click Apply & Reset to save this entry to the list of clients and send a reset message to that gateway to immediately implement the settings. Note: To use Apply & Reset you must enable ARP Manipulation in the Preferences window. Also, you must have administrator privileges for the computer you are using. An easy way to create several clients that use similar settings is to create a template.
PAGE 389
H.323 User's Manual C. BootP/TFTP Configuration Utility C.11.4 Testing the Client There should only be one BootP utility supporting any particular client MAC active on the network at any time. ¾ To check if other BootP utilities support this client, take these 4 steps: 1. Select the client that you wish to test by clicking on the client name in the main area of the Client Configuration Window. 2. Click the Test Selected Client button 3. Examine the Log Window on the Main Application Screen.
PAGE 390
Mediant 1000 Boot File: This field specifies the file name for the software (cmp) file that is loaded by the TFTP utility to the VoIP gateway after the VoIP gateway receives the BootReply message. The actual software file is located in the TFTP utility directory that is specified in the BootP Preferences window. The software file can be followed by command line switches. For information on available command line switches, refer to Section C.11.6 on page 390.
PAGE 391
H.323 User's Manual C. BootP/TFTP Configuration Utility Table C-1: Command Line Switch Descriptions Switch -fb -em # -br Description Burn ram.cmp in flash (only for cmp files) Use this switch to set Ethernet mode. 0 = 10 Base-T half-duplex 1 = 10 Base-T full-duplex 2 = 100 Base-TX half-duplex 3 = 100 Base-TX full-duplex 4 = auto-negotiate (default) For detailed information on Ethernet interface configuration, refer to Section 9.1 on page 279.
PAGE 392
Mediant 1000 C.12 Managing Client Templates Templates can be used to simplify configuration of clients when most of the parameters are the same. Figure C-5: Templates Screen ¾ To create a new template, take these 4 steps: 1. Click the Add New Template button 2. Fill in the default parameter values in the parameter fields. 3. Click Apply to save this new template. 4. Click OK when you are finished adding templates. ¾ To edit an existing template, take these 4 steps: 1.
PAGE 393
H.323 User's Manual D D. RTP/RTCP Payload Types and Port Allocation RTP/RTCP Payload Types and Port Allocation RTP Payload Types are defined in RFC 3550 and RFC 3551. We have added new payload types to enable advanced use of other coder types. These types are reportedly not used by other applications. D.1 Packet Types Defined in RFC 3551 Table D-1: Packet Types Defined in RFC 3551 D.2 Payload Type Description Basic Packet Rate [msec] 0 2 4 8 18 200 G.711 µ-Law G.726-32 G.723 (6.3/5.3 kbps) G.
PAGE 394
Mediant 1000 D.3 Default RTP/RTCP/T.38 Port Allocation The following table shows the default RTP/RTCP/T.38 port allocation. Channel Number 1 2 3 4 5 6 7 8 : n : 96 : 120 RTP Port 4000 4010 4020 4030 4040 4050 4060 4070 : 4000 + 10(n-1) : 4950 : 5190 RTCP Port 4001 4011 4021 4031 4041 4051 4061 4071 : 4001 + 10(n-1) : 4951 : 5191 T.38 Port 4002 4012 4022 4032 4042 4052 4062 4072 : 4002 + 10(n-1) : 4952 : 5192 Note: To configure the gateway to use the same port for both RTP and T.
PAGE 395
H.323 User's Manual E E. Accessory Programs and Tools Accessory Programs and Tools The accessory applications and tools shipped with the device provide you with friendly interfaces that enhance device usability and smooth your transition to the new VoIP infrastructure. The following applications are available: E.1 TrunkPack Downloadable Conversion Utility (refer to Section E.1 below). Call Progress Tones Wizard (refer to Section E.2 on page 401). PSTN Trace Utility (refer to Section E.
PAGE 396
Mediant 1000 E.1.1 Converting a CPT ini File to a Binary dat File For detailed information on creating a CPT ini file, refer to Section 16.1 on page 367. ¾ To convert a CPT ini file to a binary dat file, take these 10 steps: 1. Execute the TrunkPack Downloadable Conversion Utility, DConvert.exe (supplied with the software package); the utility’s main screen opens (shown in Figure E-1). 2.
PAGE 397
H.323 User's Manual E.1.2 E. Accessory Programs and Tools Creating a loadable CAS Protocol Table File ¾ To create a loadable CAS protocol table file take the next 11 steps: 1. Construct the CAS protocol files (xxx.txt and UserProt_defines_xxx.h). 2. Copy the files generated in the previous step to the same directory the TrunkPack Downloadable Conversion utility is located and ensure that the files CASSetup.h and cpp.exe are also located in the same directory. 3.
PAGE 398
Mediant 1000 9. To create a file (for troubleshooting purposes) that contains the name of the States and their actual values: Check the Output state names to file checkbox; the default file name TableStateNames.txt appears in the adjacent field (you can modify the name of the file). The generated file is to be located in the same directory as the TrunkPack Downloadable Conversion utility. 10. Uncheck the Force old table header checkbox. 11.
PAGE 399
H.323 User's Manual E. Accessory Programs and Tools ¾ To decode an encoded ini file, take these 4 steps: 1. Click the Select File… button under the ‘Decode ini File(s)’ section. 2. Navigate to the folder that contains the file you want to decode. 3. Click the file and click the Open button. the name and path of both the encode ini file and the output decoded file appear in the fields under the Select File button. Note that the name of the output file can be modified. 4.
PAGE 400
Mediant 1000 Figure E-5: Prerecorded Tones Screen 4. 5. To add the prerecorded tone files (you created in Step 1) to the ‘Prerecorded Tones’ screen follow one of these procedures: • Select the files and drag them to the ‘Prerecorded Tones’ screen. • Click the Add File(s) button; the ‘Select Files’ screen opens. Select the required Prerecorded Tone files and click the Add>> button. Close the ‘Select Files’ screen.
PAGE 401
H.323 User's Manual E. Accessory Programs and Tools • In the ’Default’ field, enter the default duration this raw data file is repeatedly played. • Close the ‘File Data’ window (press the Esc key to cancel your changes); you are returned to the Prerecorded Tones File(s) screen. Figure E-6: File Data Window E.2 6. In the ‘Output’ field, specify the output directory in which the PRT file is generated followed by the name of the PRT file (the default name is prerecordedtones.dat).
PAGE 402
Mediant 1000 E.2.3 Initial Settings ¾ To start the CPTWizard, take these 5 steps: 1. Execute the CPTWizard.exe file; the wizard’s initial settings screen is displayed. Figure E-7: Initial Settings Screen 2. Enter the IP address of the Mediant 1000/FXO module you are using. 3. Select the gateway’s ports that are connected to your PBX, and specify the phone number of each extension. 4. In the Invalid phone number field, enter a number that generates a ‘fast busy’ tone when dialed.
PAGE 403
H.323 User's Manual E.2.4 E. Accessory Programs and Tools Recording Screen – Automatic Mode After the connection to the Mediant 1000/FXO module is established, the recording screen is displayed. Figure E-8: Recording Screen –Automatic Mode ¾ To start recording in automatic mode, take these 3 steps: 1. Click the Start Automatic Configuration button; the wizard starts the following Call Progress Tones detection sequence (the operation takes approximately 60 seconds to complete): a. b. c. d. 2.
PAGE 404
Mediant 1000 Figure E-9: Recording Screen after Automatic Detection 3. All four Call Progress Tones are saved (as standard A-law PCM at 8000 bits per sample) in the same directory as the CPTWizard.exe file is located, with the following names: • cpt_recorded_dialtone.pcm • cpt_recorded_busytone.pcm • cpt_recorded_ringtone.pcm • cpt_recorded_invalidtone.
PAGE 405
H.323 User's Manual E.2.5 E. Accessory Programs and Tools Recording Screen – Manual Mode In manual mode you can record and analyze tones, included in the Call Progress Tones ini file, in addition to those tones analyzed when in automatic mode. ¾ To start recording in manual mode, take these 6 steps: 1. Click the Manual tab at the top of the recording screen, the manual recording screen is displayed. Figure E-10: Recording Screen - Manual Mode 2.
PAGE 406
Mediant 1000 E.2.6 The Call Progress Tones ini File After the Call Progress Tones detection is complete, a text file named call_progress_tones.ini is created in the same directory as the directory in which the CPTWizard.exe is located. This file contains: Information about each tone that was recorded and analyzed by the wizard. This information includes frequencies and cadence (on/off) times, and is required for using this file with the TrunkPack Downloadable Conversion utility.
PAGE 407
H.323 User's Manual E. Accessory Programs and Tools Information related to matches of all tones recorded with the CPTWizard’s internal database. The database is scanned to find one or more PBX definitions that match all recorded tones (i.e., dial tone, busy tone, ringing tone, reorder tone and any other manually-recorded tone – all match the definitions of the PBX). If a match is found, the entire PBX definition is reported (as comments) in the ini file using the same format.
PAGE 408
Mediant 1000 9. In the Call Progress Tones file, add a new Reorder Tone with the attributes you found in the previous step. Ensure that you update the numbers of the successive tones and the total number of tones in the beginning of the file. 10. Create a Call Progress Tones.dat file using the DConvert Utility (refer to Section E.1 on page 395). 11. Load the new file to the gateway, and then reset the gateway. E.
PAGE 409
H.323 User's Manual 9. E. Accessory Programs and Tools Determine the UDP port (the same as in step 3). 10. Click the Submit button => the board starts to send the trace messages. In the UDP2File utility (Refer to Figure E-15) you should see the number in the packets counter increasing. Figure E-14: Trunk Traces Figure E-15: UDP2File Utility Version 5.
PAGE 410
Mediant 1000 Reader's Notes H.
PAGE 411
H.323 User's Manual F F. SNMP Traps SNMP Traps This section provides information on proprietary SNMP traps currently supported by the gateway. There is a separation between traps that are alarms and traps that are not (logs). Currently all have the same structure made up of the same 11 varbinds (Variable Binding) (1.3.6.1.4.1.5003.9.10.1.21.1). The source varbind is composed of a string that details the component from which the trap is being sent (forwarded by the hierarchy in which it resides).
PAGE 412
Mediant 1000 Table F-2: acBoardConfigurationError Alarm Trap Alarm: acBoardConfigurationError OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.2 Default Severity Critical Event Type: equipmentAlarm Probable Cause: underlyingResourceUnavailable (56) Alarm Text: Board Config Error: Status Changes: Condition: A configuration error was detected Alarm status: critical value: A run-time specific string describing the configuration error.
PAGE 413
H.323 User's Manual F. SNMP Traps Table F-4: acBoardEvResettingBoard Alarm Trap Alarm: acBoardEvResettingBoard OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.5 Default Severity: critical Event Type: equipmentAlarm Probable Cause: outOfService (71) Alarm Text: User resetting board Status Changes: Condition: Alarm status: Condition: Alarm status: Corrective Action: When a soft reset is triggered via the Web interface or SNMP. Critical After raise Status stays critical until reboot.
PAGE 414
Mediant 1000 Table F-7: acBoardControllerFailureAlarm Alarm Trap Alarm: acBoardControllerFailureAlarm OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.9 Default Severity: Minor Event Type: processingErrorAlarm Probable Cause: softwareError (46) Alarm Text: Controller failure alarm Status Changes: Condition: Proxy has not been found Alarm Status: Major Additional Info: Proxy not found. Use internal routing, or Proxy lost. Looking for another Proxy Condition: Alarm Status: Proxy is found.
PAGE 415
H.323 User's Manual F. SNMP Traps Table F-9: acgwAdminStateChange Alarm Trap Alarm: acgwAdminStateChange OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.7 Default Severity Major Event Type: processingErrorAlarm Probable Cause: outOfService (71) Alarm Text: Network element admin state change alarm Gateway is Status Changes: Condition: Admin state changed to shutting down Alarm status: Major : Shutting down. No time limit.
PAGE 416
Mediant 1000 F.1.2 Component: AlarmManager#0 The source varbind text for all the alarms under this component is Board#/AlarmManager#0 where n is the slot number. Table F-11: acActiveAlarmTableOverflow Alarm Trap acActiveAlarmTableOverflow Alarm: OID: 1.3.6.1.4.15003.9.10.1.21.2.0.
PAGE 417
H.323 User's Manual F. SNMP Traps The source varbind text for the alarm under this component Chassis#0/PowerSupply#, where m is the power supply’s slot number. is Table F-13: acPowerSupplyAlarm Alarm Trap acPowerSupplyAlarm Alarm: OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.30 Default Severity: Critical Event Type: equipmentAlarm Probable Cause: powerProblem Alarm Text: Power-Supply Alarm. Power-Supply is missing. Status Changes: Condition: Alarm status: Condition: Alarm status: F.1.
PAGE 418
Mediant 1000 F.1.5 Log Traps (Notifications) This section details traps that are not alarms. These traps are sent with the severity varbind value of ‘indeterminate’. These traps don’t ‘clear’, they don’t appear in the alarm history or active tables. One log trap that does send clear is acPerformanceMonitoringThresholdCrossing. Table F-15: acKeepAlive Log Trap Trap: acKeepAlive OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.
PAGE 419
H.323 User's Manual F. SNMP Traps Table F-17: acHTTPDownloadResult Log Trap Trap: acHTTPDownloadResult OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.28 Default Severity: Indeterminate Event Type: processingErrorAlarm (3) for failures and other (0) for success. Probable Cause: other (0) Status Changes: Condition: Trap Text: Condition: Trap Text: HTTP Download successful Failed download. HTTP download failed, a network error occurred.
PAGE 420
Mediant 1000 Table F-21: AcDChannelStatus Trap Trap Name: acDChannelStatus OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.37 MIB AcBoard Severity Minor Event Type: communicationsAlarm Probable Cause: communicationsProtocolError Alarm Text: D-Channel Trap. Source: Trunk where m is the trunk number (starts from 0). Status Changes: D-Channel un-established. Condition: Trap status: Trap status: F.1.7 Trap is sent with the severity of Minor. D-Channel established.
PAGE 421
H.323 User's Manual G G. Installation and Configuration of Apache HTTP Server Installation and Configuration of Apache HTTP Server This appendix describes the installation and configuration of Apache’s HTTP server with Perl script environment (required for recording). G.1 Windows 2000/XP Operation Systems Note: For detailed installation information, refer to http://perl.apache.org/docs/2.0/os/win32/config.html.
PAGE 422
Mediant 1000 7. Open the Apache2/conf/perl.conf file for editing and add the line “Script PUT /perl/put.cgi” after the last line in the following section (note that if the following section is omitted or different in the file, insert it into the file or change it there accordingly): Alias /perl/ "C:/Apache2/perl/ SetHandler perl-script PerlResponseHandler ModPerl::Registry Options +ExecCGI PerlOptions +ParseHeaders 8. Locate the file put.
PAGE 423
H.323 User's Manual d. e. G. Installation and Configuration of Apache HTTP Server Set MaxClients to 250 Change the mod_perl module lines to: Alias /perl/ /var/www/perl/ SetHandler perl-script PerlHandler Apache::Registry Options +ExecCGI PerlSendHeader On Script PUT /perl/put.cgi Version 5.
PAGE 424
Mediant 1000 Reader's Notes H.
PAGE 425
H.323 User's Manual H H. OSN Server Hardware Installation OSN Server Hardware Installation This section is intended for customers who have already purchased the Mediant 1000 Media Gateway and want to install the added Mediant 1000 OSN (Open Solution Network) Server functionality. The OSN server module hosts third-party VoIP applications such as IP-PBX, Pre-Paid, and IP-PBX redundancy.
PAGE 426
Mediant 1000 Figure H-2: iPMX Module Figure H-3: Hard Drive Module (HDMX) H.
PAGE 427
H.323 User's Manual H. OSN Server Hardware Installation ¾ To install the CM module, take these 5 steps: 1. Place the Mediant 1000, so that the front panel is facing you, as shown in Figure H-4. 2. Using a Phillips screwdriver, remove the black metal cover plate from the slot below the module labeled CPU, as shown in Figure H-4. Figure H-4: Mediant 1000 Front Panel View 3. Insert the CM module in the slot below the CPU, with the plain side of the Printed Circuit Board (PCB) facing up.
PAGE 428
Mediant 1000 ¾ To install the iPMX module, take these 6 steps: 1. Place the Mediant 1000, so that the rear panel is facing you, as shown in Figure H-6. Figure H-6: Mediant 1000 Rear Panel View 2. Remove the black metal cover plates in the first and second slots located on the right side of the power connection, as shown in Figure H-7. Figure H-7: Mediant 1000 With Cover Plates Removed H.
PAGE 429
H.323 User's Manual 3. H. OSN Server Hardware Installation Use the cutter tool to remove the small metal strip between the upper and lower slots, as shown in Figure H-8. Figure H-8: Mediant 1000 With Cutter Tool 4. Insert the iPMX module in the first slot, closest to the power connection, as shown in Figure H-9. Figure H-9: Inserting the iPMX Module 5. Push the iPMX module into the slot and press on it firmly to ensure it has been fully inserted. 6.
PAGE 430
Mediant 1000 ¾ To install the Hard Drive (HDMX) module, take these 6 steps: 1. Place the Mediant 1000, so that the rear panel is facing you, as shown in Figure H-6. 2. Remove the black metal cover plates in the first and second slots located on the right side of the power connection, as shown in Figure H-7. 3. Use the cutter tool to remove the small metal strip between the upper and lower slots, as shown in Figure H-8. 4.
PAGE 431
H.323 User's Manual I I. Linux™ Operating System Installation for the OSN Server Linux™ Operating System Installation for the OSN Server The purpose of this appendix is to describe how to install the various distributions of the LinuxTM Operating System, on the Mediant 1000 Media Gateway. This document targets RedHatTM, DebianTM and SUSETM distributions. It can also serve as a reference when trying to install other LinuxTM distributions.
PAGE 432
Mediant 1000 I.3 Physical Mounting Requirements I.3.1 Mediant 1000 Front Panel Connection ¾ To connect to the front panel, take these 3 steps: 1. Connect the RS-232 cable from the PC to the RS-232 port on the Mediant 1000. 2. Connect the USB connection cable from the external CD-ROM to the USB port. Refer to the figure below. Figure I-1: Mediant 1000 Front Panel Connections I.3.2 Mediant 1000 Rear Panel Connection ¾ To connect to the rear panel, take these 3 steps: I.4 1.
PAGE 433
H.323 User's Manual I.5.1.1 I. Linux™ Operating System Installation for the OSN Server Downloading an updated LinuxTM Redhat ISO Image ¾ To download an ISO image from the AudioCodes Web site, take these 6 steps: I.5.1.2 1. From http://www.audiocodes.com, navigate to the Support page. 2. Login with your Username and Password. 3. Under Product Documentation, select the Mediant 1000 link and click on Mediant 1000 OSN Server. 4. Select Linux Boot Image and select the installation you need. 5.
PAGE 434
Mediant 1000 5. Locate the boot.iso file in the images folder on the CD. Figure I-3: "Images" Folder Note: The “images” folder may be named differently on different Linux™ distributions. 6. Copy the boot.iso file to the Partner Install folder created in Step 1 and open it with an ISO image editor. The isolinux.cfg file should appear as shown in the screen below. Figure I-4: ISO Screen H.
PAGE 435
H.323 User's Manual I.5.2 I. Linux™ Operating System Installation for the OSN Server Stage 2: Editing the isolinux.cfg File ¾ To edit the isolinux.cfg file, take these 19 steps: 1. Right-click the isolinux.cfg file, and then from the shortcut menu, choose Extract. Figure I-5: Selecting Extract Option 2. Extract the isolinux.cfg file to the Partner Install folder created in Stage 1. Figure I-6: Extract Files Version 5.
PAGE 436
Mediant 1000 3. Click Extract; a screen opens containing the extracted isolinux folder. Figure I-7: ISO-Extract screen 4. Open the isolinux.cfg file with a text editor that supports UNIX file format (e.g., PSPad, UltraEdit). The following screen appears. Figure I-8: Text Edit screen H.
PAGE 437
H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server 5. Insert the following line in the beginning of the file, so that it is the first line. serial 0 115200 6. Locate the line "default ". Usually "default linux" appears. 7. Locate the line "label ". Usually "label linux" appears. Under this line, the following appears: kernel ... append ... 8.
PAGE 438
Mediant 1000 16. Right-click the isolinux.cfg file, and then from the shortcut menu, choose Delete to delete this file. Figure I-9: Deleting CFG 17. From the ISO edit utility menu, select the Actions option, followed by Add Files. Figure I-10: File Add H.
PAGE 439
H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server 18. Navigate to the Partner Install folder, select the isolinux.cfg file, and then click Open. Figure I-11: ISO Open Function The updated isolinux.cfg file has now been copied from the Partner Install folder to the boot.iso image. 19. Save the boot.iso image in the Partner Install folder. I.5.3 Stage 3: Burn the CD ¾ To burn the CD, take these 3 steps: 1. Open a burning utility. 2.
PAGE 440
Mediant 1000 I.5.4 Stage 4: Installation Now you have the boot media which enables the installation of the Mediant 1000 using the serial connection (terminal) with RS-232 cable. ¾ To complete the installation, take these 9 steps: 1. Connect your Windows™ PC via serial cable to the Mediant 1000. 2. Connect the USB CD ROM device via USB cable to the Mediant 1000. 3. Power up the PC. 4. Open the Terminal application (e.g. HyperTerminal) on your Windows™ PC.
PAGE 441
H.323 User's Manual I.5.5 I. Linux™ Operating System Installation for the OSN Server Additional RedHat™ and Fedora™ Installation Notes (7) Please refer to the following notes for the remaining part of the installation. 1. Select LILO as your bootloader where possible, otherwise select GRUB. 2. It is recommended that you disable the firewall when prompted (select “No Firewall”). 3.
PAGE 442
Mediant 1000 I.6 Linux™ Debian Installation Instructions Perform the following five stages for the Linux™ Debian Installation. (Some Debian distributions may vary slightly). I.6.1 Stage 1: Obtaining the ISO Image To obtain an updated ISO image, create it using the steps detailed in the section below. ¾ To create an ISO image using an ISO editor utility, take these 5 steps: 1. Insert the 1st installation disk of the Linux™ Debian distribution into the CD-ROM drive of the Windows™ PC. 2.
PAGE 443
H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server The .iso file starts being created. Figure I-15: Creating .iso file I.6.2 Stage 2: Preparing the Boot Media ¾ To prepare the Boot Media, take these 5 steps: 1. If you have not already done so, download a utility that allows editing of an ISO image. The WinISO™ program (http://www.winiso.com/download.htm) may be used. 2. Using Internet Explorer, download a Unix File Format text editor. PSPad™ (http://www.pspad.
PAGE 444
Mediant 1000 4. Extract the isolinux.cfg file by right-clicking the file name, and then from the shortcut menu, choosing Extract. Figure I-17: Extract isolinux.cfg 5. Extract the isolinux.cfg file to the Partner Install folder. Figure I-18: Extracting to Partner Install folder I.6.3 Stage 3: Editing the isolinux.cfg File In order to obtain an updated isolinux.cfg file, either download it from the AudioCodes website as described in Section I.6.3.1, or edit it using the steps detailed in Section I.6.3.2.
PAGE 445
H.323 User's Manual I.6.3.2 I. Linux™ Operating System Installation for the OSN Server Editing the isolinux.cfg File ¾ To edit the isolinux.cfg file, take these 16 steps: 1. Open the Partner Install folder and select the isolinux.cfg file, with a text editor that supports UNIX file format (e.g., PSPad, UltraEdit). 2. Insert the following line in the beginning of the file, so that it is the first line. serial 0 115200 3. Locate the line 'default '.
PAGE 446
Mediant 1000 F7 F8 F9 F0 f7.txt f8.txt f9.txt f10.txt Note: If the timeout line does not exist, do not add it.1. If you want to install 'kernel 2.6' rather than the 'default 2.4 version', then: a) Take the options from 'kernel' and 'append' lines under the label called 'LABEL linux26'. b) Replace the options of 'DEFAULT' and 'APPEND' lines (at the start of the file). c) Apply the changes from Step 8. 9. Save the changes to the isolinux.cfg file. 10. Close the text editor. 11.
PAGE 447
H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server 14. From the ISO edit utility menu, select the Actions option, followed by Add Files. Figure I-20: File Add 15. Navigate to the Partner Install folder, select the isolinux.cfg file, and then click Open. Figure I-21: ISO Open Function The updated isolinux.cfg file is copied to the Partner Install\isolinux directory. 16. Save the boot.iso in the Partner Install folder. I.6.
PAGE 448
Mediant 1000 I.6.5 Stage 5: Installation Now you have the boot media which enables the installation of the Mediant 1000 using the serial connection (terminal) with RS-232 cable. ¾ To complete the installation, take these 7 steps: 1. Connect your Windows™ PC via serial cable to the Mediant 1000. 2. Connect the USB CDROM device via USB cable to the Mediant 1000. 3. Power up the PC. 4. Open the Terminal application on your PC.
PAGE 449
H.323 User's Manual 4. I. Linux™ Operating System Installation for the OSN Server Continue with the installation, going through the following screens: • 'Partition disks' • 'Installing the Debian base system' 5. In the 'Install the GRUB boot loader on hard disk' screen, select Go Back. This returns you to the 'Debian installer main menu' screen. This is the main menu of the installation. 6. Scroll down in the menu and instead of using GRUB select Install LILO boot loader on a hard disk. 7.
PAGE 450
Mediant 1000 I.7 Linux™ SUSE Installation Instructions Perform the following five stages for the LinuxTM SUSE Installation. (Some SUSE distributions may vary slightly). I.7.1 Additional Requirement for Linux™ SUSE Installation In order to install Linux™ SUSE, a terminal emulation program is needed which supports: I.7.2 ANSI colors (or LinuxTM emulation) Changing terminal size (to 132x47). The Tera Term™ program may be used. Refer to http://hp.vector.co.jp/authors/VA002416/teraterm.
PAGE 451
H.323 User's Manual 4. I. Linux™ Operating System Installation for the OSN Server Create a Partner Install folder on your hard drive. Select boot.iso as the output filename, and then click Make. Figure I-23: Create ISO from CD-ROM The .iso file begins being created. Figure I-24: Creating .iso file I.7.3 Stage 2: Preparing the Boot Media ¾ To prepare the Boot Media, take these 5 steps: 1. If you have not already done so, download a utility that allows editing of an ISO image.
PAGE 452
Mediant 1000 4. Extract the isolinux.cfg file by right-clicking the filename, and then from the shortcut menu, choosing Extract. Figure I-26: Extract isolinux.cfg 5. Extract the isolinux.cfg file to the Partner Install folder. Figure I-27: Extracting to Partner Install folder I.7.4 Stage 3: Editing the isolinux.cfg File To obtain an updated isolinux.cfg file, either download it from the AudioCodes Web site as described in Section I.7.4.1, or edit it using the steps detailed in Section I.7.4.2. I.7.4.
PAGE 453
H.323 User's Manual I.7.4.2 I. Linux™ Operating System Installation for the OSN Server Editing the isolinux.cfg File ¾ To edit the isolinux.cfg file, take these 19 steps: 1. From the Partner Install folder, open the isolinux.cfg file with a text editor that supports UNIX file format (e.g., PSPad, UltraEdit). Figure I-28: isolinux.cfg 2. Insert the following line in the beginning of the file, so that it is the first line. serial 0 115200 3. Locate the line 'DEFAULT '.
PAGE 454
Mediant 1000 8. Add the following parameters to the 'append' line: text console=ttyS0,115200. Note: In the above string, 'ttyS0,115200' consists of a capital 'S', only zeros and one comma. 9. The following examples show how the 'label linux' line and its kernel & append sublines could look like, after you change them:: label linux kernel linux append initrd=initrd text console=ttyS0,115200 or label linux kernel linux append initrd=initrd ramdisk_size=65536 text console=ttyS0,115200 10.
PAGE 455
H.323 User's Manual I. Linux™ Operating System Installation for the OSN Server # rescue label rescue kernel linux append initrd=initrd splash=silent rescue=1 showopts # memory test label memtest kernel memtest implicit 1 gfxboot display prompt timeout readinfo 2 framebuffer notice bootlogo message 0 0 1 2 13. Save the changes to the isolinux.cfg file. 14. Close the text editor. 15. Open the Partner Install folder and with the ISO edit utility, open the boot.iso file. 16. Navigate to the isolinux.
PAGE 456
Mediant 1000 18. Navigate to the Partner Install folder, select the isolinux.cfg file, and then click Open. Figure I-31: Partner Install Folder The updated isolinux.cfg file is added to the Partner Install folder. 19. Save the boot.iso in the Partner Install folder. Figure I-32: Save boot.iso H.
PAGE 457
H.323 User's Manual I.7.5 I. Linux™ Operating System Installation for the OSN Server Stage 4: Burn the CD ¾ To burn the CD image, take these 3 steps: 1. Open a burning utility. 2. Use the Burn Image option to burn the boot.iso to an empty CD media. 3. Mark the media as the “Boot CD”. Note: Ensure that the boot.iso file should be burned as an image and not as a data file. I.7.
PAGE 458
Mediant 1000 5. Power up the Mediant 1000. 6. On the Terminal screen, the BIOS phase will start and the Linux™ installation will begin. The installation will uncompress the kernel, load it and its drivers and start the interactive installation. Note: After the BIOS phase, some badly formatted text may appear on the screen. Note: From this point on, you should proceed with the screen instructions, as instructed by your Linux distributor. 7.
PAGE 459
H.323 User's Manual J J. Regulatory Information (Digital Interface) Regulatory Information (Digital Interface) Declaration of Conformity 73/23/EEC (including amendments) Application of Council Directives: 89/336/EEC (including amendments) 1999/5/EC Annex-II of the Directive EN55022: 1998 + A1: 2000 + A2: 2003 Standards to which Conformity is Declared: EN55024:1998 + A1: 2001 + A2: 2003 EN61000-3-2: 2000 + A2: 2005 EN61000-3-3: 1995 + A1: 2001 EN60950-1: 2001 Manufacturer’s Name: AudioCodes Ltd.
PAGE 460
Mediant 1000 Safety Notices 1. Installation and service of this gateway must only be performed by authorized, qualified service personnel. 2. The equipment must be connected by service personnel to a socket-outlet with a protective earthing connection. 3. This equipment should be installed in restricted access locations with maximum allowed temperature 40°C (104°F) 4. To avoid risk of fire use 26 AWG or higher wiring to connect the telecom ports.
PAGE 461
H.323 User's Manual J. Regulatory Information (Digital Interface) Reader's Notes Version 5.
PAGE 462
™ Mediant™ Media Gateways H.323 Mediant 1000 User’s Manual Version 5.0 www.audiocodes.