The destination (in this case) is the 1st server in the loadbalancer list (as
there are no other calls).
I've upgraded this machine to ubuntu 10 (from 8) and started getting Connection
Tracking drop messages in my
syslog. I've disabled connection tracking and the issue hasn't appeared since...
I have done no recording so I can't speak to those formats used.
-dg
On Thu, May 6, 2010 at 6:33 AM, Indiver nehru.i...@gmail.com wrote:
Thanks for your response Daniel. I included the patch and it's started
working !. Now i'm testing the rtpproxy with different scenarios. Both
clients
Hi,
try using any software specialized in monitoring or testing applications
(monit, nagios, sipsak, etc) to detect the failure of opensips service
and to trigger heartbeat switching.
Regards,
Bogdan
rajib deka wrote:
Hi Bogdan,
I have seen that heartbeat is supporting box level failure
Hi Alejandro,
Alejandro Recarey wrote:
I am using OpenSIPS to load balance incoming calls between my asterisk
boxes, with great results! The LB module is perfect for this.
I am currently configuring OpenSIPS to also act as an outbound proxy
to my asterisk boxes. This is because some VoIP
So, after all, it was a network layer configuration issue... :)
Regards,
Bogdan
Erik Versaevel wrote:
The destination (in this case) is the 1st server in the loadbalancer list (as
there are no other calls).
I've upgraded this machine to ubuntu 10 (from 8) and started getting
Connection
That might be :)
I'm now running into problems with the dialog module (which i use to limit
concurrent calls).
Calls seem to stick in the dialog module (thus denying additional calls) while
the endpoint isn't
listing the same amount of calls :/
Regards,
Erik
Op 6-5-2010 11:02, Bogdan-Andrei
What is the state of the dialog stuck in memory? (use dlg_list MI
command to see them).
Also check that the sequential requests (ACK, re-INVITE, BYE) do go
through your proxy (via loose_route).
Regards,
Bogdan
Erik Versaevel - InfoPact Netwerkdiensten wrote:
That might be :)
I'm now
Hi everybody,
I try to generate SIP traffic to test the power of OpenSIPS but I don't know
how to do a simple test. I did : /sipp -sn uas and ./sipp -sn uac
192.168.0.190 (ip of my opensips) but all calls are failed. I have not
understood yet how to do the test yet.
Can someone help me?
Thanks
Hi,
I've configured OpenSIPs using Nathelper module and rtpproxy. the problem
I'm facing is when I try to register my softphone, it got registered but as
I issue the command opensipsctl ul show, in contact header the IP is private
not public. The configuration of OpenSIPs is listed down below;
Hi Rajib,
I have several customers using opensips in HA, and I use in all of then
Keepalived (instead of Heartbeat), and the Sipsak to test the service level,
so Sipsak send an OPTIONS request to Opensips and if does not receive the
answer, Sipsak trigger the failover in the Keepalived.
In other
Hi Samoh,
It could be because your calls are not allowed at the Opensips, the default uri
of the sipp is something like service@ope.nsi.ps.ip.
try to Ngrep it to see the uri and allow it at opensips or change at sipp.
Regards.
- - -
Andrey Cassemiro
(11) 6343-0411
Date: Thu, 6 May
Hi Andrey,
I use my opensips without authentification, I used ngrep and I noticed that
it try to join serv...@192.168.0.190 but the opensips answer don't found it,
I don't know if I must start another sipp process which will be the
serv...@192.168.0.190 ??!
Thanks.
Sam.
--
View this message in
Hi Ahmed,
check the following things:
1) you do fix_nated_register() before save(location)
2) the received_avp param has the same value in registrar and nathelper
module
3) you configured the nat_bflag param in usrloc module and you are
setting it before save(location)
Regards,
Bogdan
Hi,
I am just moving to 1.6.2 and it works great except for the drouting
module crashes out under load. I saw this happening before in the
forum but never saw a resolution. Is there a fix for this? The same
config works under 1.5.1.
When the crash happens the threads just go away one by one
I just compiled the STUN module on Debian 5.0.4 x64 and added the following
stun parameters to my config
port=5060
/* uncomment and configure the following line if you want opensips to
bind on a specific interface/port/proto (default bind on all available)
*/
15 matches
Mail list logo