|
- I have instances when calling over IP into an E&M channel were I get a busy tone even though the channel is not in use. If I originate a call from the E&M channel it clears this condition. I'm using firmware version 6.03 or 6.03a.
|
- Upgrade to firmware version 6.03b.
ftp://ftp.multitech.com/multivoip/misc/6.03b/
There is a bug in the MVP210/410/810 version 6.03/6.03a firmware where it is possible for an E&M call to not hang up. When the E&M channel sees the M lead drop indicating hang up, it starts a 250ms hang up timer. If that same E&M channel receives a hang up from the remote channel during that 250ms, the channel will not hang up. The next call attempt originated on that E&M channel will not go through but will clear the condition. Until the condition is cleared by originating a call on the E&M channel, calls from the remote channel will not go through to the E&M side, but will get a busy. Of course resetting the VoIP will also clear it.
|
- Models: MVP210, MVP410, MVP810
|
|
- Can I upgrade my MultiVOIP remotely?
|
- Yes, but only through TFTP, not via Telnet or Web browser.
Do not upgrade boot code remotely.
When upgrading firmware, be sure to enter the correct IP Address assigned to the MultiVOIP when prompt, or you will lose the ability to communicate, and you will be traveling on site.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- Can I use a dial up modem connected to the voice channels?
|
- Dial-up modem connections through the voice channels (called modem-relay) are supported by the MultiVOIP
models mvp130, mvp210, mvp410, mvp810, mvp2410, mvp3010. G.711 at 64k voice coder is required. The maximum analog baud rate between the modems is 14.4Kbps.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- Can I view the MultiVOIP logs, or print console remotely?
|
- No, they can only be access when the PC running the GUI is connected directly to the serial port.
Note: Due to on-board log storage limitations, running the GUI in the Log Entries field will store the logs on the local HD and remove the limitation. This is done by connecting the PC to the VOIP via serial port as described above.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- Does the MultiVOIP support H.323?
|
- The MultiVOIP family of products (except the MVP800) supports the H.323 protocol.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400
|
|
- How do I get my MultiVOIP to work through a firewall or proxy server?
|
- The H.323 protocol uses dynamic ports. Current Multi-Tech proxy or firewall products do not support H.323 dynamic ports. You will need a H.323 compatible proxy or firewall product for this to work.
The Proprietary Protocol uses special UDP ports to pass information, and these ports will need to be added to your firewall or proxy server. Example protocol and ports required for the MultiVOIP are listed below.
Q.931 signaling, RTP and RTCP are used for call handling.
Ports used:
Q.931: Q.931 signaling port
Channel 1 = 900
Channel 2 = 902
Channel 3 = 904
Etc.
RTP:
Channel 1 = 5004
Channel 2 = 5006
Channel 3 = 5008
Etc.
RTCP:
Channel 1 = 5005
Channel 2 = 5007
Channel 3 = 5009
Etc.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- On our private network, voice quality is great 85% of the time, while intermittently we experience poor quality of service. How do we troubleshoot this problem?
|
- Start troubleshooting by analyzing what software packages utilize the connection for sending data. Look for processes that occur during business hours that could be scheduled for after hours. Investigate the bandwidth being utilized on the connections to determine if you are over-driving the circuit. Your routers, along with the VOIPs, can give clues to packets being lost, and other network traffic statistics. Set up your routers to support DiffServ, or IP Precedence. This will allow the voice packets to have higher priority than data, when your bandwidth is being utilized heavily.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- Our growth is steady, and with the savings incurred, we need to add another MVP800 to our local PBX. What do we need to do in order to utilize the second set of 8 channels, for all of our remote callers on the IP Network?
|
- You may need to order more analog ports for your PBX, and configure them for FXS or FXO. You will also need a valid IP Address for the additional MultiVOIP on the local network. On your master VOIP, set up the additional ports to be in a hunt group, allowing the additional voice traffic to overflow into the second VOIP. This will allow calls coming into the VOIP from the IP Network to access a free port on the PBX. For hunting to occur from the PBX side to the additional 8 ports would be a function of the PBX.
|
- Models: MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- We are already sending data over frame relay on a private network. Can we use MultiVOIPs on this private network, even though we are not sending voice across the Internet?
|
- Provided that the private network uses a Class C IP addressing scheme, the MultiVOIPs may be used on a private network.
Before installing a MultiVOIP network into any existing network, verify that the "pipes" between sites have enough available bandwidth to accommodate voice traffic.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- What can I do to test my MultiVOIP?
|
- You can try the DOS ping command to verify that the MultiVOIP can be seen on your network. If there are two MultiVOIP gateways at the same location, you could set them up on the same network and configure them as master/slave and call from one to the other using a handset as an FXS to FXS connection. If you have the equipment available, you could set everything up as if it were live and verify that the routers or firewall have the correct ports open (see question 6).
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- What IP information do I need in order to configure my MultiVOIP?
|
- You will need to know your local network’s IP scheme so the MultiVOIP can become part of that network. The MultiVOIP requires one valid IP address on your network. The MultiVOIP also needs the Gateway IP Address of the device through which it is accessing the Internet, such as a router or proxy server.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- What is Classic Mac OS?
|
- Classic Mac OS is any Mac OS system software version previous to Mac OS X 10.0. This includes Mac OS 9.x, Mac OS 8.x and System 7.x (Multi-Tech does not support any Mac OS previous to System 7). The Classic environment in Mac OS X does not allow the use of most Classic Mac OS control panels, so refer to the Mac OS X installation instructions when installing a Multi-Tech modem for use in Mac OS X.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- What types of connections will the MultiVOIP support?
|
- The H.323 protocol can support all combinations of PBX connectivity. Multi-Tech's proprietary implementation supports three main types of connections: FXS, FXO, and E&M. Following are examples of such combinations:
An FXS-to-FXS circuit may use a standard (analog) telephone or key telephone system connected at each endpoint.
An FXS-to-FXO circuit may use a standard (analog) telephone or key telephone system at one end and uses an analog PBX extension at the other endpoint.
An FXO-to-FXO circuit uses an analog PBX extension at each endpoint.
An E&M-to-E&M circuit uses PBX trunk card connections at each endpoint.
Other combinations include:
∙ E&M wink to FXS ground
∙ E&M dial tone to FXS loop
∙ E&M dial tone to FXO loop
The MultiVOIP supports connections to standard (analog) telephones and key telephone systems using its FXS port(s).
Station-side (extension) connections to the PBX are done by connecting the MultiVOIP's FXO port to an analog station-side (extension) port on the PBX.
Trunk connections to the PBX require a special (analog)trunk card within the PBX and use the E&M port on the MultiVOIP. If one of the MultiVOIPs is connected to a PBX trunk, then the corresponding channel in the other MultiVOIP must be connected to another E&M circuit or to a standard (analog) telephone or key telephone system.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
- Will my MultiVOIP software function on Windows 2000?
|
- The GUI management application for the MultiVOIPs runs on Windows 2000.
|
- Models: MVP110, MVP120, MVP200, MVP2400, MVP3010, MVP400, MVP800
|
|
