Hello,
this is a call for developers and community users to update the page
collecting upgrade guidelines from current stable (4.0.x) to upcoming
major release (4.1.0):
- https://www.kamailio.org/wiki/install/upgrade/4.0.x-to-4.1.0
If you are aware of a change in the behaviour for some parameters,
functions or statements, list them there.
I added the sql statements for MySQL that will allow to get to the new
database structure. Would be good to have the same for other popular sql
servers (maybe postgres, sqlite ...).
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
Hello,
while trying to create mohqcalls it gives an error:
ERROR 1064 (42000) at line 2: You have an error in your SQL syntax;
check the manual that corresponds to your MySQL server version for the
right syntax to use near 'yyyy-mm-dd hh24:mi:ss')' NOT NULL,
CONSTRAINT mohqcalls_idx UNIQUE (call_id)' at line 8
ERROR: Creating extra tables failed at mohqueue!
The sqlscript is:
CREATE TABLE mohqcalls (
id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL,
mohq_id INT(10) UNSIGNED NOT NULL,
call_id VARCHAR(100) NOT NULL,
call_status INT UNSIGNED NOT NULL,
call_from VARCHAR(100) NOT NULL,
call_contact VARCHAR(100),
call_time DATETIME DEFAULT 'to_date('','yyyy-mm-dd hh24:mi:ss')'
NOT NULL,
CONSTRAINT mohqcalls_idx UNIQUE (call_id)
);
The problem is that the only very recent mysql versions support
functions as default value. Another rather strange for my eye is the
hh24 specifier for the hour, but that can be valid, I haven't checked
the manual as I didn't get that far.
Is the code relying on mysql populating the value with current date? If
yes, it should be changed so that the value is given from the c code --
it is not a big coding effort and it will make it compatible with most
of stable OS distributions out there. The the column definition can be
just to constrain not to be a null value.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
Hello,
being discussed during last Devel IRC Meeting, we are planing to build a
Kamailio Project Technical Administration Group:
https://www.kamailio.org/wiki/devel/irc-meetings/2013blog#technical_adminis…
Its goal is to get a bunch of people that volunteer to do administration
tasks for the project, such as:
- helping with releases (e.g., patch backports, packaging, uploading
files for download, etc)
- doing sysadmin tasks for our servers (e.g., performing upgrades to
wiki, web site, etc)
- preparing technical decisions and doing them (e.g., what applications
to use to make operations easier, cloning git repository to github, ...)
From the devel meeting, so far we have Victor Seva, Fred Posner, Peter
Dunkley and Olle Johansson. Existing people doing admin tasks will
probably stay in (if they don't opt out): me, Elena-Ramona Modroiu,
Henning Westerholt (owner of devel.kamailio.org hardware), Jan Janak
(owner of sip-router.org hardware), Jesus Rodriguez and Oriol Capsada
(owners of kamailio.org hardware).
Requirements for candidates and other details:
- volunteer to do the work, it is not a paid job
- an existing record of activity within the project is a plus (e.g.,
developer, active mailing list member)
- reply to the lists detailing where and how you can help
- possibility to spend 1-4 hours a week for project administration (more
is welcome, sometime is not necessary at all)
Rewards:
- you will be listed as part of project administration on the website
- get to interact more with the project and the nice guys around it ;-)
- more spam - admin list address will be public and the list open so
everyone can send in case of critical situations (content/archive will
be kept private)
Note that we will try to build a group of an adequate size, thus not
everyone willing to participate may get in (at least on the first
phase). One criteria is to have skills that complement existing team
knowledge.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
i made a test call from rtp/avp baresip to rtp/savppf jjsip. at invite,
i made offer
Oct 29 16:45:28 rautu /usr/sbin/sip-proxy[24964]: INFO: ===== making rtpproxy_offer(co1SP+r)
and at 200 ok i made answer:
Oct 29 16:45:36 rautu /usr/sbin/sip-proxy[24959]: INFO: ===== making rtpproxy_answer(co2sp+r)
when handling the answer, mediaproxy-ng wrote to syslog:
Oct 29 16:45:36 rautu mediaproxy-ng[25548]: Error generating SRTP session keys
still the call worked fine and thus generation of the session keys must
have succeeded.
why the error message?
-- juha
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Kristian Høgh (kfhdk)
Attached to Project - sip-router
Summary - Dialog callback on pua_dialoginfo after restart
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - After restarting kamailio, pua_dialoginfo doesn't get updated when active dialogs change status.
I see the dialogs are read from the database, but when they receive eg. BYE the callback are not called.
I use db_mode 0 in pua, but tried mode 2 with no luck.
Should pua_dialoginfo register DLGCB_LOADED?
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=360
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.