Hi Bobby,
Thanks for the feedback, see my inline comments.
On 02/11/2013 06:32 PM, Bobby Smith wrote:
1) TCP fixes (async/non-blocking) -- I know these are already on the
list, but as we move more and more traffic to TCP on older versions,
we are seeing reduced performance and odd deadlocks/socket problems
from time to time
yes, this is a bit of a painful matter and it will be addressed in the
next release.
2) better support of RFC 6140 (the gruu fixes that saul mentioned come
to mind)
OK, if you also have examples of cases which do not work, please fill in
some bug reports on SF tracker - it will help the developers in fixing
things.
3) not really related to the release, but representation at SIPNOC
this year would be pretty awesome. A lot of people from the standards
bodies meet here (IETF), and seeing some pursuit around sipconnect
1.1/2.0 would be great for the community IMO as most of the people
here offering competing choices are vendors selling black box
products, however there is asterisk representation and everyone uses
SER in one flavor on their networks :).
Indeed, it will be interested and useful, and I would love to do it if
we find fonds to support the participation to such an event...as OSS
project, there is no much income to help with the participation to
various events.
Best regards,
Bogdan
On Mon, Feb 11, 2013 at 10:38 AM, Saúl Ibarra Corretgé
<[email protected] <mailto:[email protected]>> wrote:
On Feb 11, 2013, at 12:38 PM, Saúl Ibarra Corretgé wrote:
> Hi Bogdan and team,
>
> On Feb 9, 2013, at 7:40 PM, Bogdan-Andrei Iancu wrote:
>
>> Hi all,
>>
>> According the the release policy
(http://www.opensips.org/Development/Development), I would like to
call for a brainstorming, ideas, discussion, etc regarding what
should be the roadmap for OpenSIPS 1.10 - more or less, what new
goodies should be in 1.10 release (next major release).
>>
>> The page is already ready
(http://www.opensips.org/Main/Ver1100) and pre-populated with the
pending items from 1.9 release plus some items from my side .
>>
>>
>> I would like to stat the discussion here, on the mailing list
first, to get from all community ideas on what should be done in
1.10 - things to improve, supporting new RFC/drafts, new
functionalitites, etc.
>>
>> So, please do not be shy and make your points here ;).
>>
>> Also we plan a second round of discussion / selection via an
IRC meeting (probably in 2 weeks or so).
>>
>
> You asked for it :-)
>
> Here are 3 big items I think we should have in OpenSIPS:
>
> 1. Non-blocking TCP operations (this is already on the list)
> 2. "Outbound" support (RFC5626) - supporting this may affect the
design of point 1.
> 3. WebSocket transport
>
> As for bug fixes, there are a few that come to mind:
>
> 1. Proper routing of in-dialog messages when GRUU is used. (the
dialog should remember the path and loose_route should route the
message to the right place even if an AoR is found in the contact,
which happens when GRUU is used. This is a problem if a user
re-registers while on a call and she chooses a different inbound
proxy, as the in-dialog requests would now follow a different path).
> 2. PUA module should refresh outgoing subscriptions until told
otherwise
> 3. presence_xml should validate incoming PIDF documents
(validate them against the schema, that is). Right now it doesn't,
and if a client sends a broken document then the aggregated PIDF
document will also be broken. Those broken docs should not be stored.
>
> I can elaborate on any of the points in case there are any
doubts :-)
>
Oh, since I'm here, let me add one more thing:
- Get rid of the lumps or add a way to apply all pending lumps to
a message manually. This would fix a number of issues that can now
happen, like using engage_mediaproxy and removing the SDP of a 183
response.
Regards,
--
Saúl Ibarra Corretgé
AG Projects
_______________________________________________
Devel mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
