Re: [OpenSIPS-Users] Opensips3: segfaults

2019-04-23 Thread Bogdan-Andrei Iancu 

Hi Abdoul,

Unfortunately without the corefile, it is almost impossible to 
troubleshoot this.


For the future, see 
https://opensips.org/Documentation/TroubleShooting-Crash to understand 
how to properly get the core files.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 04/23/2019 06:40 PM, Abdoul Osséni wrote:

Hello,

I am testing Opensips3 (last commit from github) and I encounter an issue:

dmesg:
[Tue Apr 23 17:03:27 2019] traps: opensips[16387] general protection 
ip:7f86ed1a2676 sp:7ffef01c70b8 error:0


below is the log of opensips
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16387]: 
CRITICAL:core:sig_usr: segfault in process pid: 16387, id: 28
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:handle_sigs: child process 16387 exited by a signal 11
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:handle_sigs: core was not generated
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:handle_sigs: terminating due to SIGCHLD
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16360]: 
INFO:core:sig_usr: signal 15 received
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 7(16366) [SIP receiver 
udp:x.x.x.x:5060] terminated, still waiting for 27 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16362]: 
INFO:core:sig_usr: signal 15 received
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 3(16362) [timer] terminated, 
still waiting for 26 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 5(16364) [SIP receiver 
udp:x.x.x.x:5060] terminated, still waiting for 25 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 6(16365) [SIP receiver 
udp:x.x.x.x:5060] terminated, still waiting for 24 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 12(16371) [SIP receiver 
hep_udp:x.x.x.x:6060] terminated, still waiting for 23 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 14(16373) [SIP receiver 
hep_udp:x.x.x.x:6060] terminated, still waiting for 22 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 15(16374) [SIP receiver 
hep_udp:x.x.x.x:6060] terminated, still waiting for 21 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 17(16376) [SIP receiver 
hep_udp:x.x.x.x:6060] terminated, still waiting for 20 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 18(16377) [SIP receiver 
hep_udp:x.x.x.x:6060] terminated, still waiting for 19 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 19(16378) [SIP receiver 
hep_udp:x.x.x.x:6060] terminated, still waiting for 18 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16361]: 
INFO:core:sig_usr: signal 15 received
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 2(16361) [time_keeper] 
terminated, still waiting for 17 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 20(16379) [TCP receiver] 
terminated, still waiting for 16 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 21(16380) [TCP receiver] 
terminated, still waiting for 15 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 22(16381) [TCP receiver] 
terminated, still waiting for 14 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 23(16382) [TCP receiver] 
terminated, still waiting for 13 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 24(16383) [TCP receiver] 
terminated, still waiting for 12 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 25(16384) [TCP receiver] 
terminated, still waiting for 11 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 26(16385) [TCP receiver] 
terminated, still waiting for 10 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 27(16386) [TCP receiver] 
terminated, still waiting for 9 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 29(16388) [TCP main] terminated, 
still waiting for 8 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: 
INFO:core:shutdown_opensips: process 16(16375) [SIP receiver 
hep_udp:x.x.x.x:6060] terminated, still waiting for 7

[OpenSIPS-Users] Opensips3: segfaults

2019-04-23 Thread Abdoul Osséni 
Hello,

I am testing Opensips3 (last commit from github) and I encounter an issue:

dmesg:
[Tue Apr 23 17:03:27 2019] traps: opensips[16387] general protection
ip:7f86ed1a2676 sp:7ffef01c70b8 error:0

below is the log of opensips
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16387]:
CRITICAL:core:sig_usr: segfault in process pid: 16387, id: 28
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:handle_sigs: child process 16387 exited by a signal 11
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:handle_sigs: core was not generated
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:handle_sigs: terminating due to SIGCHLD
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16360]:
INFO:core:sig_usr: signal 15 received
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 7(16366) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 27 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16362]:
INFO:core:sig_usr: signal 15 received
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 3(16362) [timer] terminated, still
waiting for 26 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 5(16364) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 25 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 6(16365) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 24 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 12(16371) [SIP receiver
hep_udp:x.x.x.x:6060] terminated, still waiting for 23 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 14(16373) [SIP receiver
hep_udp:x.x.x.x:6060] terminated, still waiting for 22 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 15(16374) [SIP receiver
hep_udp:x.x.x.x:6060] terminated, still waiting for 21 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 17(16376) [SIP receiver
hep_udp:x.x.x.x:6060] terminated, still waiting for 20 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 18(16377) [SIP receiver
hep_udp:x.x.x.x:6060] terminated, still waiting for 19 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 19(16378) [SIP receiver
hep_udp:x.x.x.x:6060] terminated, still waiting for 18 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16361]:
INFO:core:sig_usr: signal 15 received
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 2(16361) [time_keeper] terminated,
still waiting for 17 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 20(16379) [TCP receiver] terminated,
still waiting for 16 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 21(16380) [TCP receiver] terminated,
still waiting for 15 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 22(16381) [TCP receiver] terminated,
still waiting for 14 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 23(16382) [TCP receiver] terminated,
still waiting for 13 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 24(16383) [TCP receiver] terminated,
still waiting for 12 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 25(16384) [TCP receiver] terminated,
still waiting for 11 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 26(16385) [TCP receiver] terminated,
still waiting for 10 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 27(16386) [TCP receiver] terminated,
still waiting for 9 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 29(16388) [TCP main] terminated, still
waiting for 8 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 16(16375) [SIP receiver
hep_udp:x.x.x.x:6060] terminated, still waiting for 7 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 4(16363) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 6 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 11(16370) [SIP receiver
udp:x.x.x.x:5060] terminated, still waiting for 5 more
Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]:
INFO:core:shutdown_opensips: process 13(16372) [SIP receiver
hep_udp:x.x.x.x:6060]

[OpenSIPS-Users] Book

2019-04-23 Thread Marcelo Nogueira via Users 
Hi to all

I can sat is great developer open sips


i like to get is any book i can buy about clustering  and federations 


Thank you



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

Re: [OpenSIPS-Users] b2b top hiding with opensips 3.0.0-beta gives "Wrong Scenary ID"

2019-04-23 Thread Vlad Patrascu 

Hi,

Thanks for the report, this was a bug and I've pushed the fix for it, it 
should be fine now.


Regards,

Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 04/23/2019 01:54 PM, Konrad Malewski wrote:

Hello,

I switched to opensips3 and b2b internal scenario stopped working:

Apr 23 10:33:29 [55] ERROR:b2b_logic:fixup_b2b_logic: Wrong Scenary 
ID. No scenario with this ID [�Ͷ�s]

Apr 23 10:33:29 [55] ERROR:core:fix_cmd: Fixup failed for param [1]
Apr 23 10:33:29 [55] ERROR:core:fix_actions: Failed to fix command 

Apr 23 10:33:29 [55] ERROR:core:fix_actions: fixing failed (code=-1) 
at /etc/opensips/opensips.cfg:185
Apr 23 10:33:29 [55] ERROR:core:main: failed to fix configuration with 
err code -1


Line 185 of configuration contains only
 -> b2b_init_request("top hiding");

did scenario name changed ?

--
--
Konrad Malewski


___
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] opensips3.0/dev requires huge amount of memory and crashes

2019-04-23 Thread Konrad Malewski 
fm_malloc is first error:
Apr 23 12:11:27 [50] INFO:core:mod_init: initializing UDP-plain protocol
Apr 23 12:11:27 [50] INFO:dialog:mod_init: Dialog module - initializing
Apr 23 12:11:27 [50] INFO:core:evi_publish_event: Registered event

Apr 23 12:11:27 [50] INFO:topology_hiding:mod_init: initializing...
Apr 23 12:11:27 [50] INFO:rest_client:mod_init: Module initialized!
Apr 23 12:11:27 [50] NOTICE:signaling:mod_init: initializing module ...
Apr 23 12:11:27 [50] ERROR:core:fm_malloc: not enough free shm memory
(62949808 bytes left, need 2824938474944), please increase the "-m" command
line parameter!
Apr 23 12:11:27 [50] INFO:core:fm_malloc: attempting defragmentation...
Apr 23 12:11:27 [50] INFO:core:fm_malloc: unable to alloc a big enough
fragment!
Apr 23 12:11:27 [50] ERROR:core:init_multi_proc_support: out of memory
Apr 23 12:11:27 [50] ERROR:core:main: failed to init multi-proc support
Apr 23 12:11:27 [50] INFO:core:cleanup: cleanup
Apr 23 12:11:27 [50] NOTICE:event_datagram:destroy: destroy module ...
Apr 23 12:11:27 [50] NOTICE:core:main: Exiting

TCP alone is the problem
TCP + UDP works fine
UDP alone works fine



On Tue, Apr 23, 2019 at 12:49 PM Bogdan-Andrei Iancu 
wrote:

> Is there any following error / warning log ? Or you get only that single
> err line ??
>
> And you get that error by using TCP without UDP ? using TCP + UDP is fine ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com 
> 
> OpenSIPS Summit 2019
>   https://www.opensips.org/events/Summit-2019Amsterdam/ 
> 
>
> On 04/23/2019 01:08 PM, Konrad Malewski wrote:
>
> I checked just now.
> It sufficient to comment out UDP listening port and leave just TCP
>
> ///
> #listen=udp:172.17.0.2:5060
> 
>  # CUSTOMIZE ME
> listen=tcp:172.17.0.2:5060
> 
>  # CUSTOMIZE ME
> ///
>
> ERROR:core:fm_malloc: not enough free shm memory (63093216 bytes left,
> need 8843713106240), please increase the "-m" command line parameter!
>
>
> On Tue, Apr 23, 2019 at 9:00 AM Bogdan-Andrei Iancu 
> wrote:
>
>> Hi Konrad,
>>
>> For sure there was something wrong - could you give it a another try with
>> latest 3.0 beta ?
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com 
>> 
>> OpenSIPS Summit 2019
>>   https://www.opensips.org/events/Summit-2019Amsterdam/ 
>> 
>>
>> On 04/08/2019 12:38 PM, Konrad Malewski wrote:
>>
>> Hello,
>>
>> If I enabled TCP only as only protocol, opensips3 starts crashing at
>> startup with following error:
>>
>> ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left,
>> need 17109592486272), please increase the "-m" command line parameter!
>>
>> The amount of "need" is different every time I restart opensips
>>
>> ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left,
>> need 8689571889280), please increase the "-m" command line parameter!
>>
>> when I enable udp and add appropriate listen=udp:IP:PORT entry problem
>> goes away.
>>
>> The issue is odd, so what am I doing wrong? Maybe this is a bug ?
>>
>> --
>> --
>> Konrad Malewski
>>
>>
>> ___
>> Users mailing 
>> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>  
>>

Re: [OpenSIPS-Users] check_source_address()

2019-04-23 Thread Liviu Chircu 

Hi, Mark!

The best way to proceed is to add an xlog("checking $si:$sp\n") before 
check_source_address(), then some useful xlog() messages on each if 
branch, so we can confirm the theory that this is an OpenSIPS issue, and 
not a problem specific to your setup.


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

On 23.04.2019 14:18, Mark Farmer wrote:

Should've added I'm running OpenSIPS 2.4.4

Mark.


On Tue, 23 Apr 2019 at 12:10, Mark Farmer > wrote:


Hi everyone,

I'm seeing some odd behaviour in tha initial requests are allowed
but RE-INVITES are resulting in 403. From my logging I can see the
INVITE coming in so I think it must be matching. Why would it not
obey and route the request?

This is the bit of my request route that identifies the source:

if (check_source_address("1","$avp(trunk_attrs)")) {
                # request comes from trunks
                xlog ("MF - $rm FROM $avp(trunk_attrs)");
                setflag(IS_TRUNK);
        } else {
                send_reply("403","Forbidden");
                exit;
        }

Many thanks
Mark.

-- 
Mark Farmer

farm...@gmail.com 



--
Mark Farmer
farm...@gmail.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] check_source_address()

2019-04-23 Thread Mark Farmer 
Should've added I'm running OpenSIPS 2.4.4

Mark.


On Tue, 23 Apr 2019 at 12:10, Mark Farmer  wrote:

> Hi everyone,
>
> I'm seeing some odd behaviour in tha initial requests are allowed but
> RE-INVITES are resulting in 403. From my logging I can see the INVITE
> coming in so I think it must be matching. Why would it not obey and route
> the request?
>
> This is the bit of my request route that identifies the source:
>
> if (check_source_address("1","$avp(trunk_attrs)")) {
> # request comes from trunks
> xlog ("MF - $rm FROM $avp(trunk_attrs)");
> setflag(IS_TRUNK);
> } else {
> send_reply("403","Forbidden");
> exit;
> }
>
> Many thanks
> Mark.
>
> --
> Mark Farmer
> farm...@gmail.com
>


-- 
Mark Farmer
farm...@gmail.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] check_source_address()

2019-04-23 Thread Mark Farmer 
Hi everyone,

I'm seeing some odd behaviour in tha initial requests are allowed but
RE-INVITES are resulting in 403. From my logging I can see the INVITE
coming in so I think it must be matching. Why would it not obey and route
the request?

This is the bit of my request route that identifies the source:

if (check_source_address("1","$avp(trunk_attrs)")) {
# request comes from trunks
xlog ("MF - $rm FROM $avp(trunk_attrs)");
setflag(IS_TRUNK);
} else {
send_reply("403","Forbidden");
exit;
}

Many thanks
Mark.

-- 
Mark Farmer
farm...@gmail.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] b2b top hiding with opensips 3.0.0-beta gives "Wrong Scenary ID"

2019-04-23 Thread Konrad Malewski 
Hello,

I switched to opensips3 and b2b internal scenario stopped working:

Apr 23 10:33:29 [55] ERROR:b2b_logic:fixup_b2b_logic: Wrong Scenary ID. No
scenario with this ID [�Ͷ�s]
Apr 23 10:33:29 [55] ERROR:core:fix_cmd: Fixup failed for param [1]
Apr 23 10:33:29 [55] ERROR:core:fix_actions: Failed to fix command

Apr 23 10:33:29 [55] ERROR:core:fix_actions: fixing failed (code=-1) at
/etc/opensips/opensips.cfg:185
Apr 23 10:33:29 [55] ERROR:core:main: failed to fix configuration with err
code -1

Line 185 of configuration contains only
 -> b2b_init_request("top hiding");

did scenario name changed ?

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

Re: [OpenSIPS-Users] opensips3.0/dev requires huge amount of memory and crashes

2019-04-23 Thread Bogdan-Andrei Iancu 
Is there any following error / warning log ? Or you get only that single 
err line ??


And you get that error by using TCP without UDP ? using TCP + UDP is fine ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 04/23/2019 01:08 PM, Konrad Malewski wrote:

I checked just now.
It sufficient to comment out UDP listening port and leave just TCP

///
#listen=udp:172.17.0.2:5060    # CUSTOMIZE ME
listen=tcp:172.17.0.2:5060    # CUSTOMIZE ME
///

ERROR:core:fm_malloc: not enough free shm memory (63093216 bytes left, 
need 8843713106240), please increase the "-m" command line parameter!



On Tue, Apr 23, 2019 at 9:00 AM Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi Konrad,

For sure there was something wrong - could you give it a another
try with latest 3.0 beta ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com


OpenSIPS Summit 2019
   https://www.opensips.org/events/Summit-2019Amsterdam/



On 04/08/2019 12:38 PM, Konrad Malewski wrote:

Hello,

If I enabled TCP only as only protocol, opensips3 starts crashing
at startup with following error:

ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes
left, need 17109592486272), please increase the "-m" command line
parameter!

The amount of "need" is different every time I restart opensips

ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes
left, need 8689571889280), please increase the "-m" command line
parameter!

when I enable udp and add appropriate listen=udp:IP:PORT entry
problem goes away.

The issue is odd, so what am I doing wrong? Maybe this is a bug ?

-- 
-- 
Konrad Malewski



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






--
--
Konrad Malewski


___
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] opensips3.0/dev requires huge amount of memory and crashes

2019-04-23 Thread Konrad Malewski 
I checked just now.
It sufficient to comment out UDP listening port and leave just TCP

///
#listen=udp:172.17.0.2:5060   # CUSTOMIZE ME
listen=tcp:172.17.0.2:5060   # CUSTOMIZE ME
///

ERROR:core:fm_malloc: not enough free shm memory (63093216 bytes left, need
8843713106240), please increase the "-m" command line parameter!


On Tue, Apr 23, 2019 at 9:00 AM Bogdan-Andrei Iancu 
wrote:

> Hi Konrad,
>
> For sure there was something wrong - could you give it a another try with
> latest 3.0 beta ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com 
> 
> OpenSIPS Summit 2019
>   https://www.opensips.org/events/Summit-2019Amsterdam/ 
> 
>
> On 04/08/2019 12:38 PM, Konrad Malewski wrote:
>
> Hello,
>
> If I enabled TCP only as only protocol, opensips3 starts crashing at
> startup with following error:
>
> ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left,
> need 17109592486272), please increase the "-m" command line parameter!
>
> The amount of "need" is different every time I restart opensips
>
> ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left,
> need 8689571889280), please increase the "-m" command line parameter!
>
> when I enable udp and add appropriate listen=udp:IP:PORT entry problem
> goes away.
>
> The issue is odd, so what am I doing wrong? Maybe this is a bug ?
>
> --
> --
> Konrad Malewski
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>  
> 
>
>
>

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

[OpenSIPS-Users] TLS connection problem

2019-04-23 Thread Yury Kirsanov 
Hi,
I'm getting a problem connecting to one of my uplink peers, every time I
can see this error:

Apr 23 19:01:04 INFO:core:probe_max_sock_buff: using snd buffer of 416 kb
Apr 23 19:01:04 INFO:core:init_sock_keepalive: TCP keepalive enabled on
socket 6
Apr 23 19:01:04 ERROR:core:tcp_connect_blocking_timeout: timeout 99221 ms
elapsed from 10 s
Apr 23 19:01:04 ERROR:proto_tls:tls_sync_connect: tcp_blocking_connect
failed
Apr 23 19:01:04 ERROR:proto_tls:proto_tls_send: connect failed
Apr 23 19:01:04 ERROR:tm:msg_send: send() to X.X.X.X:5061 for proto tls/3
failed
Apr 23 19:01:04 ERROR:tm:t_forward_nonack: sending request failed

At the very same time from the same server I can issue a curl -vvvI
https://X.X.X.X:5061 and it connects fine, gets SSL certificate and
validates it fine too. Also I can connect with telnet on that port without
any issues. But every time OpenSIPS tries to connect it just logs the error
above. From tcpdump I can see that server has replied and OpenSIPS
immediately sent a TCP RESET packet:

19:01:50.337572 IP OpenSIPS.42145 > X.X.X.X.5061: Flags [S], seq
2223035123, win 29200, options [mss 1460,sackOK,TS val 1224726953 ecr
0,nop,wscale 7], length 0
.-..p%.PV.gx..E..<*.@.@...g]R.4rK...r.9%.
H...
19:01:50.634142 IP X.X.X.X.5061 > OpenSIPS.42145: Flags [S.], seq
4293652737, ack 2223035124, win 8192, options [mss 1440,nop,wscale
8,sackOK,TS val 789606171 ecr 1224726953], length 0
.PV.gx.-..p%..E..<`<@.d.}.4rK.g]R... .-n.
/.o.H...
19:01:50.634219 IP OpenSIPS.42145 > X.X.X.X.5061: Flags [R], seq
2223035124, win 0, length 0
.-..p%.PV.gx..E..(^q@.@..hg]R.4rK.P...g...

I've got a very basic TLS configuration on my server, here it is:

modparam("tls_mgm", "tls_method", "TLSv1_2")
modparam("tls_mgm", "tls_handshake_timeout", 2)
modparam("tls_mgm", "tls_send_timeout", 2)

modparam("tls_mgm", "client_domain_avp", "tls_sip_dom")

modparam("tls_mgm", "ca_list", "/etc/opensips/ssl/ca_list.crt")
modparam("tls_mgm", "certificate", "/etc/opensips/ssl/wildcard.crt")
modparam("tls_mgm", "private_key", "/etc/opensips/ssl/wildcard.pem")
modparam("tls_mgm", "verify_cert", "0")
modparam("tls_mgm", "require_cert", "0")

loadmodule "proto_udp.so"
loadmodule "proto_hep.so"

loadmodule "proto_tls.so"
modparam("proto_tls", "tls_port", 7061)

In the routing logic script I'm doing this (it's a test server so I'm only
trying to connect via TLS):

add_uri_param("transport=TLS");
rewritehostport("X.X.X.X:5061");
t_relay("tls:X.X.X.X:5061");

Any ideas why this may be happening? Thanks a lot!

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

Re: [OpenSIPS-Users] opensips3.0/dev requires huge amount of memory and crashes

2019-04-23 Thread Bogdan-Andrei Iancu 

Hi Konrad,

For sure there was something wrong - could you give it a another try 
with latest 3.0 beta ?


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 04/08/2019 12:38 PM, Konrad Malewski wrote:

Hello,

If I enabled TCP only as only protocol, opensips3 starts crashing at 
startup with following error:


ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left, 
need 17109592486272), please increase the "-m" command line parameter!


The amount of "need" is different every time I restart opensips

ERROR:core:fm_malloc: not enough free shm memory (62949296 bytes left, 
need 8689571889280), please increase the "-m" command line parameter!


when I enable udp and add appropriate listen=udp:IP:PORT entry problem 
goes away.


The issue is odd, so what am I doing wrong? Maybe this is a bug ?

--
--
Konrad Malewski


___
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] Some delusions in module dialog documentation.

2019-04-23 Thread Bogdan-Andrei Iancu 

Hi Kirill,

Indeed, the explanations are not 100% clear - if the dialog replication 
is enabled, the profile info (profiles used by dialogs) is also 
replicated and seen as part of the local profiles, not shared profile. 
So you can use the profiles without the /b or /s


Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 04/15/2019 09:12 AM, Kirill Galinurov wrote:

Hi all. In dialog module documentation we see:
"Also configuring profile replication via 
the/profile_replication_cluster/parameter is not necessary when dialog 
replication is already configured. The profile information is included 
in the dialog updates sent in the dialog replication cluster. The 
profiles must still be marked for sharing though in 
the/profiles_with_value/or/profiles_no_value/parameters.

"
https://opensips.org/html/docs/modules/2.4.x/dialog.html#dialog-clustering

But when we set only params in config:
modparam("dialog", "dialog_replication_cluster", 1)
modparam("dialog","profiles_with_value","reknumber/b;nccqueue/b;")
modparam("dialog","profiles_no_value","incoming/b;")
We have some warnings at startup

"WARNING:dialog:add_profile_definitions: profile incoming configured 
to be replicated over BIN, but 'profile_repl

ication_cluster' is not defined
Apr 15 01:46:22 nau-sbc-test-spb /usr/sbin/opensips[14330]: 
WARNING:dialog:add_profile_definitions: profile reknumber configured 
to be replicated over BIN, but 'profile_rep

lication_cluster' is not defined
Apr 15 01:46:22 nau-sbc-test-spb /usr/sbin/opensips[14330]: 
WARNING:dialog:add_profile_definitions: profile nccqueue configured to 
be replicated over BIN, but 'profile_repl

ication_cluster' is not defined

"


___
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-cp 8.2.4 MI page and drop-down Servers

2019-04-23 Thread Bogdan-Andrei Iancu 

Hello Albary,

You if you have a single OpenSIPS box configured into boxes file, the 
drop-down in the MI tool does not work by default ?


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 04/22/2019 04:51 PM, Albary Franco Pimpao Junior wrote:

Hi people,

Recently I did a git clone of cp for opensips 2.4.x and setup for just 
one server with MI conn via json. In order to be successfull in the 
connection my collegue Frederico helped me and did a workaround in ... 
mi/lib/functions.inc.php. In function show_boxes it was included 
before foreach statement:


if ( empty( $_SESSION['mi_current_box'] ) )
   echo '- select -';

Maybe others have already passed into the same problem. I don't know 
if there's a better way to do it.


Thanks and Best Regards

Albary - Celepar


___
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