[OpenSIPS-Users] Changing transport protocol to SCTP

[Moreira Yokoyama, Daniel]

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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Relay SCTP instead of UDP

[Moreira Yokoyama, Daniel]

Hi.

I'm trying to relay a message using SCTP instead of UDP.

I found some examples from people trying to relay using TCP and tried using the 
same approach, but using SCTP instead.

So, in my route script I did:

t_relay("sctp:10.0.8.108:5060");

I logged the state of my $du to make sure it was null at the time of the 
t_relay, but although I get SCTP init in the dump, the sip message is never 
sent and I have no error information.

After that I found other information about setting the forced socket ($fs) but 
still having no success.

Is it possible that opensips simply doesn't relay the message using the SCTP 
protocol? Or am I missing something?


Best regards.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] SCTP Symetric Multi Home

[Moreira Yokoyama, Daniel]

Hi.

I'm trying to set Opensips to work on SCTP Symetric Multi Home.

To do this, I've set two endpoints:

listen=sctp:10.0.0.1:5070
listen=sctp:10.0.0.2:5070

and set mhomed

mhomed=1

Using SIPp to make some tests, I could see the association being successfully 
stablished, and as I turn down one of the client's network adapter it manages 
to successfully use other path with the another adapter. Problem is when I turn 
off one of the opensips adapter (10.0.0.1, for instance).

When I run the tcpdump I can notice that the heartbeat doesn't aknowledge the 
10.0.0.2 to the association. But when searching on the internet I find a post 
on the list asking about multi home, whether it is supported or not, and the 
answer is that it does support, althought there is some lack of guidance to 
figure out how to set it up.

Looking through the source code, it seems that for each listen setting, it 
creates a separate socket association... what I need is to set a single socket 
and add both addresses to the same association (setting a multi home 
association).

The question is:

Does opensips really support this feature?
In case it does, what am I doing wrong to set it up?


Thanks.

Best regards.


Atenciosamente,

Daniel Moreira Yokoyama.


PS: Moderator, I apologize for the duplicated message. But the first one was 
sent by another address than this one and I assume it was blocked. Thank you.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users