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

NOTE: After calling rtsp_free_msg, do not use msg again without a call
to (1) in the previous list.
• For rtsp_conn_t, call either rtsp_open or rtsp_create_conn before calling
APIs that require arguments of type rtsp_conn_t *.
In other words, you must obtain the rtsp_conn_t* data structure only from
rtsp_open or rtsp_create_conn.
After calling rtsp_close, you must not reference the memory location passed
to the rtsp_close.
The call sequence with respect to rtsp_conn_t structure is as follows:
1. rtsp_open (..., &conn) or rtsp_create_conn (..., &conn).
2. APIs that require rtsp_conn_t* arguments
3. rtsp_close_conn(conn);
NOTE: After calling rtsp_close_conn, do not use conn again without a
call to (1) in the previous list.
• You must initialize rtsp_*_t data structures before using them. You may use
certain APIs to initialize statically declared structures and some others to
dynamically allocate memory and initialize the structures. You must call either of
these APIs before passing these structures to other APIs.
The call sequence with respect to the rtsp_xport_spec_t* structure is as follows:
1. xspec = rtsp_alloc_xport_spec(NULL) or
rtsp_init_xport_spec(&xspec);
2. Set information in the xpec structure, for example, as follows:
xspec->cport.rtp = 7000; xpec->cport.rtcp = 7001;
3. Use xspec in RTSP APIs:
rtsp_set_msg_hdr(msg, RTSP_TRANSPORT_HDR, xspec, 0);
4. Free the resources:
rtsp_free_xport_spec(xspec)
RTSP Call Order Sequence 65