sr-dev January 2009

sr-dev@lists.kamailio.org

3 participants
3 discussions

FOSDEM 2009 - Kamailio (OpenSER)/SIP-Router Social Networking Event

by Daniel-Constantin Mierla

Hello, a bunch of us will be at FOSDEM 2009: http://fosdem.org/2009/ Therefore is the opportunity for first Social Networking Event in 2009. Everyone interested in Kamailio (OpenSER), SIP Router, SER, SIP and not only are invited to join -- participation is free, everybody pays for its expenses. The event is very likely to be a dinner on Saturday evening, Feb 7, 2009. So far, from Kamailio (OpenSER) community you can meet there: - Henning Westerholt - http://www.kamailio.org/mos/view/Management/ - Elena-Ramona Modroiu - http://www.kamailio.org/mos/view/Management/ - Daniel-Constantin Mierla - http://www.kamailio.org/mos/view/Management/ - Dan Bogos - http://itsyscom.com/ In order to know properly the size of the place we need, please drop me an email if you intend to attend. People knowing Brussels are welcome to suggest a nice place to meet (good beer and food are a must). Looking forward to meeting you in Brussels. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

15 years, 9 months

Any usable release up to now?

by Anto

Dear All, I wanted to seriously use OpenSER last September, but I dropped it after I read all the disputes. And for some reasons, I don't want to use SER or OpenSIPS. It looks to me that this SIP Router project is more promising especially for long run. Now to the question. It looks to me there is no useable release of SIP Router up to now. Is that right? If so, when could we have the merged release of Kamailio and SER? Kind regards, Anto

15 years, 10 months

compare uri and aor

by Daniel-Constantin Mierla

Hello, this should be valueable for sip-router.org as well. I have introduced in siputils module of Kamailio functions to compare SIP URI and AoR in a more RFC manner, related to: https://sourceforge.net/tracker/index.php?func=detail&aid=2047019&group_id=… Now, for URI it does comparison of: - username - password - hostname - port For AoR, it does: - username - hostname - port (if port is missing, it assumes 5060 -- for URI comparison this is not used, conform to RFC3261) The questions are: - shall the comparison for URI be extended to follow full RFC? could get complex when taking URI headers in account -- haven't seen many, but the RFC allow them. Where to stop then the rules for comparing the URI? - for AoR, I am not sure if port should be considered, but when running multiple instances on different ports, it may make the difference? What do you think? Has SER now dedicated functions to match AoRs and URIs? Cheers, Daniel

15 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev January 2009