![background image](http://html.mh-extra.com/html/cisco/3521/3521_administrators-manual_64813083.webp)
3-21
Administrator’s Guide for Cisco IPVC 3521 BRI Gateway, Cisco IPVC 3526 PRI Gateway, and Cisco IPVC 3540 PRI Gateway
OL-7995-01
Chapter 3 Configuring the Cisco IPVC 3500 Series Gateway
Configuring Gateway Settings
Procedure
Step 1
In the Gateway interface, on the sidebar, click
Gateway
(if not already selected).
Step 2
Click the
Settings
tab.
Step 3
Click the
Alert Indications
button.
Step 4
In the Events section, select events in the
Disabled events
field and click
Add
to select an event to
monitor. Or, select an event in the
Enabled events
field and click
Remove
to remove that event from
monitoring.
Step 5
Select the
Send SNMP Traps to
check box to configure the IP address of the SNMP server to which the
gateway sends SNMP trap notifications of the events selected in the Enabled events field. You can
configure up to three different SNMP trap servers.
Step 6
In the
Trap server IP
and
Port
fields, enter the IP address and port number for each SNMP server you
want to configure the gateway to send SNMP trap notifications to. To remove an SNMP server, select
those entries and press the delete key on your keyboard.
Configuring Gateway Resources for Calls
Note
This section applies only to Cisco IPVC 3500 PRI Gateways.
In the Resources section of the Settings tab, you can reserve gateway resources for T.120 enabled calls
and for audio transcoded video calls. This section also displays the total number of calls that the gateway
supports at specified bandwidths.
The gateway provides full end-to-end T.120 data collaboration sessions, provided that all terminals
support the T.120 standard in their conferencing applications. In video calls with data transfer, the
gateway accepts whatever bandwidth the ISDN connection defines for the data and dynamically adjusts
the outgoing bandwidth used for data by using the MLP, HMLP, and VarMLP formats.
You can also configure the gateway to prioritize the transcoding, giving preference to a particular codec
that is applied to calls, thus optimizing the resource allocation utilized by each call.
Incompatible sw version
install
incompatibleSwBurnAttemp
RV
.0.73
An attempt to burn a
version of the gateway
software onto
incompatible hardware
occurs.
Warning
Call from non-peer H.323
entity rejected
peerCallRejectedNonPeer
RV
.0.75
The gateway has rejected
an incoming IP call
because the source does
not appear in the peer list.
Warning
Table 3-6
Cisco IPVC 3500 PRI Gateway SNMP Trap Event Types (continued)
Event Type
Trap Name
Trap
OID
Trap is sent when...
State
Severity
Содержание 3521
Страница 137: ......