[OpenSIPS-Users] Changing transport protocol to SCTP

Liviu Chircu liviu at opensips.org
Mon Mar 7 16:19:49 CET 2016


Hi Daniel,

The + ";transport=sctp" protocol switching trick works on my 2.1.2 
testbed just as before. Make sure you remove any OBP-altering logic, 
(e.g. ds_select_dst()) before doing the t_relay(). If the issue 
persists, you should open a GitHub ticket and we'll take a closer look.

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 29.02.2016 23:37, Moreira Yokoyama, Daniel wrote:
>
> Hi.
>
> In a given scenario my routing script has to change the transport 
> protocol to SCTP.
>
> I tried to do it by using the t_relay(proto:server:port) version, but 
> although it worked fine on my tests, when I used in my real case 
> (which has not a predefined server to use as a literal) I found out 
> that OpenSIPS give an error on StartUp-time complaining about the 
> config file. So I assume it tries to eval the string at start up, and 
> every way tried (“sctp:” + $od + “:” + $oP, or simply “sctp:$od:$oP”)… 
> none have worked.
>
> But, when I tried to just concatenate the transport clause to $du, it 
> worked just fine.
>
> *$du = "sip:" + $od + ":" + $op + ";transport=sctp";*
>
> The thing is, that was on 1.9.1.
>
> But now I got a pretty new 2.1.2 version running on a test environment 
> in order to see how would it be to migrate to a newer version… and as 
> odd as it may be, the transport clause has no effect in the relay 
> anymore (it keeps it in UDP instead).
>
> Am I doing something wrong? The t_relay(proto:server:port) still seem 
> to not work with anything other than literal strings, and I really 
> need to be able to convert the request to sctp in this scenario.
>
> Thanks.
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160307/c9d756b4/attachment-0001.htm>


More information about the Users mailing list