Module: sip-router
Branch: master
Commit: 91123f6c510e3fc127adaa1b4ffa1adba4a1a287
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=91123f6…
Author: Carsten Bock <carsten(a)ng-voice.com>
Committer: Carsten Bock <carsten(a)ng-voice.com>
Date: Tue Dec 2 21:22:56 2014 +0100
ims_qos: Updated example-config and documentation for the Rx-Interface
---
examples/pcscf/kamailio.cfg | 27 ++++++++++++++++++++++++---
modules/ims_qos/doc/ims_qos_admin.xml | 16 ++++++++++++++++
2 files changed, 40 insertions(+), 3 deletions(-)
diff --git a/examples/pcscf/kamailio.cfg b/examples/pcscf/kamailio.cfg
index 21a0146..c09cdc9 100644
--- a/examples/pcscf/kamailio.cfg
+++ b/examples/pcscf/kamailio.cfg
@@ -795,8 +795,25 @@ route[REGISTER] {
#!ifdef WITH_RX
xlog("L_DBG","Subscribing to signalling bearer status\n");
- if (Rx_AAR_Register("REG_AAR_REPLY", "location") == 0)
- exit;
+
+ Rx_AAR_Register("REG_AAR_REPLY", "location");
+ switch ($retcode) {
+ case -1:
+ # There was an error sending the AAR-Request:
+ xlog("L_ERR", "Diameter: AAR failed on subscription to signalling\n");
+ send_reply("403", "Can't register to QoS for signalling");
+ exit;
+ break;
+ case 0:
+ # We are waiting for an async reply, just exit here.
+ exit;
+ break;
+ case 1:
+ # We did not need to send AAR, so just continue as normal
+ route(REGISTER_CONTINUE);
+ break;
+ }
+ exit;
}
route[REG_AAR_REPLY] {
@@ -809,8 +826,12 @@ route[REG_AAR_REPLY] {
send_reply("403", "Can't register to QoS for signalling");
exit;
}
-#!endif
+ # Proceed with Registering:
+ route(REGISTER_CONTINUE);
+}
+route[REGISTER_CONTINUE] {
+#!endif
#!ifndef WITH_SBC
#!ifdef WITH_WEBSOCKET
if (($Rp == MY_WS_PORT || $Rp == MY_WSS_PORT) && (proto == WS || proto == WSS)) {
diff --git a/modules/ims_qos/doc/ims_qos_admin.xml b/modules/ims_qos/doc/ims_qos_admin.xml
index 726e441..05f76c5 100644
--- a/modules/ims_qos/doc/ims_qos_admin.xml
+++ b/modules/ims_qos/doc/ims_qos_admin.xml
@@ -229,6 +229,22 @@ modparam("ims_qos", "authorize_video_flow", 0)
</listitem>
</itemizedlist>
+ <para>Return codes:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>-1</emphasis> - error: There was an error, so we must either ignore it (no subscription) or send 403 (depends on behaviour you want)
+ </para>
+ <para>
+ <emphasis>0</emphasis> - Success: AAR-Request sent, reply is processed asynchronously.
+ </para>
+ <para>
+ <emphasis>1</emphasis> - Success: No need to send AAR-Request, as a subscription still exists (continue as normal)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+
<para>This function can be used from REQUEST_ROUTE.</para>
<para>p.s. this is executed asynchronously. See example on how to
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#496 - Dialog state changed after restart Kamailio for db_mode=REALTIME
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Not a bug
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=496
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#496 - Dialog state changed after restart Kamailio for db_mode=REALTIME
User who did this - Seudin Kasumovic (seudin)
----------
The problem was in "ref_count = 2". The issue was caused by custom module. Please close.
Thanks,
Seudin
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=496#comment1715
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,
I have been debugging a memory leak and found that since the default memory manager was changed to F_MALLOC, I can't dump the used fragments using "kamcmd cfg.seti core mem_dump_pkg 12345" I assume this is due to the commented code in mem/f_malloc.c:769. Is there any reason for not uncommenting it?
Also, the leak troubleshooting guide at http://www.kamailio.org/dokuwiki/doku.php/troubleshooting:memory doesn't cover F_MALLOC - but I can start porting this to the new wiki.
Hugh
________________________________
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#495 - Kamailio Crash in WEBSOCKET module
User who did this - Daniel-Constantin Mierla (miconda)
----------
Cannot test that for you, the code you are using it is old. As said, you should use the latest stable in 4.1 or 4.2 branches, specially that it has fixes to the module you reported. If you have an issue with latest stable, it can be investigated, otherwise in an old version an issue can be a matter of side effects from something already fixed.
I am closing this item on the tracker, re-open in case of troubles with the latest stable versions.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=495#comment1714
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.