Home
>
Multi-Tech Systems
>
Communications System
>
Multi-Tech Systems Mvp-2400/2410/3010, Mvp-210/410/810 Voice/ip Gateways User Guide
Multi-Tech Systems Mvp-2400/2410/3010, Mvp-210/410/810 Voice/ip Gateways User Guide
Have a look at the manual Multi-Tech Systems Mvp-2400/2410/3010, Mvp-210/410/810 Voice/ip Gateways User Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 104 Multi-Tech Systems manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
MultiVOIP User Guide Operation and Maintenance 381 Web Browser Interface Beginning with the 4.03/6.03 software release, you can control the MultiVOIP unit with a graphic user interface (GUI) based on the common web browser platform. Qualifying browsers are InternetExplorer6 and Netscape6. MultiVOIP Web Browser GUI Overview FunctionRemote configuration and control of MultiVOIP units. Configuration PrerequisiteLocal Windows GUI must be used to assign IP address to MultiVOIP. Browser Version RequirementInternet Explorer 6.0 or higher Netscape 6.0 or higher Java RequirementJava Runtime 1.0 or higher (application program included with MultiVOIP) Video Useabilitylarge video monitor recommended
Operation and Maintenance MultiVOIP User Guide 382 The initial configuration step of assigning the voip unit an IP address must still be done locally using the Windows GUI. However, all additional configuration can be done via the web GUI. The content and organization of the web GUI is directly parallel to the Windows GUI. For each screen in the Windows GUI, there is a corresponding screen in the web GUI. The fields on each screen are the same, as well. The Windows GUI gives access to commands via icons and pulldown menus whereas the web GUI does not. The web GUI, however, cannot perform logging in the same direct mode done in the Windows GUI. However, when the web GUI is used, logging can be done by email (SMTP).
MultiVOIP User Guide Operation and Maintenance 383 The graphic layout of the web GUI is also somewhat larger-scale than that of the Windows GUI. For that reason, it’s helpful to use as large of a video monitor as possible. The primary advantage of the web GUI is remote access for control and configuration. The controller PC and the MultiVOIP unit itself must both be connected to the same IP network and their IP addresses must be known. In order to use the web GUI, you must also install a Java application program on the controller PC. This Java program is included on the MultiVOIP product CD. ). Java is needed to support drop-down menus and multiple windows in the web GUI. To install the Java program, go to the Java directory on the MultiVOIP product CD. Double-click on the EXE file to begin the installation. Follow the instructions on the Install Shield screens.
Operation and Maintenance MultiVOIP User Guide 384 During the installation, you must specify which browser you’ll use in the Select Browsers screen. When installation is complete, the Java program becomes accessible in your Start | Programs menu (Java resources are readily available via the web). However, the Java program runs automatically in the background as a plug-in supporting the MultiVOIP web GUI. No overt user actions are required.
MultiVOIP User Guide Operation and Maintenance 385 After the Java program has been installed, you can access the MultiVOIP using the web browser GUI. Close the MultiVOIP Windows GUI. Start the web browser. Enter the IP address of the MultiVOIP unit. Enter a password when prompted. (A password is needed here only if password has been set for the local Windows GUI or for the MultiVOIP’s FTP Server function. See “Setting a Password -- Web Browser GUI” earlier in this chapter.) The web browser GUI offers essentially the same control over the voip as can be achieved using the Windows GUI. As noted earlier, logging functions cannot be handled via the web GUI. And, because network communications will be slower than direct communications over a serial PC cable, command execution will be somewhat slower over the web browser GUI than with the Windows GUI.
Operation and Maintenance MultiVOIP User Guide 386 SysLog Server Functions Beginning with the 4.03/6.03 software release, we have built SysLog server functionality into the software of the MultiVOIP units. SysLog is a de facto standard for logging events in network communication systems. The SysLog Server resides in the MultiVOIP unit itself. To implement this functionality, you will need a SysLog client program (sometimes referred to as a “daemon”). SysLog client programs, both paid and freeware, can be obtained from Kiwi Enterprises, among other firms. Read the End-User License Agreement carefully and observe license requirements. See www.kiwisyslog.com. SysLog client programs essentially give you a means of structuring console messages for convenience and ease of use. MultiTech Systems does not endorse any particular SysLog client program. SysLog client programs by qualified providers should suffice for use with MultiVOIP units. Kiwi’s brief description of their SysLog program is as follows: “Kiwi Syslog Daemon is a freeware Syslog Daemon for the Windows platform. It receives, logs, displays and forwards Syslog messages from hosts such as routers, switches, Unix hosts and any other syslog enabled device. There are many customisable options available.”
MultiVOIP User Guide Operation and Maintenance 387 Before a SysLog client program is used, the SysLog functionality must be enabled within the MultiVOIP in the Logs menu under Configuration. The IP Address used will be that of the MultiVOIP itself. In the Port field, entered by default, is the standard (‘well-known’) logical port, 514.
Operation and Maintenance MultiVOIP User Guide 388 Configuring the SysLog Client Program. Configure the SysLog client program for your own needs. In various SysLog client programs, you can define where log messages will be saved/archived, opt for interaction with an SNMP system (like MultiVoipManager), set the content and format of log messages, determine disk space allocation limits for log messages, and establish a hierarchy for the seriousness of messages (normal, alert, critical, emergency, etc.). A sample presentation of SysLog info in the Kiwi daemon is shown below. SysLog programs will vary in features and presentation.
389 Chapter 11: Warranty, Service, and Tech Support
Warranty, Service, & Tech Support MultiVOIP User Guide 390 Limited Warranty Multi-Tech Systems, Inc. (“MTS”) warrants that its products will be free from defects in material or workmanship for a period of two years from the date of purchase, or if proof of purchase is not provided, two years from date of shipment. MTS MAKES NO OTHER WARRANTY, EXPRESSED OR IMPLIED, AND ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE HEREBY DISCLAIMED. This warranty does not apply to any products which have been damaged by lightning storms, water, or power surges or which have been neglected, altered, abused, used for a purpose other than the one for which they were manufactured, repaired by the customer or any party without MTS’s written authorization, or used in any manner inconsistent with MTS’s instructions. MTS’s entire obligation under this warranty shall be limited (at MTS’s option) to repair or replacement of any products which prove to be defective within the warranty period, or, at MTS’s option, issuance of a refund of the purchase price. Defective products must be returned by Customer to MTS’s factory—transportation prepaid. MTS WILL NOT BE LIABLE FOR CONSEQUENTIAL DAMAGES AND UNDER NO CIRCUMSTANCES WILL ITS LIABILITY EXCEED THE PURCHASE PRICE FOR DEFECTIVE PRODUCTS. Repair Procedures for U.S. and Canadian Customers In the event that service is required, products may be shipped, freight prepaid, to our Mounds View, Minnesota factory: Multi-Tech Systems, Inc. 2205 Woodale Drive Mounds View, MN 55112 Attn: Repairs, Serial # ________________ A Returned Materials Authorization (RMA) is not required. Return shipping charges (surface) will be paid by MTS. Please include, inside the shipping box, a description of the problem, a return shipping address (it must be a street address, not a P.O. Box number), your telephone number, and if the product is out of warranty, a check or purchase order for repair charges.