Hello,
following some discussions on users mailing list, seems we may get a
group of people willing to digest documentation and contribute to
modules' readme or wiki pages. Hopefully Alex Balashov (who volunteered
so far) would have some time to coordinate contributions to git docs,
for wiki being easier, as anyone has access.
I am willing to help as much I can, but time is always a constraint for
a dev. I invite you to join IRC channel #sip-router hosted on
freenode.net to plan an synchronize easier.
Thanks,
Daniel
--
Daniel-Constantin Mierla
* http://www.asipto.com/
i'm in branch 'master' and pull it to up to date:
jh@rautu:/usr/src/orig/sip-router$ eg switch master
Already on "master"
Your branch is behind the tracked remote branch 'origin/master' by 283 commits,
and can be fast-forwarded.
jh@rautu:/usr/src/orig/sip-router$ eg pull
remote: Counting objects: 176, done.
remote: Compressing objects: 100% (108/108), done.
remote: Total 109 (delta 70), reused 0 (delta 0)
Receiving objects: 100% (109/109), 45.86 KiB, done.
Resolving deltas: 100% (70/70), completed with 29 local objects.
>From ssh://jh@git.sip-router.org/sip-router
ea1f8a2..77523f3 andrei/cdefs2doc -> origin/andrei/cdefs2doc
e6eceeb..f572564 kamailio_3.0 -> origin/kamailio_3.0
73655cc..482db59 master -> origin/master
b0853ed..0e1baf0 sr_3.0 -> origin/sr_3.0
* [new branch] tmp/pipelimit -> origin/tmp/pipelimit
First, rewinding head to replay your work on top of it...
Fast-forwarded master to 482db59aa2788737d9c6c0294a625bd3002d54c3.
i then switch to another branch, say 'kamailio_3.0', and it tells me:
jh@rautu:/usr/src/orig/sip-router$ eg switch kamailio_3.0
Switched to branch "kamailio_3.0"
Your branch is behind the tracked remote branch 'origin/kamailio_3.0' by 1 commit,
and can be fast-forwarded.
how can i do this 'fast-forwarding' without pulling again in this
branch?
-- juha
Module: sip-router
Branch: master
Commit: 5783579581b4f04afd8ea341c7519becabece1a9
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=5783579…
Author: Marius Zbihlei <marius.zbihlei(a)1and1.ro>
Committer: Marius Zbihlei <marius.zbihlei(a)1and1.ro>
Date: Thu Jan 28 12:10:24 2010 +0200
modules_k:siputils Improved documentation of ring_timeout parameter
---
modules_k/siputils/README | 5 +++--
modules_k/siputils/doc/siputils_admin.xml | 4 ++--
modules_k/siputils/ring.c | 2 +-
modules_k/siputils/siputils.c | 2 +-
4 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/modules_k/siputils/README b/modules_k/siputils/README
index 80381c5..9078784 100644
--- a/modules_k/siputils/README
+++ b/modules_k/siputils/README
@@ -187,9 +187,10 @@ Chapter 1. Admin Guide
3.1. ring_timeout (int)
Timeout value in seconds, define how long the call-id is stored in the
- internal list. A reasonable value is "30".
+ internal list kept for replacing 183 messages with 180. A reasonable
+ value is "30".
- Default value is "0".
+ Default value is "0". This means functionality is disabled.
Example 1.1. Set ring_timeout parameter
...
diff --git a/modules_k/siputils/doc/siputils_admin.xml b/modules_k/siputils/doc/siputils_admin.xml
index 982dd84..84f546e 100644
--- a/modules_k/siputils/doc/siputils_admin.xml
+++ b/modules_k/siputils/doc/siputils_admin.xml
@@ -75,12 +75,12 @@
<section>
<title><varname>ring_timeout</varname> (int)</title>
<para>
- Timeout value in seconds, define how long the call-id is stored in the internal list.
+ Timeout value in seconds, define how long the call-id is stored in the internal list kept for replacing 183 messages with 180.
A reasonable value is <quote>30</quote>.
</para>
<para>
<emphasis>
- Default value is <quote>0</quote>.
+ Default value is <quote>0</quote>. This means functionality is disabled.
</emphasis>
</para>
<example>
diff --git a/modules_k/siputils/ring.c b/modules_k/siputils/ring.c
index 4d59a02..f895572 100644
--- a/modules_k/siputils/ring.c
+++ b/modules_k/siputils/ring.c
@@ -237,7 +237,7 @@ static int contains(str callid)
/*!
- * \brief Convert a 180 to a 180 message.
+ * \brief Convert a 183 to a 180 message.
* \param msg SIP message
*/
static int conv183(struct sip_msg *msg)
diff --git a/modules_k/siputils/siputils.c b/modules_k/siputils/siputils.c
index a018462..461dd30 100644
--- a/modules_k/siputils/siputils.c
+++ b/modules_k/siputils/siputils.c
@@ -120,7 +120,7 @@ static param_export_t params[] = {
{"options_accept_encoding", STR_PARAM, &opt_accept_enc.s},
{"options_accept_language", STR_PARAM, &opt_accept_lang.s},
{"options_support", STR_PARAM, &opt_supported.s},
- {"contact_flds_separator", STR_PARAM,&contact_flds_separator},
+ {"contact_flds_separator", STR_PARAM, &contact_flds_separator},
{0, 0, 0}
};
Revision: 5970
http://openser.svn.sourceforge.net/openser/?rev=5970&view=rev
Author: henningw
Date: 2010-01-27 16:39:01 +0000 (Wed, 27 Jan 2010)
Log Message:
-----------
* docs extension, dependency on tm
Modified Paths:
--------------
branches/1.5/modules/sl/README
branches/1.5/modules/sl/doc/sl_admin.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Hello,
I came across a post by Stefan Sayer regarding an rtpproxy transcoder
patch http://lists.iptel.org/pipermail/serdev/2008-July/012794.html.
We are interested in having rtpproxy perform transcoding, both in
software and using DSP array cards, and are currently running rtpproxy
version 1.2.1.
Is this link http://user.cs.tu-berlin.de/~sayer/transcoder/ that is
mentioned on the post our starting point or is there an updated
version ?
Thanks and Regards,
Vikram.
Hi!
The sr/ser/kamailio smaple configs contain:
if (!t_relay()) {
sl_reply_error();
}
I wonder if this is still the case. I did some TCP tests and when the
TCP forwarding fails (e.g. RST received or set_forward_no_connect()
activated), then tm module itself replies stateful with 477 and then
returning to script with FALSE. Thus, sl_reply_error will send 500
response stateless too.
IMO if tm module already sent a final response, it should exit without
entering script again.
Even better would be to reply only if there is no failure route sent.
Further, if TCP forwarding fails due to set_forward_no_connect() it logs:
ERROR: tm [../../forward.h:169]: msg_send: ERROR: tcp_send failed
ERROR: tm [t_fwd.c:1235]: ERROR: t_send_branch: sending request on
branch 0 failed
IMO it would be good to log this only with L_INFO, as it is not an
error, but intended behavior.
Thanks
Klaus