Global Search—Search all parameters in all records.
|
Enter the URI formatted string of the call
source information you are searching. Valid values are alpha-numeric
characters. For example, sipp<sip:sipp@172.16.34.10:5060;tag=24.
|
From URI—Search on the From-URI header.
|
Enter the URI formatted string that contains a
protocol, name, location, or any other applicable characteristic, that is sent
by the
E-SBC in the REQUEST
header. Valid values are alpha-numeric characters. For example,
sip:service@172.16.34.226:5060.
|
Request URI—Search on the Request-URI header.
|
Enter the URI formatted string that contains a
protocol, name, location, or any other applicable characteristic, that is sent
by the
E-SBC in the REQUEST
header. Valid values are alpha-numeric characters. For example,
sip:service@172.16.34.226:5060.
|
To URI—Search on the To-URI header.
|
Enter URI formatted string of the call
destination information you are searching. Valid values are alpha-numeric
characters. For example, sut<sip:service@172.16.34.226:5060;tag=99.
|
Start Date— Search from messages that start at the
specified date and time.
|
- Enter a starting
date to search on in the first text box in the format YYYY-MM-DD (where Y
=year, M=month, and D=day). For example, 2012-04-15 would search for all
records starting on April 15, 2012. Valid values are numeric characters only.
- Enter a start
time to search on in the last three text boxes in the format HH mm ss (where
H=hour, m=minutes, and s=seconds). For example, 01 30 45 would search for all
records starting at 1:30 and 45 seconds. Valid value are numeric characters
only.
|
End Date—Search from messages that end at the
specified date and time.
|
- Enter an end
date to search on in the first text box in the format YYYY-MM-DD (where Y
=year, M=month, and D=day). For example, 2012-04-15 would search for all
records starting on April 15, 2012. Valid values are numeric characters only.
- Enter an end
time to search on in the last three text boxes in the format HH mm ss (where
H=hour, m=minutes, and s=seconds). For example, 01 30 45 would search for all
records starting at 1:30 and 45 seconds. Valid value are numeric characters
only.
|
Session ID—Search on the monitored SIP session ID,
as shown in the Summary table.
|
Enter the ID of the call session you want to
search. Valid values are alpha-numeric characters. For example,
22-3412@172.16.34.1.
|
In Call ID—Search on the SIP call ID of the initial
received request.
|
Enter the ID of the incoming call (phone
number and source IP address). Valid values are alpha-numeric characters. For
example, 25-3412@172.16.34.10.
|
Out Call ID—Search on the SIP call ID of the first
routed request.
|
Enter the ID of the outgoing call (phone
number and IP address). Valid values are alpha-numeric characters. For example,
14-3412@172.14.54.6.
|
State (with result code)—Search on the state of the
call, as shown in the Summary table.
|
Enter the status of the call session with the
result code for which you want to search. Result codes can range from 1xx to
5xx. For example, terminated-200, or failed-400. Case-sensitive. Valid values
include:
- INITIAL-<result code>
- EARLY-<result
code>
- ESTABLISHED-<result code>
- TERMINATED-<result code>
- FAILED-<result code>
|
Notable Event—Search on a notable event type that
you select from the drop-down list.
|
Select the notable event for which you want to
search. Valid values include:
- any-event -
search displays any notable event that was stored in memory.
- hort-session -
search displays only records that indicate a short-session duration has
occurred.
- local-rejection
- search displays only records that indicate a local-rejection has occurred.
|
In Realm—Search the realm from which the initial
request was received.
|
Enter the name of the realm for which the
incoming call belongs. Valid values are alpha-numeric characters. For example,
access.
|
Out realm—Search the realm to which the first
routed request was sent.
|
Enter the name of the realm for which the
outgoing call belongs. Valid values are alpha-numeric characters. For example,
backbone.
|
In SA—Search on the name of the session agent from
which the initial request was received.
|
Enter the name of the session agent (SA) on
the incoming call session. Valid values are alpha-numeric characters. For
example, SA1.
|
Out SA—Search on the realm to which the first
routed request was sent.
|
Enter the name of the session agent (SA) on
the outgoing call session. Valid values are alpha-numeric characters. For
example, SA2.
|
In Source Addr—Search on the IP address from which
the initial request was received.
|
Enter the source IP address of the SA that
accepted the incoming call session. IP Address must be entered in dotted
decimal format (0.0.0.0). For example, 172.45.6.7.
|
Out Dest Addr—Search on the IP address to which the
initial request was sent.
|
Enter the destination IP address of the SA
that accepted the outgoing call session. IP Address must be entered in dotted
decimal format (0.0.0.0). For example, 172.64.56.7.
|
In Network Interface—Search on the IP address on
which the initialƒ request was received.
|
Enter the incoming core network interface that
connects the Net-Net ECB to your network. IP Address must be entered in dotted
decimal format (0.0.0.0). For example, 192.45.6.7.
|
Out Network Interface—Search on the IP address that
was the source for the routed request.
|
Enter the outgoing network interface that
connects your Net-Net ECB to the outside network. IP Address must be entered in
dotted decimal format (0.0.0.0). For example, 192.45.6.8.
|