Cabletron Systems CSX1000 User Manual
USER’S GUIDE
410 CyberSWITCH
D
IAL
O
UT
Problem:
A Dial Out call was not completed successfully.
A Dial Out call was not completed successfully.
Action:
1.
1.
If you issued the
call device <device name>
console command to initiate the call, check
to see that you entered the device name correctly. Device names are case sensitive.
2.
If you issued the
call peer <telephone number data rate>
console command to
initiate the call, check to see that you entered the correct telephone number and data rate. The
telephone number must contain all required prefixes such as the area code, or a “9” if Centrex
is used.
telephone number must contain all required prefixes such as the area code, or a “9” if Centrex
is used.
3.
If you have entered the call device or the call peer command correctly, follow the set up and
actions listed below.
actions listed below.
Set Up:
1.
1.
Enable the call trace messages by issuing the
trace on
console command.
2.
Erase the current system messages (issue the
er
console command).
3.
Initiate a call to a remote device by issuing the
call device <device name>
console
command.
4.
Display the system messages (issue the
dr
console command).
5.
Look for the following call request messages among the system messages.
Out - CALL RQST ACK Call Id=<call Id> Rate=<data rate> Slot=<slot#>
Port=<port#> Chans=<bearer channel map> TN=<telephone number di-
aled> Ces=<communication endpoint suffix> ConnId=<connect Id
In - CALL RQST ACK CallId=<call Id> Slot=<slot#> Port=<port#>
CES=<ces> ConnId=<connection Id>
In - PROCEEDING Call Id=<call Id> Slot=<slot #> Port=<port #>
Chans=<bearer channel map> Ces=<communication endpoint suffix>
ConnId=< connect Id>
In - CONNECT Call Id=<call Id> Slot=<slot#> Port=<port #>
Chans=<bearer channel map> Ces=<communication endpoint suffix>
ConnId=<connect Id>
Action:
1.
1.
If the system does not report a call request message for the remote device, then the system did
not attempt to make a call. Check to see if there is enough call resources (lines, channels,
supported connections) to make the missing call. For example, if your system supports only
one BRI line, and you have no hunt groups, then only two active connections are possible. The
system would not attempt to make a third call.
not attempt to make a call. Check to see if there is enough call resources (lines, channels,
supported connections) to make the missing call. For example, if your system supports only
one BRI line, and you have no hunt groups, then only two active connections are possible. The
system would not attempt to make a third call.
If this is not the case, contact Customer Support.
2.
If the system reports a call request message but it does not connect, then the system attempted
to make a call. Check to see if the remote device has already completed the installation and
verification processes, and is currently running with no active errors.
to make a call. Check to see if the remote device has already completed the installation and
verification processes, and is currently running with no active errors.