The VoipMediaEngine..::.RtpPacketAccess type exposes the following members.


The EnableRawRtpPacketAccess procedure allows application software to access all RTP media packets that are received or are "ready-to-be" transmitted by the media engine. Using this capability, application software can modify any aspect of RTP media packets. The primary use of this API procedure is to allow applications to perform custom encryption of the call's media.

If your VOIP application exchanges fully encrypted RTP packets with another telephony device (RTP headers and payloads are fully encrypted), you will have to disable the media engine's default RTP packet filtering behavior. For additional details, see the remarks section below.

An application should call this API procedure any time prior to initiating or receiving phone calls.

The FilterReceivedRtpPackets procedure allows application software to change the default receive RTP packet filtering behavior of the media engine. This capability is useful if the application receives encrypted RTP packets from another telephony device.

By default the media engine performs RTP payload ID and packet size filtering for all incoming RTP media packets. The application can use this API procedure to selectively enable or disable the filtering behavior. For additional information regarding RTP packet encryption, see the EnableRawRtpPacketAccess(VoipMediaEngine, Int32, Boolean, VoipMediaEngine..::.RTP_CALLBACK_PROC, Object) API procedure.

The Object's finalizer.
(Overrides Object..::.Finalize()()().)

See Also