Port Conflicts - Nortel TAPI User Manual

180 Chapter 8 Troubleshooting
Table 20 Resolving connectivity issues (continued)
Problem
The switch connection drops and
terminates calls. You receive an
error message: Failed to allocate
call info memory. The following
message appears in the error log:
Resource_limitation _rejection.
Symposium TAPI SP stops
responding.
An incoming call over an Inbound
ANI (IANI) trunk carrying a 10-digit
ANI terminates at an ACD agent's
In-Calls key. However, if the call
appears in a TAPI-compliant
application and the incoming caller
hangs up (abandons the call), all
subsequent calls to the InCalls key
are not recognized.

Port conflicts

To identify whether any port conflicts exist, in a command console, enter the
command:
information about ports:
• protocol — either TCP or UDP
• local address of the machine and the port that are in use
• foreign address and port number
• state — LISTENING, ESTABLISHED, CLOSE_WAIT, or TIME_OUT
The presence of a port 5000 on this list before you install Symposium TAPI SP
indicates a potential conflict.
213346.02
Solution
All existing calls are aborted. While the connection is down, no new
requests are allowed; however, Symposium TAPI SP continues to
advertise services. The reason for this behavior is that Symposium
TAPI SP has run out of memory and the solution is to add more
memory to the server.
• If the Succession switch fail, use Succession procedures to identify
and correct the problem.
• Verify that Symposium TAPI SP is registered and operational.
• Access the Windows task manager by right-clicking the mouse on
the Windows menu bar to verify that the TAPI SRV application is
running.
If Symposium TAPI SP still does not respond, shut down and restart
your machine to close the TAPISRV application file. Uninstall and
reinstall Symposium TAPI SP.
The agent must answer the next call by pressing the In-Calls key on the
set manually.
. This command generates a list containing the following
netstat -a