Module: kamailio
Branch: master
Commit: 9f92b33c5eb35c32e5d07789bac86e850dfd0d83
URL: https://github.com/kamailio/kamailio/commit/9f92b33c5eb35c32e5d07789bac86e8…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2015-03-26T21:19:49+01:00
presence: option to set priority for presentity documents
- xavp_cfg - new parameter to specify the name of xavp use to store
attributes for publish processing
- priority can be set inside xavp_cfg with $xavp(xavp_cfg=>priority)
- priority is stored in a new column inside database table presentity
for each publish that has the xavp set
- retrieve_order - new parameter to specify the order to retrieve the
records from database. Default value is 0 (retrieve by received_time
like so far). If set to 1, retrieve by priority value
- if xavp_cfg parameter is set but priority field inside it is not, then
inside the database is stored a value based on timestamp so the newest
records will have a higher value, preserving the old behaviour even
the retrieve_order=1
---
Modified: modules/presence/notify.c
Modified: modules/presence/notify.h
Modified: modules/presence/presence.c
Modified: modules/presence/presence.h
Modified: modules/presence/presentity.c
Modified: modules/presence/presentity.h
---
Diff: https://github.com/kamailio/kamailio/commit/9f92b33c5eb35c32e5d07789bac86e8…
Patch: https://github.com/kamailio/kamailio/commit/9f92b33c5eb35c32e5d07789bac86e8…
Hello Daniel,
I have RCS based client.
I would like to implement MUC(multi chat user) in existing Kamailio IMS
Server.
Please help me to input the procedure.Is it really possible to do it ?
Please share me URL for any existing "C" source code which I can directly
imbibe into Kamailio IMS server.
--
View this message in context: http://sip-router.1086192.n5.nabble.com/Regarding-multi-user-chat-in-Kamail…
Sent from the Development mailing list archive at Nabble.com.
adds 3rd parameter to registered to optionally restrict the contacts
adds module parameter to optionally
add contact xavp on successful match when calling registered
add contact xavp to the $ulc structure
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/101
-- Commit Summary --
* registrar - add registered extra parameter
-- File Changes --
M modules/registrar/api.c (2)
M modules/registrar/lookup.c (66)
M modules/registrar/lookup.h (2)
M modules/registrar/reg_mod.c (88)
M modules/registrar/reg_mod.h (8)
M modules/registrar/regpv.c (313)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/101.patchhttps://github.com/kamailio/kamailio/pull/101.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/101
Hi all
I'd like to know if kamailio is creating SHA-2 certificates by default for the
TLS module. I'd say no but not 100% sure.
Checking kamctl and provided ca.conf seem like Kamailio creates a SHA-1
cert by default. Should we modify that default?
More info: https://shaaaaaaaaaaaaa.com/
cheers,
Jon
Module: kamailio
Branch: master
Commit: 0ee3dc5e3edc49cf62f97ddd87a40b12c59b73ff
URL: https://github.com/kamailio/kamailio/commit/0ee3dc5e3edc49cf62f97ddd87a40b1…
Author: jaybeepee <jason.penton(a)gmail.com>
Committer: jaybeepee <jason.penton(a)gmail.com>
Date: 2015-03-20T13:29:34+02:00
modules/tm: restore code to set blind uac branch last_reply > 200
---
Modified: modules/tm/t_suspend.c
---
Diff: https://github.com/kamailio/kamailio/commit/0ee3dc5e3edc49cf62f97ddd87a40b1…
Patch: https://github.com/kamailio/kamailio/commit/0ee3dc5e3edc49cf62f97ddd87a40b1…
---
diff --git a/modules/tm/t_suspend.c b/modules/tm/t_suspend.c
index 4abfe72..cc4dd61 100644
--- a/modules/tm/t_suspend.c
+++ b/modules/tm/t_suspend.c
@@ -215,10 +215,15 @@ int t_continue(unsigned int hash_index, unsigned int label,
return 1;
}
- /*we really don't need this next line anymore otherwise we will
- never be able to forward replies after a (t_relay) on this branch.
- We want to try and treat this branch as 'normal' (as if it were a normal req, not async)' */
- //t->uac[branch].last_received=500;
+ /* Set last_received to something >= 200,
++ * the actual value does not matter, the branch
++ * will never be picked up for response forwarding.
++ * If last_received is lower than 200,
++ * then the branch may tried to be cancelled later,
++ * for example when t_reply() is called from
++ * a failure route => deadlock, because both
++ * of them need the reply lock to be held. */
+ t->uac[branch].last_received=500;
uac = &t->uac[branch];
}
/* else