FOSDEM is one of the world's premier meetings of free software developers,
with over five thousand people attending each year. FOSDEM 2016
takes place 30-31 January 2016 in Brussels, Belgium. http://fosdem.org
This email contains information about:
- Real-Time communications dev-room and lounge,
- speaking opportunities,
- volunteering in the dev-room and lounge,
- related events around FOSDEM, including the XMPP summit,
- social events (including the Saturday night dinner),
- the Planet aggregation sites for RTC blogs
Call for participation - Real Time Communications (RTC)
=======================================================
The Real-Time dev-room and Real-Time lounge is about all things involving
real-time communication, including: XMPP, SIP, WebRTC, telephony,
mobile VoIP, codecs, privacy and encryption. The dev-room is a successor
to the previous XMPP and telephony dev-rooms. We are looking for speakers
for the dev-room and volunteers and participants for the tables in the
Real-Time lounge.
The dev-room is only on Saturday, 30 January 2016. The lounge will
be present for both days.
To discuss the dev-room and lounge, please join the FSFE-sponsored
Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc
Speaking opportunities
----------------------
Note: if you used Pentabarf before, please use the same account/username
Main track: the deadline for main track presentations is midnight
today, 30 October. Leading developers in the Real-Time Communications
field are encouraged to consider submitting a presentation to
the main track at https://fosdem.org/submit
Real-Time Communications dev-room: deadline 27 November
Please also use the Pentabarf system to submit a talk proposal for the
dev-room. On the "General" tab, please look for the "Track" option and
choose "Real-Time devroom". https://penta.fosdem.org/submission/FOSDEM16/
Other dev-rooms: some speakers may find their topic is in the scope of more
than one dev-room. It is permitted to apply to more than one dev-room but
please be kind enough to tell us if you do this. You can find the full
list of dev-rooms at https://www.fosdem.org/2016/schedule/tracks/
Lightning talks: deadline 27 November
The lightning talks are an excellent opportunity to introduce
a wider audience to your project. Given that dev-rooms are
becoming increasingly busy, all speakers are encouraged to
consider applying for a lightning talk as well as a slot in the dev-room.
On the "General" tab, please look for the "Track" option and
choose "Lightning Talks". https://fosdem.org/submit
First-time speaking?
--------------------
FOSDEM dev-rooms are a welcoming environment for people who have never
given a talk before. Please feel free to contact the dev-room administrators
personally if you would like to ask any questions about it.
Submission guidelines
---------------------
The Pentabarf system will ask for many of the essential details. Please
remember to re-use your account from previous years if you have one.
In the "Submission notes", please tell us about:
- the purpose of your talk
- any other talk applications (dev-rooms, lightning talks, main track)
- availability constraints and special needs
You can use HTML in your bio, abstract and description.
If you maintain a blog, please consider providing us with the
URL of a feed with posts tagged for your RTC-related work.
We will be looking for relevance to the conference and dev-room themes,
presentations aimed at developers of free and open source software about
RTC-related topics.
Please feel free to suggest a duration between 20 minutes and 55 minutes
but note that the final decision on talk durations will be made by the
dev-room administrators. As the two previous dev-rooms have been
combined into one, we may decide to give shorter slots than in previous
years so that more speakers can participate.
Please note FOSDEM aims to record and live-stream all talks.
The CC-BY license is used.
For any questions, please join the FSFE-sponsored
Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc
Volunteers needed
=================
To make the dev-room and lounge run successfully, we are looking for
volunteers:
- FOSDEM provides video recording equipment and live streaming,
volunteers are needed to assist in this
- organizing one or more restaurant bookings (dependending upon number of
participants) for the evening of Saturday, 30 January
- participation in the Real-Time lounge
- helping attract sponsorship funds for the dev-room to pay for the
Saturday night dinner and any other expenses
- circulating this Call for Participation to other mailing lists
FOSDEM is made possible by volunteers and if you have time to contribute,
please feel free to get involved through https://volunteers.fosdem.org/
Related events - XMPP and RTC summits
=====================================
The XMPP Standards Foundation (XSF) has traditionally held a summit
in the days before FOSDEM. There is discussion about a similar
summit taking place on 28 and 29 January 2016
http://wiki.xmpp.org/web/Summit_19 - please join the mailing
list for details: http://mail.jabber.org/mailman/listinfo/summit
We are also considering a more general RTC or telephony summit,
potentially on 29 January. Please join the Free-RTC mailing list
and send an email if you would be interested in participating,
sponsoring or hosting such an event.
Social events and dinners
=========================
The traditional FOSDEM beer night occurs on Friday, 29 January
On Saturday night, there are usually dinners associated with
each of the dev-rooms. Most restaurants in Brussels are not so
large so these dinners have space constraints. Please subscribe
to the Free-RTC mailing list for further details about the
Saturday night dinner options and how you can register for a seat:
https://lists.fsfe.org/mailman/listinfo/free-rtc
Spread the word and discuss
===========================
If you know of any mailing lists where this CfP would be relevant, please
forward this email. If this dev-room excites you, please blog or microblog
about it, especially if you are submitting a talk.
If you regularly blog about RTC topics, please send details about your
blog to the planet site administrators:
http://planet.jabber.org ralphm(a)ik.nu
http://planet.sip5060.net daniel(a)pocock.pro
http://planet.opentelecoms.org daniel(a)pocock.pro
Please also link to the Planet sites from your own blog or web site.
Contact
=======
For discussion and queries, please join the free-rtc mailing list:
https://lists.fsfe.org/mailman/listinfo/free-rtc
The dev-room administration team:
Daniel Pocock <daniel(a)pocock.pro>
Ralph Meijer <ralphm(a)ik.nu>
Saúl Ibarra Corretgé <saul(a)ag-projects.com>
Iain R. Learmonth <irl(a)debian.org>
Ok, good to know it was solved.
For the records, if you want to have different number of max contact per
user, then you can rely on the xavp configured to registrar xavp_cfg
parameter, e.g.,:
modparam("registrar", "xavp_cfg", "reg")
$xavp(reg=>max_contacts) = 2;
save("location");
Cheers,
Daniel
On 04/11/15 12:23, Marino Mileti wrote:
>
> Thank you Daniel!!
>
> I've removed the 0x04 flag and now works great!!
>
>
>
> Cheers,
>
> Marino
>
>
>
> On 03/11/15 17:30, Daniel-Constantin Mierla wrote:
>
>
>
> Hello,
>
> On 03/11/15 11:29, Marino Mileti wrote:
>
> I would like to avoid multiple registration with the same AOR...
>
> I know that there's a parameter for this (max_contacts) but if I
> set it to 1, all REGISTER overwrite location info.
>
>
> max_contacts will reject new registrations/contacts if there is
> already a valid contact in the location table.
>
> A flag as second parameter to save(...) is the option to overwrite
> existing contact with the one from current registration request.
>
> Cheers,
> Daniel
>
>
>
> Instead i would like to reply with error if a REGISTER arrive with the
> same AOR just registered on location server.
>
>
>
> Is that possible? Any help is appreciated J
>
>
>
> /Marino Maria Mileti/
>
> /marino.mileti(a)alice.it <mailto:marino.mileti@alice.it>/
>
> / /
>
> /cid:006a01cb6b0e$67eecdae$_CDOSYS2.0//Reduce your energy consumption
> and keep polar bears on ice!/
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Avast logo <https://www.avast.com/antivirus>
>
>
>
> Questa e-mail è stata controllata per individuare virus con Avast
> antivirus.
> www.avast.com <https://www.avast.com/antivirus>
>
>
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> --
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
>
>
> ------------------------------------------------------------------------
> Avast logo <https://www.avast.com/antivirus>
>
> Questa e-mail è stata controllata per individuare virus con Avast
> antivirus.
> www.avast.com <https://www.avast.com/antivirus>
>
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
Hello,
On 03/11/15 11:29, Marino Mileti wrote:
>
> I would like to avoid multiple registration with the same AOR...
>
> I know that there's a parameter for this (max_contacts) but if I set
> it to 1, all REGISTER overwrite location info.
>
max_contacts will reject new registrations/contacts if there is already
a valid contact in the location table.
A flag as second parameter to save(...) is the option to overwrite
existing contact with the one from current registration request.
Cheers,
Daniel
>
>
>
> Instead i would like to reply with error if a REGISTER arrive with the
> same AOR just registered on location server.
>
>
>
> Is that possible? Any help is appreciated J
>
>
>
> /Marino Maria Mileti///
>
> /marino.mileti(a)alice.it <mailto:marino.mileti@alice.it>/
>
> / /
>
> /cid:006a01cb6b0e$67eecdae$_CDOSYS2.0//Reduce your energy consumption
> and keep polar bears on ice!/
>
>
>
>
>
> ------------------------------------------------------------------------
> Avast logo <https://www.avast.com/antivirus>
>
> Questa e-mail è stata controllata per individuare virus con Avast
> antivirus.
> www.avast.com <https://www.avast.com/antivirus>
>
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
Hi All,
I am sending 300 REGISTER per second and getting response properly.When I
am sending 50 SUBSCRIBE per second the Kamailio is not responding properly.
Now We are using kamailio-4.2.5 version.
Is there any procedure to increase the performance to handle more SUBSCRIBE
in a second ?
Thanks,
Priyaranjan
> On 03 Nov 2015, at 11:29, Marino Mileti <marino.mileti(a)alice.it> wrote:
>
> I would like to avoid multiple registration with the same AOR...
> I know that there's a parameter for this (max_contacts) but if I set it to 1, all REGISTER overwrite location info.
>
> Instead i would like to reply with error if a REGISTER arrive with the same AOR just registered on location server.
>
> Is that possible? Any help is appreciated J
>
A simple glance at the documentation page for the REGISTRAR shows me a function called “registred”.
http://kamailio.org/docs/modules/4.3.x/modules/registrar.html#registrar.f.r…
"The function returns true if the AOR in the URI is registered, false otherwise. “
If you use that one and refuse a registration if true, you will get exactly what you want.
Reading available documentation is a good thing (TM) :-)
Regards,
/Olle
Looking for some clarification / direction on setting up forking.
I have configured clients to use q-value and is stored in location table. I see several examples as described in TM module documentation but does not mention use of lookup() function.
Per registrar documentation-
lookup()
The functions extracts username from Request-URI and tries to find all contacts for the username in usrloc. If there are no such contacts, -1 will be returned. If there are such contacts, Request-URI will be overwritten with the contact that has the highest q value and optionally the rest will be appended to the message (depending on append_branches parameter value).
Append_branch parameter
The parameter controls how lookup function processes multiple contacts. If there are multiple contacts for the given username in usrloc and this parameter is set to 1, Request-URI will be overwritten with the highest-q rated contact and the rest will be appended to sip_msg structure and can be later used by tm for forking.
Does lookup() build the destination set and then I can proceed by doing t_load_contacts(), t_next_contacts() and setup failure route? Any direction is appreciated!
Thanks,
-dan
Hi List,
I've been reaching a strange thing lately, trying to upgrade to kamailio
4.2.6 ( identical config ):
- 35% loss of performance on TLS connections ( Sipp REGISTER scenario,
easily reproduced ).
- more TCP workers needed to ease the TCP queues ( 32 workers on 3.3.7,
at least 64 are needed on 4.2.6 to avoid "queue full" messages in logs ).
- kamailio 4.2.6 intermittent processing of requests ( Kamailio stops
accepting new tcp connections, then resume a bit later, then stops
again,... ) => starts happening when Kamailio is treating more than 20k
tcp connections, with between 500-1k req/s. During those periods, trying
to connect to kamailio with an openssl s_client -connect will end up in
a timeout or with a long delay before the certificate is received ( 03
CONNECTED ).
- kamailio 4.2.6 dropping connections, kamailio 3.3.7 keeping those
connections: after a while, the number of active connections starts to
decrease on kam4, on kam3 it stays constant.
I was wondering if I was alone in this situation or if someone else is
impacted, has some advices ?
It does not seem to be a config issue, as it is the same that was
deployed with both versions.
Hi friends,
I have configured kamailio to work with rtp proxy and i have followed this
link
http://nil.uniza.sk/sip/kamailio/rtp-proxy-kamailio-32-configuration-debian…
However i am not sure that it is working perfectly or not.
My Question is..
1.Is above link ensures that rtp proxy will work with kamailio or there is
another way to deal with rtp proxy and kamailio?
2.If the above link is successful integration of rtp proxy and kamailio
then how to test it.
Thank you
I would like to avoid multiple registration with the same AOR...
I know that there's a parameter for this (max_contacts) but if I set it to
1, all REGISTER overwrite location info.
Instead i would like to reply with error if a REGISTER arrive with the same
AOR just registered on location server.
Is that possible? Any help is appreciated J
Marino Maria Mileti
<mailto:marino.mileti@alice.it> marino.mileti(a)alice.it
cid:006a01cb6b0e$67eecdae$_CDOSYS2.0Reduce your energy consumption and keep
polar bears on ice!
---
Questa e-mail è stata controllata per individuare virus con Avast antivirus.
https://www.avast.com/antivirus
