Module: sip-router
Branch: master
Commit: 38f8a8e2151337c1515bd50a888c450399a9da9d
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=38f8a8e…
Author: Richard Good <richard.good(a)smilecoms.com>
Committer: Richard Good <richard.good(a)smilecoms.com>
Date: Thu Mar 6 11:00:24 2014 +0200
modules/ims_qos: use cscf_get_public_identity instead of cscf_get_to_uri in ex_aar.c
When getting public identity from To header use ims_getters method instead of reading directly from message
This allows ims_qos to identify subscribers to authorize even when clients add extra info
(e.g. phone context) after the identity in the request URI
---
modules/ims_qos/rx_aar.c | 6 +-----
1 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/modules/ims_qos/rx_aar.c b/modules/ims_qos/rx_aar.c
index 3d7fc22..8d59b69 100644
--- a/modules/ims_qos/rx_aar.c
+++ b/modules/ims_qos/rx_aar.c
@@ -509,11 +509,7 @@ int rx_send_aar(struct sip_msg *req, struct sip_msg *res,
if ((identifier = cscf_get_asserted_identity(res, 0)).len == 0) {
LM_DBG("No P-Asserted-Identity hdr found in response. Using To hdr in resp");
-
- if (!cscf_get_to_uri(res, &identifier)) {
- LM_ERR("Error assigning P-Asserted-Identity using To hdr in resp");
- goto error;
- }
+ identifier = cscf_get_public_identity(res); //get public identity from to header
}
}
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#404 - Coredump on using jsonrpc_request
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=404
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#404 - Coredump on using jsonrpc_request
User who did this - Daniel-Constantin Mierla (miconda)
----------
Looking at the source code, if the function execution was ok, then it does an exit from config. The request is suspended and should not be processed anymore. It will go over it in the case of an internal error. This is how the function was developed, many other functions do internal config exit.
I am closing this one, if you find something else, open a new one.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=404#comment1338
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#397 - Kamailio doesn't to handle any SIP message at all after several dialogs... (CPU high usage)
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Not a bug
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=397
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.
Hello,
we are considering to release new versions from stable branches of
Kamailio starting with Thursday, March 6. First is v4.1.2 from latest
stable branch and if the time allows in the same day, the v4.0.6.
The reason to release v3.3.7 is to have a proper debian packages built
and hosted on the new repositories -- the specs had a conflict for
latest 3.3 version of some sub-packages.
If there are known issues that were not addressed, please report them to
the tracker.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference - April 2-4, 2014, in Berlin, Germany
http://www.kamailioworld.com
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#397 - Kamailio doesn't to handle any SIP message at all after several dialogs... (CPU high usage)
User who did this - Jack Wang (GoGoJack)
----------
I've tested over one day and it still works well - with the right make procedure of compiling kamailio :)
Thanks for your help very much !
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=397#comment1337
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.