Module: sip-router
Branch: rbetancor/drouting
Commit: 75837023e6793499720e06cff4a867633e8f21e5
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7583702…
Author: Raul Alexis Betancor Santana <rabs(a)dimension-virtual.com>
Committer: Raul Alexis Betancor Santana <rabs(a)dimension-virtual.com>
Date: Thu Jul 2 21:14:37 2009 +0100
Merge branch 'master' into drouting
* master: (728 commits)
tm: suspended transaction was not always replied and freed
core: fix EXTRA_DEBUG information about second via in parse_msg
nathelper(k): fix for very long payload-type
nathelper (k): fix for flag 'l'
avpops: merge avpops modules
according to Di-Shi are K's and ser's osp module more or less the same, whereas Kamailio's osp module should be more up2date than ser's module. Thus, ser's osp module will be removed and K's osp module will be used as common OSP module.
remove shm_str_dup() from tls_util.[c|h] as it breaks compilation and is not used at all
cfg framework: documentation for cfg_read_var*
Add missed <sys/select.h> include.
cfg framework: read variables by name with a handle
domain: init db connection for RPC process
presence: use event name from parsed structure
core: parse_event - skip first ; for parameters
select_core: fix @ruri.rn_user moving parsed ptr
modules/lcr: fixed printing of lcr_id by lcr.dump_lcrs
carrierroute: port from 1.5 branch, r5885
siputils(k): port from 1.5 branch, r5880
carrierroute: port from 1.5 branch, r5877
carrierroute: port from 1.5 branch, r5876, remove dead code (double return)
registrar(k): port from 1.5 branch, r5873
...
---
Before doing a dissaster .. :-P
How should I merge the rbentancor/drouting branch into the master branch
taking into account that master branch have changes I do not have on drouting
branch.
There are not possible conflicts, because I only worked on the drouting
module, anything more.
--
Raúl Alexis Betancor Santana
Dimensión Virtual
Hello,
within K project, we had from time to time an IRC meeting for short term
planning. IMO it is the time for next one since probably we need at
least a kamailio 1.5.2 release. The place was the irc channel #kamailio
on freenode.net, now we can host it on #sip-router. Presence is not
mandatory and anyone is welcome to join.
From the perspective of K project, here are the topics I would like to
approach:
- kamailio 1.5.2 - show-stoppers, when?
- shall we do another branch 1.4-based release
- kamailio 3.0
- current status
- what is missing, what can be worked-around, prioritizing tasks...
- documentation - migration tutorials
- release roadmap
For sip router:
- logistics: anything missing for project now?
- what can be done to make adoption easier (new tools, etc...)
- suggestions for future development
I propose Tuesday, July 7, 2009, we can adjust to fit the best for the
people that want to attend. I started a wiki page, feel free to add there:
https://sip-router.org/wiki/devel/irc-meetings/2009-07-07
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com/
Revision: 5896
http://openser.svn.sourceforge.net/openser/?rev=5896&view=rev
Author: henningw
Date: 2009-07-07 14:50:00 +0000 (Tue, 07 Jul 2009)
Log Message:
-----------
- fix recently introduced error in postinst, user is called kamailio
- add migration helper preinst for core and radius
- add watch file
Modified Paths:
--------------
branches/1.5/packaging/debian/kamailio.postinst
Added Paths:
-----------
branches/1.5/packaging/debian/kamailio-radius-modules.preinst
branches/1.5/packaging/debian/kamailio.preinst
branches/1.5/packaging/debian/watch
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 5895
http://openser.svn.sourceforge.net/openser/?rev=5895&view=rev
Author: henningw
Date: 2009-07-07 14:26:47 +0000 (Tue, 07 Jul 2009)
Log Message:
-----------
- fix (partly) wrong Changelog update in r5886, this belong to a _new_ release
Modified Paths:
--------------
branches/1.4/ChangeLog
branches/1.5/ChangeLog
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Bob McGilvray (rmcgilvr)
Attached to Project - sip-router
Summary - (kamailio) Modify branch attributes via psuedo variables
Task Type - Feature Request
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - It's not currently possible (in kamailio) to modify the Q value of a branch via psuedo variables and since append_branch doesn't support avps or script variables it's not possible to do at all dynamically (at least from the script itself).
It would be nice to see something along the lines of what was just introduced into opensips, using the $branch(...) pv, or a modification to $br to allow assignment of a Q when creating the branch.
$br = "<sip:" + $avp(s:newuri) + ";q=" + $avp(s:newuri_q);
$(branch(q)[0]) = 1.0;
$(branch(q)[1]) = 0.9;
I apologize if this isn't the right tracker, I'm following a suggestion by someone on the kam users list.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=8
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.
Hi!
Kamailio allows to set the Server: and User-Agent: header in
configuration script.
AFAIS this is not possible in sip-router.
In Kamailio we have the parameters:
user_agent_header and
server_header
I thought about copy/paste from Kamailio, but I think this is not
possible as core is BSD now, not GPL anymore?
regards
klaus
Revision: 5894
http://openser.svn.sourceforge.net/openser/?rev=5894&view=rev
Author: henningw
Date: 2009-07-06 15:27:00 +0000 (Mon, 06 Jul 2009)
Log Message:
-----------
- fix error in module initialization which happened if a custom table name was
configured in carrierroute and also userblacklist
- it was reported as table version mismatch, which was of course really misleading
- many thanks to Uriel Rozenbaum (uriel dot rozenbaum at gmail dot com) for his
help in debugging this problem with a sample cfg and a binary build
Modified Paths:
--------------
branches/1.5/modules/carrierroute/db_carrierroute.h
branches/1.5/modules/userblacklist/db_userblacklist.h
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.