Table of Contents
Advertisement
A
BOUT
P
-
-P
EER
TO
EER
H.323 C
ALL
D
ISCONNECT
R
EASONS
the peer list. If deselected, the Gateway allows incoming calls from
IP-side entities not defined in the Peer list section.
(PRI Gateways only) In the Reject calls from peer devices when less
9
than n B channels are free field, enter the lower capacity threshold for
rejecting calls from H.323 peer devices. The default setting is 6.
Table 3-7
lists the reasons for which the Gateway peer-to-peer hunting module
might disconnect a call.
Table 3-7
Disconnect Reasons
Number
H.323 Call Disconnect Reason
1
There is no available bandwidth.
2
Gatekeeper resources have been exhausted.
3
The destination cannot be reached.
4
The destination rejected the transaction request.
5
Version is not compatible.
6
No permission to perform requested transaction.
7
The destination gatekeeper cannot be reached.
8
Gateway resources have been exhausted.
9
Destination address is not formatted correctly.
10
LAN crowding has caused the call to be dropped.
11
The destination is busy and cannot respond to the call transaction.
12
Undefined reason for transaction failure.
13
Call should be routed to a gatekeeper.
14
Call should be forwarded.
15
Call should be routed to an MC.
Configuring Gateway Settings
Configuring the SCOPIA Gateway
91
Advertisement
Table of Contents
