Hello,
during the last devel meeting on IRC, done before the summer, we set the
4.2.0 release time frame for this autumn.
As planned by that moment, we have to decide the development freezing
date and more accurate milestones at the end of summer, therefore it is
about the time.
My proposal is to freeze development by end of September 10, 2014, have
about one month of testing and release sometime around mid of October.
If anyone has constraints to meet this date, just send here another
proposal and we can decide together which one fits most of us.
This one gives about 2 weeks and a half for new features development.
Therefore, if you plan to include a new module (many were announced at
the IRC devel meeting, hopefully some are ready), hurry up.
It is also a good time to start filling the wiki page with what is new
in upcoming release:
- http://www.kamailio.org/wiki/features/new-in-devel
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Next Kamailio Advanced Trainings 2014 - http://www.asipto.com
Sep 22-25, Berlin, Germany ::: Oct 15-17, San Francisco, USA
Hello Kamailio Team,
I am using kamailio server successfully for some time now. I have a
specific set of problem. We have a Kamailio Server setup in Amazon EC2
Cloud, the users are able to register on the server and make use of this.
*Now the problem:*
If I am trying to register multiple SIP clients from same
Public_IP:Private_IP (i.e. alice and bob from same computer) on a kamailio
server which is sitting behind Amazon EC2 Cloud Based Server, then only the
first user (who sends REGISTER packet first) is able to register
successfully on the server and all the other users after the first one are
not able to register on the server. Am I missing something in the
configuration file such that this is happening.
Please help in this regard. Waiting in anticipation
Thanks & Best Regards
Saurabh Srivastava
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#444 - FTBFS on powerpcspe because of AltiVec assumption
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: Pushed to master, to be backported soon.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=444
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#448 - usrloc driver error on query: Duplicate entry 'XXXXXXXXXXXX' for key 'ruid_idx'
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=448
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#442 - crash when using append_body_part()
User who did this - Daniel-Constantin Mierla (miconda)
----------
Is this still active? If yes, can you force a core dump to get the backtrace?
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=442#comment1608
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#352 - UAC Module Fail to refresh REGISTER
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=352
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#260 - RPC dns.delete_all doesn't deliver response
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Implemented
Additional comments about closing: Pushed patch to return 'OK' as string in rpc result.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=260
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.