Avaya Site Administration Reference
121
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.
Line noise can corrupt the messages being sent from the voice system or messaging
system. Because Avaya Site Administration will not connect to a system until it hears
the correct response, if line noise is corrupting the responses, then Avaya Site
Administration may wait for the correct response until the Login timeout value is
exceeded.
Comentarios a estos manuales