Re: [OpenSIPS-Users] [OpenSIPS-News] Schedule for OpenSIPS Summit is available

[Bogdan-Andrei Iancu]

Hi all.

Video Recordings, PDFs and photos from the OpenSIPS Summit in Amsterdam 
are now available - 
http://www.opensips.org/Community/Summit-2016Amsterdam-Content


Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 27.04.2016 13:31, Bogdan-Andrei Iancu wrote:

Hello all,

The complete schedule for OpenSIPS Summit Amsterdam is now available. 
See the list of our speakers and their presentations on

http://www.opensips.org/events/Summit-2016Amsterdam.html

We have a comprehensive set of workshops and presentations that aims 
to bring to our participants the latest technical how-to on hot topics 
like clustering, SIP capturing or WebRTC. Thanks to our speakers, 
valuable OpenSIPS usage scenarios (setups, monitoring, 
troubleshooting, FreeSwitch integration) are to be presented.


If you are an OpenSIPS fan, you should not mis this ;). See you in 
Amsterdam !


Best regards,




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

Re: [OpenSIPS-Users] Multi homed setup

[John Nash]

Thank you. I tested using manual and so far seems to be working fine.

On Mon, May 30, 2016 at 7:04 PM, Bogdan-Andrei Iancu 
wrote:

> Hello Nash,
>
> This is a limitation of how mhomed works - basically opensips asks the OS
> to provide a suitable source interface to reach a certain destination. But
> OS will consider all the network interface, not only the ones configured in
> OpenSIPS. So, the OS may select and return an interface not used by
> OpenSIPS.
>
> What you can do:
> 1) make 1.1.1.1 default interface, to favor it in the OS selection
> 2) disable mhomed and use manual selection of the interface via
> force_send_socket()[1] or $fs[2]
>
> For each GW, dr_gateway, you can store in attributes string some info
> about the interface to be used to reach that GW.
>
> [1] http://www.opensips.org/Documentation/Script-CoreFunctions-2-2#toc16
> [2] http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc43
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 30.05.2016 11:33, John Nash wrote:
>
> On my linux box we have multiple public IP addressess
> 1.1.1.1
> 2.2.2.2
> 3.3.3.3
>
> I am listening on two of them as
> udp:1.1.1.1:5060
> udp:2.2.2.2:5060
>
> I have mhomed=1 in my config. I am also using drouting module. What I
> expect is when an Invite comes to 1.1.1.1:5060 . drouting should send
> outgoing invite using 1.1.1.1 as source IP but it tries to send using
> 3.3.3.3 (Which is default interface)
>
> Is this the expected behavior of mhomed ?..should I manually try to
> control this?
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] contact after fix_nated_contact()

[Bogdan-Andrei Iancu]

Hi Rahul,

the fix_nated_contact() replaces the IP and port from the Contact URI 
with the source IP and port from network level - so, the outcome is 
really predictable ; you can print the incoming contact $ct and the 
source network coordinates $si and $sp - this will give all the info you 
need to see.


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 23.05.2016 19:17, Gupta, Rahul wrote:

Hi Alex, thanks for the quick reply. I don't see if msg_apply_changes() is 
available in opensips. When I use it, I get the bad config file error. I did 
add loadmodule textops.so


Thanks
Rahul Gupta


---

Vote for IPC in the 2016 Waters Technology Awards. Winners are decided by people who are 
most important to us - our customers! Please vote for us (#27, #29) by 
"https://www.surveymonkey.com/r/R6Y27GJ;.



-Original Message-
From: users-boun...@lists.opensips.org 
[mailto:users-boun...@lists.opensips.org] On Behalf Of Alex Balashov
Sent: Monday, May 23, 2016 12:00 PM
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] contact after fix_nated_contact()

On 05/23/2016 11:55 AM, Gupta, Rahul wrote:

How do I get the updated contact after fix_nated_contact(), for
example in the log statement  $ct prints the old Contact.

xlog("Contact before fix_nated_contact: $ct");

fix_nated_contact();

xlog("Contact after fix_nated_contact: $ct");

You can run msg_apply_changes() after calling fix_nated_contact(), assuming it 
doesn't have any effects harmful to your cause:

http://kamailio.org/docs/modules/4.4.x/modules/textopsx.html#textopsx.f.msg_apply_changes

-- Alex

--
Alex Balashov | Principal | Evariste Systems LLC
1447 Peachtree Street NE, Suite 700
Atlanta, GA 30309
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

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


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




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

Re: [OpenSIPS-Users] Multi homed setup

[Bogdan-Andrei Iancu]

Hello Nash,

This is a limitation of how mhomed works - basically opensips asks the 
OS to provide a suitable source interface to reach a certain 
destination. But OS will consider all the network interface, not only 
the ones configured in OpenSIPS. So, the OS may select and return an 
interface not used by OpenSIPS.


What you can do:
1) make 1.1.1.1 default interface, to favor it in the OS selection
2) disable mhomed and use manual selection of the interface via 
force_send_socket()[1] or $fs[2]


For each GW, dr_gateway, you can store in attributes string some info 
about the interface to be used to reach that GW.


[1] http://www.opensips.org/Documentation/Script-CoreFunctions-2-2#toc16
[2] http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc43

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 30.05.2016 11:33, John Nash wrote:

On my linux box we have multiple public IP addressess
1.1.1.1
2.2.2.2
3.3.3.3

I am listening on two of them as
udp:1.1.1.1:5060 
udp:2.2.2.2:5060 

I have mhomed=1 in my config. I am also using drouting module. What I 
expect is when an Invite comes to 1.1.1.1:5060  . 
drouting should send outgoing invite using 1.1.1.1 as source IP but it 
tries to send using 3.3.3.3 (Which is default interface)


Is this the expected behavior of mhomed ?..should I manually try to 
control this?



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


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

Re: [OpenSIPS-Users] compiling opensips on a raspberry pi

[Bogdan-Andrei Iancu]

Hi Steve,

Please update from git and give it a try again (there were couple of 
small fixes). Still, I recommend to go for 2.2 .


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 27.05.2016 22:21, Steve Woolley wrote:
Am trying to run opensips on a raspberry pi OS:Raspbian (based on 
Debian Jessie).


Compiled successfully but take a long time to start up 
opensips. (35-45 minutes).

Shows the following in the log (during the long pause):
DBG:tm:lock_initialize: lock initialization started


Bogan-Andrei Iancu has suggested this is probably due to "System V 
locking support”.
He suggested trying to set USE_PTHREAD_MUTEX or USE_POSIX_SEMS compile 
options.

However, both of these options fail on:

Compiling net/net_tcp.c
net/net_tcp.c: In function ‘tcpconn_new’:
net/net_tcp.c:844:7: error: used union type value where scalar is
required
   if (c->write_lock) lock_destroy(>write_lock);
   ^
Makefile.rules:25: recipe for target 'net/net_tcp.o' failed
make: *** [net/net_tcp.o] Error 1


Anyone had any luck on setting these compile options and/or getting 
opensips (efficiently) running on a Raspberry Pi?


--
Steve Woolley
steve.wool...@me.com 





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


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

Re: [OpenSIPS-Users] Too many Hops error

[Johan De Clercq]

1_ in loadbalancing module there is a function :
lb_is_destination(ip,port[,group[,active]])


this one should be used to check if the invite is not coming back from the
servers on which you loadbalance.



2_ Monitoring state of servers is easy : just check fi they respond to
options.


br,

2016-05-28 12:15 GMT+02:00 Francjos <35...@heb.be>:

> Thank you Johan,
>
> In fact, i have this scenario:
>
> 1) i have to do load balancing
> 2) i have to verify opensips servers using sipsak. sipsak is used to
> moniter
> and verify the state of opensips servers.
>
> So, how can i perform the two actions without generating errors?
>
>
>
> --
> View this message in context:
> http://opensips-open-sip-server.1449251.n2.nabble.com/Too-many-Hops-error-tp7603151p7603171.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Multi homed setup

[John Nash]

On my linux box we have multiple public IP addressess
1.1.1.1
2.2.2.2
3.3.3.3

I am listening on two of them as
udp:1.1.1.1:5060
udp:2.2.2.2:5060

I have mhomed=1 in my config. I am also using drouting module. What I
expect is when an Invite comes to 1.1.1.1:5060 . drouting should send
outgoing invite using 1.1.1.1 as source IP but it tries to send using
3.3.3.3 (Which is default interface)

Is this the expected behavior of mhomed ?..should I manually try to control
this?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] force_send_socket arguments

[John Nash]

wow. Cool !!!

On Mon, May 30, 2016 at 1:57 PM, Bogdan-Andrei Iancu 
wrote:

> Hi John,
>
> The function does not accept any kind of variables, but, with the same
> behavior, you can use the $fs variable (instead of the function):
> http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc43
>
> So, instead of
> force_send_socket(tcp:10.10.10.10:5060);
> you can do
> $fs = "tcp:10.10.10.10:5060";
>
> And on the right side of the assignment you can use any vars you need:
> $fs = "tcp:"+$avp(my_IP)+":5060";
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 29.05.2016 16:20, John Nash wrote:
>
> Is it possible to use avp or any other vraiable as argument
> to force_send_socket ?
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] force_send_socket arguments

[Bogdan-Andrei Iancu]

Hi John,

The function does not accept any kind of variables, but, with the same 
behavior, you can use the $fs variable (instead of the function):

http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc43

So, instead of
force_send_socket(tcp:10.10.10.10:5060);
you can do
$fs = "tcp:10.10.10.10:5060";

And on the right side of the assignment you can use any vars you need:
$fs = "tcp:"+$avp(my_IP)+":5060";

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 29.05.2016 16:20, John Nash wrote:
Is it possible to use avp or any other vraiable as argument 
to force_send_socket ?



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


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