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 | |
| 26 | Although 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.'' |