request unified-edge tdf call-trace start

Syntax

Description

Start TDF subscriber call tracing.

Options

none	Start call tracing for all TDF subscribers.
imsi `imsi`	(Optional) Start the call tracing for subscribers with the specified International Mobile Subscriber Identity (IMSI) number.
msisdn `msisdn`	(Optional) Start call tracing for subscribers with the specified Mobile station ISDN (MSIDSN) number.
next-call `next-call`	(Optional) Start call tracing for the specified number of next call events (1 through 50). For example, if you specify 10, then the next 10 calls are traced. Note: If you do not include the `next-call` keyword while tracing subscribers on a domain, the default value of 1 is used.
routing-instance `routing-instance`	(Optional) Start call tracing for subscribers for the specified routing instance.
subscriber-name `string`	(Optional) Start call tracing for the specified IFL-based subscriber.
user-name `string`	(Optional) Start call tracing for the specified IP-based subscriber.
v4-addr `v4-addr`	(Optional) Start call tracing for subscribers for the specified IPv4 address of the subscriber’s user equipment (UE).
v6-addr `v6-addr`	(Optional) Start call tracing for subscribers for the specified IPv6 address of the subscriber’s user equipment.

Required Privilege Level

unified-edge

Output Fields

Table 1 lists the output fields for the request unified-edge tdf call-trace start command. Output fields are listed in the approximate order in which they appear.

Table 1: request unified-edge tdf call-trace start Output Fields
Field Name	Field Description
`Session PIC`	Identifier of the session PIC for which the call trace status is displayed.
`Status`	Status of the call trace: `duplicate`—Another call trace record is present that has the same attributes. `success`—Call trace started successfully. `fail`—Call tracing cannot be started.

Sample Output

request unified-edge tdf call-trace start next-call

Release Information

Statement introduced in Junos OS Release 17.1.

ON THIS PAGE