User`s guide

USER’S GUIDE
122 SFVRA Connection Manager
REASONS FOR FAILURE
The reasons for failure work in conjunction with the Failure types. While the Failure Type is listed
in the PROBLEM_LIST table, a corresponding reason is listed in the REASON_STRING table. The
following is a list of Reasons for Failure:
Cannot aggregate this call.
Connect Failed. In a Hunt Group situation, SFVRA-CONN aggregates calls across multiple
CyberSWITCHES. Ensure Hunt Group phone number is specific to one CyberSWITCH.
Cannot find this device name.
Authenticate Failed. The call from the user was rejected because the user name is not defined in the
SQL database. Configure this device name in the SQL database and try to connect again.
CSX Connection Active
CSX Up. The SFVRA Service has a connections to the CyberSWITCH.
CSX Keepalive failure
CSX Down. The SFVRA Service lost the connection to the CyberSWITCH.
CyberSWITCH call back.
The user was successfully authenticated. However, since the Callback feature was enabled for the
user, the connection was dropped and re-established by a CyberSWITCH.
CyberSWITCH load level call back.
The user was successfully authenticated. However, since the Load Level feature was enabled for
the user, the connection was dropped and re-established by a CyberSWITCH with less current
connections.
Error accessing the database.
Authenticate Failed or Connect Failed. The CyberSWITCH was unable to receive authorization to
accept the call because it was unable to communicate with SFVRA-CONN. Ensure the physical
connection between the CyberSWITCH and the SFVRA-CONN is intact.
Exceeded the bandwidth limit.
Connect Failed. The call from the user was rejected or disconnected because the bandwidth
limitation was exceeded for the user. Reconfigure the user to allow a higher bandwidth, or demand
that the user request a bandwidth within the limitation.
Exceeded the time limit.
Connect Failed. The call from the user was rejected or disconnected because the of a time limit
restriction. You may reconfigure the user with additional time without changing the cumulative
statistics or you may reset the cumulative statistics for the user.
Incorrect Ethernet Address.
Authenticate Failed. The call from the user was rejected because the Ethernet Address was
incorrect. Ensure that the Ethernet Address configured on the user matches the address in the
database.
Invalid calling number.
Connect Failed. The call from the user was rejected based on an invalid Calling Line ID. Ensure that
the CLID configured on the user matches the CLID in the database.