Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
Name |
Description |
|---|---|
Rule Name |
Name of the signaling rule. |
Inbound |
|
Requests |
Drop-box to determine how incoming SIP request messages will be treated by this policy. The following options are available:
|
Non-2xx Final Responses |
Drop-box to determine how incoming Non-2xx Final SIP response messages will be treated by this policy. The following options are available:
|
Optional Request Headers |
Drop-box to determine how optional request headers contained in incoming SIP messages will be treated by this policy. The following options are available:
|
Optional Response Headers |
Drop-box to determine how optional response headers contained in incoming SIP messages will be treated by this policy. The following options are available:
|
Outbound |
|
Requests |
Drop-box to determine how outbound SIP request messages are treated by this policy. The following options are available:
|
Non-2xx Final Responses |
Drop-box to determine how outbound Non-2xx Final SIP response messages are treated by this policy. The following options are available:
|
Optional Request Headers |
Drop-box to determine how optional request headers contained in outbound SIP messages will be treated by this policy. The following options are available:
|
Optional Response Headers |
Drop-box to determine how optional response headers contained in outbound SIP messages will be treated by this policy. The following options are available:
|
Content-Type Policy |
|
Enable Content-Type Checks |
Option to enable checks for the content part of the SIP signaling message. |
Action |
Drop-down menu from which you choose the action to be taken by the Avaya SBC security device when considering the content portion of SIP signaling messages. The following options are available:
|
Exception List |
The specific terms to be passed or blocked, according to the action specified in the Action field. |
Multipart Action |
Drop-down menu from which you choose the action to be taken by the Avaya SBC security device when considering the multipart content portion of SIP signaling messages. The following options are available:
|
Exception List |
The specific terms to be passed or blocked, according to the action specified in the Multipart Action field. |
QoS |
|
Enabled |
Indicates whether the Signaling Quality-of-Service (QoS) feature is enabled. |
ToS |
Indicates whether Type-of-Service (ToS) is enabled. The Precedence and ToS fields are activated only if the ToS option is selected. The following options are available for the Precedence field:
The following options are available for the ToS field:
|
DSCP |
Indicates the most significant values for Differentiated Services (DiffServ). These values, referred to as the Differentiated Services Point Code (DSCP), are used to provide guaranteed service to critical network traffic. The following options are available for the Value field:
|
UCID |
|
Enabled |
The status indicates whether UCID is enabled. You must enable this method to have unique identifier at call level. |
Node ID |
A unique two-byte network node identifier that is assigned to the Avaya SBC device. |
Protocol Discriminator |
Valid values are 0x00 (User-Specific) and 0x04 (IA5). Communication Manager uses this value for processing the external ASAI UUI field, if any, associated with the call. |
Name |
Description |
|---|---|
Proprietary Request |
A check box indicating whether the Request being defined is a non-standard SIP request. Select the check box to designate a non standard SIP request message or clear the check box to indicate a standard SIP request message. |
Method Name |
The type of standard SIP request message for which this signaling policy will apply. Select the desired Method Name from the corresponding drop-down box. If you select the Proprietary Request field, you can type a method name in the Method Name. |
In-Dialog Action |
The action to be taken for the SIP request message defined in the Method Name field when the session is in-dialog. Available action options are Allow, and Block with.... If you select the Block with... option, the two fields below are activated, and you can provide the type of response to be sent. |
Out-of-Dialog Action |
The action to be taken for the SIP request message defined in the Request field when the session is out-of-dialog. Available action options are Allow, Block, and Block with Response. If you select the Block with Response option, the two fields below are activated, and you can provide the type of response to be sent. |
Name |
Description |
|---|---|
Proprietary Response |
A checkbox indicating whether the Response being defined is a non standard SIP response. Select the checkbox to designate a non-standard SIP response or clear the check box to indicate a standard SIP response. |
Response Code |
The specific response message to be sent for the received SIP request. Select the desired response from the drop-down box. If you select the Proprietary Response field, you can type a response code in the Response Code field. |
Method Name |
The SIP message that triggers the Response Code selected in the previous field. Select the desired SIP message from the drop-down box. |
In-Dialog Action |
The action to be taken if the proprietary response is generated in-dialog when the session is established. Available action options are Allow and Change response to…. If you select the Change response to… option, the two fields below are activated, and you can provide the type of response to be sent. |
Name |
Description |
|---|---|
Proprietary Request Header |
A check box indicating whether the header being defined is a nonstandard SIP header. Select the check box to designate a nonstandard SIP header or clear the checkbox to indicate a standard SIP header. |
Header Name |
The name of the proprietary SIP header. Make your selection from the corresponding drop-down list. If you select the Proprietary Request Header check box, you can type a header name in the Header Name field. |
Method Name |
The context or call sequence in which the header is contained. |
Header Criteria |
The header criteria. The available options are Forbidden, Mandatory, and Optional. The Action field specifies the action to be taken if the header is present in the SIP message designated in the Method Name field. Depending on the option you select for the Header Criteria, different selections are available for the Action field:
If you select Block with..., then the system displays two text boxes to type the response message. The default value in the text boxes are 486 and Busy Here respectively. |
Name |
Description |
|---|---|
Proprietary Response Header |
A checkbox indicating whether the header being defined is a nonstandard SIP response header. Select the checkbox to designate a nonstandard SIP response header or clear the checkbox to indicate a standard SIP response header. |
Header Name |
The standard SIP message header for which the signaling policy will apply. Make your selection from the corresponding drop-down list. If you select the Proprietary Response Header field, you can type a header name in the Header Name field. |
Response Code |
The code to be sent as the SIP response. Select the desired code from the drop-down box. |
Method Name |
SIP signaling message name, such as CANCEL, INVITE, or PUBLISH. Make your selection from the corresponding drop-down list. |
Header Criteria |
Whether the presence of the header in the response field is Forbidden, Mandatory, or Optional. |
Action |
The Action field specifies the action to be taken if the header is present in the SIP message designated in the Method Name field. Depending on the option you select for the Header Criteria, different selections are available for the Action field:
If you select Block with..., then the system displays two text boxes to type the response message. The default value in the text boxes are 486 and Busy Here respectively. |