THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Juha Heinanen (jh)
Attached to Project - sip-router
Summary - infinit loop in sdp parser
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - High
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - this bug exists also in sip router:
Revision: 8377
http://opensips.svn.sourceforge.net/opensips/?rev=8377&view=rev
Author: bogdan_iancu
Date: 2011-09-21 17:42:32 +0000 (Wed, 21 Sep 2011)
Log Message:
-----------
- fixed bug leading into infit looping over the same character if the SDP 'c' line is malformed
This is a dangerous bug as it can be used to attack and exploit opensips with malformed pacakges.
Credits for reporting and fix go to Christophe Sollet
Modified Paths:
--------------
trunk/parser/sdp/sdp_helpr_funcs.c
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=160
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.
A user has added themself to the list of users assigned to this task.
FS#160 - infinit loop in sdp parser
User who did this - Juha Heinanen (jh)
http://sip-router.org/tracker/index.php?do=details&task_id=160
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.
Hello,
since I am attending GSoC'11 Mentors Summit and come to Bay Area again,
it is time to bring the developer training in USA, therefore I am
planning to organize a two-day seminar focused on developing Kamailio
extensions in C.
Among topics to be approached:
- internal architecture
- SIP parser
- memory manager
- locking manager
- database API
- config file language interpreter
- RPC interface
- pseudo-variables and transformations framework
- module interface – write your own extensions in C as modules
- inter-module APIs - tm, presence, a.s.o.
- documentation docbook format
This kind of training follows the pattern from the past, trying to keep
a low attendee fee, targeting just to cover the expenses with the
organization. I am discussing with several people for a good location at
a convenient price, however, I am open for new alternatives, including
companies/institutes that want to host the event at no cost in exchange
of sending few attendees free of charge. Contact me if you can help here.
Training is planned for October 24-25, right now the estimated fee per
participant is 350USD (it will not exceed 400USD). The policy to accept
people is first come, first served.
You can register at this time to reserve your seat(s), emailing to me or
to registration(a)kamailio.org. Number of seats is usually 10 to 20, last
one organized in February in Barcelona filled up quickly. Once there
will be enough interested people and a location selected, I will have
more precise details regarding the participation to this seminar and I
will send updates.
Looking forward to meeting many of you and get new US developers on
board of the project in the near future.
Cheers,
Daniel
--
http://www.kamailio.org/w/daniel-constantin-mierla/
opensips as persence_xcapdiff module that allows users to subscribe
changes in xcap documents and xcap server to publish such changes via mi
interface.
any interest in adding xcap diff support to sip router and in its xcap
server?
-- juha
Hello list,
last week I switched to a new mysql table structure for the LCR module.
Because of proper permission management and mapping of our internal
structures to kamailio's structures we are using mysql views.
When I tried to run kamailio with the new settings the column type check
failed, even if the view worked with the mysql "CONVERT" function to
convert the output to what kamailio expects.
So I thought about a module-specific or server-wide setting to
skip/ignore the column-type check...
Jasmin
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#159 - Default expires value in dialog-info
User who did this - Sebastian Zaprzalski (-sz-)
http://sip-router.org/tracker/index.php?do=details&task_id=159
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.
A new Flyspray task has been opened. Details are below.
User who did this - Sebastian Zaprzalski (-sz-)
Attached to Project - sip-router
Summary - Default expires value in dialog-info
Task Type - Bug Report
Category - dialog
Status - Assigned
Assigned To - Timo Reimann
Operating System - Linux
Severity - Very Low
Priority - Normal
Reported Version - 3.1
Due in Version - Undecided
Due Date - Undecided
Details - PUA_DIALOGINFO should take Expires value form DIALOG module. It should take value form default_timeout param or from AVP set in timeout_avp param.
If you don't use timeout_avp and use only default_timeout, it doen't work correctly:
Sep 19 12:19:16 node00 /usr/sbin/kamailio[21476]: DEBUG: pua_dialoginfo [dialog_publish.c:51]: publ:
Sep 19 12:19:16 node00 /usr/sbin/kamailio[21476]: DEBUG: pua_dialoginfo [dialog_publish.c:52]: uri= sip:testcrx2sternikp@sip.dev.avecezar.org
Sep 19 12:19:16 node00 /usr/sbin/kamailio[21476]: DEBUG: pua_dialoginfo [dialog_publish.c:53]: id= DIALOG_PUBLISH.a588b393-26a4666(a)192.168.2.23
Sep 19 12:19:16 node00 /usr/sbin/kamailio[21476]: DEBUG: pua_dialoginfo [dialog_publish.c:54]: expires= 0
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=159
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.