[OpenSIPS-Users] Opensips CP DROUTING GATEWAY enable/disable issue

[Jeff Wilkie]

OPENSIPS 1.10.x
I have the following set

opensips.cfg

 FIFO Management Interface

loadmodule "mi_fifo.so"

modparam("mi_fifo", "fifo_name", "/tmp/opensips_proxy_fifo")

modparam("mi_fifo", "fifo_mode", 0666)

opensipsctlrc

## path to FIFO file

OSIPS_FIFO="/tmp/opensips_proxy_fifo"


Attempting to disable gateways via the CP gives the following errors:


>From DROUTING-Gateway interface:


Error while disabling gateway 2
(the GWID is 2 for the gateway I'm attempting to disable)

>From the MI Commands:
Initiating the following command: *dr_gw_status 2 0*
404 GW ID not found

>From the DROUTING-Gateway interface I am able to enable the interface if it
is disabled
I'm able to also enable the Gateway from the MI Commands section.

I'm also able to enable and disable the Gateway using opensipsctl fifo
commands

opensipsctl fifo dr_gw_status 2

Enabled:: yes

opensipsctl fifo dr_gw_status 2 0

opensipsctl fifo dr_gw_status 2

Enabled:: no

opensipsctl fifo dr_gw_status 2 1

opensipsctl fifo dr_gw_status 2

Enabled:: yes

Not sure where the problem is but I feel its somewhere in the syntax of how
its delivered.  I'm sure it's something easy I've overlooked.  Any help on
this?

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

Re: [OpenSIPS-Users] [OpenSIPS-News] OpenSIPS 2.2.0 moves from beta to RC1

[Bogdan-Andrei Iancu]

Hi all,

We are one step closer to the stable release. After fixing several more 
bugs, 2.2.0 release was upgraded today to RC2. The git branch and 
tarballs are available to download.


The stable 2.2.0 release is planed for 27th of May, so heads up if there 
are any other issues to be reported. IF not, just be ready to use it ;)


Best regards,

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

On 09.05.2016 20:52, Bogdan-Andrei Iancu wrote:

Hi all,

We are glad to announce that now, on the verge of the OpenSIPS Summit, 
the 2.2.0 release was upgraded to RC1 (Release Candidate). Thanks to 
the community's joint effort in testing, reporting and fixing, 
OpenSIPS 2.2.0 made this important leap forward, getting closer and 
closer to the stable release.


Many thanks to all who contributed and please enjoy this release !

Best regards,




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

Re: [OpenSIPS-Users] Possible dialog/topology hiding bug

[Bogdan-Andrei Iancu]

Pete, Razvan just made a fix for this issue. It was tested and uploaded 
on GIT, still please give it try and let me know if ok.


Many thanks for the report,

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

On 19.05.2016 12:04, Pete Kelly wrote:

I can confirm the bug is still present with a SIGTERM shutdown.


On 18 May 2016 at 10:52, Bogdan-Andrei Iancu > wrote:


Hi Pete,

By doing kill -9, you completely kill ALL opensips processes, so
there is no cleanup/flush during shutdown. On crashes, the worker
processes crashes - the attendant cannot crash (as it is not doing
anything), so this process can do the shutdown in a proper way.

Can you try to see if the call is properly recover if you do
normal restart (no SIGKILL, but SIGTERM) ? If it does, please take
a snapshot of the db entry (for that call) while opensips is down
- one for KILL, one for TERM; and let's see the differences -
maybe some dialog data gets flushed only during shutdown.

Regards,

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

On 18.05.2016 10:53, Pete Kelly wrote:

Yes exactly - in fact I did not restart opensips, I waited until
the call is established, and until dialog had flushed to DB and
then killall -9 opensips to simulate a crash.

Upon restart the dialog was loaded in from database

On 17 May 2016 at 18:18, Bogdan-Andrei Iancu > wrote:

Hi Pete,

No, this is not a know bug, nor an intended behavior. So,
simply restarting opensips during a TH call will lead to this
error ? no special setup, just a proxy between 2 end points,
right ?

Regards,

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

On 17.05.2016 16:36, Pete Kelly wrote:

I am seeing something interesting with topology_hiding +
dialog on 2.1. If I let the dialog flush to the DB and kill
opensips, opensips loads back in the dialog info on startup
as expected.

However any new in dialog requests (e.g. BYE) do not proxy -
it looks like Via, Call-ID and Contact are restored but ruri
is not - which makes OpenSIPS loop the request back to itself.

For reference, to "enable" topology hiding, I am simply
calling topology_hiding("C") then in has_totag() I am
calling topology_hiding_match()

If I perform the same test without topology hiding, the
in-dialog requests continue to proxy as normal.

Is this a known bug/quirk, is it likely I am not performing
some check or test that i need to?


___
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] Can we disable pre-allocation of memory?

[Liviu Chircu]

Hi surya,

The Linux kernel will not immediately reserve the big chunk of memory 
OpenSIPS requests on startup (depleting your overall system memory), but 
rather it will break it into pieces of 4096 bytes called "pages", and 
carefully link/unlink each page to "4096" bytes of physical RAM as your 
OpenSIPS server does any kind of memory-related processing.


Time for theory in action! My dev environment only has 6 GB of RAM, but 
Linux allows OpenSIPS to start even if it requests 8GB of shared memory 
+ another 4.6GB of pkg memory (512 x 9). That's ~ 13GB - more than 
double my physical memory!


[liviu ◄ Rivendell opensips (master)]
$ ./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w . &> log
[liviu ◄ Rivendell opensips (master)]
$ ps aux | grep opensi
liviu 3495  0.6  0.1 9002472 6148 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3496  0.0  0.0 9081648 2968 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3497  0.0  0.0 9081644 2964 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3499  0.0  0.0 9002472 1648 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3500  0.0  0.0 9002472 1648 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3502  0.0  0.0 9081644 3456 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3504  0.0  0.0 9081644 2976 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3505  0.0  0.0 9081644 3468 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3507  0.0  0.0 9081644 2976 ?S11:25   0:00 
./opensips -m8192 -M512 -f etc/opensips_2_2.cfg -w .
liviu 3523  0.0  0.0  20396   972 pts/15   S+   11:25   0:00 grep 
--color=auto opensi
liviu 7019  0.0  0.0  50968  4504 pts/4S+   mai19   0:00 vim 
etc/opensips_2_2.cfg

[liviu ◄ Rivendell opensips (master)]
$ cat /proc/meminfo
MemTotal:5995856 kB

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

On 20.05.2016 01:51, surya wrote:

Hi,

Just a simple question. can we disable the pre-allocation of memory and
allow use of whatever memory is available?

Thanks



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Can-we-disable-pre-allocation-of-memory-tp7603033.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