Changes between Version 5 and Version 6 of 3rd_Party_Media


Ignore:
Timestamp:
Mar 16, 2008 10:14:15 AM (11 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 3rd_Party_Media

    v5 v6  
    99== Introduction == 
    1010 
    11 PJSIP consists of several libraries which mostly are independent from one another. The library architecture diagram below shows how libraries are interacting with each other. 
     11PJSIP consists of several libraries which interaction can be seen from the diagram below. 
    1212 
    1313[[Image(diagram.jpg)]] 
    1414 
     15Below are the components that are related to media stack and SIP stack integration. 
     16 
    1517'''PJSUA-LIB''': 
    16  This is a library which integrates all other libraries into very high level API. Due to its nature, it is tightly coupled with all of the libraries. 
     18 This is a library which integrates PJSIP, PJMEDIA, and PJNATH libraries into very high level and easy to use API. Due to its nature, it is tightly coupled with all of the libraries. 
    1719 
    1820'''SIP Libraries''': 
    19  This includes PJSIP core library (pjsip-core), SIP user agent client library (pjsip-ua), and SIP presence and instant messaging library (pjsip-simple). 
     21 This includes PJSIP core library (pjsip-core), SIP user agent library (pjsip-ua), and SIP presence and instant messaging library (pjsip-simple). The SIP user agent library (pjsip-ua) uses the SDP components of PJMEDIA for negotiating offer/answer. 
    2022 
    2123'''Media Stack''': 
    22  The media stack is PJMEDIA and PJMEDIA-CODEC. 
    23  
    24 '''SDP components''': 
    25  Although the SDP components (message representation, parsing, and SDP offer answer negotiation) is packaged with PJMEDIA, actually it is independent from PJMEDIA and it can be (and has been) used independently from PJMEDIA. This is because although media can be optional for some application (for example, a server), SDP and SDP negotiation are needed by the invite session, so it should be able to use these parts without having to use PJMEDIA. 
    26  
    27  In fact in Symbian build system, these SDP parts are packaged on separate static library (as '''pjsdp''' library). On GNU build system, both PJMEDIA and PJSDP libraries are built, although only PJMEDIA is linked with the application since unlike the Symbian build system, the PJMEDIA library here also contains PJSDP parts. 
     24 The media stack is PJMEDIA and PJMEDIA-CODEC. Depending on the library packaging, it may contain '''SDP components''' (message representation, parsing, and SDP offer answer negotiation). 
     25 
     26Although the SDP components (message representation, parsing, and SDP offer answer negotiation) may be packaged with PJMEDIA, actually it is independent from PJMEDIA and it can be (and has been) used independently from PJMEDIA. This is because although media can be optional for some application (for example, a server), SDP and SDP negotiation are needed by the invite session, so it should be able to use these parts without having to use PJMEDIA. 
     27 
     28  ''Note: in Symbian build system, these SDP parts are packaged on separate static library (as '''PJSDP''' library) and removed from PJMEDIA. On GNU build system, both PJMEDIA and PJSDP libraries are built, although only PJMEDIA is linked with the application since unlike the Symbian build system, the PJMEDIA library here also contains PJSDP parts.'' 
    2829 
    2930