Module: kamailio
Branch: master
Commit: b4488aa7d743b7f14bc0232beaa69f3591aa1b66
URL: https://github.com/kamailio/kamailio/commit/b4488aa7d743b7f14bc0232beaa69f3…
Author: Hugh Waite <hugh.waite(a)acision.com>
Committer: Hugh Waite <hugh.waite(a)acision.com>
Date: 2015-05-27T14:33:06+01:00
usrloc: Update documentation concerning xavp_contact parameter
- Note that tm xavp_contact parameter must match
---
Modified: modules/usrloc/README
Modified: modules/usrloc/doc/usrloc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/b4488aa7d743b7f14bc0232beaa69f3…
Patch: https://github.com/kamailio/kamailio/commit/b4488aa7d743b7f14bc0232beaa69f3…
---
diff --git a/modules/usrloc/README b/modules/usrloc/README
index bd5daaa..b0d551a 100644
--- a/modules/usrloc/README
+++ b/modules/usrloc/README
@@ -807,8 +807,10 @@ modparam("usrloc", "timer_procs", 4)
3.34. xavp_contact (string)
- The name of XAVP storring the attributes per contact. They are saved in
- location record and restored at lookup.
+ The name of XAVP storing the attributes per contact. They are saved in
+ location record and restored at lookup. The tm module parameter
+ xavp_contact must also be set to the same value to use the
+ t_load_contacts and t_next_contacts functions.
Default value is "NULL".
diff --git a/modules/usrloc/doc/usrloc_admin.xml b/modules/usrloc/doc/usrloc_admin.xml
index ee569a4..eb5c53d 100644
--- a/modules/usrloc/doc/usrloc_admin.xml
+++ b/modules/usrloc/doc/usrloc_admin.xml
@@ -895,8 +895,10 @@ modparam("usrloc", "timer_procs", 4)
<section id="usrloc.p.xavp_contact">
<title><varname>xavp_contact</varname> (string)</title>
<para>
- The name of XAVP storring the attributes per contact. They are saved
- in location record and restored at lookup.
+ The name of XAVP storing the attributes per contact. They are saved
+ in location record and restored at lookup. The tm module parameter
+ <varname>xavp_contact</varname> must also be set to the same value to use the
+ <varname>t_load_contacts</varname> and <varname>t_next_contacts</varname> functions.
</para>
<para>
<emphasis>
Module: kamailio
Branch: master
Commit: c9adb0fa4a3943999b3350d03c60d4d8c884584b
URL: https://github.com/kamailio/kamailio/commit/c9adb0fa4a3943999b3350d03c60d4d…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2015-06-11T10:10:50+02:00
core: fixed typo of year in README
- reported by Anthony Messina
---
Modified: README
---
Diff: https://github.com/kamailio/kamailio/commit/c9adb0fa4a3943999b3350d03c60d4d…
Patch: https://github.com/kamailio/kamailio/commit/c9adb0fa4a3943999b3350d03c60d4d…
---
diff --git a/README b/README
index afb147e..6d9992b 100644
--- a/README
+++ b/README
@@ -90,7 +90,7 @@ Kamailio.org and SIP Express Router (SER) from iptel.org.
Kamailio is the result of a merge of the code base and years of experience from
both developer teams. During the development of the release 4.0, autumn-winter
-of 201w, the merger of the products was completed and a unified product was
+of 2012, the merger of the products was completed and a unified product was
released.
See http://www.kamailio.org/ for the story of SER, OpenSER and Kamailio.
Hello,
I am looking for some recommendations on how to move forward with
asynchronous call processing.
Our adoption and standardisation of async processing in >= 4.2 into our
core product has been a disaster. I don't mean that to sound accusatory;
it's open source, there's no reason to blame anyone. It's just a matter
of fact.
1) We can't use async_task_route()/the standard async task worker
approach in the 'async' module because of this problem, which both Olle
and I have reported:
http://sr-dev.sip-router.narkive.com/5Sfc5cUU/async-module-cpu-load
Most users run Kamailio inside a VM and the problem shows up for ~50% of
them.
2) Using t_suspend -> mqueue -> rtimer -> t_continue(), we continue to
see deadlocks and occasional crashes. They are rare, and are most likely
to happen in high-throughput, short-duration environments, but when they
do happen, they're politically disastrous. We've had to roll back use of
this method of async processing for pretty much all customers for whom
it was enabled.
After the last time we visited this issue earlier this spring, the
problem has shifted away from crashes and mostly toward deadlocks.
Regardless, the customer's enthusiasm for pausing call processing long
enough to attach a debugger and grab a backtrace or something like that
is exactly 0.0%. I think most of them have more of an enthusiasm for
firing us as a vendor than for doing any diagnostic work.
I know there's a way to invoke a process in such a way that when it
crashes, gdb auto-attaches and pulls a backtrace, then restarts the
process. I've written such a wrapper script before in the distant past.
I just don't remember how to do it, especially with modern versions of
GDB; any suggestions would be appreciated.
Otherwise, I don't really know what to do. We need async processing for
higher-CPS systems, and would like to standardise upon it in principle,
but so far it has, from a strictly functional point of view, been an
enormous economic blunder.
I still prefer to be an "early adopter" of such novelties - when useful
- in high-volume production systems in order to contribute the testing
and feedback back to the project. But I have to strike some realistic
balance here and not lose the customers. :-)
Thanks!
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Module: kamailio
Branch: master
Commit: 9d87603ca0f8a7d1df62cb776fe8dc7558f2f3bf
URL: https://github.com/kamailio/kamailio/commit/9d87603ca0f8a7d1df62cb776fe8dc7…
Author: Robert Boisvert <rdbprog(a)gmail.com>
Committer: Robert Boisvert <rdbprog(a)gmail.com>
Date: 2015-06-05T18:56:21-04:00
* support Route in REFER/BYE
* added stop_stream ()
* updated copyright
* added trailing linefeed to LM_* () messages
* add create call strings into buffer
* drop calls that to respond to REFER
* changed Referred-By to mohqueue
* added TRYING status
* only INVITE can come in w/o to tag
* use TM for first reply on INVITE
* changed the way messages are entered into the queue
* 180 Ringing not sent if not required
---
Modified: modules/mohqueue/mohq.c
Modified: modules/mohqueue/mohq.h
Modified: modules/mohqueue/mohq_common.h
Modified: modules/mohqueue/mohq_db.c
Modified: modules/mohqueue/mohq_db.h
Modified: modules/mohqueue/mohq_funcs.c
Modified: modules/mohqueue/mohq_funcs.h
Modified: modules/mohqueue/mohq_locks.c
Modified: modules/mohqueue/mohq_locks.h
---
Diff: https://github.com/kamailio/kamailio/commit/9d87603ca0f8a7d1df62cb776fe8dc7…
Patch: https://github.com/kamailio/kamailio/commit/9d87603ca0f8a7d1df62cb776fe8dc7…
* support Route in REFER/BYE
* added stop_stream ()
* updated copyright
* added trailing linefeed to LM_* () messages
* add create call strings into buffer
* drop calls that to respond to REFER
* changed Referred-By to mohqueue
* added TRYING status
* only INVITE can come in w/o to tag
* use TM for first reply on INVITE
* changed the way messages are entered into the queue
* 180 Ringing not sent if not required
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/197
-- Commit Summary --
* * support Route in REFER/BYE
-- File Changes --
M modules/mohqueue/mohq.c (173)
M modules/mohqueue/mohq.h (28)
M modules/mohqueue/mohq_common.h (10)
M modules/mohqueue/mohq_db.c (28)
M modules/mohqueue/mohq_db.h (4)
M modules/mohqueue/mohq_funcs.c (1011)
M modules/mohqueue/mohq_funcs.h (4)
M modules/mohqueue/mohq_locks.c (10)
M modules/mohqueue/mohq_locks.h (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/197.patchhttps://github.com/kamailio/kamailio/pull/197.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/197