THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Andrey 'Krieger' Utkin (andrey.utkin.2)
Attached to Project - sip-router
Summary - Strange symbols in NOTIFY dialog-info+xml body
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Happy New Year to all!
I notice such things frequently in NOTIFYies generated by Kamailio from my PUBLISHes (injected by MI command).
<code><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="2" ll" entity="sip:1010@192.168.1.113"></code>
This looks to be xml syntax violation, and i think it may be reason why my snom phone does not react to NOTIFY with desired BLF behaviour.
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=25
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.
Module: sip-router
Branch: master
Commit: 2cf0bb2cf1b98ea54c0085a48da27e0db0f9d522
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2cf0bb2…
Author: Carsten Bock <lists(a)bock.info>
Committer: Carsten Bock <lists(a)bock.info>
Date: Wed Jan 6 16:38:04 2010 +0100
According to the docs, stream2uac / stream2uas should accept a "-1" as a valid parameter, in order to repeat forever. With the old conversion, a value of "-1" would be considered invalid.
Credits go to Min Wang (wang(a)basis-audionet.com) for finding and fixing this.
---
modules_k/nathelper/rtpproxy_stream.c | 11 +++++++----
1 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/modules_k/nathelper/rtpproxy_stream.c b/modules_k/nathelper/rtpproxy_stream.c
index 437cc5c..520bd2d 100644
--- a/modules_k/nathelper/rtpproxy_stream.c
+++ b/modules_k/nathelper/rtpproxy_stream.c
@@ -38,7 +38,6 @@
int
fixup_var_str_int(void **param, int param_no)
{
- unsigned long go_to;
int ret;
pv_elem_t *model;
str s;
@@ -57,10 +56,14 @@ fixup_var_str_int(void **param, int param_no)
}
*param = (void *)model;
} else if (param_no == 2) {
- go_to = str2s(*param, strlen(*param), &ret);
- if (ret == 0) {
+ /* According to
+ * http://www.kamailio.org/docs/modules/1.5.x/nathelper.html#rtpproxy_stream2x…
+ * this could be -1 */
+ s.s = (char *)(*param);
+ s.len = strlen(s.s);
+ if (str2sint(&s, &ret)==0) {
pkg_free(*param);
- *param = (void *)go_to;
+ *param = (void *)ret;
} else {
LM_ERR("bad number <%s>\n", (char *)(*param));
return E_CFG;
Revision: 5963
http://openser.svn.sourceforge.net/openser/?rev=5963&view=rev
Author: carstenbock
Date: 2010-01-06 15:34:00 +0000 (Wed, 06 Jan 2010)
Log Message:
-----------
According to the docs, stream2uac / stream2uas should accept a "-1" as a valid parameter, in order to repeat forever. With the old conversion, a value of "-1" would be cosidered invalid.
Credits go to Min Wang (wang(a)basis-audionet.com) for finding and fixing this.
Modified Paths:
--------------
branches/1.5/modules/nathelper/rtpproxy_stream.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Module: sip-router
Branch: kamailio_3.0
Commit: d8af3a4b17bf1ca71df1d977d986f407ff34cfc2
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=d8af3a4…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Wed Jan 6 15:39:46 2010 +0100
tm: documented t_relay_to() function
---
modules/tm/README | 39 +++++++++++++++++++++-
modules/tm/doc/functions.xml | 74 ++++++++++++++++++++++++++++++++++++++++-
2 files changed, 109 insertions(+), 4 deletions(-)
diff --git a/modules/tm/README b/modules/tm/README
index 33125c8..a971836 100644
--- a/modules/tm/README
+++ b/modules/tm/README
@@ -104,6 +104,7 @@ Juha Heinanen
1.5.34. t_set_disable_6xx(0|1)
1.5.35. t_set_disable_failover(0|1)
1.5.36. t_replicate(params)
+ 1.5.37. t_relay_to(proxy, flags)
1.6. TM Module API
@@ -2014,14 +2015,48 @@ route {
# sent to 1.2.3.4:5060 over tcp
t_replicate("sip:1.2.3.4:5060;transport=tcp");
-# sent to 1.2.3.4:5060 over tls
-$var(h) = "1.2.3.4:5060";
+# sent to 1.2.3.4:5061 over tls
+$var(h) = "1.2.3.4:5061";
t_replicate("sip:$var(h);transport=tls");
# sent to 1.2.3.4:5060 over udp
t_replicate_to_udp("1.2.3.4", "5060");
...
+1.5.37. t_relay_to(proxy, flags)
+
+ Forward the SIP request to a specific address, controlling internal
+ behavior via flags.
+
+ There are several function prototypes:
+ * t_relay_to(),
+ * t_relay_to(proxy),
+ * t_relay_to(flags)
+ * t_relay_to(proxy, flags)
+
+ Meaning of the parameters is as follows:
+ * proxy - address where the request should be sent. Format is:
+ "proto:host:port" - any of proto or port can be ommitted, along
+ with the semicolon after or before.
+ * flags - bitmask integer value to control the internal behavior.
+ Bits can be:
+ + 0x01 - do not generate 100 reply.
+ + 0x02 - do not generate reply on internal error (NOTE: has no
+ effect anymore).
+ + 0x04 - disable dns failover.
+
+ Example 74. t_replicate usage
+...
+# sent to 1.2.3.4:5060 over tcp
+t_relay_to("tcp:1.2.3.4:5060");
+
+# sent to 1.2.3.4 over tls
+t_relay_to("tls:1.2.3.4");
+
+# sent to dst URI or R-URI without a 100 reply
+t_relay_to("0x01");
+...
+
1.6. TM Module API
Revision History
diff --git a/modules/tm/doc/functions.xml b/modules/tm/doc/functions.xml
index dc2835d..dc4207c 100644
--- a/modules/tm/doc/functions.xml
+++ b/modules/tm/doc/functions.xml
@@ -1387,8 +1387,8 @@ route {
# sent to 1.2.3.4:5060 over tcp
t_replicate("sip:1.2.3.4:5060;transport=tcp");
-# sent to 1.2.3.4:5060 over tls
-$var(h) = "1.2.3.4:5060";
+# sent to 1.2.3.4:5061 over tls
+$var(h) = "1.2.3.4:5061";
t_replicate("sip:$var(h);transport=tls");
# sent to 1.2.3.4:5060 over udp
@@ -1397,5 +1397,75 @@ t_replicate_to_udp("1.2.3.4", "5060");
</programlisting>
</example>
</section>
+ <section id="t_relay_to">
+ <title>
+ <function>t_relay_to(proxy, flags)</function>
+ </title>
+ <para>
+ Forward the SIP request to a specific address, controlling internal
+ behavior via flags.
+ </para>
+ <para>
+ There are several function prototypes:
+ <itemizedlist>
+ <listitem>
+ <function>t_relay_to()</function>,
+ </listitem>
+ <listitem>
+ <function>t_relay_to(proxy)</function>,
+ </listitem>
+ <listitem>
+ <function>t_relay_to(flags)</function>
+ </listitem>
+ <listitem>
+ <function>t_relay_to(proxy, flags)</function>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>Meaning of the parameters is as follows:</para>
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>proxy</emphasis> - address where the request should
+ be sent. Format is: "proto:host:port" - any of proto or port can be
+ ommitted, along with the semicolon after or before.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>flags</emphasis> - bitmask integer value to control
+ the internal behavior. Bits can be:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>0x01</emphasis> - do not generate 100 reply.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>0x02</emphasis> - do not generate reply on internal
+ error (NOTE: has no effect anymore).
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>0x04</emphasis> - disable dns failover.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ <example>
+ <title><function>t_replicate</function> usage</title>
+ <programlisting>
+...
+# sent to 1.2.3.4:5060 over tcp
+t_relay_to("tcp:1.2.3.4:5060");
+
+# sent to 1.2.3.4 over tls
+t_relay_to("tls:1.2.3.4");
+
+# sent to dst URI or R-URI without a 100 reply
+t_relay_to("0x01");
+...
+ </programlisting>
+ </example>
+ </section>
</section>
Module: sip-router
Branch: kamailio_3.0
Commit: 9cf36478222aaf573a6cd7b65e6a4fd6227eb8cd
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9cf3647…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Tue Jan 5 18:27:46 2010 +0100
snmpstats: fix param type checking
- parameter type is given from definition of params not from modparam
value type, resulting in mismatches for parameters that have
USE_FUNC_PARAM flag set
- reported by Santiago Gimeno
---
modules_k/snmpstats/snmpObjects.c | 2 +-
modules_k/snmpstats/utilities.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/modules_k/snmpstats/snmpObjects.c b/modules_k/snmpstats/snmpObjects.c
index b797317..b9b36af 100644
--- a/modules_k/snmpstats/snmpObjects.c
+++ b/modules_k/snmpstats/snmpObjects.c
@@ -611,7 +611,7 @@ static int set_if_valid_threshold(modparam_t type, void *val, char *varStr,
return -1;
}
- if (type != INT_PARAM) {
+ if (PARAM_TYPE_MASK(type) != INT_PARAM) {
LM_ERR("%s called with type %d instead of %d!\n",
varStr, type, INT_PARAM);
return -1;
diff --git a/modules_k/snmpstats/utilities.c b/modules_k/snmpstats/utilities.c
index 2097f88..9b4011d 100644
--- a/modules_k/snmpstats/utilities.c
+++ b/modules_k/snmpstats/utilities.c
@@ -78,7 +78,7 @@ int stringHandlerSanityCheck( modparam_t type, void *val, char *parameterName)
char *theString = (char *)val;
/* Make sure the function was called correctly. */
- if (type != STR_PARAM) {
+ if (PARAM_TYPE_MASK(type) != STR_PARAM) {
LM_ERR("the %s parameter was assigned a type %d instead of %d\n",
parameterName, type, STR_PARAM);
return 0;