Your modem or data module has reported an error pertaining to the phone number or initialization string that Avaya Site Administration is sending it.
1 Have you successfully used this modem (or data module) to connect to this voice system or messaging system in the past?
If yes, then someone or something has changed the setup of your modem (or data module).
Determine whether any connection settings have changed in Avaya Site Administration by accessing the Connection Properties screen for that connection.
If you have not successfully used this modem (or data module) to connect to this voice system or messaging system in the past, see the questions below.
2 Can you use the modem (or data module) to dial other locations?
If yes, the modem (or data module) is working, and so is the serial cable and the phone cord. However,
Something may wrong in your connection setup to the voice system or messaging system. The problem could be with any of the following: An incorrect phone number
An incorrect initialization string.
Network connection failed
Avaya Site Administration has encountered a problem initiating a network connection to the voice system or messaging system. Avaya Site Administration cannot reach the system, or can not find the system with the details you have provided in the Connection Properties screen.
1 You may want to re-try the connection. There may be a temporary problem with your computer network.
2 If Windows Networking is set up on you computer, do you have access to your normal network services (like e-mail or the web)?
If you do, and they are working as you expect them to, then your Windows Networking is probably OK. If you do not have access, then you may want to troubleshoot your Windows Networking setup.
3 Check that the host system you are trying to connect to exists on your network and is operating.
Check the spelling of the host and port number in the Connection Properties screen for the system you are trying to connect to.
Check that the system you are trying to connect to can be reached from your computer by pinging it. If the system does not respond to the ping, then:
that the system you are trying to connect to is working. Check its power and use the manufacturer’s instructions to check the health of the system. If the system is okay, check your network cable.
If you are operating in an environment without a Domain Name Server (DNS) or in an environment where your DNS is untrustworthy, then you should use the IP address of the system you wish to connect to instead of the host name in the Connection Properties screen (i.e. Use 123.192.10.17 instead of mysystem or mysystem.mycompanyname.com).
4 Check that the port number you are using is correct in the Connection Properties screen for the system you are trying to connect to.
Check with your system administrator or the system’s manual to determine what the correct port number is. A common port number is 23. 23 is the "well-known" port number for telnet, a network text terminal utility and is also the standard port number for INTUITY AUDIX.
If you are connecting through a terminal server, then the port number is configured through the terminal server. Ask your administrator, or use your terminal server documentation to determine what the correct port number is.
5 Check how many network connections the system that you are trying to reach supports.
The system you are connecting to may only support a limited number of network
connections. If the system has reached the maximum number of connections, then it will refuse connections and display this error message. The documentation for the system you are connecting to will indicate the connection limitations of that system. In this situation, you will be able to connect if another user disconnects.
If you have defined several network connections to the same system, then you may be the person who is holding a connection open. If a system only supports one network connection, and you define two network connections, your second connection will fail. Check Avaya Site Administration’s Connection Status tab to see if you already have a connection open to this system.
No carrier
Your modem or data module was not able to make a connection with the remote modem or data module.
Possible causes:
Your modem may not have had enough time to make the connection. To fix the problem:
1 Give your modem more time to make a connection with the remote modem by increasing your modem’s timeout value (see Designing new initialization strings or refer to the documentation that came with your modem or data module). If you do, then also:
2 Give Avaya Site Administration more time to make the initial connection with the remote voice system or messaging system, by increasing the Login timeout value in the Connection Properties screen.
Your modem settings may be incompatible with those of the remote modem (the modems could not negotiate a common protocol to communicate with). To fix the problem, make sure you are using the correct initialization string.
You may be experiencing line noise.
If you suspect you are experiencing line noise, try placing the call again to get a different line. If the problem continues, you may want to talk to your
telecommunications manager or the telephone company about line quality. If your modem (or data module) and the remote modem (or data module) both support error correction (a feature that is designed to mitigate line noise), then make sure it is turned on. (See Choosing the correct initialization string.)