Module: sip-router
Branch: master
Commit: 74641106779c13fa2f6bf2384293e35dc21f3b5a
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=7464110…
Author: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Committer: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Date: Mon Jun 11 22:39:10 2012 +0100
pkg/kamailio/fedora/16: Updated ver and rel in .spec to 3.4.0 and dev0
---
pkg/kamailio/fedora/16/kamailio.spec | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/pkg/kamailio/fedora/16/kamailio.spec b/pkg/kamailio/fedora/16/kamailio.spec
index ac3ca9f..ecd9405 100644
--- a/pkg/kamailio/fedora/16/kamailio.spec
+++ b/pkg/kamailio/fedora/16/kamailio.spec
@@ -1,6 +1,6 @@
%define name kamailio
-%define ver 3.3.0
-%define rel pre3%{dist}
+%define ver 3.4.0
+%define rel dev0%{dist}
%define _sharedir %{_prefix}/share
@@ -941,6 +941,8 @@ fi
%changelog
+* Mon Jun 11 2012 Peter Dunkley <peter(a)dunkley.me.uk>
+ - Updated ver to 3.4.0 and rel to dev0
* Mon Jun 4 2012 Peter Dunkley <peter(a)dunkley.me.uk>
- Added a number of %dir lines to make sure the RPMs are properly cleaned up
on uninstall
Hello list.
I am developing a module that keeps track of all calls passing through the
server. The goal is to maintain a state in order to be able to hang up the
calls that run out of credit when the time comes. The module makes use of
the tm public interface and shared memory mechanism to maintain all the
relevant data in shared memory and precisely this was the motivation for
building this module from scratch instead of writing a client for the
dialog module with an external app doing the credit control logic and a
MySQL database in the backend.
Basically, this is how it works:
- In the config script it receives a unique identifier of the client along
with the credit available for it and the discount that should be made every
second.
- A loop iterates over the current calls and when the credit is exhausted,
a BYE message is sent to both legs.
- Everything is kept in shared memory, no need to having an external
database nor dialog module.
- It is transaction-oriented.
The project needs to implement some business-specific (private) logic and
before that to happen I would like to know if the raw version of the
module, with its features, could be useful to the community?, or I just
reinvented the wheel?
Regards.
Carlos.
Hello,
GIT branch 3.3 was created to hold the release series 3.3.x -- version
3.3.0 will be out in max. 1 week, a decision after collecting eventual
issues still open to be reported today.
Here are few details about how to use it.
Download and use branch 3.3 from git:
git clone --depth 1 git://git.sip-router.org/sip-router kamailio
cd kamailio
git checkout -b 3.3 origin/3.3
Pushing patches:
- only bug fixes or documentation improvements have to be committed
to branch 3.3
- first commit to master branch (if the bug applies there as well),
cherry-pick the commit to branch 3.3 and push to remote repository
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
Hello,
short note to let everyone know that new features can be committed again
to the master branch -- they will be part of future version 3.4.0 (if no
other numbering release will be decided).
Testing phase of version 3.3.0 within master is ended, a dedicated
branch being created for it (details in a separate message).
Happy coding,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
Hello,
I am going to create the GIT branch 3.3 in short time -- this branch
will be used for releasing 3.3.x versions.
After that master can take again commits of new features, to be part of
next major release 3.4.x. Branch 3.3 will take only fixes.
From my point of view, I have two issues that I am trying to solve and
the 3.3.0 is ready to go out, namely:
- a solaris sigbus
- pua_dialoginfo issue reported on mailing list
Otherwise, nothing else critcal is out there, to my knowledge. Report
them if you have other ones. Packaging specs were updated, so we are
pretty much ready to release when no relevant issues is open.
The wiki page with what is new in this release was updated a bit as
well, add if you find something missing at:
- http://www.kamailio.org/wiki/features/new-in-devel
Also, contribute to the upgrade guidelines:
- http://www.kamailio.org/wiki/install/upgrade/3.2.x-to-3.3.0
Cheer,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw