sr-dev June 2014

sr-dev@lists.kamailio.org

21 participants
152 discussions

Re: [sr-dev] DB ERROR using presence status persistence

by Nuno Reis

Could this be a bug in pua? Using kamailio 4.1.3 (642428c) Looking forward to hear from you. BR, -- *Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis(a)wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* [image: Description: Description: WavecomSignature] <http://www.wavecom.pt/pt/wavecom/premios.php> [image: Publicity] <http://www.wavecom.pt/pt/mail_eventos.php> On Tue, Jun 3, 2014 at 3:23 PM, Nuno Reis <nreis(a)wavecom.pt> wrote: > Hi guys. > > I've setup presence management in kamailio and i'm currently persisting > the presence info in a postgres DB. > I'm having a recurring issue on DB key violations, here's a log error > output on that: > > Jun 3 15:09:46 144227 ERROR: pua_dialoginfo [pua_dialoginfo.c:264]: > __dialog_sendpublish(): bad reply or missing CONTACT hdr > Jun 3 15:10:01 723993 ERROR: presence [presentity.c:807]: > update_presentity(): No E_Tag match a.1401768964.671509.1990.6 > Jun 3 15:10:06 242334 WARNING: db_postgres [km_dbase.c:235]: > db_postgres_submit_query(): postgres result check failed with code 7 > (PGRES_FATAL_ERROR) > Jun 3 15:10:06 242370 WARNING: db_postgres [km_dbase.c:239]: > db_postgres_submit_query(): postgres query command failed, connection > status 0, error [ERROR: duplicate key value violates unique constraint > "pua_pua_idx"#012DETAIL: Key (etag, tuple_id, call_id, > from_tag)=(a.1401768964.671497.1902.6, , , ) already exists.#012] > Jun 3 15:10:06 243415 WARNING: db_postgres [km_dbase.c:235]: > db_postgres_submit_query(): postgres result check failed with code 7 > (PGRES_FATAL_ERROR) > Jun 3 15:10:06 243449 WARNING: db_postgres [km_dbase.c:239]: > db_postgres_submit_query(): postgres query command failed, connection > status 0, error [ERROR: duplicate key value violates unique constraint > "pua_pua_idx"#012DETAIL: Key (etag, tuple_id, call_id, > from_tag)=(a.1401768964.671497.1902.6, , , ) already exists.#012] > Jun 3 15:10:06 244458 WARNING: db_postgres [km_dbase.c:235]: > db_postgres_submit_query(): postgres result check failed with code 7 > (PGRES_FATAL_ERROR) > Jun 3 15:10:06 244487 WARNING: db_postgres [km_dbase.c:239]: > db_postgres_submit_query(): postgres query command failed, connection > status 0, error [ERROR: duplicate key value violates unique constraint > "pua_pua_idx"#012DETAIL: Key (etag, tuple_id, call_id, > from_tag)=(a.1401768964.671497.1902.6, , , ) already exists.#012] > Jun 3 15:10:06 244504 ERROR: db_postgres [km_dbase.c:247]: > db_postgres_submit_query(): 0x7f21476b1910 PQsendQuery Error: ERROR: > duplicate key value violates unique constraint "pua_pua_idx"#012DETAIL: > Key (etag, tuple_id, call_id, from_tag)=(a.1401768964.671497.1902.6, , , ) > already exists.#012 Query: update kamailio.pua set > expires=1401807715,cseq=0,etag='a.1401768964.671497.1902.6',desired_expires=1401811600,version=2 > where pres_uri='sip:208@freguesiadearroios.govoice.pt' AND > pres_id='DIALOG_PUBLISH.440163220-35219-52(a)BJC.BGI.B.BAI' AND flag=1024 > AND event=32 > Jun 3 15:10:06 244521 ERROR: <core> [db_query.c:337]: db_do_update(): > error while submitting query > Jun 3 15:10:06 244548 ERROR: db_postgres [km_dbase.c:537]: > db_postgres_store_result(): invalid query, execution aborted > Jun 3 15:10:06 244560 ERROR: db_postgres [km_dbase.c:538]: > db_postgres_store_result(): driver error: PGRES_FATAL_ERROR, ERROR: > duplicate key value violates unique constraint "pua_pua_idx"#012DETAIL: > Key (etag, tuple_id, call_id, from_tag)=(a.1401768964.671497.1902.6, , , ) > already exists.#012 > Jun 3 15:10:06 244584 WARNING: db_postgres [km_dbase.c:647]: > db_postgres_update(): unexpected result returned > Jun 3 15:10:06 244591 ERROR: pua [pua.c:1076]: db_update(): while > updating in database > > > I've read the module documentation, but there isn't much documentation on > it and i'm basically guessing and trying here. > Can someone tell me what am i doing wrong or maybe what should a try to be > able to persist the presence status in a postgres database. > I know that i could use in memory persistence or other type of DB, but i > really want to know if i can use a normal postgres DB for presence > persistence and what could be used to avoid key violations. > > Looking forward to hear from you. > Best Regards, > > -- > > *Nuno Miguel Reis* | *Unified Communication** Systems* > M. +351 913907481 | nreis(a)wavecom.pt > WAVECOM-Soluções Rádio, S.A. > Cacia Park | Rua do Progresso, Lote 15 > 3800-639 AVEIRO | Portugal > T. +351 309 700 225 | F. +351 234 919 191 > *GPS > <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> > | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* > > [image: Description: Description: WavecomSignature] > <http://www.wavecom.pt/pt/wavecom/premios.php> > > [image: Publicity] <http://www.wavecom.pt/pt/mail_eventos.php> > > >

9 years, 11 months

[tracker] Task closed: memory leak in mysql module

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task is now closed: FS#436 - memory leak in mysql module 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=436 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.

9 years, 11 months

git:master: modules/ims_registrar_scscf: updated doc for cxdx_forced_peer

by Jason Penton

Module: sip-router Branch: master Commit: f30f7bf4d723f78546ee2a8db607d80279bdd529 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=f30f7bf… Author: Jason Penton <jason.penton(a)gmail.com> Committer: Jason Penton <jason.penton(a)gmail.com> Date: Tue Jun 3 09:42:41 2014 +0200 modules/ims_registrar_scscf: updated doc for cxdx_forced_peer --- .../doc/ims_registrar_scscf_admin.xml | 19 ++++++++++--------- 1 files changed, 10 insertions(+), 9 deletions(-) diff --git a/modules/ims_registrar_scscf/doc/ims_registrar_scscf_admin.xml b/modules/ims_registrar_scscf/doc/ims_registrar_scscf_admin.xml index 26de7fc..d54561e 100644 --- a/modules/ims_registrar_scscf/doc/ims_registrar_scscf_admin.xml +++ b/modules/ims_registrar_scscf/doc/ims_registrar_scscf_admin.xml @@ -249,7 +249,10 @@ <section> <title>cxdx_forced_peer (string)</title> - <para>Forced HSS Peer to use for CxDx Diameter interface</para> + <para>FQDN of Diameter Peer (HSS) to use for communication (SAR). If you + use this, the routing defined in your diameter xml configuration file + (CDP) will be ignored and as a result you will lose the benefits of load + balancing and failover.</para> <para><emphasis> Default value NULL (none)</emphasis></para> @@ -686,7 +689,7 @@ if (can_subscribe_to_reg("location")){ </programlisting> </example> </section> - + <section> <title><function moreinfo="none">can_publish_reg(domain)</function></title> @@ -731,13 +734,12 @@ if (can_publish_reg("location")){ </programlisting> </example> </section> - + <section> - <title><function - moreinfo="none">publish_reg(domain)</function></title> + <title><function moreinfo="none">publish_reg(domain)</function></title> - <para>Save the publish to the REG event for the UAC or the - appropriate P-CSCF (in the path to the UAC).</para> + <para>Save the publish to the REG event for the UAC or the appropriate + P-CSCF (in the path to the UAC).</para> <para>Meaning of the parameters is as follows:</para> @@ -761,8 +763,7 @@ if (can_publish_reg("location")){ </programlisting> </example> </section> - - </section> + </section> <section> <title>RPC Commands</title>

9 years, 11 months

git:master: modules/ims_qos: updated doc for rx_forced_peer

by Jason Penton

Module: sip-router Branch: master Commit: b957dfd27e5350828f500520af33394806142296 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b957dfd… Author: Jason Penton <jason.penton(a)gmail.com> Committer: Jason Penton <jason.penton(a)gmail.com> Date: Tue Jun 3 09:42:18 2014 +0200 modules/ims_qos: updated doc for rx_forced_peer --- modules/ims_qos/doc/ims_qos_admin.xml | 119 ++++++++++++++++----------------- 1 files changed, 57 insertions(+), 62 deletions(-) diff --git a/modules/ims_qos/doc/ims_qos_admin.xml b/modules/ims_qos/doc/ims_qos_admin.xml index 913d558..43223c3 100644 --- a/modules/ims_qos/doc/ims_qos_admin.xml +++ b/modules/ims_qos/doc/ims_qos_admin.xml @@ -12,12 +12,11 @@ <section> <title>Overview</title> - <para>This module contains all method related to the IMS policy and - charging control functions performed by an Application Function (e.g. - P-CSCF) over the Rx interface. This module is dependent on the CDP (C - Diameter Peer) modules for communicating with PCRF as specified in 3GPP - specification TS 29.214. - </para> + <para>This module contains all method related to the IMS policy and + charging control functions performed by an Application Function (e.g. + P-CSCF) over the Rx interface. This module is dependent on the CDP (C + Diameter Peer) modules for communicating with PCRF as specified in 3GPP + specification TS 29.214.</para> </section> <section> @@ -32,11 +31,11 @@ <listitem> <para>Dialog2</para> </listitem> - + <listitem> <para>Usrloc PCSCF</para> </listitem> - + <listitem> <para>TM - Transaction Manager</para> </listitem> @@ -64,7 +63,7 @@ <section> <title><varname>rx_dest_realm</varname> (string)</title> - <para>This is the name of the Diameter realm of the Diameter server + <para>This is the name of the Diameter realm of the Diameter server (typically a PCRF).</para> <para><emphasis> Default value is 'ims.smilecoms.com'. @@ -80,15 +79,17 @@ modparam("ims_qos", "rx_dest_realm", "ims.smilecoms.com") </programlisting> </example> </section> - + <section> <title><varname>rx_forced_peer</varname> (string)</title> - <para>This is the optional name of the origin host of the Diameter server - (typically a PCRF). If not set then realm routing is used.</para> + <para>FQDN of the Diameter server (typically a PCRF) to communicate + with. If not set then realm routing is used. If you use this, the + routing defined in your diameter xml configuration file (CDP) will be + ignored and as a result you will lose the benefits of load balancing and + failover. </para> - <para><emphasis> Default value is ''. - </emphasis></para> + <para><emphasis> Default value is ''. </emphasis></para> <example> <title><varname>rx_forced_peer</varname> parameter usage</title> @@ -100,15 +101,14 @@ modparam("ims_qos", "rx_forced_peer", "pcrf.ims.smilecoms.com") </programlisting> </example> </section> - + <section> <title><varname>rx_auth_expiry</varname> (integer)</title> - <para>This is the expiry length in seconds of the initiated - Diameter sessions.</para> + <para>This is the expiry length in seconds of the initiated Diameter + sessions.</para> - <para><emphasis> Default value is 7200. - </emphasis></para> + <para><emphasis> Default value is 7200. </emphasis></para> <example> <title><varname>rx_auth_expiry</varname> parameter usage</title> @@ -120,15 +120,14 @@ modparam("ims_qos", "rx_auth_expiry", 14400) </programlisting> </example> </section> - + <section> <title><varname>cdp_event_latency</varname> (integer)</title> - <para>This is a flag to determine whether or slow CDP responses should be - reported in the log file. 1 is enabled and 0 is disabled.</para> + <para>This is a flag to determine whether or slow CDP responses should + be reported in the log file. 1 is enabled and 0 is disabled.</para> - <para><emphasis> Default value is 1. - </emphasis></para> + <para><emphasis> Default value is 1. </emphasis></para> <example> <title><varname>cdp_event_latency</varname> parameter usage</title> @@ -140,18 +139,16 @@ modparam("ims_qos", "cdp_event_latency", 1) </programlisting> </example> </section> - + <section> <title><varname>cdp_event_threshold</varname> (integer)</title> - <para>This time in milliseconds is the limit we should report a CDP - response as slow. i.e. if a CDP response exceeds this limit it will be - reported in the log file. This is only relevant is cdp_event_latency is - enabled (set to 0). - </para> + <para>This time in milliseconds is the limit we should report a CDP + response as slow. i.e. if a CDP response exceeds this limit it will be + reported in the log file. This is only relevant is cdp_event_latency is + enabled (set to 0).</para> - <para><emphasis> Default value is 500. - </emphasis></para> + <para><emphasis> Default value is 500. </emphasis></para> <example> <title><varname>cdp_event_threshold</varname> parameter usage</title> @@ -163,20 +160,19 @@ modparam("ims_qos", "cdp_event_threshold", 500) </programlisting> </example> </section> - + <section> <title><varname>cdp_event_latency_log</varname> (integer)</title> - <para>This time log level at which we should report slow CDP responses. - 0 is ERROR, 1 is WARN, 2 is INFO and 3 is DEBUG. This is only - relevant is cdp_event_latency is enabled (set to 0) - </para> + <para>This time log level at which we should report slow CDP responses. + 0 is ERROR, 1 is WARN, 2 is INFO and 3 is DEBUG. This is only relevant + is cdp_event_latency is enabled (set to 0)</para> - <para><emphasis> Default value is 0. - </emphasis></para> + <para><emphasis> Default value is 0. </emphasis></para> <example> - <title><varname>cdp_event_latency_log</varname> parameter usage</title> + <title><varname>cdp_event_latency_log</varname> parameter + usage</title> <programlisting format="linespecific"> ... @@ -185,21 +181,20 @@ modparam("ims_qos", "cdp_event_latency_log", 1) </programlisting> </example> </section> - </section> <section> <title>Functions</title> <section> - <title><function - moreinfo="none">Rx_AAR_Register(route_block, domain)</function></title> + <title><function moreinfo="none">Rx_AAR_Register(route_block, + domain)</function></title> - <para>Perform a AAR on Diameter RX interface to subscribe to signalling - status. This purpose of this is tell a Diameter server (typically a PCRF) - to inform the requesting Diameter client on changes to the status of - signalling bearer for the same framed IP address. For more details see - 3GGP TS 29.214. </para> + <para>Perform a AAR on Diameter RX interface to subscribe to signalling + status. This purpose of this is tell a Diameter server (typically a + PCRF) to inform the requesting Diameter client on changes to the status + of signalling bearer for the same framed IP address. For more details + see 3GGP TS 29.214.</para> <para>Meaning of the parameters is as follows:</para> @@ -207,8 +202,9 @@ modparam("ims_qos", "cdp_event_latency_log", 1) <listitem> <para>Route block to resume after async UAR Diameter reply.</para> </listitem> + <listitem> - <para><emphasis>domain</emphasis> that usrloc_pcscf uses to store + <para><emphasis>domain</emphasis> that usrloc_pcscf uses to store user information.</para> </listitem> </itemizedlist> @@ -242,28 +238,30 @@ route[REG_AAR_REPLY] </programlisting> </example> </section> - + <section> - <title><function - moreinfo="none">Rx_AAR(route_block, direction)</function></title> + <title><function moreinfo="none">Rx_AAR(route_block, + direction)</function></title> + + <para>Perform a AAR on Diameter RX interface to request resource + authorisation from a Diameter server (typically a PCRF). For more + details see 3GGP TS 29.214.</para> - <para>Perform a AAR on Diameter RX interface to request resource - authorisation from a Diameter server (typically a PCRF). For more details - see 3GGP TS 29.214. </para> - <para>Meaning of the parameters is as follows:</para> <itemizedlist> <listitem> <para>Route block to resume after async UAR Diameter reply.</para> </listitem> + <listitem> - <para><emphasis>direction</emphasis>the direction of this message - + <para><emphasis>direction</emphasis>the direction of this message - orig, term, etc.</para> </listitem> </itemizedlist> - <para>This function can be used from REQUEST_ROUTE or ONREPLY_ROUTE.</para> + <para>This function can be used from REQUEST_ROUTE or + ONREPLY_ROUTE.</para> <para>p.s. this is executed asynchronously. See example on how to retrieve return value</para> @@ -290,10 +288,7 @@ route[ORIGN_SESSION_AAR_REPLY] </programlisting> </example> </section> - - - - </section> + </section> <section> <title>Statistics</title>

9 years, 11 months

git:master: modules/ims_auth: updated docs for cxdx_forced_peer

by Jason Penton

Module: sip-router Branch: master Commit: 50f28af8d9bf4088da44753c3b8e3948aaa9f544 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=50f28af… Author: Jason Penton <jason.penton(a)gmail.com> Committer: Jason Penton <jason.penton(a)gmail.com> Date: Tue Jun 3 09:41:05 2014 +0200 modules/ims_auth: updated docs for cxdx_forced_peer --- modules/ims_auth/doc/ims_auth_admin.xml | 40 +++++++++++++++++++++---------- 1 files changed, 27 insertions(+), 13 deletions(-) diff --git a/modules/ims_auth/doc/ims_auth_admin.xml b/modules/ims_auth/doc/ims_auth_admin.xml index 240c3ef..ca57bd3 100644 --- a/modules/ims_auth/doc/ims_auth_admin.xml +++ b/modules/ims_auth/doc/ims_auth_admin.xml @@ -223,7 +223,10 @@ modparam("ims_auth", "registration_qop", "auth-int") <section> <title><varname>cxdx_forced_peer</varname> (string)</title> - <para>FQDN of Diameter Peer (HSS) to use for communication (MAR)</para> + <para>FQDN of Diameter Peer (HSS) to use for communication (MAR). If you + use this, the routing defined in your diameter xml configuration file + (CDP) will be ignored and as a result you will lose the benefits of load + balancing and failover. </para> <para>Default value is <quote/>.</para> @@ -259,7 +262,8 @@ modparam("ims_auth", "cxdx_dest_realm", "ims.smilecoms.com") <section> <title><varname>max_nonce_reuse</varname> (integer)</title> - <para>Defines, how many times a nonce can be reused (provided nc is incremented)</para> + <para>Defines, how many times a nonce can be reused (provided nc is + incremented)</para> <para>Default value is <quote>0</quote> (don't allow reuse).</para> @@ -277,9 +281,11 @@ modparam("ims_auth", "max_nonce_reuse", 1) <section> <title><varname>add_authinfo_hdr</varname> (integer)</title> - <para>Should an Authentication-Info header be added on 200 OK responses?</para> + <para>Should an Authentication-Info header be added on 200 OK + responses?</para> - <para>Default value is <quote>1</quote> (add Authentication-Info header).</para> + <para>Default value is <quote>1</quote> (add Authentication-Info + header).</para> <example> <title><varname>add_authinfo_hdr</varname> parameter usage</title> @@ -296,9 +302,12 @@ modparam("ims_auth", "add_authinfo_hdr", 0) <title><varname>ignore_failed_auth</varname> (integer)</title> <para>Ignore invalid passwords (only IMPI/IMPU is checked).</para> - <para>It should be used only for testing, e.g. load balancing with SIPP where we don't want to worry about auth.</para> - <para>Default value is <quote>0</quote> (don't ingnore the failed authentication).</para> + <para>It should be used only for testing, e.g. load balancing with SIPP + where we don't want to worry about auth.</para> + + <para>Default value is <quote>0</quote> (don't ingnore the failed + authentication).</para> <example> <title><varname>ignore_failed_auth</varname> parameter usage</title> @@ -314,10 +323,16 @@ modparam("ims_auth", "ignore_failed_auth", 1) <section> <title><varname>av_check_only_impu</varname> (integer)</title> - <para>When storing the authentication vectors for an account, use either IMPI/IMPU (=0, default) or IMPU (=1).</para> - <para>In case the IMPI is different from the IMPU, this option needs to be enabled to allow registration from - classic "SIP-clients", such as Snom phones and others, as they do not send an authentication username in the first REGISTER.</para> - <para>Default value is <quote>0</quote> (store authentication vectors based on IMPI/IMPU).</para> + <para>When storing the authentication vectors for an account, use either + IMPI/IMPU (=0, default) or IMPU (=1).</para> + + <para>In case the IMPI is different from the IMPU, this option needs to + be enabled to allow registration from classic "SIP-clients", such as + Snom phones and others, as they do not send an authentication username + in the first REGISTER.</para> + + <para>Default value is <quote>0</quote> (store authentication vectors + based on IMPI/IMPU).</para> <example> <title><varname>av_check_only_impu</varname> parameter usage</title> @@ -329,9 +344,6 @@ modparam("ims_auth", "av_check_only_impu", 1) </programlisting> </example> </section> - - - </section> <section> @@ -442,6 +454,7 @@ if (!www_authorize("kamailio.org", "subscriber")) { <listitem> <para>Route block to resume after async MAR Diameter reply.</para> </listitem> + <listitem> <para><emphasis>realm</emphasis> - Realm is a opaque string that the user agent should present to the user so he can decide what username @@ -528,6 +541,7 @@ route[REG_MAR_REPLY] <listitem> <para>Route block to resume after async MAR Diameter reply.</para> </listitem> + <listitem> <para><emphasis>realm</emphasis> - Realm is a opaque string that the user agent should present to the user so he can decide what username

9 years, 11 months

git:master: modules/ims_icscf: updated doc for cxdx_forced_peer

by Jason Penton

Module: sip-router Branch: master Commit: 6fa36e1d98a64a9d5d3d40444068fde69dc5b1b3 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=6fa36e1… Author: Jason Penton <jason.penton(a)gmail.com> Committer: Jason Penton <jason.penton(a)gmail.com> Date: Tue Jun 3 09:41:56 2014 +0200 modules/ims_icscf: updated doc for cxdx_forced_peer --- modules/ims_icscf/doc/ims_icscf_admin.xml | 48 +++++++++++++++-------------- 1 files changed, 25 insertions(+), 23 deletions(-) diff --git a/modules/ims_icscf/doc/ims_icscf_admin.xml b/modules/ims_icscf/doc/ims_icscf_admin.xml index aa5573d..4712bbb 100644 --- a/modules/ims_icscf/doc/ims_icscf_admin.xml +++ b/modules/ims_icscf/doc/ims_icscf_admin.xml @@ -55,14 +55,14 @@ <section> <title><varname>route_lir_user_unknown</varname> (string)</title> - <para>This is the route which is executed if HSS returns "user unknown" in LIR - </para> + <para>This is the route which is executed if HSS returns "user unknown" + in LIR</para> - <para><emphasis> Default value is ''. - </emphasis></para> + <para><emphasis> Default value is ''. </emphasis></para> <example> - <title><varname>route_lir_user_unknown</varname> parameter usage</title> + <title><varname>route_lir_user_unknown</varname> parameter + usage</title> <programlisting format="linespecific"> ... @@ -71,19 +71,18 @@ modparam("ims_icscf","route_lir_user_unknown", "lir_term_user_unknown") </programlisting> </example> </section> - + <section> <title><varname>route_uar_user_unknown</varname> (string)</title> - <para>This is the route which is executed if HSS returns "user unknown" - in UAR. - </para> + <para>This is the route which is executed if HSS returns "user unknown" + in UAR.</para> - <para><emphasis> Default value is ''. - </emphasis></para> + <para><emphasis> Default value is ''. </emphasis></para> <example> - <title><varname>route_uar_user_unknown</varname> parameter usage</title> + <title><varname>route_uar_user_unknown</varname> parameter + usage</title> <programlisting format="linespecific"> ... @@ -92,16 +91,14 @@ modparam("ims_icscf","route_uar_user_unknown", "uar_term_user_unknown") </programlisting> </example> </section> - + <section> <title><varname>scscf_entry_expiry</varname> (integer)</title> - <para>This is the time in s after which S-CSCF entries in the I-CSCF's - SCSCF list will expire. - </para> + <para>This is the time in s after which S-CSCF entries in the I-CSCF's + SCSCF list will expire.</para> - <para><emphasis> Default value is 300. - </emphasis></para> + <para><emphasis> Default value is 300. </emphasis></para> <example> <title><varname>scscf_entry_expiry</varname> parameter usage</title> @@ -113,14 +110,16 @@ modparam("ims_icscf","scscf_entry_expiry", 300) </programlisting> </example> </section> - + <section> <title><varname>cxdx_forced_peer</varname> (string)</title> - <para>FQDN of Diameter Peer (HSS) to use for communication (MAR)</para> + <para>FQDN of Diameter Peer (HSS) to use for communication (UAR, LIR). + If you use this, the routing defined in your diameter xml configuration + file (CDP) will be ignored and as a result you will lose the benefits of + load balancing and failover. </para> - <para><emphasis> Default value is "". - </emphasis></para> + <para><emphasis> Default value is "". </emphasis></para> <example> <title><varname>cxdx_forced_peer</varname> parameter usage</title> @@ -215,7 +214,8 @@ I_scscf_drop(); <section> <title><function - moreinfo="none">I_perform_user_authorization_request(route_block, capabalities)</function></title> + moreinfo="none">I_perform_user_authorization_request(route_block, + capabalities)</function></title> <para>Perform a UAR on Diameter CXDX interface. This function will build a list of SCSCFs to be used and populate the SCSCF list for the request. @@ -226,6 +226,7 @@ I_scscf_drop(); <listitem> <para>Route block to resume after async UAR Diameter reply.</para> </listitem> + <listitem> <para>capabilities - whether to request capabilities or not "1" - with capabilities, "0" - no capabilities.</para> @@ -334,6 +335,7 @@ route[SESSION_LIR_REPLY] </example> </section> </section> + <section> <title>Statistics</title>

9 years, 11 months

git:master: modules/ims_charging: updated doc for ro_forced_peer

by Jason Penton

Module: sip-router Branch: master Commit: c95b3e610708178b643db484cdc63f40ac6d8a45 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=c95b3e6… Author: Jason Penton <jason.penton(a)gmail.com> Committer: Jason Penton <jason.penton(a)gmail.com> Date: Tue Jun 3 09:41:29 2014 +0200 modules/ims_charging: updated doc for ro_forced_peer --- modules/ims_charging/doc/ims_charging_admin.xml | 752 ++++++++++++++--------- 1 files changed, 458 insertions(+), 294 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=c95…

9 years, 11 months

git:master: srdb1: fix memory leak in db-id

by Torrey Searle

Module: sip-router Branch: master Commit: 69de17d3bb1d032f9a41752362194d718336e20d URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=69de17d… Author: Torrey Searle <tsearle(a)gmail.com> Committer: Torrey Searle <tsearle(a)gmail.com> Date: Mon Jun 2 19:51:19 2014 +0200 srdb1: fix memory leak in db-id - When getting an existing connection from the pool, free the newly created db-id as the pool connection already has a reference to the existing one. Fixes FS#436 --- lib/srdb1/db.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/lib/srdb1/db.c b/lib/srdb1/db.c index 3eea708..f717464 100644 --- a/lib/srdb1/db.c +++ b/lib/srdb1/db.c @@ -325,6 +325,8 @@ db1_con_t* db_do_init2(const str* url, void* (*new_connection)(), db_pooling_t p pool_insert((struct pool_con*)con); } else { LM_DBG("connection %p found in pool\n", id); + free_db_id(id); // free the new id, as we use the pool instead + id = 0; } res->tail = (unsigned long)con;

9 years, 11 months

[tracker] Comment added: memory leak in mysql module

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#436 - memory leak in mysql module User who did this - Daniel-Constantin Mierla (miconda) ---------- Thanks for troubleshooting further. You can commit the patch. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=436#comment1502 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.

9 years, 11 months

Re: [sr-dev] [SR-Users] app_python not able to import from Router

by Olle E. Johansson

On 02 Jun 2014, at 16:38, Örn Arnarson <orn(a)arnarson.net> wrote: > In lieu of better documentation, perhaps the sample code should be > changed or altogether removed. To sr-dev: Documentation needs an update. /O

9 years, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2014