Changes between Version 5 and Version 6 of Media_Transport_Adapter

Timestamp:

Sep 24, 2011 8:57:41 AM (13 years ago)

Author:

bennylp

Comment:

--

Media_Transport_Adapter

@@ -39 +39 @@
 
 Implementing a new adapter should not be too difficult. The following steps provide rough guidance to implementing your own adapter:
- - see the [http://www.pjsip.org/docs/latest/pjmedia/docs/html/group__PJMEDIA__TRANSPORT.htm#details reference documentation] again to understand how the media transport will be operated by pjsip. If your media transport needs to interact with SDP, then make sure you read and understand the ''Interaction with SDP Offer/Answer'' section in the documentation.
+ - see the [http://www.pjsip.org/docs/latest/pjmedia/docs/html/group__PJMEDIA__TRANSPORT.htm#details reference documentation] again to understand how the media transport will be operated by pjsip. If your media transport needs to interact with SDP, then make sure you read and understand the ''Interaction with SDP !Offer/Answer'' section in the documentation.
  - next, start with the transport adapter sample from pjmedia directory. Copy this to your application directory (you don't need to add the transport to pjmedia directory).
  - implement the media transport methods (i.e., [http://www.pjsip.org/docs/latest/pjmedia/docs/html/structpjmedia__transport__op.htm pjmedia_transport_op]) as necessary. At the very minimum, you'd need to implement: ''get_info()'', ''attach()'', ''detach()'', ''send_rtp()'', ''send_rtcp2()'', and ''destroy()''. You'll need to implement more if the adapter needs to interact with SDP. Again, the info is provided in the reference documentation.
@@ -59 +59 @@
  - your transport may be destroyed while the call is running, and/or the {{{on_create_media_transport()}}} callback is called again for the same call. You cannot assume that {{{on_create_media_transport()}}} callback is only called once for a call. These happen when media is removed or added for a call.
 
+[[BR]]
 
 {{{