Справочник Пользователя для Netopia R310
F-2 User’s Reference Guide
Received Clear Ind. from DN: Received clear indication from switch. Associated parameter: called director y
number. Secondar y associated parameter: cause code.
number. Secondar y associated parameter: cause code.
Connection Confirmed to our DN: Received connect confirmation for Connect Request sent to the switch.
Associated parameter: called director y number.
Associated parameter: called director y number.
Received Connect Ind. for DN: Received connect indication for Call Request sent to the switch. Associated
parameter: called director y number.
parameter: called director y number.
Received Disc. Ind. from DN: Received disconnect indication from switch. Associated parameter: called
director y number. Secondar y associated parameter: cause code.
director y number. Secondar y associated parameter: cause code.
Received Setup Ind. from DN: Received call indication from switch. Associated parameter: called director y
number.
number.
Issued Setup Request from our DN: Call request was sent to switch. Associated parameter: called director y
number.
number.
Requested Connect to our DN: Connect request for the received call was sent to the switch. Associated
parameter: called director y number.
parameter: called director y number.
Issued Clear Request for our DN: Clear request was sent to the switch. Associated parameter: called director y
number.
number.
Issued Clear Response to DN: Clear response was sent to the switch. Associated parameter: called director y
number.
number.
Disconnect Reqested: Disconnect request was sent to switch. Associated parameter: called director y number.
Secondar y associated parameter: cause code.
Secondar y associated parameter: cause code.
ISDN event cause codes
These codes appear as associated (secondar y) parameters in some of the ISDN events.
Cause No. 1: unallocated (unassigned number). This cause indicates that the destination requested by the
calling user cannot be reached because, although the number is in a valid format, it is not currently assigned
(allocated).
calling user cannot be reached because, although the number is in a valid format, it is not currently assigned
(allocated).
Cause No. 2: no route to specified transit network. This cause indicates that the equipment sending this
cause has received a request to route the call through a par ticular transit network which it does not recognize.
The equipment sending this cause does not recognize the transit network either because the transit network
does not exist or because that par ticular network, while it does exist, does not ser ve the equipment that is
sending this cause.
cause has received a request to route the call through a par ticular transit network which it does not recognize.
The equipment sending this cause does not recognize the transit network either because the transit network
does not exist or because that par ticular network, while it does exist, does not ser ve the equipment that is
sending this cause.
This cause is suppor ted on a network-dependent basis.
Cause No. 3: no route to destination. This cause indicates that the called user cannot be reached because
the network through which the call has been routed does not ser ve the destination desired.
the network through which the call has been routed does not ser ve the destination desired.
This cause is suppor ted on a network-dependent basis.
Cause No. 6: channel unacceptable. This cause indicates that the channel used in this call is not acceptable
to the sending entity.
to the sending entity.
Cause No.7: call awarded and being delivered in an established channel. This cause indicates that the user
is receiving an incoming call, which is being connected to a channel already used by that user for similar calls
(e.g., packet-mode X.25 vir tual calls).
is receiving an incoming call, which is being connected to a channel already used by that user for similar calls
(e.g., packet-mode X.25 vir tual calls).