[OpenSIPS-Devel] [ opensips-Patches-3519778 ] B2B_LOGIC: completely lumps support
Patches item #3519778, was opened at 2012-04-20 03:03 Message generated for change (Settings changed) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3519778&group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: trunk Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Altmann (nikbyte) >Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: B2B_LOGIC: completely lumps support Initial Comment: Now you can change all parts of message before b2b_init_request call and in b2b_request/b2b_reply routes. It useful for add additional headers before b2b_init_request to pass through b2b (don't forget custom_headers param) and also for NAT processing in b2b_request/b2b_reply routes. Instead of patch #3515749. Please, ignore/remove old patch. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3519778&group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Patches-3520528 ] B2B_LOGIC - choose method how to generate To: header
Patches item #3520528, was opened at 2012-04-23 00:56 Message generated for change (Settings changed) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3520528&group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: trunk Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Altmann (nikbyte) >Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: B2B_LOGIC - choose method how to generate To: header Initial Comment: It depends on #3516387 patch, that provides b2b_logic per session flags. It adds new flag "t". When it enabled, To: header generates from To: header of source INVITE, when it disabled To header generates from request uri (old behavior). I need it for balance b2b sessions to multidomain proxy, when To: header should not be changed. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3520528&group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Patches-3519714 ] NATHELPER - Check by port number in contact
Patches item #3519714, was opened at 2012-04-19 21:48 Message generated for change (Settings changed) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3519714&group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: trunk Status: Open >Resolution: Accepted >Priority: 7 Private: No Submitted By: Nick Altmann (nikbyte) >Assigned to: Vladut-Stefan Paiu (vladut-paiu) Summary: NATHELPER - Check by port number in contact Initial Comment: I need to check port in contact against source port (for STUN clients). It's additional check flag (64) for nat_uac_test: 64 - port in Contact is compared against source port of signaling -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3519714&group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Patches-3516387 ] B2B_LOGIC - transparent authentication
Patches item #3516387, was opened at 2012-04-10 03:35
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3516387&group_id=232389
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: trunk
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nick Altmann (nikbyte)
>Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: B2B_LOGIC - transparent authentication
Initial Comment:
New option:
auth_mode = 0 - normal authentication
auth_mode = 1 - transparent authentication
Passes authentication from one to another side thorough b2b.
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-05-29 04:29
Message:
I've added updated version with fixed bug in late variables initialization.
opensips_b2b_transp_auth_v3.patch It's production patch now.
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-04-23 00:51
Message:
I've added per b2b session flags. And the first flag - "a" for transparent
authentication.
Usage:
b2b_set_mode("a");
b2b_init_request("scenario");
It affects only this b2b session.
The new patch attached in file opensips_b2b_transp_auth_v2.patch file.
Also I attached opensips_b2b_lumpsbug_v2.patch that fixes lumps bug when
opensips_b2b_transp_auth_v2.patch and opensips_b2b_lumps.patch (#3519778)
applied together.
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-04-20 21:10
Message:
Okay, let it be separate command and one-character flags.
Like
b2b_set_mode("A");
A - Enable transparent authentication
b2b_set_mode("AxSZ"); // For example
--
Comment By: Ovidiu Sas (osas)
Date: 2012-04-20 17:12
Message:
If we want this functionality implemented as a flag, then it shouldn't be
passed as an extension to the first parameter because:
- it's an awkward syntax
- and it's really messy when you want to pass more flags.
Best thing would be to set up the flag(s) before calling b2b_init_request
and leave the syntax for b2b_init_request as is.
Regards,
Ovidiu Sas
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-04-20 12:22
Message:
Wow! I think flags in the first param is the best solution!
--
Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2012-04-20 12:13
Message:
I agree with Ovidiu on both things - it should not be a global option and
it should be backward compatible.
The only options I see here is either use a kind of module variable to set
the flags before the init:
$b2b_flags = xx ;
or as Nick suggested, with a function, to do more or less the same.
Another approach may be to quiz the flags in the first param, using a
separator - this will be backward compat. Like:
b2b2_init_request("my_scenario","","");
->
b2b2_init_request("my_scenario/flags","","");
Regards,
Bogdan
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-04-15 22:41
Message:
What do you think about new command, like b2b_set_flags("flags")?
I think that there are more than one option (flag) will be needed in
future.
Something like:
b2b_set_flags("T"); # transparent authentication
b2b_init_request("top hiding");
I think it would be better than just a variable.
--
Comment By: Ovidiu Sas (osas)
Date: 2012-04-10 08:05
Message:
I would prefer a variable to be set.
Even if auth mode would be controlled as a parameter for b2b_init_request,
it must accept pvars and the work is pretty much there. Also, inserting a
param in the middle of existing ones, will break forward compatibility (old
scripts will no longer work with new opensips versions).
--
Comment By: Nick Altmann (nikbyte)
Date: 2012-04-10 07:51
Message:
What do you think about change b2b_init_request parameters?
First - scenario
Second - FLAGS (I think it will be useful in future)
Third-Sixth - scenario params
And make first flag to manage authentication mode?
--
Comment By: Ovidiu Sas (osas)
Date: 2012-04-10 07:28
Message:
Controlling auth mode globally (via a module param) is a little bit
restrictive.
I would prefer having a variable the will will be set before initiating the
b2b call. This will allow both authentication modes to coexist on the same
server.
-
[OpenSIPS-Devel] SIP/XMPP gateway for Presence and MSRP chat sessions
Hello, SylkServer SIP/XMPP gateway application is now available for testing. SylkServer can now act as a transparent gateway between SIP and XMPP protocols. This functionality can be used by a SIP service provider to bridge out to XMPP domains or to receive incoming requests from XMPP domains for its local SIP users. In a similar fashion, a XMPP service provider can use the gateway to bridge out to SIP domains and handle incoming requestes from SIP domains to the XMPP users it serves. More information about this beta release is available here: http://sylkserver.ag-projects.com/news/7 Regards, Adrian___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Patches-3513129 ] Regexp support in transformations
Patches item #3513129, was opened at 2012-03-30 01:08
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3513129&group_id=232389
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: trunk
Status: Open
Resolution: None
>Priority: 7
Private: No
Submitted By: Nick Altmann (nikbyte)
>Assigned to: Vladut-Stefan Paiu (vladut-paiu)
Summary: Regexp support in transformations
Initial Comment:
Based on kamailio textops module regexp support in transformations
implementation by Elena-Ramona Modroiu (asipto.com).
{re.subst,expression}
Perform Perl-like substitutions on string value pseudo-variables.
# Assign Request-URI user to PV
$var(user) = $(ru{re.subst,/^sip:(.*)@(.*)/\1/});
# Assign Request-URI user to PV, where every 'A' has been replaced by 'a'
$var(user) = $(rU{re.subst,/A/a/g});
The prototype is:
{re.subst,/match_expression/replacement_expression/flags}
match_expression - Posix regular expression
replacement_expression - substitution expression with back references to
matched tokes: \1, \2, …, \9
flags:
i - match ignore case
s - match within multi-lines strings
g - replace all matches
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3513129&group_id=232389
___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Patches-3530859 ] Handle case where reply after engage_mediaproxy has no body
Patches item #3530859, was opened at 2012-05-30 09:24 Message generated for change (Settings changed) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3530859&group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: trunk Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dynamic Packet (dpacket) >Assigned to: saghul (saghul) Summary: Handle case where reply after engage_mediaproxy has no body Initial Comment: Currently if you remove the body via strip_body() of an in-dialog reply which is using engage_mediaproxy() you end up with junk in the body. IT seems the reply is still processed and the lump with the ip and port of the mediaproxy is appended as junk. This patch skips processing the reply if there is no body or it has been removed. Let me know your thoughts Saul and others so we can get this applied to trunk and possibly 1.8.x or even older branches. -- Comment By: Dynamic Packet (dpacket) Date: 2012-05-30 11:20 Message: Attached new patch to check for body being deleted inside get_sdp_message() . -- Comment By: saghul (saghul) Date: 2012-05-30 10:14 Message: As discussed on IRC, the proper fix for this would be as follows: Modify the get_sdp_message function (in the mediaproxy module) so that it returns false also when the body was removed with a lump. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1086412&aid=3530859&group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] disable_gruu parameter in 1.8 branch
Hi Vlad, On May 31, 2012, at 11:01 AM, Vlad Paiu wrote: > Hello Saúl, > > The 'disable_gruu' parameter addition has happened after the OpenSIPS 1.8 was > released as beta ( beta was on Mar 22, parameter was added on Apr 24 ), this > is why is was not back-ported. > > Thus, it will be present in the next OpenSIPS release. Oh, I see now. Thanks for clarifying! Regards, -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] disable_gruu parameter in 1.8 branch
Hello Saúl, The 'disable_gruu' parameter addition has happened after the OpenSIPS 1.8 was released as beta ( beta was on//Mar 22, parameter was added on Apr 24 ), this is why is was not back-ported. Thus, it will be present in the next OpenSIPS release. Regards, Vlad Paiu OpenSIPS Developer http://www.opensips-solutions.com On 05/30/2012 04:17 PM, Saúl Ibarra Corretgé wrote: Hi Vlad, About a month ago a patch adding the disable_gruu parameter was added to trunk but it was never backported to the 1.8 branch. At that time 1.8 was still under development IIRC. Could we get that backported to 1.8 please? :-) Regards, -- Saúl Ibarra Corretgé AG Projects ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
