HP-UX Multimedia Streaming Protocols (MSP) Programmer's Guide

Table 3-1 RTP Troubleshooting Tips (continued)
TipsScenarioAPI
At least one successful call to
rtp_ioctl for RTP_SSENDTOADDR
should be made on a valid RTP
descriptor before rtp_send can send
packets to the other side.
The rtp_send API does not send
packets to the other side. The
descriptor is valid and correct. It also
does not return errors.
rtp_send
Check if the arguments are
re-initialized.
You may be passing NULL to
rtp_recv for the buffer argument so
that rtp_recv allocates its own buffer
and return you the RTP packet. In such
a case, the buflen field is set to the size
of the first packet. If the *buf argument
is not set to null in the second call, the
same buffer is used and the maximum
length of the buffer is assumed to be the
size specified in buflen: the size of the
first RTP packet. In such a case, if a
longer RTP packet is received,
rtp_recv returns an error.
Second call to rtp_recv always fails
or the user is not able to receive the
second RTP packet, but the first is
obtained successfully.
rtp_recv and
rtcp_recv
Troubleshooting RTSP
Table 3-2 describes how to troubleshoot Real-Time Streaming Protocol (RTSP) suite of
APIs.
82 Troubleshooting MSP