Vodia PBX Posted April 10, 2007 Report Share Posted April 10, 2007 We have prepared a version 2.0.3. See the release notes at http://wiki.pbxnsip.com/index.php/Release_Notes_2.0.3. Images are available from the following locations (Comment added later: please note that there are new version available today!) http://www.pbxnsip.com/download/pbxctrl-2.0.3.1707.exe (Windows XP) http://www.pbxnsip.com/download/pbxctrl-debian3.1-2.0.3.1707 (Debian 3.1) http://www.pbxnsip.com/download/pbxctrl-rhes4-2.0.3.1707 (RedHat ES4) http://www.pbxnsip.com/download/pbxctrl-suse10-2.0.3.1707 (SuSE10) As far as we can see there are no major issues with this version. However, as usual we recommend to be careful with this update. Especially when you are using SRTP, we ask you to be careful because there was a critical change. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 13, 2007 Author Report Share Posted April 13, 2007 Here we go with the first important fix (the 1707 had a very aggressive DoS protection): http://www.pbxnsip.com/download/pbxctrl-2.0.3.1708.exe (Windows XP) http://www.pbxnsip.com/download/pbxctrl-debian3.1-2.0.3.1708 (Debian 3.1) http://www.pbxnsip.com/download/pbxctrl-rhes4-2.0.3.1708 (RedHat ES4) http://www.pbxnsip.com/download/pbxctrl-suse10-2.0.3.1708 (SuSE10) Quote Link to comment Share on other sites More sharing options...
Andrew D Kirch Posted April 20, 2007 Report Share Posted April 20, 2007 Anything new in 2.0.3? eta for stable release? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 20, 2007 Author Report Share Posted April 20, 2007 2.0.3 has just been moved to the "released" state. It seems to be a great improvement to the 2.0.2, although the 2.0.2 was also not bad. See the (updated) release notes at http://wiki.pbxnsip.com/index.php/Release_Notes_2.0.3. The big bullet points are T.38 fix and SRTP fix. For Linux, the great thing is the strict scheduler usage, in our day-to-day usage that made a big difference regarding jitter. In Windows, we now (again) support Windows 2000 (fingers crossed a little bit). Quote Link to comment Share on other sites More sharing options...
Jan Forcier Posted April 24, 2007 Report Share Posted April 24, 2007 BUG: TZ support It's very useful that time zones are now supported, however, there are only a limited number included. We often have customers in time zones other than the ones listed. I would suggest this should follow the standard which is UTC (GMT) +/- some offset and support any valid zone. Note that in Canada, (and other contries) there are 30 minute offset time zones (UTC -2.5 TZ) Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 25, 2007 Author Report Share Posted April 25, 2007 Can you tell us what timezones that are? Ideally in the PBX timezone format... (see http://wiki.pbxnsip.com/index.php/Localization#Time_Zones). Then we will include it in the next build. It is clear that we don't have all time zones, but don't forget that we want to support multiple zones at the same time and we want to be able to automatically provision them! Quote Link to comment Share on other sites More sharing options...
Jan Forcier Posted May 8, 2007 Report Share Posted May 8, 2007 Can you tell us what timezones that are? Ideally in the PBX timezone format... (see http://wiki.pbxnsip.com/index.php/Localization#Time_Zones). Then we will include it in the next build. It is clear that we don't have all time zones, but don't forget that we want to support multiple zones at the same time and we want to be able to automatically provision them! We require all Canadian time zones, described here: http://www.timetemperature.com/tzca/canada_time_zone.shtml In addtion, we have a number of customer in the middle east so have interest in the following zones http://www.worldtimezone.com/map-time-middle-east24.php Also, a number of people are using our service on the pacific rim: http://www.worldtimezone.com/time-asia24.php As you can see, it would be much easier if all TZ's are supported with a simple UTC offset value which can be set to any valid numeric zone. JF Quote Link to comment Share on other sites More sharing options...
djanjic Posted July 26, 2007 Report Share Posted July 26, 2007 What is the latest supported stable version of the software? Can someone keep the group informed about this? The releases seem to be flying on a daily basis. It is hard to have a confidence in an upgrade unless we know full details of the release. The latest post in the section on versions and updates is dated April 10th and talks about 2.0.3.1707. I am seeing posts which make references to 2.0.4 and 2.0.9. Hard to know what to use??? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted July 26, 2007 Author Report Share Posted July 26, 2007 The 2.0.3.1715 is the latest release. Later builds are builds, but no releases. 1715 seems to be pretty stable and unless you are not missing features there is no need to move to another version. Quote Link to comment Share on other sites More sharing options...
djanjic Posted July 28, 2007 Report Share Posted July 28, 2007 The 2.0.3.1715 is the latest release. Later builds are builds, but no releases. 1715 seems to be pretty stable and unless you are not missing features there is no need to move to another version. We deo not need any new features, we are trying to implement some SOAP applications and we were told that 2.0.2 had some bugs. That is the only reason for upgrade... Quote Link to comment Share on other sites More sharing options...
pbx_admin Posted July 29, 2007 Report Share Posted July 29, 2007 We deo not need any new features, we are trying to implement some SOAP applications and we were told that 2.0.2 had some bugs. That is the only reason for upgrade... Whether or not to make use of the new features, the best bet in your case is to upgrade to 2.0.3.1715. I don't think there were any major SOAP bugs in versions 2.0.2, however we did come across minor socket issues with the latest version (2.0.9.x), although I have managed to work around with that AND we will correct it... Should you encounter *any* SOAP bugs with your implementation, please post it here (http://forum.pbxnsip.com/index.php?showforum=28) and we'll be glad to address your issues ASAP. Happy coding! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.