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 |
|---|---|
Name |
Select one or more configured Session Manager instances for which the specific filters should be used.
Note:
When you select a Session Manager from the list, the View button is activated. You can click this button to retrieve the current Trace Configuration information for the selected Session Manager. A warning symbol indicates the Session Manager instance is in the Maintenance Mode service state. |
Syslog Server 1 |
Specifies the Syslog server 1 configuration, if configured. |
Syslog Server 2 |
Specifies the Syslog server 2 configuration, if configured. |
Description |
Specifies the details of the Session Manager configuration. |
Button |
Description |
|---|---|
View |
Retrieves the current trace configuration details for the selected Session Manager and displays the details on the Trace Configuration page. |
Commit |
Saves the configuration changes. |
Name |
Description |
|---|---|
Tracer Enabled |
Enable or disable SIP message tracing. The default is enabled. If Tracer Enabled is disabled, the system disables all the check boxes. If the syslog server configuration and SIP Tracer is enabled for the Session Manager instance, then SIP trace information is also sent to a remote syslog server. |
Trace All Messages |
Enable or disable SIP message tracing for all SIP messages. If Trace All Messages is disabled, the system disables all the check boxes. |
From Network to Security Module |
Enable or disable SIP message tracing for ingress calls sent to the Session Manager instance from the network. |
From Security Module to Network |
Enable or disable SIP message tracing for egress calls originating from the Session Manager instance and sent to the network. |
From Server to Security Module |
Enable or disable tracing of local SIP messages originating from the Session Manager instance. |
From Security Module to Server |
Enable or disable tracing of local SIP messages originating from the security module. |
Trace Dropped Messages |
Enable or disable tracing of messages from calls dropped by the SIP firewall as well as the SM100 proxy. |
Max Dropped Message Count |
If Trace Dropped Messages is enabled, this field displays the value of the maximum number of traced dropped messages. |
Button |
Description |
|---|---|
New |
Create a new filter for filtering SIP messages based on the users. You can define a maximum of three user filters. |
Delete |
Delete a selected user filter or filters. |
Name |
Description |
|---|---|
From |
Filter SIP messages based on the user from whom the message is sent. Type the user string. For example, a rule to trace all messages from user “pqr”: to=”” from=”pqr” stop-count=50 |
To |
Filter SIP messages based on the user to whom the message is sent. For example, to create a rule to trace all messages to user “xyz”: to=”xyz” from=”” stop-count=50 |
Source |
Filter SIP messages based on the source address. |
Destination |
Filter SIP messages based on the destination address. |
Max Message Count |
Value for the maximum number of messages matching the filter that the Session Manager should trace. The default is 25 messages. |
Button |
Description |
|---|---|
New |
Create a new filter for filtering all SIP messages that start a new call. You can define a maximum of three call filters. |
Delete |
Delete a selected call filter or filters. |
Name |
Description |
|---|---|
From |
Filter SIP messages from a specific user. Call tracing identifies a call by capturing the Call ID from the first message that matches the From filter. Thereafter, tracing all the messages that have the matching call ID. For example, to create a rule to trace all messages related to a CALL from user “pqr”: to=”” from=”pqr” request-uri=”” stop-count=50 |
To |
Filter SIP messages based on the user to whom the message is sent. Call tracing identifies a call by capturing the Call ID from the first message that matches the To filter, thereafter tracing all the messages that have the matching call ID. For example, a rule to trace all messages related to a CALL to user “xyz”: to=”xyz” from=”” request-uri=”” stop-count=50 |
Source |
Filter SIP messages based on the source address. |
Destination |
Filter SIP messages based on the destination address. |
Max Call Count |
Value for maximum number of messages matching the filter that the Session Manager should trace. The default is 25 messages. |
Request URI |
Filter calls based on the called party (URI address). A valid Request URI format, for example, is .@122.111.11. |