SVC-2 status messages
This article describes the different status messages that can appear on a VoIP Dialer block that is linked to an SVC-2 card. These status messages appear if there is a problem during the VoIP registration process. Once an SVC-2 card has successfully registered, no status message will be displayed. The screenshot below shows the location of the status messages in the VoIP Dialer block.
- If the status field is blank, then the SVC-2 card is successfully registered and ready to make a call. (This is assuming you are connected live to the Tesira system, as the status window will also be blank when Tesira software is offline.)
- Network is Down
- A physical network connection has not been sensed on the SVC-2 card's Ethernet port.
- Network is Up
- A physical network connection has been sensed on the SVC-2 card's Ethernet port, however communication with the proxy server has not yet been established.
- Address Conflict
- The SVC-2 card has detected an IP conflict (another device on the network is using the same IP address that is assigned to the SVC-2 card).
- DHCP In Progress
- The SVC-2 card has been set to obtain an IP address automatically via DHCP, and is currently requesting an address from the DHCP server.
- Proxy Not Configured
- A valid IP address or hostname for the proxy server was not supplied in the VoIP Line Properties window of the VoIP Control/Status block.
- SIP User Not Configured
- A SIP User was not supplied in the VoIP Line Properties window of the VoIP Control/Status block.
- Auth User/Password Not Configured
- The Authorization Username or Password was not supplied in the VoIP Line Properties window of the VoIP Control/Status block.
- The SVC-2 card is attempting to contact the proxy server. If this message never goes away, the SVC-2 card may not be able to communicate with the proxy server. Double-check the network settings of the SVC-2 card and the Proxy Address.
- Authentication Failed
- The SVC-2 card has attempted to register with the proxy server but received an error message in response to its registration attempt. Double-check that the Authentication User Name and Password match what was entered into the VoIP proxy server.