|
Aricent’ RTP/RTCP Stack has
a modular architecture for easy interface with other
applications. This unique offering from Aricent is highly
scalable with a rich set of APIs for dynamic configuration
and runtime monitoring of transmission, enabling a wide
variety of applications to be built upon the Stack.
The architecture of the Aricent RTP/RTCP Stack either can
be customized to run as a separate process with the
application, or can be coupled with an application as
a function-based interface, thus enabling easy integration
of the Stack in both distributed and monolithic system
environments.
RTP/RTCP Architecture
A separate client library module has been created for
easy integration of the Stack with the application in
case of the message-based approach. Any number of other
profiles can easily be plugged in with the Aricent’
RTP/RTCP Stack without any changes in the original status.
Aricent also offers a set of Test Stubs with the stack,
which enable the user to test all its functional aspects.
These stubs also guide the application developers in
developing value-added applications over the Stack.
Aricent also provides several reference implementations
along with the Test Stubs that can be re-used by the
end application, reducing time-to-market.
The RTP/RTCP Stack from Aricent is agnostic to and can
be used with any third party voice and video codecs
whether standard or proprietary. The Stack conforms
to Aricent’ Protocol Stack Development Framework that
makes the product feature-intensive. In addition, the
RTP/RTCP Stack renders flexibility to the application
to associate custom information to further enhance the
capabilities of the Stack.
RTP/RTCP Stack: APIs
- The Event Handler API: Provides an interface to
handle events from application and peers
- Notification APIs: Notifies the application from
the stack on receipt of RTP and RTCP packets
- Indication APIs: Indicate member creation/deletion
and detect SSRC collision
- Management APIs:
- Session APIs: Create/Delete a session and start/stop
RTP/RTCP for a session
- Protocol Parameters Control APIs: Configure the
MTU limit of packets, payload, sampling rate, frame
interval, RTCP bandwidth, and user/ member information,
to specify SDES fields
- Member APIs: Block/unblock members from receiving
RTP/RTCP
- Profile APIs: Create and register new customized
profile with the stack
- Statistics Control APIs: Set/get statistics
- Debug Control APIs: Set/get Trace level
- Error Report Control: Set/get Error level indication
from the stack
OS Ports available:
- Solaris
- Windows NT/98
- Linux
- VxWorks
Porting on any other operating system can be made
available on request. Alternatively, the application
developer can port the stack to any other operating
system, using the well-defined operating system interface
layer.
|
)
