[OpenSIPS-Users] [Release] OpenSIPS 1.11.6 and 2.1.2

[Bogdan-Andrei Iancu]

Hi all,

Two new minor releases are available now - 1.11.6 and 2.1.2. As usual 
they do not bring changes in functionality, but fixes. Especially for 
2.1.2 where many issues were addressed (consistency and bug fixes) in 
regards to the architecture change (the internal reactor, async support, 
proto enhancement).
2.1.2 is an important milestone in the lifetime of 2.1 branch, and it is 
strongly recommended to upgrade - it will expose all the 2.1 goodies in 
the most reliable way .


Many thanks to everyone involved in testing, troubleshooting and 
reporting - this is a tremendous help for the project and we do 
appreciate it.


Downloads and changelogs are available under:
 http://opensips.org/pub/opensips/1.11.6/
 http://opensips.org/pub/opensips/2.1.2/


Enjoy !

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


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

Re: [OpenSIPS-Users] Planing the future OpenSIPS releases

[Bogdan-Andrei Iancu]

Hi Dragomir,

The 2.2 version is the current development version - it is not 
production ready - so crashing is part of its life routine. The async 
radius haven't made it to any stable version - it will be part of the 
first 2.2 stable release (scheduled for March 2016).


New features are not backported to existing stable versions (like 2.1 or 
1.11) .


Regards,

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

On 14.01.2016 00:34, Dragomir Haralambiev wrote:

Hi Bogdan,

Thanks for your replay.

Here is email describe Radius problem in Opensips 2.1.
===
Hi Arsen,

If i completely understand the problem, the server doesn't provide 
the deserved response. The problem in this case is that rc_send_server 
function which is used by rc_acct function (which gives you the error) 
uses a blocking socket and recvfrom blocks until it receives the 
RADIUS message response. You can see the source code here [0] line 
224. Blocking causes  problems in scheduling other timers in opensips, 
in your case tm and dialog timers, and that is the cause for your 
warnings. So it is a drawback of the freeradius-client(or 
radiusclient-ng) implementation. *We tried to solve this problem in 
opensips 2.2 with **radius** async features[1]*.


Regards,
Ionut-Razvan Ionita
=


Opensips 2.2 was crashed when make a call.

It is normal to ask for support of the radius protocol.

Best regards,

Dragomir

2016-01-13 12:27 GMT+02:00 Bogdan-Andrei Iancu >:


Hi Dragomir,

What you mean ? All OpenSIPS versions do have the radius support;
starting with 2.2 we will have the async support for radius too.

Regards,

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

On 12.01.2016 22:03, Dragomir Haralambiev wrote:

Hi,

Which Opensips version will maintain Radius?

Best regards,
Dragomir

2016-01-12 19:11 GMT+02:00 Bogdan-Andrei Iancu
>:

Hi all,

Here is the proposed planning for the next OpenSIPS releases :


Minor releases
---
Versions : OpenSIPS 1.11.6, OpenSIPS 2.1.2
When : 14th of January 2016
Activity: close important bug reports (if any to be considered)


Major release
--
Version : OpenSIPS 2.2
When : second half of March 2016
Activities: development, wrapping up and testing


Major release
--
Version : OpenSIPS 3.0
When : end of January 2016 to start
Activities: work on the new cfg file model.


The work/activities for each release will be further detailed
/ discussed in separate threads.


Best regards,

-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
http://www.opensips-solutions.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




___
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] Opensips 1.8 ds_list behavior in dispatcher

[Bogdan-Andrei Iancu]

Hi Gunjan,

In dispatcher there are 2 storages:
- primary storage which is in memory
- secondary storage (read only at startup or reload) which is the DB

First is about synchronizing the 2 storages (from secondary to primary 
via a ds_reload command). AFter that is about which storage you are 
querying for data. Like the "opensipsctl fifo ds_list" (via MI command) 
gets data from memory cache while the "opensipsctl dispatcher show" 
simply dumps db content.


Regards,

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

On 14.01.2016 03:44, Gunjan Korlekar wrote:

Hello,

I am observing some unusual behavior of the ds_list command when 
adding and removing gateways in the dispatcher table for opensips 1.8


I am running the following sequence of commands -

./opensipsctl dispatcher addgw 40 sip:2.2.2.4:5060 
 0 'test1'
 ./opensipsctl dispatcher addgw 40 sip:2.2.2.5:5060 
 0 'test1'
 ./opensipsctl dispatcher addgw 40 sip:2.2.2.6:5060 
 0 'test1'


When I view the dispatcher list using ds_list I see-
 ./opensipsctl fifo ds_list
SET_NO:: 1
SET:: 40
URI:: sip:2.2.2.4:5060  flag=A
URI:: sip:2.2.2.5:5060  flag=A
URI:: sip:2.2.2.6:5060  flag=A
and the ./opensipsctl dispatcher show output is as follows -
dispatcher gateways
++---+--++---++---+-+
| id | setid | destination  | socket | flags | weight | attrs | 
description |

++---+--++---++---+-+
|  3 |40 | sip:2.2.2.4:5060  | NULL   | 
0 |  1 |   | test1   |
|  4 |40 | sip:2.2.2.5:5060  | NULL   | 
0 |  1 |   | test1   |
|  5 |40 | sip:2.2.2.6:5060  | NULL   | 
0 |  1 |   | test1   |

++---+--++---++---+-+

However when I remove the 3 gateways one after another using 
the ./opensipsctl dispatcher rmgw command. I see that the gateway that 
was removed last can still be seen in the ds_list command even though 
'dispatcher show' does not show any gateways present. Here is the 
sequence of commands I am executing-


 ./opensipsctl dispatcher rmgw 3
./opensipsctl fifo ds_list
SET_NO:: 1
SET:: 40
URI:: sip:2.2.2.5:5060  flag=A
URI:: sip:2.2.2.6:5060  flag=A
 ./opensipsctl dispatcher show
dispatcher gateways
++---+--++---++---+-+
| id | setid | destination  | socket | flags | weight | attrs | 
description |

++---+--++---++---+-+
|  4 |40 | sip:2.2.2.5:5060  | NULL   | 
0 |  1 |   | test1   |
|  5 |40 | sip:2.2.2.6:5060  | NULL   | 
0 |  1 |   | test1   |

++---+--++---++---+-+

 ./opensipsctl dispatcher rmgw 4
 ./opensipsctl fifo ds_list
SET_NO:: 1
SET:: 40
URI:: sip:2.2.2.6:5060  flag=A
 ./opensipsctl dispatcher show
dispatcher gateways
++---+--++---++---+-+
| id | setid | destination  | socket | flags | weight | attrs | 
description |

++---+--++---++---+-+
|  5 |40 | sip:2.2.2.6:5060  | NULL   | 
0 |  1 |   | test1   |

++---+--++---++---+-+

 ./opensipsctl dispatcher rmgw 5
 ./opensipsctl fifo ds_list
SET_NO:: 1
SET:: 40
URI:: sip:2.2.2.6:5060  flag=A
 ./opensipsctl dispatcher show
dispatcher gateways


Can you please help in understanding this behavior? Is this expected 
behavior? Is there something I am missing that needs to be done to 
correct this?


--
Thanks,
Gunjan


___
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] Config Advertised_address makes OpenSIPS forward SIP ACK when it must not. How to fix? Help.

[Bogdan-Andrei Iancu]

Hi Rodrigo,

Try adding in your script:

alias="xxx.xxx.xxx.xxx"

Regards,

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

On 13.01.2016 19:53, Rodrigo Pimenta Carvalho wrote:


Dear OpenSIPS-users;


My OpenSIPS is behind a NAT. The public IP is xxx.xxx.xxx.xx.

So, I have configured advertised_address="xxx.xxx.xxx.xx" in my OpenSIPS.


It seems that such new configurations takes appropriated effect, 
because a /Record/-/Route/ header field in a SIP OK message (for a 
call that was answered) contains the IP xxx.xxx.xxx.xx, when it 
arrives to the caller (OpenSIPS adds Record-Rout xxx.xxx.xxx.xx when 
the SIP INVITE is forwarded).



So, when the caller receives that SIP OK it sends the SIP ACK to IP 
xxx.xxx.xxx.xx, port 5060. Then OpenSIPS receives the SIP ACK that has 
Route header field containing the IP xxx.xxx.xxx.xx.



Now the problem: OpenSIPS refuses the SIP ACK as this message was to 
another proxy and forward it. As log as the route is xxx.xxx.xxx.xx, 
the SIP ACK returns to OpenSIPS that forward it again. It becomes a loop.



How to solve this issue? I think there is an error in my OpenSIPS.cfg 
file.


Any hint?

--


Some details from the log is here:




Jan 13 17:15:28 [680] DBG:core:check_self: host != me
Jan 13 17:15:28 [680] DBG:rr:after_loose: Topmost URI is NOT myself
Jan 13 17:15:28 [680] DBG:rr:after_loose: URI to be processed: 
'sip:xxx.xxx.xxx.xx;transport=tcp;lr;nat=yes;did=de2.a332f873'

Jan 13 17:15:28 [680] DBG:rr:after_loose: Next URI is a loose router
Jan 13 17:15:28 [680] DBG:rr:run_rr_callbacks: callback id 1 entered 
with 

Re: [OpenSIPS-Users] latest opensips 2.2 dev revision 055f4b1

[Răzvan Crainea]

It would be great if you could provide debugging logs.

Best regards,
Răzvan

On 01/14/2016 02:21 AM, Tito Cumpen wrote:
I am seeing some strangeness in which opensips delivers a large 200 
ok/w sdp at the size of 5461 then opensips proceeds by sending a fin 
and a rst. I can supply logs if needed. This ends up causing issues 
with chrome and sipjs it no longer renders media or sends it.


Thanks,
Tito


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


--
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

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

Re: [OpenSIPS-Users] Planing the future OpenSIPS releases

[Ionut Ionita]

Hi,

Can you please open a ticket with the crash on github? Posting a 
backtrace would be nice.


Regards,
Ionut-Razan Ionita

On 01/14/2016 12:34 AM, Dragomir Haralambiev wrote:

Hi Bogdan,

Thanks for your replay.

Here is email describe Radius problem in Opensips 2.1.
===
Hi Arsen,

If i completely understand the problem, the server doesn't provide 
the deserved response. The problem in this case is that rc_send_server 
function which is used by rc_acct function (which gives you the error) 
uses a blocking socket and recvfrom blocks until it receives the 
RADIUS message response. You can see the source code here [0] line 
224. Blocking causes  problems in scheduling other timers in opensips, 
in your case tm and dialog timers, and that is the cause for your 
warnings. So it is a drawback of the freeradius-client(or 
radiusclient-ng) implementation. *We tried to solve this problem in 
opensips 2.2 with **radius** async features[1]*.


Regards,
Ionut-Razvan Ionita
=


Opensips 2.2 was crashed when make a call.

It is normal to ask for support of the radius protocol.

Best regards,

Dragomir

2016-01-13 12:27 GMT+02:00 Bogdan-Andrei Iancu >:


Hi Dragomir,

What you mean ? All OpenSIPS versions do have the radius support;
starting with 2.2 we will have the async support for radius too.

Regards,

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

On 12.01.2016 22:03, Dragomir Haralambiev wrote:

Hi,

Which Opensips version will maintain Radius?

Best regards,
Dragomir

2016-01-12 19:11 GMT+02:00 Bogdan-Andrei Iancu
>:

Hi all,

Here is the proposed planning for the next OpenSIPS releases :


Minor releases
---
Versions : OpenSIPS 1.11.6, OpenSIPS 2.1.2
When : 14th of January 2016
Activity: close important bug reports (if any to be considered)


Major release
--
Version : OpenSIPS 2.2
When : second half of March 2016
Activities: development, wrapping up and testing


Major release
--
Version : OpenSIPS 3.0
When : end of January 2016 to start
Activities: work on the new cfg file model.


The work/activities for each release will be further detailed
/ discussed in separate threads.


Best regards,

-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
http://www.opensips-solutions.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




___
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] latest opensips 2.2 dev revision 055f4b1

[Bogdan-Andrei Iancu]

Hi Tito,

Indeed, a pcap + opensips corresponding logs will help with looking into 
this.


Regards,

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

On 14.01.2016 02:21, Tito Cumpen wrote:
I am seeing some strangeness in which opensips delivers a large 200 
ok/w sdp at the size of 5461 then opensips proceeds by sending a fin 
and a rst. I can supply logs if needed. This ends up causing issues 
with chrome and sipjs it no longer renders media or sends it.


Thanks,
Tito


___
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] MenuConfig Compile Fail on Solaris Sparc

[Liviu Chircu]

Updated the patch [1]. My bad!

[1]: https://gist.github.com/liviuchircu/00bdc9bad3b750e8a265

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

On 14.01.2016 08:45, Nathaniel L. Keeling III wrote:

Liviu,

I removed the previous change and applied the patch and here is the 
error that I got:


Compiling net/net_udp.c
In file included from net/../locking.h:66:0,
 from net/../statistics.h:143,
 from net/../pt.h:70,
 from net/net_udp.c:30:
net/../lock_alloc.h: In function 'lock_set_alloc':
net/../lock_alloc.h:70:13: warning: cast increases required alignment 
of target type [-Wcast-align]

ls->locks=(gen_lock_t*)((char*)ls+sizeof(gen_lock_set_t));
 ^
In file included from net/../reactor_defs.h:39:0,
 from net/../reactor.h:38,
 from net/net_udp.c:32:
net/../ip_addr.h: In function 'sockaddr2ip_addr':
net/../ip_addr.h:224:25: warning: cast increases required alignment of 
target type [-Wcast-align]

memcpy(ip->u.addr, &((struct sockaddr_in*)sa)->sin_addr, 4);
 ^
net/../ip_addr.h:229:25: warning: cast increases required alignment of 
target type [-Wcast-align]

memcpy(ip->u.addr, &((struct sockaddr_in6*)sa)->sin6_addr, 16);
 ^
In file included from net/../reactor.h:41:0,
 from net/net_udp.c:32:
net/../io_wait_loop.h: In function 'io_wait_loop_devpoll':
net/../io_wait_loop.h:403:17: error: redeclaration of 'e' with no linkage
  struct fd_map* e;
 ^
net/../io_wait_loop.h:402:17: note: previous declaration of 'e' was here
  struct fd_map* e;
 ^
Makefile.rules:25: recipe for target 'net/net_udp.o' failed
make[1]: *** [net/net_udp.o] Error 1

Thanks

Nathaniel

On 1/13/16 4:28 AM, Liviu Chircu wrote:
sed -i 's/\(struct dvpoll dpoll;\)/\1\n\tstruct fd_map* e;/' 
io_wait_loop.h



___
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] Config Advertised_address makes OpenSIPS forward SIP ACK when it must not. How to fix? Help.

[Rodrigo Pimenta Carvalho]

Thank you very much!


It worked!


One observation: the documentation for OpenSIPS dev 2.2, says:


"...It is necessary to include the port..."


However, when I do alias="xxx.xxx.xxx.xxx:5060" it fails.


Now, my next step will be to analyze the SDP and fix it when OpenSIPS and 
callee is behind the NAT. Do you have any suggestion for that?


Best regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979



De: Bogdan-Andrei Iancu 
Enviado: quinta-feira, 14 de janeiro de 2016 07:45
Para: OpenSIPS users mailling list; Rodrigo Pimenta Carvalho
Assunto: Re: [OpenSIPS-Users] Config Advertised_address makes OpenSIPS forward 
SIP ACK when it must not. How to fix? Help.

Hi Rodrigo,

Try adding in your script:

alias="xxx.xxx.xxx.xxx"

Regards,

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

[http://www.opensips-solutions.com/imgs/opensips-solutions-logo.gif]

Home — OpenSIPS Solutions
www.opensips-solutions.com
OpenSIPS is a mature Open Source implementation of a SIP server. OpenSIPS is 
more than a SIP proxy/router as it includes application-level functionalities.

On 13.01.2016 19:53, Rodrigo Pimenta Carvalho wrote:

Dear OpenSIPS-users;


My OpenSIPS is behind a NAT. The public IP is xxx.xxx.xxx.xx.

So, I have configured advertised_address="xxx.xxx.xxx.xx" in my OpenSIPS.


It seems that such new configurations takes appropriated effect, because a 
Record-Route header field in a SIP OK message (for a call that was answered) 
contains the IP xxx.xxx.xxx.xx, when it arrives to the caller (OpenSIPS adds 
Record-Rout xxx.xxx.xxx.xx when the SIP INVITE is forwarded).


So, when the caller receives that SIP OK it sends the SIP ACK to IP 
xxx.xxx.xxx.xx, port 5060. Then OpenSIPS receives the SIP ACK that has Route 
header field containing the IP xxx.xxx.xxx.xx.


Now the problem: OpenSIPS refuses the SIP ACK as this message was to another 
proxy and forward it. As log as the route is xxx.xxx.xxx.xx, the SIP ACK 
returns to OpenSIPS that forward it again. It becomes a loop.


How to solve this issue? I think there is an error in my OpenSIPS.cfg file.

Any hint?

--


Some details from the log is here:




Jan 13 17:15:28 [680] DBG:core:check_self: host != me
Jan 13 17:15:28 [680] DBG:rr:after_loose: Topmost URI is NOT myself
Jan 13 17:15:28 [680] DBG:rr:after_loose: URI to be processed: 
'sip:xxx.xxx.xxx.xx;transport=tcp;lr;nat=yes;did=de2.a332f873'
Jan 13 17:15:28 [680] DBG:rr:after_loose: Next URI is a loose router
Jan 13 17:15:28 [680] DBG:rr:run_rr_callbacks: callback id 1 entered with 

Re: [OpenSIPS-Users] Dialogs stay in memory until restart in state 5

[John Nash]

I am not able to find the commit can you please point me?

On Wed, Jan 13, 2016 at 9:07 AM, John Nash  wrote:

> OK thank you I will try to find and patch.
>
> On Tue, Jan 12, 2016 at 10:58 PM, Răzvan Crainea 
> wrote:
>
>> Hi, John!
>>
>> This issue was fixed in newer versions of OpenSIPS, and the fix will be
>> part of OpenSIPS 2.1.2.
>>
>> Best regards,
>> Răzvan
>>
>>
>> On 01/12/2016 03:19 PM, John Nash wrote:
>>
>> I am using OpenSIPS (2.1.1 (x86_64/linux)) with dialogs module and
>> topology hiding modules.
>> I am not saving dialogs in database.
>>
>> After I run it for few hours and stop traffic i see hundreds of dialogs
>> using fifo command which wont be deleted from memory until I restart. I see
>> dialogs like ..
>> dialog::  hash=4094:1281471850
>> state:: 5
>> user_flags:: 0
>> timestart:: 0
>> timeout:: 0
>> callid:: 8abe7f9e-2cd5-1234-84b0-d4ae52bce047
>> from_uri:: sip:4117834663@127.0.0.1
>> to_uri:: sip:119603452947@127.0.0.1:5060
>>
>> I saw couple of old posts and tried using "Pp" parameter in create_dialog
>> but it does not seem to be of any effect.
>>
>> In logs I also see messages like "ERROR:dialog:push_reply_in_dialog:
>> [487] reply in dlg state [2]: missing TAG param in TO hdr" which I am not
>> sure are related to my problem.
>>
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Core Developerhttp://www.opensips-solutions.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] Opensips 1.8 ds_list behavior in dispatcher

[Gunjan Korlekar]

Hi Bogdan,

Thanks for the clarification regarding the memory and the ds_list command.

>From what I see in the opensipsctl source, the 'opensipsctl dispatcher
rmgw' command also runs a 'ds_reload' after running the database query to
remove the entry. Hence in my above sequence of operations, the primary
storage should have synced with the secondary storage before I ran 'fifo
ds_list' and should not have expected data in the ds_list output -

./opensipsctl dispatcher show
dispatcher gateways
++---+--++---++---+-+
| id | setid | destination  | socket | flags | weight | attrs |
description |
++---+--++---++---+-+
|  5 |40 | sip:2.2.2.6:5060 | NULL   | 0 |  1 |   | test1
|
++---+--++---++---+-+

 ./opensipsctl dispatcher rmgw 5 -- ds_reload here
 ./opensipsctl fifo ds_list <<<- should show synced output ?
SET_NO:: 1
SET:: 40
URI:: sip:2.2.2.6:5060 flag=A
 ./opensipsctl dispatcher show
dispatcher gateways

I tried the above by running 'fifo ds_reload' explicitly after 'dispatcher
rmgw' as well. However I did not see a difference in the result. Can you
please help in understanding the issue?

Thanks,
Gunjan

On Thu, Jan 14, 2016 at 1:39 AM, Bogdan-Andrei Iancu 
wrote:

> Hi Gunjan,
>
> In dispatcher there are 2 storages:
> - primary storage which is in memory
> - secondary storage (read only at startup or reload) which is the DB
>
> First is about synchronizing the 2 storages (from secondary to primary via
> a ds_reload command). AFter that is about which storage you are querying
> for data. Like the "opensipsctl fifo ds_list" (via MI command) gets data
> from memory cache while the "opensipsctl dispatcher show" simply dumps db
> content.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 14.01.2016 03:44, Gunjan Korlekar wrote:
>
> Hello,
>
> I am observing some unusual behavior of the ds_list command when adding
> and removing gateways in the dispatcher table for opensips 1.8
>
> I am running the following sequence of commands -
>
> ./opensipsctl dispatcher addgw 40 sip:2.2.2.4:5060 0 'test1'
>  ./opensipsctl dispatcher addgw 40 sip:2.2.2.5:5060 0 'test1'
>  ./opensipsctl dispatcher addgw 40 sip:2.2.2.6:5060 0 'test1'
>
> When I view the dispatcher list using ds_list I see-
>  ./opensipsctl fifo ds_list
> SET_NO:: 1
> SET:: 40
> URI:: sip:2.2.2.4:5060 flag=A
> URI:: sip:2.2.2.5:5060 flag=A
> URI:: sip:2.2.2.6:5060 flag=A
> and the ./opensipsctl dispatcher show output is as follows -
> dispatcher gateways
>
> ++---+--++---++---+-+
> | id | setid | destination  | socket | flags | weight | attrs |
> description |
>
> ++---+--++---++---+-+
> |  3 |40 | sip:2.2.2.4:5060 | NULL   | 0 |  1 |   | test1
>   |
> |  4 |40 | sip:2.2.2.5:5060 | NULL   | 0 |  1 |   | test1
>   |
> |  5 |40 | sip:2.2.2.6:5060 | NULL   | 0 |  1 |   | test1
>   |
>
> ++---+--++---++---+-+
>
> However when I remove the 3 gateways one after another using
> the ./opensipsctl dispatcher rmgw command. I see that the gateway that was
> removed last can still be seen in the ds_list command even though
> 'dispatcher show' does not show any gateways present. Here is the sequence
> of commands I am executing-
>
>  ./opensipsctl dispatcher rmgw 3
> ./opensipsctl fifo ds_list
> SET_NO:: 1
> SET:: 40
> URI:: sip:2.2.2.5:5060 flag=A
> URI:: sip:2.2.2.6:5060 flag=A
>  ./opensipsctl dispatcher show
> dispatcher gateways
>
> ++---+--++---++---+-+
> | id | setid | destination  | socket | flags | weight | attrs |
> description |
>
> ++---+--++---++---+-+
> |  4 |40 | sip:2.2.2.5:5060 | NULL   | 0 |  1 |   | test1
>   |
> |  5 |40 | sip:2.2.2.6:5060 | NULL   | 0 |  1 |   | test1
>   |
>
> ++---+--++---++---+-+
>
>  ./opensipsctl dispatcher rmgw 4
>  ./opensipsctl fifo ds_list
> SET_NO:: 1
> SET:: 40
> URI:: sip:2.2.2.6:5060 flag=A
>  ./opensipsctl dispatcher show
> dispatcher gateways
>
> ++---+--++---++---+-+
> | id | setid | destination  | socket | flags | weight | attrs |
> description |
>
> ++---+--++---++---+-+
> |  5 |40 | sip:2.2.2.6:5060 | NULL   | 0 |  1 |   | test1
>   |
>
> 

Re: [OpenSIPS-Users] MenuConfig Compile Fail on Solaris Sparc

[Nathaniel L. Keeling III]

Liviu,

No problem, but it looks like the same patch. Also, do I need to 
un-apply the previous patch first or can I just apply the updated version?


Thanks

Nathaniel L Keeling

On 1/14/16 3:40 AM, Liviu Chircu wrote:

Updated the patch [1]. My bad!

[1]: https://gist.github.com/liviuchircu/00bdc9bad3b750e8a265

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

On 14.01.2016 08:45, Nathaniel L. Keeling III wrote:

Liviu,

I removed the previous change and applied the patch and here is the 
error that I got:


Compiling net/net_udp.c
In file included from net/../locking.h:66:0,
 from net/../statistics.h:143,
 from net/../pt.h:70,
 from net/net_udp.c:30:
net/../lock_alloc.h: In function 'lock_set_alloc':
net/../lock_alloc.h:70:13: warning: cast increases required alignment 
of target type [-Wcast-align]

ls->locks=(gen_lock_t*)((char*)ls+sizeof(gen_lock_set_t));
 ^
In file included from net/../reactor_defs.h:39:0,
 from net/../reactor.h:38,
 from net/net_udp.c:32:
net/../ip_addr.h: In function 'sockaddr2ip_addr':
net/../ip_addr.h:224:25: warning: cast increases required alignment 
of target type [-Wcast-align]

memcpy(ip->u.addr, &((struct sockaddr_in*)sa)->sin_addr, 4);
 ^
net/../ip_addr.h:229:25: warning: cast increases required alignment 
of target type [-Wcast-align]

memcpy(ip->u.addr, &((struct sockaddr_in6*)sa)->sin6_addr, 16);
 ^
In file included from net/../reactor.h:41:0,
 from net/net_udp.c:32:
net/../io_wait_loop.h: In function 'io_wait_loop_devpoll':
net/../io_wait_loop.h:403:17: error: redeclaration of 'e' with no 
linkage

  struct fd_map* e;
 ^
net/../io_wait_loop.h:402:17: note: previous declaration of 'e' was here
  struct fd_map* e;
 ^
Makefile.rules:25: recipe for target 'net/net_udp.o' failed
make[1]: *** [net/net_udp.o] Error 1

Thanks

Nathaniel

On 1/13/16 4:28 AM, Liviu Chircu wrote:
sed -i 's/\(struct dvpoll dpoll;\)/\1\n\tstruct fd_map* e;/' 
io_wait_loop.h



___
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

[OpenSIPS-Users] How to take control of Record-Routes header fields? Need remove one of two.

[Rodrigo Pimenta Carvalho]

Dear OpenSIPS-Users;


Suddenly my opensips started to add 2 Record-Routes header fields to messages 
it is handling. Ex: when forward a simple SIP-INVITE.


One header field has a private IP and another has a public IP.


I would like to take control of Record-Routes and then avoid opensips adding 
that one with private IP.


Is it possible?


If yes, when a SIP-OK arrives in a callee, the callee will send SIP-ACK to the 
public IP and then the OpenSIPS will receive it. If I let the header field with 
private IP there, it causes problem when opensips is behind a NAT, with callee, 
but the caller is outside the local network.


Can I proceed removing one Record-Route or it is a bad idea?


Any hint will be very helpful!


Best regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] How to take control of Record-Routes header fields? Need remove one of two.

[Eric Tamme]

Perhaps you should try to find out why there are now more RR headers - 
it is likely that the request is spiraling through the proxy itself.  
Generally speaking you should not remove the record route headers.


-Eric

On 01/14/2016 02:16 PM, Rodrigo Pimenta Carvalho wrote:


Dear OpenSIPS-Users;


Suddenly my opensips started to add 2 Record-Routes header fields to 
messages it is handling. Ex: when forward a simple SIP-INVITE.



One header field has a private IP and another has a public IP.


I would like to take control of Record-Routes and then avoid opensips 
adding that one with private IP.



Is it possible?


If yes, when a SIP-OK arrives in a callee, the callee will send 
SIP-ACK to the public IP and then the OpenSIPS will receive it. If I 
let the header field with private IP there, it causes problem when 
opensips is behind a NAT, with callee, but the caller is outside the 
local network.



Can I proceed removing one Record-Route or it is a bad idea?


Any hint will be very helpful!


Best regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979


___
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] latest opensips 2.2 dev revision 055f4b1

[Tito Cumpen]

Bogdan, Razvan,


I used using modparam("proto_wss", "wss_max_msg_chunks", 8) and it appears
to have resolved this issue.

Thanks,
Tito

On Thu, Jan 14, 2016 at 2:18 PM, Tito Cumpen  wrote:

> Razvan Bogdan,
>
>
> Here are the logs. I appended the opensips log with sipjs console output
> just for reference of call id as well as a pcap. I noticed a message
> claiming it had already made 4 read attempts and it was closing the socket
> "chunks ERROR:proto_wss:ws_process: Made 4 read attempts but message is
> not complete yet - closing connection" Let me know if you need any more
> information.
>
> Thanks,
> Tito
>
> On Thu, Jan 14, 2016 at 6:01 AM, Răzvan Crainea 
> wrote:
>
>> It would be great if you could provide debugging logs.
>>
>> Best regards,
>> Răzvan
>>
>>
>> On 01/14/2016 02:21 AM, Tito Cumpen wrote:
>>
>> I am seeing some strangeness in which opensips delivers a large 200 ok/w
>> sdp at the size of 5461 then opensips proceeds by sending a fin and a rst.
>> I can supply logs if needed. This ends up causing issues with chrome and
>> sipjs it no longer renders media or sends it.
>>
>> Thanks,
>> Tito
>>
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>> --
>> Răzvan Crainea
>> OpenSIPS Core Developerhttp://www.opensips-solutions.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] B2B BYEs

[Bogdan-Andrei Iancu]

Hi Søren,

Do you have an ngrep capture (taken from opensips b2b, covering all 
calls/legs involved in the scenario) showing the call with the B2B 
restarted?


Regards,

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

On 13.01.2016 14:39, Søren Andersen wrote:


Hi Bogdan-Andrei,

Only if I reload the B2B the BYEs is sent directly to the client. – 
But the funny thing is this only happens if the client is receives a 
call.  If the client initialize the call everything works fine.


/Søren

*Fra:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sendt:* 13. januar 2016 11:39
*Til:* OpenSIPS users mailling list ; Søren 
Andersen 

*Emne:* Re: [OpenSIPS-Users] B2B BYEs

Hi Søren,

With or without restarting the B2B isn;t the BYE sent by client to the 
B2B instance ?


Regards,

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

On 12.01.2016 16:32, Søren Andersen wrote:

Hello there,

I’ve some strange issues with the B2B module. – I use MySQL as
backend, and if I reload OpenSIPS the BYE is sent directly to the
client, and not my SIP proxy. My B2B and OpenSIPS is two
difference servers.

If I take a look in b2b_entities table I notice the contact1 field
contains the IP address of the client.  But if I don’t reload the
OpenSIPS the BYE will be sent correctly the my proxy, and then to
the client.

Now, my question is how can I make sure that B2B server will not
try to communicate with the clients after a reload?

My topology:

ISP -> B2B -> Proxy -> Client

My config:

loadmodule "b2b_entities.so"

loadmodule "b2b_logic.so"

modparam("b2b_logic", "script_scenario", "/etc/opensips/b2b.xml")

modparam("b2b_entities", "db_url",
"mysql://opensips:x...@xx.xx.xx.xx/b2b"
)

modparam("b2b_entities", "db_mode", 1)

modparam("b2b_logic", "db_mode", 1)

modparam("b2b_logic", "db_url",
"mysql://opensips:x...@xx.xx.xx.xx/b2b"
)

modparam("b2b_entities", "replication_mode", 1)

modparam("b2b_logic", "init_callid_hdr", "Init-CallID")

if (is_method("INVITE") && !has_totag()) {

b2b_init_request("B2B","sip:$t...@xx.xx.xx.xx"
);

exit;

}

/Søren




___

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