Re: [OpenSIPS-Users] Opensips2.1 crash

2016-03-28 Thread Denis 
Hello Bogdan,

Opensips has been downloaded/compiled/installed from git. 
Were should i check "debug symbols" for installation? 

Thank you.

 mailto:denis7...@mail.ru


Hi Denis,

I guess you have opensips installed from packages - please install the package 
with the debug symbols, so that the backtrace will get more sense.

Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 28.03.2016 16:00, Denis wrote:
Opensips2.1 crash Hello!

I am going to upgrade my Opensips to 2.1. from 1.11.6.
Opensips 2.1. had been installed on a test server and during the test i notice 
periodic Opensips crash. And i cannot understand the reason.

Thank you for any help.

P.S. In attachment you can find PID of processes before the crash, information 
from log and core file.


mailto:denis7...@mail.ru 

___

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] SIPTrace not sending to duplicate_uri

2016-03-28 Thread Kneeoh 
I need a little help figuring out why my implementation of the siptrace module 
isn't working as expected. I've placed:# Trace this dialog
    trace_dialog();
In my main route block right after:if ( !create_dialog("B") ) {
        xlog("L_INFO", "Unable to create dialog \n");
        send_reply("500","Internal Server Error");
        exit;

    } 

When I place a call and tcpdump the destination host defined 
in:modparam("siptrace", "duplicate_uri", "sip:192.168.2.142:9060")
I do not see any packets heading towards that host. I've run a debug 4 and am 
getting the following output. Which is confusing me, since I've established a 
dialog and have issued the trace_dialog command. There should be "something to 
trace here". Where am I going wrong? I'm on 1.11.5

DBG:siptrace:trace_dialog: Nothing to trace here
DBG:siptrace:trace_sl_onreply_out: trace slonreply out
DBG:siptrace:trace_sl_onreply_out: nothing to trace...
DBG:siptrace:trace_onreq_in: trace on req in
DBG:siptrace:trace_onreq_in: nothing to trace...
DBG:siptrace:trace_msg_out: trace off...

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

[OpenSIPS-Users] Enhaced sip capturing process

2016-03-28 Thread Ionita Ionut-Razvan 
Hi all,

In OpenSIPS 2.2, the whole SIP capturing process was dramatically re-worked, to 
make it more flexible, higher performance and more powerful. The re-work covers 
the whole SIP capturing flow, from the filtering traffic and  packing into HEP, 
to the routing HEP and storing it into the database. The existing sip_trace and 
sip_capture modules were re-designed and the new proto_hep module added to sync 
the implementation around the HEP protocol.

The new approach is more flexible as the sip trace module comes with a simpler 
logic in how to filter and select the traffic (message, transaction, dialog 
level). Introducing the concept of traceID gives more flexibility when comes  
to decide where to send the filtered traffic (to HEP, to DB, to SIP). Any 
combination of filters and destination is now possible, allowing the 
implementation of any complex tracing and capturing scenario.

The performance of the whole capturing process was also increased by using 
asynchronous operations when comes to sending/receiving HEP packets or to 
writing to DB - this means no more blocking under heavy load, lower changes to 
get your OpenSIPS overloaded. Also the DB operations were improved by using 
multi-row inserts, to reduce the DB overhead.

OpenSIPS 2.2 comes with a new radical concept - HEPv3 proxying. The HEP 
implementation in OpenSIPS is now more powerful - the script gives the 
possibility to access the HEP information, to change the HEP headers and to 
proxy further any incoming HEP traffic. The ability to act as HEP proxy/switch 
is the answer to heavy-load and complex capturing scenarios. 

Considering all these improvements, OpenSIPS now puts on the table new ways for 
building advanced capturing architecture. If until now the capturing node could 
only store messages in the database, not being able to do anything else since 
it was not possible to make a difference between sip and hep messages, with the 
new additions one can also choose to route the hep messages to different 
destinations based on different factors or store hep messages directly into the 
database, leaving the script available for different type of processing. 

All this work is a result of the collaboration between theSIPCapture[0] and 
OpenSIPS projects. How to improve the integration of these two pieces of 
software was the result of joined discussions and brainstorming, having the 
single goal of professional capturing system, from SIP traffic, all the way to 
the DB.

Overview of the changes:

* New proto_hep module [1] to concentrate all the HEP protocol related 
operations (async send and receive via TCP).

* sip_trace module[2] dropped all flags in favour of a single sip_trace() 
function where you can decide the tracing level (message, transaction, dialog) 
and where to trace (multiple trace-id’s[3] point directly to a DB, to a HEP 
destination or to a SIP destination)

in sip_capture module[4], the sip_capture function can now store messages in 
the database asynchronously which will save precious processing time.

* the sip_capture module now transformed into a fully hep-aware node capable of 
not only storing messages in the databases, but also acting as a hep proxy, 
forwarding messages to various hep destinations using the hep_relay[5] 
function. The routing is done the same way as the sip routing allowing using 
all the routing modules has right now. What is more, for the third version of 
the protocol it is very easy to modify the hep chunks from the script[6][7][8] 
before storing/forwarding the message.

* the sip_capture module can turn your capturing node into a hep proxy - we 
have also defined a new parameter called the hep_route through which one can 
define a special route through which all the hep messages should go[9]. The 
major advantage this route brings is that the payload of the message is not 
parsed, saving precious time. Capturing messages from this route is not allowed 
since you don’t have a parsed message. Also this parameter brings you the 
possibility to store hep messages directly into the database, without going 
through the script at all

For further documentation read the links below:

[0] http://www.sipscapture.org/

[1] http://www.opensips.org/html/docs/modules/2.2.x/proto_hep

[2] http://www.opensips.org/html/docs/modules/2.2.x/siptrace

[3]http://www.opensips.org/html/docs/modules/2.2.x/siptrace#id248959

[4] http://www.opensips.org/html/docs/modules/2.2.x/sipcapture

[5]http://www.opensips.org/html/docs/modules/2.2.x/sipcapture#id294645

[6]http://www.opensips.org/html/docs/modules/2.2.x/sipcapture#hep_set_id

[7]http://www.opensips.org/html/docs/modules/2.2.x/sipcapture#id294455

[8]http://www.opensips.org/html/docs/modules/2.2.x/sipcapture#id294587

[9]http://www.opensips.org/html/docs/modules/2.2.x/sipcapture#id293867

Regards,
Ionut Ionita
OpenSIPS Developer

___
Users mailing list
Users@lists.opensips.org

Re: [OpenSIPS-Users] How can the global variable "listen" to listen WLAN ?

2016-03-28 Thread Bogdan-Andrei Iancu 

yes, but I'm not suggesting, but saying it :).

You can use M4 text pre-processor with a define inside the cfg, so you 
can replace the name of the interface.


Regards,

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

On 28.03.2016 20:14, Rodrigo Pimenta Carvalho wrote:

Ok Bogdan-Andrei

So, are you suggesting that the opensips.cfg file should be edited by a script, 
aren't you?

Thank you for the explanation.

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


De: Bogdan-Andrei Iancu 
Enviado: segunda-feira, 28 de março de 2016 14:03
Para: Rodrigo Pimenta Carvalho; OpenSIPS users mailling list
Assunto: Re: [OpenSIPS-Users] How can the global variable "listen" to listen 
WLAN ?

Hi Rodrigo,

If you do not know the name of the interface, it is something beyond
OpenSIPS area. You should do a small shell script to detect the name of
the interface (or the IP) and to put it into the OpenSIPS cfg, before
OpenSIPS start.

Regards,

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

On 28.03.2016 17:41, Rodrigo Pimenta Carvalho wrote:

Hi Alex and Bogdan-Andrei.

The customer of my project will use wireless network or cable. It depends on 
the user preference and his home devices capabilities. That is, sometimes my 
hardware with OpenSIPS will be connected to a switch by means of wlan and 
sometimes by means of eth cable.
I can't do a forecast about it.
So, my OpenSIPS.cfg file must be prepared for both situations. How to do it?

For example, if I just write :

listen=tcp:eth0:5060   # CUSTOMIZE ME
listen=tcp:wlan0:5060   # CUSTOMIZE ME

This 2 simultaneous configurations will cause problems, because I generally only one 
interface will be used. A kind of error is: "ERROR:core:fix_socket_list: could not 
resolve wlan0"

Any idea for this case will be very helpful!

Thanks a lot.


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


De: Bogdan-Andrei Iancu 
Enviado: quinta-feira, 24 de março de 2016 06:24
Para: OpenSIPS users mailling list; Rodrigo Pimenta Carvalho
Assunto: Re: [OpenSIPS-Users] How can the global variable "listen" to listen 
WLAN ?

Hi Rodrigo,

The listen param may accept as input the name of any network interface
you may have on your system - eth0, eth1, lo, ma1, wlan1,
etcwhatever is listed by "ifconfig" as configured interface may be used.

Regards,

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

On 22.03.2016 13:54, Rodrigo Pimenta Carvalho wrote:

Hi Alex.

I have tried something similar in the past and I have problems to execute 
opensips.
I'm not sure now if I had done exactly this way, but I will try it as your 
suggestion.

By the way, the opensips documentation doesn't say about wlan for 'listen' 
variable.
Let me try it and post the result here with more details.

Regards.



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


De: users-boun...@lists.opensips.org  em nome de 
Alex Balashov 
Enviado: segunda-feira, 21 de março de 2016 21:03
Para: users@lists.opensips.org
Assunto: Re: [OpenSIPS-Users] How can the global variable "listen" to listen 
WLAN ?

On 03/21/2016 04:36 PM, Rodrigo Pimenta Carvalho wrote:


According to the documentation "...It can be an IP address, hostname or
network interface id".

So, can I do the following configuration?


listen=tcp:wlan0:5060

Why can't you just do exactly that?

--
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] How can the global variable "listen" to listen WLAN ?

2016-03-28 Thread Bogdan-Andrei Iancu 

Hi Rodrigo,

If you do not know the name of the interface, it is something beyond 
OpenSIPS area. You should do a small shell script to detect the name of 
the interface (or the IP) and to put it into the OpenSIPS cfg, before 
OpenSIPS start.


Regards,

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

On 28.03.2016 17:41, Rodrigo Pimenta Carvalho wrote:

Hi Alex and Bogdan-Andrei.

The customer of my project will use wireless network or cable. It depends on 
the user preference and his home devices capabilities. That is, sometimes my 
hardware with OpenSIPS will be connected to a switch by means of wlan and 
sometimes by means of eth cable.
I can't do a forecast about it.
So, my OpenSIPS.cfg file must be prepared for both situations. How to do it?

For example, if I just write :

listen=tcp:eth0:5060   # CUSTOMIZE ME
listen=tcp:wlan0:5060   # CUSTOMIZE ME

This 2 simultaneous configurations will cause problems, because I generally only one 
interface will be used. A kind of error is: "ERROR:core:fix_socket_list: could not 
resolve wlan0"

Any idea for this case will be very helpful!

Thanks a lot.


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


De: Bogdan-Andrei Iancu 
Enviado: quinta-feira, 24 de março de 2016 06:24
Para: OpenSIPS users mailling list; Rodrigo Pimenta Carvalho
Assunto: Re: [OpenSIPS-Users] How can the global variable "listen" to listen 
WLAN ?

Hi Rodrigo,

The listen param may accept as input the name of any network interface
you may have on your system - eth0, eth1, lo, ma1, wlan1,
etcwhatever is listed by "ifconfig" as configured interface may be used.

Regards,

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

On 22.03.2016 13:54, Rodrigo Pimenta Carvalho wrote:

Hi Alex.

I have tried something similar in the past and I have problems to execute 
opensips.
I'm not sure now if I had done exactly this way, but I will try it as your 
suggestion.

By the way, the opensips documentation doesn't say about wlan for 'listen' 
variable.
Let me try it and post the result here with more details.

Regards.



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


De: users-boun...@lists.opensips.org  em nome de 
Alex Balashov 
Enviado: segunda-feira, 21 de março de 2016 21:03
Para: users@lists.opensips.org
Assunto: Re: [OpenSIPS-Users] How can the global variable "listen" to listen 
WLAN ?

On 03/21/2016 04:36 PM, Rodrigo Pimenta Carvalho wrote:


According to the documentation "...It can be an IP address, hostname or
network interface id".

So, can I do the following configuration?


listen=tcp:wlan0:5060

Why can't you just do exactly that?

--
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] OpenSips 2.2 - Segmentation fault.

2016-03-28 Thread Bogdan-Andrei Iancu 
You should thanks to John (Ionut) as he made the debugging and the fix 
:) He deserves all the credits .


Regards,

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

On 28.03.2016 18:26, Dragomir Haralambiev wrote:

Hi,

Now working fine!

THANKS!

2016-03-28 18:18 GMT+03:00 Bogdan-Andrei Iancu >:


Hi,

Thank you for the report, the fix is already on GIT, please give
it a try.

Best regards,

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

On 26.03.2016 10:23, Dragomir Haralambiev wrote:

Hello,

I try to make call with new Opensips 2.2. When cal is finish
OpenSips crashed.
here is bt full :

http://pastebin.com/5yUy0buF

Best regards,
Dragomir



___
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 2.2 - Segmentation fault.

2016-03-28 Thread Bogdan-Andrei Iancu 

Hi,

Thank you for the report, the fix is already on GIT, please give it a try.

Best regards,

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

On 26.03.2016 10:23, Dragomir Haralambiev wrote:

Hello,

I try to make call with new Opensips 2.2. When cal is finish OpenSips 
crashed.

here is bt full :

http://pastebin.com/5yUy0buF

Best regards,
Dragomir



___
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] Opensips2.1 crash

2016-03-28 Thread Bogdan-Andrei Iancu 

Hi Denis,

I guess you have opensips installed from packages - please install the 
package with the debug symbols, so that the backtrace will get more sense.


Regards,

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

On 28.03.2016 16:00, Denis wrote:

Opensips2.1 crash Hello!

I am going to upgrade my Opensips to 2.1. from 1.11.6.
Opensips 2.1. had been installed on a test server and during the test 
i notice periodic Opensips crash. And i cannot understand the reason.


Thank you for any help.

P.S. In attachment you can find PID of processes before the crash, 
information from log and core file.



mailto:denis7...@mail.ru


___
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] Opensips2.1 crash

2016-03-28 Thread Denis 
Hello!

I am going to upgrade my Opensips to 2.1. from 1.11.6.
Opensips 2.1. had been installed on a test server and during the test i notice 
periodic Opensips crash. And i cannot understand the reason.

Thank you for any help.

P.S. In attachment you can find PID of processes before the crash, information 
from log and core file.


mailto:denis7...@mail.ruPID:

Process::  ID=0 PID=9950 Type=attendant
Process::  ID=1 PID=9962 Type=event-route handler
Process::  ID=2 PID=9963 Type=RTPP timeout receiver
Process::  ID=3 PID=9964 Type=MI Datagram
Process::  ID=4 PID=9966 Type=MI FIFO
Process::  ID=5 PID=9968 Type=time_keeper
Process::  ID=6 PID=9969 Type=timer
Process::  ID=7 PID=9970 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=8 PID=9971 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=9 PID=9973 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=10 PID=9974 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=11 PID=9977 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=12 PID=9978 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=13 PID=9981 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=14 PID=9982 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=15 PID=9984 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=16 PID=9985 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=17 PID=9989 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=18 PID=9990 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=19 PID=9991 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=20 PID=9993 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=21 PID=9995 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=22 PID= Type=SIP receiver udp:213.170.100.146:5068

LOG:

Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9950]: 
INFO:core:handle_sigs: child process 9966 exited by a signal 11
Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9950]: 
INFO:core:handle_sigs: core was generated
Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9950]: 
INFO:core:handle_sigs: terminating due to SIGCHLD
Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9982]: 
INFO:core:sig_usr: signal 15 received
Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9964]: 
INFO:core:sig_usr: signal 15 received

GDB (bt full):
#0  0x0050c2fc in ?? ()
No symbol table info available.
#1  0x0020 in ?? ()
No symbol table info available.
#2  0x0050c42e in ?? ()
No symbol table info available.
#3  0x0400 in ?? ()
No symbol table info available.
#4  0x7f36cd10b310 in ?? ()
No symbol table info available.
#5  0x0014 in ?? ()
No symbol table info available.
#6  0x004de9e6 in ?? ()
No symbol table info available.
#7  0x7f36c6858388 in ?? ()
No symbol table info available.
#8  0x004de788 in ?? ()
No symbol table info available.
#9  0x7f36ed0c9f58 in ?? ()
No symbol table info available.
#10 0x7f36ed0c9f78 in ?? ()
No symbol table info available.
#11 0x in ?? ()
No symbol table info available.

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

Re: [OpenSIPS-Users] How can the global variable "listen" to listen WLAN ?

2016-03-28 Thread Rodrigo Pimenta Carvalho 

Hi Alex and Bogdan-Andrei.

The customer of my project will use wireless network or cable. It depends on 
the user preference and his home devices capabilities. That is, sometimes my 
hardware with OpenSIPS will be connected to a switch by means of wlan and 
sometimes by means of eth cable.
I can't do a forecast about it.
So, my OpenSIPS.cfg file must be prepared for both situations. How to do it?

For example, if I just write :

listen=tcp:eth0:5060   # CUSTOMIZE ME 
listen=tcp:wlan0:5060   # CUSTOMIZE ME 

This 2 simultaneous configurations will cause problems, because I generally 
only one interface will be used. A kind of error is: 
"ERROR:core:fix_socket_list: could not resolve wlan0"

Any idea for this case will be very helpful!

Thanks a lot.


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


De: Bogdan-Andrei Iancu 
Enviado: quinta-feira, 24 de março de 2016 06:24
Para: OpenSIPS users mailling list; Rodrigo Pimenta Carvalho
Assunto: Re: [OpenSIPS-Users] How can the global variable "listen" to listen 
WLAN ?

Hi Rodrigo,

The listen param may accept as input the name of any network interface
you may have on your system - eth0, eth1, lo, ma1, wlan1,
etcwhatever is listed by "ifconfig" as configured interface may be used.

Regards,

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

On 22.03.2016 13:54, Rodrigo Pimenta Carvalho wrote:
> Hi Alex.
>
> I have tried something similar in the past and I have problems to execute 
> opensips.
> I'm not sure now if I had done exactly this way, but I will try it as your 
> suggestion.
>
> By the way, the opensips documentation doesn't say about wlan for 'listen' 
> variable.
> Let me try it and post the result here with more details.
>
> Regards.
>
>
>
> RODRIGO PIMENTA CARVALHO
> Inatel Competence Center
> Software
> Ph: +55 35 3471 9200 RAMAL 979
>
> 
> De: users-boun...@lists.opensips.org  em 
> nome de Alex Balashov 
> Enviado: segunda-feira, 21 de março de 2016 21:03
> Para: users@lists.opensips.org
> Assunto: Re: [OpenSIPS-Users] How can the global variable "listen" to listen 
> WLAN ?
>
> On 03/21/2016 04:36 PM, Rodrigo Pimenta Carvalho wrote:
>
>> According to the documentation "...It can be an IP address, hostname or
>> network interface id".
>>
>> So, can I do the following configuration?
>>
>>
>> listen=tcp:wlan0:5060
> Why can't you just do exactly that?
>
> --
> 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

[OpenSIPS-Users] Opensips2.1 crash

2016-03-28 Thread Denis 
Hello!

I am going to upgrade my Opensips to 2.1. from 1.11.6.
Opensips 2.1. had been installed on a test server and during the test i notice 
periodic Opensips crash. And i cannot understand the reason.

Thank you for any help.

P.S. In attachment you can find PID of processes before the crash, information 
from log and core file.


mailto:denis7...@mail.ruPID:

Process::  ID=0 PID=9950 Type=attendant
Process::  ID=1 PID=9962 Type=event-route handler
Process::  ID=2 PID=9963 Type=RTPP timeout receiver
Process::  ID=3 PID=9964 Type=MI Datagram
Process::  ID=4 PID=9966 Type=MI FIFO
Process::  ID=5 PID=9968 Type=time_keeper
Process::  ID=6 PID=9969 Type=timer
Process::  ID=7 PID=9970 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=8 PID=9971 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=9 PID=9973 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=10 PID=9974 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=11 PID=9977 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=12 PID=9978 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=13 PID=9981 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=14 PID=9982 Type=SIP receiver udp:213.170.100.146:5060
Process::  ID=15 PID=9984 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=16 PID=9985 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=17 PID=9989 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=18 PID=9990 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=19 PID=9991 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=20 PID=9993 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=21 PID=9995 Type=SIP receiver udp:213.170.100.146:5068
Process::  ID=22 PID= Type=SIP receiver udp:213.170.100.146:5068

LOG:

Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9950]: 
INFO:core:handle_sigs: child process 9966 exited by a signal 11
Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9950]: 
INFO:core:handle_sigs: core was generated
Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9950]: 
INFO:core:handle_sigs: terminating due to SIGCHLD
Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9982]: 
INFO:core:sig_usr: signal 15 received
Mar 28 15:49:32 opensips-mirror /usr/local/opensips2.1/sbin/opensips[9964]: 
INFO:core:sig_usr: signal 15 received

GDB (bt full):
#0  0x0050c2fc in ?? ()
No symbol table info available.
#1  0x0020 in ?? ()
No symbol table info available.
#2  0x0050c42e in ?? ()
No symbol table info available.
#3  0x0400 in ?? ()
No symbol table info available.
#4  0x7f36cd10b310 in ?? ()
No symbol table info available.
#5  0x0014 in ?? ()
No symbol table info available.
#6  0x004de9e6 in ?? ()
No symbol table info available.
#7  0x7f36c6858388 in ?? ()
No symbol table info available.
#8  0x004de788 in ?? ()
No symbol table info available.
#9  0x7f36ed0c9f58 in ?? ()
No symbol table info available.
#10 0x7f36ed0c9f78 in ?? ()
No symbol table info available.
#11 0x in ?? ()
No symbol table info available.

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

Re: [OpenSIPS-Users] Delay requests to avoid CPS provider's CPS limits

2016-03-28 Thread Bogdan-Andrei Iancu 

Hi Mateusz,

You have 2 approaches:

1) send the calls to the carriers as you get them (same rate) - 90 calls 
will be rejected and you can capture that in failure route (I guess they 
will use a given reply code to indicate rejection when exceeding cps); 
in failure route, do a async sleep (or usleep) and send the call again 
to the carrier (serial forking). Hopefully, 10 more will be accepted to 
this new iteration, and you will have to get in failure route only 80.

This is a bit of a brutal approach, but it is the simple.

2) on the carrier side, use ratelimit module to control the cps (not 
more than 10 cps) - each time you send a call to the carrier, check the 
cps for that carrier -> if more than 10 -> do sleep / usleep (in async 
mode !) and retry (you can do a "while(cps>10) usleep()" )


Regards,

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

On 28.03.2016 01:03, Mateusz Bartczak wrote:

Hi

I'm looking for a solution to nicely handle call spikes

The issue is like this:

I have customer generating 100 calls every 10 seconds. Not during 10 
seconds, but exactly every 10 seconds I get 100 calls in one second, 
next 9 seconds nothing and then next 100 calls...


On the other side, I have provider that has 10 CPS limit

In current setup I can only handle every 10 first calls, 90 are 
discarded by the provider. So I can handle only 10% of customer's traffic


I'm thinking about a solution to delay calls above CPS limit to the 
nearly future. If I could delay calls 10-20 by one second, 20-30 by 
two seconds and so on. This way, in theory, I could handle 100% of 
calls not just 10%


I can implement such thing with FreeSWITCH, call parking and some 
fancy scripting, but FS is many, many times slower than OpenSIPS and 
I'd like to avoid using it in such high CPS scenario


Is there any pure OpenSIPS solution to this kind of problem?

Best Regards

Ten e-mail został wysłany z komputera wolnego od wirusów chronionego 
przez Avast.
www.avast.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] New Accounting - PROBLEM

2016-03-28 Thread Bogdan-Andrei Iancu 

Hi Dragomir,

Indeed, there was a typo in the docs and in an export file. Problem 
fixed, please update from GIT.


Regards

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

On 25.03.2016 21:54, Dragomir Haralambiev wrote:

I try with:

do_accounting("log", "cdr");
and
do_accounting("aaa", "cdr");

and receive same error.

2016-03-25 21:49 GMT+02:00 Alex Balashov >:


On 03/25/2016 03:48 PM, Dragomir Haralambiev wrote:

unknown command , missing loadmodule?


That sounds like a typo in the config.

-- 
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] CLUSTERER and PROTO_BIN modules in ver.2.2

2016-03-28 Thread Răzvan Crainea 

Hi, Yuri!

We are working on this examples as we speak. They will be published by 
the time OpenSIPS 2.2 will be released.


Best regards,

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

On 03/25/2016 03:44 PM, Yuri Ritvin wrote:

Since introduction of the CLUSTERER and PROTO_BIN modules the previous
approach of contacts / dialogues replication between OpenSIPS servers
has rendered obsolete. The addition of the actual use case description
of the aforementioned modules (as a replacement of the BIN_LISTEN
directive) will be highly beneficial , particularly a DB table
"clusterer" population method.


___
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