Hi,
I am sorry for re-posting this issue.
I have configured the OpenSIPS to work as REGISTRAR and proxy.
The SIP UA are all mobile devices (PJSIP client running on iOS and Android
devices).
Devices are connecting to the OpenSIPS using TLS.
Registration and Call-routing work fine;
But, the OpenS
Hi,
I am using opensips 1.11.3-tls (x86_64/linux)
git revision: 41408f0
The log file is getting flooded with messages like this:
ERROR:core:io_watch_del: BUG - trying to del fd 175 with flags 2 1
Any tips?
Best Regards,
- Gary
___
Users mailing l
Hello PlayMen,
Looks like you are replying with "100 Trying" after calling t_relay().
Can you reorganize the script so that the "100 Trying" is replied immediately after receiving the intitial INVITE?
sl_send_reply("100", "Trying");
This will hopefully prevent the sender fro
Hi,
I am getting this httpd related memory error
after sending a couple of hundred http GET requests.
WARNING:core:fm_malloc: Not enough free memory, will attempt defragmentation
ERROR:httpd:answer_to_connection: oom while allocating post_request structure
Any advice?
I am using "opensips 1.1
Hi,
What is the meaning of the following error?
ERROR:core:io_watch_del: BUG - trying to del fd 191 with flags 2 1
How to fix it?
I am using "opensips 1.11.3-tls (x86_64/linux)"
Best Regards,
- Gary
___
Users mailing list
Users@lists.opensips.org
h
Hi,
I am using "opensips 1.11.3-tls (x86_64/linux)" git revision: 7e5bbcf
My log file is getting flooded with following errors.
ERROR:core:_tls_read: SYSCALL error -> (0)
ERROR:core:_tls_read: TLS connection to 66.81.1.2:7604 read failed
ERROR:core:_tls_read: TLS read error: 5
ERROR:core:tcp_rea
Hi,
I have one opensips server deployed on Amazon cloud.
I am using AWS health monitoring service which pings opensips intermittently.
(TCP port 5060)
The following error showed up in the log after a few days:
"ERROR:core:tcpconn_new: No more SHM for send chunks pointers"
Tried to know more a
Hi,
I am trying to use the lua module.
It built OK; but throwing the following error on start.
siplua: child_init
siplua: Lua state opened
siplua: siplua error loading file : cannot open : No such file or directory
siplua: failed to load siplua's file
Nov 3 18:57:07 [2556] ERROR:core:init_mod_c
hem working
> > for replies too.
> >
> > Regards,
> >
> > Bogdan-Andrei Iancu
> > OpenSIPS Founder and Developer
> > http://www.opensips-solutions.com
> >
> > On 23.10.2014 02:06, Gary Nyquist wrote:
> >> Hi Bogdan,
> >>
>
> }
>
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 21.10.2014 00:56, Gary Nyquist wrote:
> > Hi,
> >
> > I need to call an external program from the REPLY_ROUTE (on getting
> Hi Gary,
>
> You can do an ugly trick like:
>
> route[EXEC] {
> exec();
> }
>
> onreply_route[...] {
>
> route(EXEC);
>
> }
>
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Develo
Hi,
I need to call an external program from the REPLY_ROUTE (on getting 200 OK).
As per the doc, "exec_msg" and "exec_avp" can be used from REQUEST_ROUTE &
FAILURE_ROUTE only.
Is there any alternative methods to run external programs from the REPLY_ROUTE?
Best Regards,
- Gary
__
s.org/html/docs/modules/1.11.x/tm.html#id295158) to
> see if any rely was received.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 07.10.2014 04:58, Gary Nyquist wrote:
> > Hi,
> >
>
Hi,
Is it possible to know (inside a failure_route[] block), which timeout caused
to land up in the failure_route?
# E.g. in the main route, I have:
if(is_method("INVITE")){
...
...
$T_fr_timeout=8;
$T_fr_inv_timeout=30;
t_on_failure("1");
t_relay();
exit;
}
# And in
Hi,
OpenSIPS routes a call to a SIP device (destination).
And (say) the device returns "486 BUSY" to OpenSIPS.
Now the call needs to be routed to the Voice-Mail server (another SIP device).
How to do it in opensips.cfg?
Any ideas?
Thanks.
Best Regards,
- Gary
__
Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutions
> www.opensips-solutions.com
>
> On 10/02/2014 11:36 PM, Gary Nyquist wrote:
> > Răzvan,
> >
> > Yes, that's the only error showing up (related to rabbitmq).
> >
> > [...]# opensips -V
s.com[http://www.opensips-solutions.com]
On 10/01/2014 08:22 PM, Gary Nyquist wrote:
Hi,
I am using the "event_rabbitmq Module" to "raise_event".
It works fine.
If "raise_event" is not used for a long time, perhaps the MQ socket is getting
closed.
The following message is
Hi,
I am using the "event_rabbitmq Module" to "raise_event".
It works fine.
If "raise_event" is not used for a long time, perhaps the MQ socket is getting closed.
The following message is appearing in the log:
ERROR:event_rabbitmq:rmq_process: cannot send message
What is a good way
.0.0.30\r\nContent-Type: text/plain\r\n"
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 09/23/2014 09:45 PM, Gary Nyquist wrote:
Hi Răzvan,
I tried enclosing with quotes; but it made no difference
OPTIONS packet did not go out o
xt/plain"
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 09/22/2014 07:23 PM, Gary Nyquist wrote:
Hi Răzvan,
Thanks for the response.
The "get_statistics" command works fine with the comma-separated params.
Facing problem with 't_uac_dlg
rameters separated
by comma. You can try something like this:
curl "http://127.0.0.1:/JSON/get_statistics?params=tm:,dialog:"
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 09/18/2014 11:41 PM, Gary Nyquist wrote:
> Hi,
>
> I am trying to use t
Hi,
I am trying to use the MI interface to generate SIP MESSAGE packets locally
and send out to remote SIP UA.
The 'opensipsctl fifo' method works fine.
The 'mi_datagram' method works fine.
But not able to make "mi_json" work with "t_uac_dlg".
Basically, can't figure out how the parameters for
Sent: Tuesday, August 26, 2014 at 1:01 PM
From: "Bogdan-Andrei Iancu"
To: "Gary Nyquist"
Cc: "OpenSIPS users mailling list"
Subject: Re: [OpenSIPS-Users] MESSAGE t_relay()
Hi Gary,
By default, if sending fails, t_relay() will internally generate back a
negative re
nsips.org/Documentation/TroubleShooting-Crash
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 07/14/2014 11:27 PM, Gary Nyquist wrote:
> Hi Razvan..
> I applied the patch and rebuilt opensips.
> Now it fails to start with follwoing error:
> kernel
Hi,
The following type errors are showing up in the log:
ERROR:core:_tls_read: TLS connection to 64.71.31.202:55271 read failed
I am guessing that this error appears when the TLS connection is broken.
Am I correct?
If yes, how can this event be used to remove the corresponding AOR fr
pensips?
BR
-Gary
Sent: Saturday, August 23, 2014 at 6:29 AM
From: "Bogdan-Andrei Iancu"
To: "Gary Nyquist"
Cc: "OpenSIPS users mailling list"
Subject: Re: [OpenSIPS-Users] MESSAGE t_relay()
Hi Gary,
Maybe your request is not leaving OpenSIPS, so no failu
Hi Bogdan,
I am arming the failure route correctly before calling t_relay().
In my case the transport is TLS.
Could that be the reason for not hitting the failure route?
BR
-Gary
Sent: Friday, August 22, 2014 at 4:12 PM
From: "Bogdan-Andrei Iancu"
To: "Gary Nyquist&
outes-1-11#toc3
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 15.08.2014 00:11, Gary Nyquist wrote:
Hi,
I am using t_relay() function to send some text using SIP MESSAGE method.
What is a smart way to confirm if the MESSAGE got tr
Hi,
I am using t_relay() function to send some text using SIP MESSAGE method.
What is a smart way to confirm if the MESSAGE got transmitted successfuly or not?
Any ideas?
Thanks
-Gary
___
Users mailing list
Users@lists.opensips.org
http:
Hi,
I am getting TLS errors like this:
ERROR:core:tls_accept: New TLS connection from 64.71.31.202:61509 failed to accept: rejected by client
Any tips how to proceed with troubleshooting?
Thanks
-Gary
___
Users mailing list
Users@lis
s,
Răzvan
On 08/04/2014 10:40 PM, Gary Nyquist wrote:
Hi Răzvan,
I am using 1.11.2-tls
version: opensips 1.11.2-tls (x86_64/linux)
flags: STATS: On, USE_IPV6, USE_TCP, USE_TLS, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAP
so using rtpproxy/media proxy for your calls? Most likely you are changing the SDP information twice.
Best regards,
Răzvan
On 08/02/2014 04:31 AM, Gary Nyquist wrote:
Hi,
Found that, fix_nated_sdp() is changing the connection info from:
Connection Information (c): IN IP4 64.71.31.
Hi,
Found that, fix_nated_sdp() is changing the connection info from:
Connection Information (c): IN IP4 64.71.31.202
to
Connection Information (c): IN IP4 64.71.31.20264.71.31.202
Is this the expected behavior?
Thanks
-Gary
___
Users m
by OpenSIPS is not signed by a Certificate Authority recognised by the SIP client.
Adrian
On 18 Jul 2014, at 18:08, Gary Nyquist <g...@gmx.us> wrote:
Hi Bogdan,
Thanks for the response.
I have a bunch of SIP softphones pointing to the OpenSIPS.
The OpenSIPS is lestening on:
at 6:31 AM
From: "Bogdan-Andrei Iancu"
To: "OpenSIPS users mailling list" , "Gary Nyquist"
Subject: Re: [OpenSIPS-Users] WARNING:core:get_send_socket: protocol/port mismatch
Hi,
That error means OpenSIPS detected a conflict when comes to what protocol to be used for s
Hi,
The follwoing line works fine:
t_relay("udp:192.168.1.10:5060");
But the following throwing error:
$var(ru)="udp:192.168.1.10:5060";
t_relay($var(ru));
Error is: bad arguments for command
Is there any way to make it work?
Thanks
-Gary
_
I am getting the following WARNING:
DBG:tm:t_relay_to: forwarding ACK
DBG:core:mk_proxy: doing DNS lookup...
DBG:core:get_send_socket: force_send_socket of different proto (3)!
WARNING:core:get_send_socket: protocol/port mismatch
I am using opensips 1.11.2 script_helper module.
I b
Hi,
I am getting this error in the log.
WARNING:core:get_send_socket: protocol/port mismatch
Any advice how to fix it?
Thanks
-Gary
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo
7;timeout' occurred?
Thanks
-Gary
Sent: Wednesday, July 16, 2014 at 8:37 AM
From: "Bogdan-Andrei Iancu"
To: "OpenSIPS users mailling list" , "Gary Nyquist"
Subject: Re: [OpenSIPS-Users] t_relay
Gary,
Maybe take a look at the 0x02 flag for t_relay()
Hi,
Looking for some insight into the t_relay().
I am using the t_relay() to route INVITE to the Callee device (sip client running on a mobile device).
I was expecting the t_relay() to fail (returning a -ve number), when the sip client is not running on the mobile device.
But I find that
Hi,
Please see the attached picture.
The middle IP is OpenSIPS.
It is taking more than 3 seconds to relay some of the responses.
This is opensips 1.11.2
Using script_helper_module.
Any advices?
Thanks
-Gary
___
Users mailing list
Use
are working on fixing it asap.
>
> Thanks and regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 11.07.2014 00:00, Gary Nyquist wrote:
>> I am setting the FQDN like this:
>> modparam("cachedb_
e a glitch in there
> (FQDN versus IP) - we are working on fixing it asap.
>
> Thanks and regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com
>
> On 11.07.2014 00:00, Gary Nyquist wrote:
>> I am setting the
ain to "go-around" trip to impossible destination. Of course while this is happening, you should send fake "180 Ringing" message to caller so s/he won't suffer from dead-air silence.
Thank you.
On 2014-07-10 22:17, Gary Nyquist wrote:
Hi,
I am looking for s
p://www.opensips.org/html/docs/modules/1.12.x/tm.html#id294475
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 07/11/2014 12:07 AM, Gary Nyquist wrote:
Hi,
I am getting following error:
CRITICAL:core:timer_ticker: timer handler lasted (791 us) for more th
Hi,
I am looking for some idea for the following use case:
1. opensips receives initial INVITE from the caller.
2. finds that the callee is not registered.
3. sends a non-SIP message to the callee device to register.
4. callee registers and opensips routes the INVITE to the callee contac
ssages, starting with the following line:
ERROR:cachedb_redis:redis_connect_node: failed to open redis connection rediscluster.vhr�#030:6379 - Name or service not known
BR
-Gary
Sent: Thursday, July 10, 2014 at 12:41 PM
From: "Bogdan-Andrei Iancu"
To: "OpenSIPS users mailling list" ,
Hi,
I am getting following error:
CRITICAL:core:timer_ticker: timer handler lasted (791 us) for more than timer tick (100 us) -> potential timer shifting
Can't figure out what could be the reason...
I am setting : $T_fr_inv_timeout
Not using the "timer_route"
Any advice?
Hi,
I am trying to use the FQDN for specifying the 'cachedb_url' like this:
modparam("cachedb_redis", "cachedb_url","redis:cluster://my_redis_server.com:6379/")
But it is not working;
Whereas the following is working fine:
modparam("cachedb_redis", "cachedb_url","redis:cluster://10.0.0.
n buffer in the script. You
have to modify the PV_PRINT_BUF_SIZE (from pvar.c) variable and then
recompile opensips to make it work.
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 07/04/2014 12:17 AM, Gary Nyquist wrote:
>
> I am sorry... Please i
I am sorry... Please ignore the below email.
The 'buf_size' setting is working fine.
I am using "add_body()" function like this:
add_body($avp(s), "text/plain");
It is adding/replacing the body only if the length of $avp(s) is less than 1024.
How to make it work for 'longer than 1024'?
My tran
Hi,
I am trying to increase the avpops buf_size to 4096:
modparam("avpops", "buf_size", 4096)
But it seems to be set to 1024.
I am using opensips-1.11.2
Is there something else to be done to increase the buf_size?
BR
-Gary
___
Users mailing list
U
. Thank you for reporting - it should actually be a debugging message.
Best regards,
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 06/30/2014 07:00 PM, Gary Nyquist wrote:
Hi Vlad,
Thanks for taking up this issue.
1. Yes. tcp_async=1
2. Running on CentOS ( 2.6.32-
Hi,
I am trying to migrate to OpenSIPS 1.11.
Observing that, it is sending out OPTIONS packets, when the session is going on (after the ACK); using the same Call-ID as that of the ongoing Call.
Is there a way to stop these OPTIONS packets to be originated (during ongoing sessions) from the
p option in your OpenSIPS script ?
Also, what architecture / OS are you running on ?
What steps are you taking in reproducing this ?
Best Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 27.06.2014 19:59, Gary Nyquist wrote:
Thanks Bogdan for looking into it.
Here is
, 2014 at 10:56 AM
From: "Bogdan-Andrei Iancu"
To: "Gary Nyquist"
Cc: "OpenSIPS users mailling list"
Subject: Re: [OpenSIPS-Users] TCP Errors
Hi,
That bug log actually says OpenSIPS tries to remove a connection marked as READ from a list for WRITEs :)..
I will look
Hi,
I am little confused about nat_traversal and nathelper modules.
There is a "keepalive_interval" and there is a "natping_interval".
What is the difference?
Best
--Gary
___
Users mailing list
Users@lists.opensips.org
http://lists.ope
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 24.06.2014 21:34, Gary Nyquist wrote:
Hi,
The following lines are repeating in the log.
ERROR:core:tcp_blocking_connect: timeout 10 s elapsed from 10 s
ERROR:core:tcpconn_connect: tcp_
Hi,
The following lines are repeating in the log.
ERROR:core:tcp_blocking_connect: timeout 10 s elapsed from 10 s
ERROR:core:tcpconn_connect: tcp_blocking_connect failed
ERROR:core:tcp_send: connect failed
ERROR:tm:msg_send: tcp_send failed
INFO:core:send2child: no free tcp receiver, c
Hi,
The following 4 lines are repeating in the log.
ERROR:core:tcp_blocking_connect: timeout 10 s elapsed from 10 s
ERROR:core:tcpconn_connect: tcp_blocking_connect failed
ERROR:core:tcp_send: connect failed
ERROR:tm:msg_send: tcp_send failed
Any guess, what could be the reason?
Bes
Never mind...
Got the culprit...
- Original Message -
From: Gary Nyquist
Sent: 05/08/14 05:20 PM
To: OpenSIPS users mailling list
Subject: [OpenSIPS-Users] bad r-uri
Hi,
On sending CANCEL request ro OpenSIPS (which looks like this):
Request-Line: CANCEL sip:+12488317282@69.84.64.23 SIP
Hi,
On sending CANCEL request ro OpenSIPS (which looks like this):
Request-Line: CANCEL sip:+12488317282@69.84.64.23 SIP/2.0
OpenSIPS is responding back with this:
Status-Line: SIP/2.0 400 bad r-uri
There is nothing in the opensips.cfg to return "400 bad r-uri".
Perhaps the OpenSIPS core is return
/html/docs/modules/1.4.x/cfgutils.html#id293666
Thanks,
Tito
On Wed, Apr 30, 2014 at 2:47 PM, Gary Nyquist < g...@gmx.us > wrote:
Hello,
I am using to use a 'while()' loop in the opensips.cfg file.
And need to put a delay of 1 second in the loop.
Is there any 'sleep' fu
Hello,
I am using to use a 'while()' loop in the opensips.cfg file.
And need to put a delay of 1 second in the loop.
Is there any 'sleep' function to create the delay?
Best
--Gary
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/c
file a bug report on the GitHub tracker
[1]. We will take care of it as soon as possible!
[1]: https://github.com/OpenSIPS/opensips/issues
Best regards,Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com
On 04/25/2014 08:22 PM, Gary Nyquist wrote:
Hello,
I am using opensips 1.10.0
Hello,
I am using opensips 1.10.0-tls (x86_64/linux)
The ACK for 200 OK (INVITE) reaches OpenSIPS with "TO Header" as shown below:
To: ;tag=317502E0-535A8FD70008B114-90183700
But... OpenSIPS sends out the ACK with "TO Header" mangled as shown below:
To: =?716N94.84.190.24>;tag=317502E0-535A8FD7000
Hi,
I am trying to configure the OpenSIPS v.1.10 to make it write the CDRs to flat
files.
But no luck yet.
The "opensips.cfg" looks like this:
...
loadmodule "dialog.so"
modparam("dialog", "dlg_match_mode", 1)
loadmodule "acc.so"
modparam("acc", "detect_direction", 1)
modparam("acc", "failed_trans
67 matches
Mail list logo
