SCP Configuration (Trace Traps)
When an inbound
InitialDP is received, the normalised calling and called party numbers
are checked to see if either is a “number of interest” in the trace traps list.
If these numbers match a configured trace trap, then the trace (in-memory debug) level
is raised, subject to any throttling limitations applied by the
parameter, by the
The in-memory trace debug is available via the management GUI / API / command-line, and
will be retained until overridden in the cyclic buffer of
Note that it is unusal to statically configure trace traps. Typically they will be created on-the-fly using the management GUI / API / command-line, and should be removed when no longer needed.
... <config> ... <trace_traps> <trace_trap calling_party="6141400112233" trace_level="3"/> </trace_traps> </config> ...
The available configuration for trace traps are as below:
||Object||A single trace trap.|
Trace Trap Entry
Each Trace Trap defines a rule for potentially enabling tracing for an inbound call.
trace_trap Object is configured as follows:
The normalised calling party, as it would appear in the
The normalised called party, as it would appear in the
At least one of
If both are defined, then both must match before the trace trap is considered matched.
[Required] The trace level.
Levels higher than debug should be used with caution in a production environment.