Avaya Administering Aura Session Manager Release 6.1 Manual de usuario Pagina 384

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 532
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 383
Firewall. Refer to the SIP Firewall Configuration Section in the Avaya Aura Security
Guide for details and examples on using IP/SIP Layer Track
• None—No tracking used.
• Remote IP address—Track messages for a specific IP address of the remote
host.
• Local Port—Track messages for a specific local port.
• From—Track messages for a specific sender.
• To—Track messages sent to a particular receiver.
• Contact—Track messages for a specific contact.
• Request URI—Track messages for a specific request-URI.
8. Under Threshold, specify the following options only if you have selected either Rate
Block or Rate Limit in the Action Type field or with None in the Action Type with Log
Type enabled. You cannot use Threshold with Permit/Drop Actions.
• Count (packets)—Threshold for the number of matching packets. The value
can range from 10 to 100000. The default value is 20.
• Period (secs)—Threshold for the period for matching packets. The value can
range from 1 to 60. The default value is 20.
• Timeout (secs)—Action timeout in seconds. Specify Timeout only if you have
selected the Rate Block action. The value can range from 30 to 36000. The
default value is 900.
9. Under Connection Type, select from one of the following options:
Any: This is a default choice. If this option is selected, SIP Firewall rule is
matched against all incoming SIP Traffic
SIP UA Connection: If this option is selected, SIP Firewall rule is matched
against the incoming SIP traffic from entities that are not the Trusted SIP Entity
(as defined by the Routing Policy). This option is suitable for creating SIP
Firewall filtering rules for SIP telephones that are directly connected to Session
Manager.
NRP Trusted SIP Entity: If this option is selected, SIP Firewall rule is matched
against the incoming SIP traffic from entities that are marked as Trusted SIP Entity
in the Routing Policy.
Note:
If there are any untrusted SIP Entities connected to the Session Manager (as
defined by Routing Policy), these entities will be treated/filtered as SIP UA
connection by SIP Firewall (if there are any rules defined and enabled in SIP
Firewall with connection type as SIP UA connection). If this behavior is
undesirable, specific rules can be added for the untrusted SIP Entity IP Address/
port. These rules shall be defined before SIP Firewall rules for SIP UA connection
(Note: SIP Firewall traverse rules in the rule list from top to bottom).
Configuring and monitoring Session Manager instances
384 Administering Avaya Aura
®
Session Manager November 2010
Vista de pagina 383
1 2 ... 379 380 381 382 383 384 385 386 387 388 389 ... 531 532

Comentarios a estos manuales

Sin comentarios