| | |
|
How to connect the gateway?[TOP] |
|
1)Rack-mountable gateway: Plug in the power cord in one end to the gateway, |
|
| and plug in the other end to the power outlet on the wall, then turn the Power switch |
|
| On of the gateway. |
|
|
| 2) Desk Top gateway: Connect one side of the power adaptor to the gateway and |
|
| the other side to the power outlet, if it's a one-piece adaptor. For 2-piece adaptor, |
|
| connect another side of the power adaptor to the power cord, then plug the power |
|
| cord in to the power outlet. |
|
How to connect serial ports of the gateway and your computer?[TOP] |
|
here is a white 9-pin serial port cable supplied with the gateway. Connect the |
|
| male end of the cable to the Console port on the front end of the gateway and the |
|
| female end to the serial port (COM1) of your computer, Then, configure correct |
|
| communication parameters for serial port via HyperTerminal, for information of |
|
| parameters setting , please refer to the Manual. |
|
How to connect the gateway to the Internet? [TOP] |
|
There are two Ethernet ports on the gateway, one is marked as LAN, another as |
|
| WAN. |
|
| |
|
How to log onto the gateway via Telnet?[TOP] |
|
Log onto the gateway from a remote computer via Telnet to view configuration |
|
| information of gateway (e.g. IP address, Version, Mode, etc) providing the gateway |
|
| is connected to the public network with fixed IP or dynamic IP. To prevent others |
|
| from logging onto your gateway, one can assign a login password, details are as |
|
| follows: |
|
| 1) Log onto the gateway via HyperTerminal |
|
| 2) Input “passwdSet” after prompt character “Voipack” |
|
| 3) Enter the password |
|
| 4) Re-enter the password |
|
| Now the Telnet login password is set. You will be required to enter the password |
|
| when logging onto the gateway via Telnet. |
|
How to view debug information on the gateway?[TOP] |
|
Input “dbgcmd” after “Voipack>” to enter debug mode. |
|
| Input “spy xgcp 2” after “MXP>” to display mgcp-related information such as call |
|
| connection, communication and call release. |
|
| Input “spy tiu 0” after “MXP>” to display ringing detection related information for |
|
| FXO detection. |
|
Why FXO fails to terminate calls?[TOP] |
|
FXO release failure-where FXO fails to terminate the call while the call is actually |
|
| released, occasionally occurs when FXO fails to detect the power down and/or busy |
|
| tone status. Firmware Version 5.37 features automatic busy tone detection which |
|
| may effectively resolve this problem however, some busy tone signals sent by PBX |
|
| are not under the default detection range, so necessary modification is required. |
|
| Details are as follows: |
|
| View default parameters: |
|
| Voipack>showBusytoneParam |
|
| Set new parameters: |
|
| Voipack>flash_set_bztone_param (1000,50, 1000, 50, 30). |
|
| If FXO release failure still occurs, set mute detection parameters. |
|
| |
|
| |
|
|
|