PJSIP version 1.5.5

Released on 2010-01-11T10:34:50Z

This release is for bug fixes only, no new features are included.

For more details about the ticket list, please see Release Notes

PJSIP version 1.5

Released on 2009-11-25T16:51:05Z

Release Focus

Release focus:

• Work on TLS transport (#957):
  • generic secure socket abstraction in PJLIB
  • rewrite SIP TLS transport
  • TLS transport in Symbian
• Socket QoS (TOS/DSCP, WMM) support in all components (#950)
• Support for SIP Message Summary / Message Waiting Indication extension (#982)
• Many presence related works (#937, #411, #364)
• More mature native WMME audio backend, it is now used by default on Windows (#983)

Incompatibility Info

SSL

On GNU build system: please re-run configure

On other build systems: Previously the macro PJSIP_HAS_TLS_TRANSPORT is used to enable TLS transport in PJSIP. Now use (new) configuration macro PJ_HAS_SSL_SOCK to enable SSL/TLS support in PJLIB. By default, TLS support in PJSIP (the PJSIP_HAS_TLS_TRANSPORT macro) will be enabled based on this (PJ_HAS_SSL_SOCK) macro value.

Presence

There have been some behavioral changes which may need some attention to:

• presence: ticket #937 among other things implemented automatic buddy's presence resubscription upon receiving several specific termination causes. Ticket #411 and #364 improved the PUBLISH request handling. If you have these features implemented in your application you may want to disable it.

Deprecation Info

None detected

---

For more details about the ticket list, please see Release Notes

PJSIP version 1.4.5

Released on 2009-10-08T10:14:52Z
This release contains major bug fixes against 1.4. Ticket list:

For more details about the ticket list, please see Release Notes

PJSIP version 1.4

Released on 2009-08-17T22:45:49Z

Release Focus

Release focus:

• Nokia VAS and VAS-Direct Support
• Initial porting for Symbian 5th Edition
• Support for SIP Session Timer extension (RFC 4028)
• New test applications for testing audio subsystem and media handling

Incompatibility Info

Changes that may break compatibility with previous versions.

• ticket #930 changes the semantic of various SIP contact parameters/settings:
  • the contact_param field of pjsua_acc_config is now used to represent additional Contact header parameters (not Contact URI parameters).
  • the contact argument in pjsip_dlg_create_uac(), pjsip_dlg_create_uas(), and pjsip_endpt_create_request() now represents the value of the Contact header rather than the Contact URI. This may break the compatibility if application specifies the value without the brackets, for example, "sip:10.0.0.1;transport=udp" instead of "sip:10.0.0.1;transport=udp", due to the treatment of the parameters in the Contact header. In the former example, the "transport=udp" parameter will be treated as header parameter and not URI parameter.

Deprecation Info

Info about deprecated APIs:

• ticket #866 allows application to specify more than one STUN servers in PJSUA-LIB. New settings stun_srv_cnt and stun_srv array are introduced in pjsua_config, and the existing stun_host and stun_domain settings are now deprecated. Backward compatibility is still maintained, if stun_srv_cnt is zero then the values of stun_host and stun_domain will be used.

---

For more details about the ticket list, please see Release Notes

PJSIP version 1.0.3

Released on 2009-07-02T16:59:34Z
This release is bug-fix only release of the stable 1.0 branch. For the current version with many new enhancements, please use [milestone:release-1.2 release-1.2] instead.

For more details about the ticket list, please see Release Notes

PJSIP version 1.3

Released on 2009-06-23T17:47:46Z

Release Focus

Release focus:

• support for ICE regular nomination
• automatically switch to TCP when sending large SIP requests
• retransmit SIP provisional response every 1 minute
• bug fixes

---

For more details about the ticket list, please see Release Notes

PJSIP version 1.2

Released on 2009-05-08T00:13:07Z

Release Focus

pjnath update

Bring pjnath up to date with the latest ICE, STUN, and TURN RFCs/draft RFCs.

Visual Studio Projects Reorganization

Build configurations to control static/dynamic linking with LIBC/MSVCRT

Currently there are two build configurations in the VS 2005 project files:

• Debug: multithreaded, statically linked with LIBC, debug (i.e. the /MTd flag).
• Release: multithreaded, dynamically linked with MSVCRT, release (i.e. the /MD flag).

This release leaves the two build configurations above as is, but it adds four more settings:

• Debug-Static: multithreaded, statically linked with LIBC, debug (i.e. the /MTd flag).
• Debug-Dynamic: multithreaded, dynamically linked with MSVCRT, debug (i.e. the /MDd flag).
• Release-Static: multithreaded, statically linked with LIBC, release (i.e. the /MT flag).
• Release-Dynamic: multithreaded, dynamically linked with MSVCRT, release (i.e. the /MD flag).

This target naming convention will also apply to Windows Mobile targets (see below).

Windows Mobile targets support in the same VS 2005 project files

Currently Windows Mobile targets (including SmartPhone 2003 and !PocketPC 2003 targets) are available via separate Embedded Visual C++ projects, and one must import these projects into Visual Studio 2005.

This release adds Windows Mobile targets into existing VS 2005 projects.

Codecs work

Integrate G.722.1 and G.722.1c (SIREN7/14), licensed from Polycom.

---

For more details about the ticket list, please see Release Notes

PJSIP version 1.0.2

Released on 2009-03-25T16:48:19Z
This release is bug-fix only release of the stable 1.0 branch. For the current version with many new enhancements, please use [milestone:release-1.1 release-1.1] instead.

For more details about the ticket list, please see Release Notes

PJSIP version 1.1

Released on 2009-03-19T19:46:56Z
This release is the development in the trunk and contains both bug-fixes and features additions from the previous [milestone:release-1.0.1 release-1.0.1]. It may have non-backward compatible changes from the previous release. If you are maintaining a stable application based on the 1.0 series, you may want to have the [milestone:release-1.0.2 release-1.0.2] instead.

Release Focus

This release contains major enhancements, with the introduction of Nokia APS-Direct and new Audio Device API.

Nokia APS-Direct

The APS-Direct is a feature to make use of the hardware codecs supported by Symbian's Audio Proxy Server (APS) API. Since audio frames coming from/into APS are in encoded format, we need to bypass most of the audio processing in PJMEDIA (since PJMEDIA works with PCM audio frames). Understandably many PJMEDIA features (e.g. conference bridge and many features associated with it such as WAV playback/recording) will not be available when APS-Direct is used.

See Using APS-Direct and VAS-Direct in PJMEDIA for more information.

New Audio Device API

With the introduction of APS-Direct, we discovered that the old sound device API couldn't provide us with the features that are required, so new audio device API has been developed.

See PJMEDIA Audio Device API for more information.

Automated-Tests

This release has been equipped with automated tests to maintain the quality of the code. Please see http://dash.pjsip.org for the result!

API Changes and Incompatibility Info

We would expect some changes in the sound device interface, with the addition of a new API to expose device capabilities (such as volume control and audio routing). See PJMEDIA Audio Device API for more information.

---

For more details about the ticket list, please see Release Notes

PJSIP version 1.0.1

Released on 2008-12-23T23:00:00Z
Ticket list:

common

For more details about the ticket list, please see Release Notes