Archive for the 'Development Process' Category

PJSIP 1.x being Phased Out, Version 1.16 The Penultimate Version

PJSIP version 2.0 has been out for eight months, we’ve had two releases since then, we feel that the 2.x line should have been maturing now.

It’s time to say goodbye to the venerable version 1.x.  It’s proven to be a successful product, in my opinion. It’s been with us for four years, 25 releases, and it has met a lot of people’s expectations. Although granted that it has its share of deficiencies too. We could only hope that version 2 would be as successful.

But we can’t maintain 1.x forever. We feel our limited development resource would be better spent at developing 2.x instead. Thus we are giving version 1.x support for six more months from now, until September 2013. We hope that this, along with the eight months that we’ve had, gives enough time for everyone to upgrade their 1.x based product to PJSIP version 2. We do encourage everyone to upgrade to PJSIP version 2.

PJSIP version 1.16 was released. This version contains many bug fixes backported from version 2.1. The next version in PJSIP 1.x version line, version 1.17, will be the last of the 1.x series. It will only contain critical fixes from the 2.x, hence once again we recommend everyone to upgrade to version 2 to get the full benefit of PJSIP.

Thank you for using PJSIP!

SVN URL for version 1.x has been moved to a branch

With the release of PJSIP version 1.10, the svn repository for version 1.x has been moved from trunk to a new branch:

If you are monitoring the SVN trunk version, please switch your repository to the URL above. This can be done easily by running the following command in your work directory:

$ svn switch

Later we will put 2.0 development into the svn trunk, but for now, we have equipped the svn trunk with a build error to make people aware that the location has been changed.


Migration of svn and Trac: expect disruption

We are currently migrating svn and trac to new hosting provider, so and will be disrupted for a little while.

Sorry for any inconvenience.

[Update: Everything should back to normal now. As a bonus, https connections are now properly certified without warnings! Yay!]

Call for Symbian S60 testers for pjmedia APS direct

As we finish the current iteration of Symbian S60 implementation, most
importantly the implementation of APS-direct, we need all of you to
participate in testing it. This is from experience we know mobile
devices are very tricky and can behave differently from one firmware
to another.

So we need as many Symbian S60 3rd Edition phone as possible. The test will involve installing a test application, checking a few things, and filling in a report form

To do this we need your IMEI and a few other details, this is because
the requirements of Symbian Signed, we need to ‘burn’ your IMEI into
our test application.

Don’t reply with your details to the public list, instead fill in this

We can’t promise everyone will be accepted, because there is a hard
limit to the number of IMEIs we can burn, and we’ll prioritize
variation of devices, rather than first come first serve.

If you can get your friends family neighbours to join in that will be
even better.

If you any questions, just leave a comment and.

Thank you all!

Recognizing open source community contribution: Champion of the Month Award

At PJSIP we always feel we don’t express our gratitude well enough for all of your contributions to this project, be it comments, criticisms, bug reports, patches, and so on. Especially some people deserves our special thanks for their extra efforts in helping others, or for their perseverance in solving problems (read: bugs) when the going gets though.

Bug of the Month January 2009 Award

This award goes to the most most difficult, most elusive, or perhaps even most silly bug that was found this month. And the award goes to ….

bug #696

Bug #696

Bug #696. This had caused “RTCP clock skew detected” message to appear every now and then in the log and subsequently causing wrong RTT calculation.

What makes this bug a winner is that this has been so elusive that it had been living in the code for two and half years. We were aware of it but simply didn’t know how to fix it!

So our special thanks goes to Guido Fischer for solving this bug. You are smart. 🙂

Bug of the Year 2008 Award

The winner of Bug of The Year 2008 Award goes to …

bug #660

Bug #660

Bug #660, INVITE request is not retried with authentication, even when correct credential is available, if the 401/407 response is received after a 100 or provisional response (!).

This bug really deserves a special award. It is so trivial, and yet it had been living with us for as long as I can remember, it had passed so many tests by us and interop tests with so many products by so many people, and it even slip though undetected in two SIPit events. It simply cannot be more silly than this!

So we thank Bug #660 for truly shaming us all.

Champion of The Month Award

Champion of The Month earns our recognition for achieving expertise, participating in community activities, and sharing their knowledge with other community members in the PJSIP mailing list.  This month we would like to award this to ..

Gang Liu

Gang Liu

Gang Liu, for being actively helping other list members in the past few months, as well as contributing several patches. You have demonstrated your expertise with PJSIP and we as well as I’m sure others have found your contributions to be very valuable. You deserve this award!

This blog hasn’t been updated for sometime

In contrast with the previous post (see says the pjsip blog is a “Growing Blog”), or maybe we’ve become too complacent with it, this blog hasn’t been updated for two months since the last post. Maybe we’ve become too lazy, or too occupied with everything else, I don’t know.

And still I have nothing too interesting to report yet. Symbian is still the main focus of the next release, along with few other new features, but I guess you might have known that from PJSIP Roadmap page.

pjsip project applying for Google Summer of Code 2007

Google Code Logo

UPDATE: The list has been published and we were not accepted. Thank you for participation in the application process, apparently ours just weren’t strong enough.

For those who haven’t heard, we’re applying for Google Summer of Code 2007 (GSoC). We’ve listed our ideas so far, thanks for all the suggestions.

We’re also still accepting applications for mentors, so please don’t hesitate to contact me regarding your availability.

We’ll know on 14 March 2007 whether we are accepted or not, I’ll keep everyone posted.

Increasing visibility of development

Although pjsip as a development process has always been very open, with a public Subversion, Bugzilla and so on, we’d like to improve it even more. We’ve now deployed Trac to replace Bugzilla because it provides better integration with the Subversion repository. Also it gives us the ability to easily provide a pjsip roadmap.

Oh, almost forgot. This blog itself is also going to be one of the main channel to communicate stuff about pjsip development. We hope it will be useful for people who wants to be kept “in the loop” but does not want the traffic of the normal mailing list. And no, an announce-type mailing list won’t do, we need a reason to start a blog. Everybody has one now.

If you got any more ideas for our development process, leave a comment here, or in the mailing list if you are a subscriber, or email.