sr-dev January 2010

sr-dev@lists.kamailio.org

28 participants
289 discussions

git:kamailio_3.0: pv: fixed author name
by Daniel-Constantin Mierla 18 Jan '10

18 Jan '10

Module: sip-router Branch: kamailio_3.0 Commit: 45f76f44abca5d049c3d289a1f9d09c6821c92d9 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=45f76f4… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Jan 18 12:35:46 2010 +0100 pv: fixed author name - forgotten when creating readme files starting from another module docbook files --- modules_k/pv/README | 2 +- modules_k/pv/doc/pv.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/modules_k/pv/README b/modules_k/pv/README index 6b9b892..3740c2f 100644 --- a/modules_k/pv/README +++ b/modules_k/pv/README @@ -1,6 +1,6 @@ Pseudo-Variables Module -Daniel-Constantin Modroiu +Daniel-Constantin Mierla asipto.com <daniel(a)asipto.com> diff --git a/modules_k/pv/doc/pv.xml b/modules_k/pv/doc/pv.xml index 33590ab..c082b99 100644 --- a/modules_k/pv/doc/pv.xml +++ b/modules_k/pv/doc/pv.xml @@ -15,7 +15,7 @@ <authorgroup> <author> <firstname>Daniel-Constantin</firstname> - <surname>Modroiu</surname> + <surname>Mierla</surname> <affiliation><orgname>asipto.com</orgname></affiliation> <email>daniel(a)asipto.com</email> <address>

1 0

SF.net SVN: openser:[5968] branches/1.5/modules/pv
by Daniel-Constantin Mierla 18 Jan '10

18 Jan '10

Revision: 5968 http://openser.svn.sourceforge.net/openser/?rev=5968&view=rev Author: miconda Date: 2010-01-18 11:34:31 +0000 (Mon, 18 Jan 2010) Log Message: ----------- - fixed author name wrong due to copy&paste of initial skeleton from another module docbook files - reported by Alex Balasov Modified Paths: -------------- branches/1.5/modules/pv/README branches/1.5/modules/pv/doc/pv.xml This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.

1 0

git:kamailio_3.0: tm: set request and reply for TMCB_RESPONSE_SENT
by Daniel-Constantin Mierla 18 Jan '10

18 Jan '10

Module: sip-router Branch: kamailio_3.0 Commit: 03ab185bca42e5788eeef5f5c13e02e547c524a1 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=03ab185… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Jan 18 11:59:19 2010 +0100 tm: set request and reply for TMCB_RESPONSE_SENT - for some reason they were NULL - affected was sip_trace - credits to Nguyen Quang Tri fore report and troubleshooting --- modules/tm/t_reply.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/modules/tm/t_reply.c b/modules/tm/t_reply.c index c37db65..9166c18 100644 --- a/modules/tm/t_reply.c +++ b/modules/tm/t_reply.c @@ -605,7 +605,8 @@ static int _reply_light( struct cell *trans, char* buf, unsigned int len, trans->uas.request, FAKED_REPLY, code); #ifdef TMCB_ONSEND if (unlikely(has_tran_tmcbs(trans, TMCB_RESPONSE_SENT))){ - INIT_TMCB_ONSEND_PARAMS(onsend_params, 0, 0, rb, &rb->dst, + INIT_TMCB_ONSEND_PARAMS(onsend_params, trans->uas.request, + FAKED_REPLY, rb, &rb->dst, buf, len, TMCB_LOCAL_F, rb->branch, code); run_onsend_callbacks2(TMCB_RESPONSE_SENT, trans, &onsend_params);

1 0

git:master: nathelper(k): small code cleanup
by Klaus Darilion 18 Jan '10

18 Jan '10

Module: sip-router Branch: master Commit: a7137d2aeae928fc5b63987537763d41806141dd URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=a7137d2… Author: Klaus Darilion <klaus.mailinglists(a)pernau.at> Committer: Klaus Darilion <klaus.mailinglists(a)pernau.at> Date: Mon Jan 18 10:45:33 2010 +0000 nathelper(k): small code cleanup - remove variable "asymmetric" as it is redundant and have same behavior as "real" variable --- modules_k/nathelper/nathelper.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/modules_k/nathelper/nathelper.c b/modules_k/nathelper/nathelper.c index 90fca05..096816c 100644 --- a/modules_k/nathelper/nathelper.c +++ b/modules_k/nathelper/nathelper.c @@ -2801,7 +2801,7 @@ force_rtp_proxy(struct sip_msg* msg, char* str1, char* str2, int offer) str body, body1, oldport, oldip, newport, newip; str callid, from_tag, to_tag, tmp, payload_types; str oldrtcp, newrtcp; - int create, port, len, asymmetric, flookup, argc, proxied, real; + int create, port, len, flookup, argc, proxied, real; int orgip, commip; int pf, pf1, force, swap; struct options opts, rep_opts, pt_opts; @@ -2845,7 +2845,7 @@ force_rtp_proxy(struct sip_msg* msg, char* str1, char* str2, int offer) LM_ERR("out of pkg memory\n"); FORCE_RTP_PROXY_RET (-1); } - asymmetric = flookup = force = real = orgip = commip = swap = 0; + flookup = force = real = orgip = commip = swap = 0; for (cp = str1; cp != NULL && *cp != '\0'; cp++) { switch (*cp) { case 'a': @@ -2854,7 +2854,6 @@ force_rtp_proxy(struct sip_msg* msg, char* str1, char* str2, int offer) LM_ERR("out of pkg memory\n"); FORCE_RTP_PROXY_RET (-1); } - asymmetric = 1; real = 1; break; @@ -3110,7 +3109,7 @@ force_rtp_proxy(struct sip_msg* msg, char* str1, char* str2, int offer) extract_rtcp(&tmpstr1, &oldrtcp); ++medianum; - if (asymmetric != 0 || real != 0) { + if (real != 0) { newip = oldip; } else { newip.s = ip_addr2a(&msg->rcv.src_ip);

1 0

git:master: nathelper(k): improve documentation
by Klaus Darilion 18 Jan '10

18 Jan '10

Module: sip-router Branch: master Commit: b282d607881473a6724f61f8d8d81652507a3fac URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b282d60… Author: Klaus Darilion <klaus.mailinglists(a)pernau.at> Committer: Klaus Darilion <klaus.mailinglists(a)pernau.at> Date: Mon Jan 18 10:40:29 2010 +0000 nathelper(k): improve documentation - better description about usage of i and e flags --- modules_k/nathelper/README | 47 +++++++++++++++++----- modules_k/nathelper/doc/nathelper_admin.xml | 56 ++++++++++++++++++--------- 2 files changed, 73 insertions(+), 30 deletions(-) diff --git a/modules_k/nathelper/README b/modules_k/nathelper/README index 9f923db..11bb23c 100644 --- a/modules_k/nathelper/README +++ b/modules_k/nathelper/README @@ -194,11 +194,16 @@ Chapter 1. Admin Guide Function fix_nated_contact() rewrites Contact header field with request's source address:port pair. Function fix_nated_sdp() adds the - active direction indication to SDP (flag 0x01) and updates source IP - address too (flag 0x02). + active direction ndication to SDP (flag 0x01) and updates source IP + address too (flag 0x02). Function fix_nated_register() exports exports + the request's source address:port into an AVP to be used during save() + and should be used for REGISTER requests. - Alternative to fix_nated_contact() is add_contact_alias() that together - with handle_ruri_alias() also supports reuse of tcp connections. + Note: fix_nated_contact changes the Contact header, thus it breaks the + RFC. Although usually this is not an issue, it may cause problems with + strict SIP clients. There is an alternative approach by using + add_contact_alias() that together with handle_ruri_alias() is standard + conform and also supports reuse of TCP/TLS connections. Known devices that get along over NATs with nathelper are ATAs (as clients) and Cisco Gateways (since 12.2(T)) as servers. See @@ -565,6 +570,17 @@ force_rtp_proxy(); It can have optional parameters to force additional features. If ip_address is provided, it will be used to replace the one in SDP. + Note: Behavior of rtpproxy depends on the mode in which rtpproxy is + running: If rtpproxy listens only to a single interface, then rtpproxy + is default symmetric (port), if rtpproxy listens to two interfaces (so + called bridge-mode), then rtpproxy is default asymmetric (port). + + Note: Regardless of symmetric/asymmetric rtpproxy mode, per default + rtpproxy accepts incoming RTP packets only from the same IP address as + the SIP signaling was received. Thus, if a SIP client uses different IP + for media and SIP (often seen with SBCs), the 'r' flag must be + specified. + The function is considered depreciated and provided for the compatibility purposes. Use rtpproxy_offer() or rtpproxy_answer() instead. @@ -572,17 +588,26 @@ force_rtp_proxy(); Meaning of the parameters is as follows: * flags - flags to turn on some features. + a - flags that UA from which message is received doesn't - support symmetric RTP. + support symmetric RTP. (automatically sets the 'r' flag) + l - force "lookup", that is, only rewrite SDP when corresponding session is already exists in the RTP proxy. By default is on when the session is to be completed (reply in non-swap or ACK in swap mode). - + i - flags that message is received from UA in the LAN - (internal network). Only makes sense when RTP proxy is running - in the bridge mode. - + e - flags that message is received from UA in the WAN - (external network). Only makes sense when RTP proxy is running - in the bridge mode. + + i, e - these flags specify the direction of the SIP message. + These flags only make sense when rtpproxy is running in bridge + mode. 'i' means internal network (LAN), 'e' means external + network (WAN). 'i' corresponds to rtpproxy's first interface, + 'e' corresponds to rtpproxy's second interface. You always + have to specify two flags to define the incoming network and + the outgoing network. For example, 'ie' should be used for SIP + message received from the local interface and sent out on the + external interface, and 'ei' vice versa. Other options are + 'ii' and 'ee'. So, for example if a SIP requests is processed + with 'ie' flags, the corresponding response must be processed + with 'ie' flags. + Note: As rtpproxy is in bridge mode per default asymmetric, + you have to specify the 'w' flag for clients behind NAT! See + also above notes! + f - instructs nathelper to ignore marks inserted by another nathelper in transit to indicate that the session is already goes through another proxy. Allows creating chain of proxies. diff --git a/modules_k/nathelper/doc/nathelper_admin.xml b/modules_k/nathelper/doc/nathelper_admin.xml index 856f950..be083b0 100644 --- a/modules_k/nathelper/doc/nathelper_admin.xml +++ b/modules_k/nathelper/doc/nathelper_admin.xml @@ -24,17 +24,18 @@ address. </para> <para> - Function fix_nated_contact() - rewrites Contact header field with request's source - address:port pair. - Function fix_nated_sdp() adds the active direction - indication to &sdp; (flag - 0x01) and updates source &ip; address too (flag 0x02). + Function fix_nated_contact() rewrites Contact header field with request's source + address:port pair. Function fix_nated_sdp() adds the active direction ndication + to &sdp; (flag 0x01) and updates source &ip; address too (flag 0x02). Function + fix_nated_register() exports exports the request's source address:port into an AVP + to be used during save() and should be used for REGISTER requests. </para> - <para> - Alternative to fix_nated_contact() is add_contact_alias() that - together with handle_ruri_alias() also supports reuse of tcp - connections. + <para> + Note: fix_nated_contact changes the Contact header, thus it breaks the RFC. + Although usually this is not an issue, it may cause problems with strict + SIP clients. There is an alternative approach by using add_contact_alias() that + together with handle_ruri_alias() is standard conform and also supports reuse + of TCP/TLS connections. </para> <para> Known devices that get along over &nat;s with nathelper are ATAs @@ -596,6 +597,18 @@ force_rtp_proxy(); one in SDP. </para> <para> + Note: Behavior of rtpproxy depends on the mode in which rtpproxy is running: If + rtpproxy listens only to a single interface, then rtpproxy is default symmetric (port), + if rtpproxy listens to two interfaces (so called bridge-mode), then rtpproxy is + default asymmetric (port). + </para> + <para> + Note: Regardless of symmetric/asymmetric rtpproxy mode, per default rtpproxy accepts + incoming RTP packets only from the same IP address as the SIP signaling was received. + Thus, if a SIP client uses different IP for media and SIP (often seen with SBCs), the + 'r' flag must be specified. + </para> + <para> The function is considered depreciated and provided for the compatibility purposes. Use rtpproxy_offer() or rtpproxy_answer() instead. </para> @@ -608,7 +621,7 @@ force_rtp_proxy(); <itemizedlist> <listitem><para> <emphasis>a</emphasis> - flags that UA from which message is - received doesn't support symmetric RTP. + received doesn't support symmetric RTP. (automatically sets the 'r' flag) </para></listitem> <listitem><para> <emphasis>l</emphasis> - force <quote>lookup</quote>, that is, @@ -617,14 +630,19 @@ force_rtp_proxy(); completed (reply in non-swap or ACK in swap mode). </para></listitem> <listitem><para> - <emphasis>i</emphasis> - flags that message is received from - UA in the LAN (internal network). Only makes sense when - RTP proxy is running in the bridge mode. - </para></listitem> - <listitem><para> - <emphasis>e</emphasis> - flags that message is received from - UA in the WAN (external network). Only makes sense when RTP - proxy is running in the bridge mode. + <emphasis>i, e</emphasis> - these flags specify the direction of the SIP + message. These flags only make sense when rtpproxy is running in bridge mode. + 'i' means internal network (LAN), 'e' means external network (WAN). 'i' + corresponds to rtpproxy's first interface, 'e' corresponds to rtpproxy's + second interface. You always have to specify two flags to define + the incoming network and the outgoing network. For example, 'ie' should be + used for SIP message received from the local interface and sent out on the + external interface, and 'ei' vice versa. Other options are 'ii' and 'ee'. + So, for example if a SIP requests is processed with 'ie' flags, the corresponding + response must be processed with 'ie' flags. + </para><para> + Note: As rtpproxy is in bridge mode per default asymmetric, you have to specify + the 'w' flag for clients behind NAT! See also above notes! </para></listitem> <listitem><para> <emphasis>f</emphasis> - instructs nathelper to ignore marks

1 0

[spamtrap][#34] comment2, http://anger-management-guide.com/ levitra 10mg, http://amethyststudios.com/ acomplia onli
by spamtrap 18 Jan '10

18 Jan '10

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab. FS#34 - comment2, http://anger-management-guide.com/ levitra 10mg, http://amethyststudios.com/ acomplia onli User who did this: Daniel-Constantin Mierla (miconda) Attached to Project: sip-router -> spamtrap Assigned To: [-] -> sip-router admin More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=34 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.

1 0

[spamtrap][#35] comment4, http://lexingtonbaptistsc.com/ canada cialis, http://assbrellas.com/ doxycycline effects s
by spamtrap 18 Jan '10

18 Jan '10

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab. FS#35 - comment4, http://lexingtonbaptistsc.com/ canada cialis, http://assbrellas.com/ doxycycline effects s User who did this: Daniel-Constantin Mierla (miconda) Attached to Project: sip-router -> spamtrap More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=35 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.

1 0

[tracker] Task opened: comment4, http://lexingtonbaptistsc.com/ canada cialis, http://assbrellas.com/ doxycycline effects s
by sip-router 18 Jan '10

18 Jan '10

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Anonymous user () Attached to Project - sip-router Summary - comment4, http://lexingtonbaptistsc.com/ canada cialis, http://assbrellas.com/ doxycycline effects s Task Type - Improvement Category - logging Status - Assigned Assigned To - Andrei Pelinescu-Onciul Operating System - NetBSD Severity - Low Priority - Normal Reported Version - 2.99 Due in Version - Undecided Due Date - Undecided Details - comment4, http://lexingtonbaptistsc.com/ canada cialis, http://assbrellas.com/ doxycycline effects side, http://noattrition.com/ reductil tablets, http://n2-itall.com/ meridia 10 mg, http://flowersprescott.com/ olanzapine zyprexa side effects, http://nzingaafrocentricgreetingcards.com/ phentermine doctor consult free, http://manchestershodokan.com/ zyprexa and alzheimers, http://indistew.com/ generic for norvasc, http://amethyststudios.com/ acomplia, http://kakaservice.net/ protonix side affects, http://swlock.net/ cytotec induction of labor, http://lolliesworld.com/ singulair pregnancy, http://icttp.net/ prilosec and nexium, http://ptcscam.com/ propecia, More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=35 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.

1 0

[tracker] Assignee added: comment4, http://lexingtonbaptistsc.com/ canada cialis, http://assbrellas.com/ doxycycline effects s
by sip-router 18 Jan '10

18 Jan '10

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A user has added themself to the list of users assigned to this task. FS#35 - comment4, http://lexingtonbaptistsc.com/ canada cialis, http://assbrellas.com/ doxycycline effects s User who did this - Anonymous user () http://sip-router.org/tracker/index.php?do=details&task_id=35 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.

1 0

git:master: sl(k):Fixed documentation error
by Marius Zbihlei 18 Jan '10

18 Jan '10

Module: sip-router Branch: master Commit: 4dfb8f6a8c2efda45f9b969c665f06996a54479e URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=4dfb8f6… Author: Marius Zbihlei <marius.zbihlei(a)1and1.ro> Committer: Marius Zbihlei <marius.zbihlei(a)1and1.ro> Date: Mon Jan 18 11:17:52 2010 +0200 sl(k):Fixed documentation error The correct param is bind_tm --- modules_k/sl/doc/sl_admin.xml | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/modules_k/sl/doc/sl_admin.xml b/modules_k/sl/doc/sl_admin.xml index cd2e1cd..540c56e 100644 --- a/modules_k/sl/doc/sl_admin.xml +++ b/modules_k/sl/doc/sl_admin.xml @@ -100,7 +100,7 @@ modparam("sl", "enable_stats", 0) </example> </section> <section> - <title><varname>load_tm</varname> (integer)</title> + <title><varname>bind_tm</varname> (integer)</title> <para> If the module should use transaction support for sending the replies. A zero value means disabled. @@ -112,9 +112,9 @@ modparam("sl", "enable_stats", 0) Default value is 1 (enabled). </para> <example> - <title>load_tm example</title> + <title>bind_tm example</title> <programlisting format="linespecific"> -modparam("sl", "load_tm", 0) +modparam("sl", "bind_tm", 0) </programlisting> </example> </section>

1 0

← Newer
1
...
10
11
12
13
14
15
16
...
29
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev January 2010