Ping; Path Diagnostics; Trace Route; Twamp - Juniper TEPM AGENT - RELEASE NOTES 17-12-10 Release Note

teardown messages. It is suggested that VoIP test calls typically be configured to 45
seconds or greater in duration in order to minimize the impact of call setup and teardown.
•
VoIP/SIP tests initiated from the CLI unexpectedly attempt to place calls through an
outbound proxy and/or use the wrong transport protocol for the call SIP messages. This
is because the Controller can configure an interface-oriented SIP configuration that is
inherited by VoIP tests executed through the interface. As a result, if a test plan defined
in the CLI does not include a definition of the SIP registrar or outbound proxy, those
values are inherited from the Controller-specified SIP configuration.
•
VoIP/SIP tests between twoTePM Agents attempt to use TCP as the transport protocol
because the SIP configuration for the associated interfaces is set to 'Auto' transport
selection. TCP transport is not working properly for peer-to-peer tests. In order to get
peer-to-peer tests to work properly, it is necessary to set up the SIP interface
configuration in the Controller to 'UDP only' for the SIP transport.
•
On rare occasions, VoIP tests executed from the Junos CLI appear to 'hang' and never
report completion. Simply cancelling/stopping the test instance and re-running the test
corrects the problem when it occurs.

Ping

•
Ping tests executed/scheduled from the Junos CLI do not adhere to the requested packet
interval. Ping tests executed/scheduled from the TePM Controller do send the packets at
the appropriate intervals.
•
Ping tests do not indicate failure status when no response is received from the ping
target.

Path Diagnostics

•
Because path diagnostic tests include transmission of packets to the local host as part of
the normal course of the test, running TePM path diagnostic tests will cause the Junos
Release 10.0 to crash due to a known defect in the Junos Release 10.0 kernel.

Trace Route

•
Trace route tests may incorrectly indicate test failure status when the target is the remote
interface of a multi-homed network device.

TWAMP

•
TWAMP client is unable to connect to the TWAMP server. The TWAMP server must be
configured with an interface to listen for TWAMP client control connections. In addition,
the TWAMP client IP address MUST be configured in the TWAMP server 'client list' filter.
•
The TWAMP responder currently inserts the same timestamp for the receive and transmit
times of the reflected packets.
•
Issuing the CLI command 'show services tepm twamp-responder status...'
displays that the interface name for the interface where the TWAMP server is bound is
Issues by Supported Junos Release
- 3 -