Re: [OpenSIPS-Users] opensips to asterisk and viceversa

2010-03-15 Thread ram
On Sat, Mar 13, 2010 at 11:28 AM, bhrugu mehta mehtabhr...@gmail.comwrote:

 Hi, all
 i have used opensips as registrar.
 my scenario,

 opensips-asterisk(routing logic)-opensips

 i have done with opensips to asterisk call .
 asterisk deside where to call go , and if local call then go to opensips.

 asterisk to opensips call not done.

 any suggetion?



post some network trace to suggest

Ram,

 --
 Bhrugu Mehta
 Sr. S/W Engineer (DD)
 VOIP,Telephony Team
 India

 ___
 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] Problem with /tmp/opensips_fifo

2010-03-15 Thread Bogdan-Andrei Iancu
Hi Erick,

For the failing tools, do you have the corresponding opensips modules 
loaded ?

Like, for  Dialog tool, do you have the dialog module loaded ?

Regards,
Bogdan


Erick Chinchilla Berrocal wrote:
 Bodgan 
 I made the following change in the file etc/monit/monitrc
 The manual said insert the line 
 check process opensips with pidfile /var/run/opensips.pid
 and i changed to 
 check process opensips with pidfile /var/run/opensips/opensips.pid
  with this change in the control panel the module MONIT is working well

 with this change in the control panel the module MONIT is working well
 now the problem continues with the following modules, please let me know if
 you have idea, I read the manual for several times and no 

 - CDRViever = ok 
 - Dialog = Array ( [0] = sorry -- reply fifo opening error )
 - DialPlan = ok
 - Dispatcher = Array ( [0] = sorry -- reply fifo opening error [1] = sorry
 -- reply fifo opening error )
 - Domain = ok
 - Dymanic Routing = ok
 - Load Balancer = ok
 - MI Comands = /tmp/opensips_fifo
 - Monit = ok
 - Nathelper = ok
 - Permissions = ok
 - Prefix 2 Domain = ok
 - SIP Trace = Array ( [0] = sorry -- reply fifo opening error )
 - Static Monitor = sorry -- reply fifo opening error

 I understand the important for the files db.inc.php and
 boxes.global.inc.php , my current setup is the example in the book
 charpter 6, page 132. the only difference is the password, the primary name
 server

 This is the log 
 Mar 12 17:44:42 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command ds_list is not available
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command ds_reload is not available
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:07:59 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command sip_trace is not available
 Mar 12 18:07:59 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:08:24 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)


 Thanks

 To: 'OpenSIPS users mailling list'
 Subject: RE: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

 Bodgan
 Thanks for your assistant.
 After of change the file opensips.cfg the configuration is
 # - mi_fifo params -
 modparam(mi_fifo, fifo_name, /tmp/opensips_fifo)
 modparam ( mi_fifo, fifo_mode, 0666)

 if only use the line modparam ( mi_fifo, fifo_mode, 0666) not work

 Now in the Control Panel continues with problems a:
 -Dialog = if only use the line modparam ( mi_fifo, fifo_mode, 0666)
 not work
 -Dispatcher = 
   Array ( [0] = sorry -- reply fifo opening error )
   Array ( [0] = sorry -- reply fifo opening error
 [1] = sorry -- reply fifo opening error )
 -MI Commands = /tmp/opensips_fifo
   sorry -- reply fifo opening error

 -Monit = opensips - Execution Failed

 -SIP trace  = Array ( [0] = sorry -- reply fifo opening error )

 -Static Monitor = sorry --reply fifo opening error

 ###
 The is the email from the server

 Subject: Cron r...@netphp
 /var/www/opensips-cp/cron_job/get_opensips_stats.php  /dev/null
 Content-Type: text/plain; charset=UTF-8
 X-Cron-Env: SHELL=/bin/sh
 X-Cron-Env:
 PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bi

 ###
 This is the log from Opensips-Server
 Mar 12 13:55:01 net /sbin/opensips[2769]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 13:56:01 net /sbin/opensips[2769]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 13:56:30 net /sbin/opensips[2769]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 13:56:34 net /sbin/opensips[2769]: ERROR:mi_fifo:mi_fifo_server:
 command ds_list is not available
 Mar 12 13:56:34 net /sbin/opensips[2769]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 13:56:34 net /sbin/opensips[2769]: ERROR:mi_fifo:mi_fifo_server:
 command ds_reload is not available
 Mar 12 13:56:34 net /sbin/opensips[2769]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 

Re: [OpenSIPS-Users] keepalived for HA OpenSIPS

2010-03-15 Thread Bogdan-Andrei Iancu
Hi Gavin,

As I understand you try to solve the SPOF issue with the your opensips 
front load balancer, right ? Instead of adding another component to do 
the monitor the LB, why not using a HA system (vrrp, heartbeat, etc) to 
have an active-backup configuration for the LB ?

Regards,
Bogdan

Gavin Henry wrote:
 Hi,

 When using OpenSIPS and the load balancer module your SPOF is still
 OpenSIPS. Have others had success with keepalived looking after two
 OpenSIPS servers?

 We have OpenSIPS in front of a cluster of Asterisk boxes for a
 customer and the same setup in a different data center. We'd like to
 put a keepalived in front of both OpenSIPS servers, i.e. in front of
 both datacentres. But then that leaves a SPOF with the keepalived
 server. We could have backup server of that two (both data centers
 have real time replication between them also).

 What are the best practices you recommend here?

 Thanks,

 Gavin.

   


-- 
Bogdan-Andrei Iancu
www.voice-system.ro


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


Re: [OpenSIPS-Users] OpenSIPS + FreeRadius Accounting and Authentication

2010-03-15 Thread Bogdan-Andrei Iancu
Hi Ahmed,

Please check this tutorial:
http://www.opensips.org/Resources/DocsTutorials#toc11
or
http://voiprookie.blogspot.com/2009/04/freeradius-and-mysql.html

Regards,
Bogdan

Ahmed Munir wrote:
 Hi,

 I've configured OpenSIPS + FreeRadius Accounting and Authentication 
 setup, which was implemented success full. Using Authentication via 
 Freeradius can anybody tell me how can I populate data on  radius 
 database tables? Mean what sort of values do I required  for its 
 tables so I can authenticate and register my softphone? Like in tables 
 radreply, radgroupcheck, radgroureply, realms, etc.

 Kindly put the light on it and assist me with some sample data.

 -- 
 Regards,

 Ahmed Munir


 

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


-- 
Bogdan-Andrei Iancu
www.voice-system.ro


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


Re: [OpenSIPS-Users] keepalived for HA OpenSIPS

2010-03-15 Thread Gavin Henry
On 15 March 2010 09:52, Bogdan-Andrei Iancu bog...@voice-system.ro wrote:
 Hi Gavin,

 As I understand you try to solve the SPOF issue with the your opensips
 front load balancer, right ? Instead of adding another component to do
 the monitor the LB, why not using a HA system (vrrp, heartbeat, etc) to
 have an active-backup configuration for the LB ?

Hi Bogdan,

That's what I said:

We'd like to put a keepalived in front of both OpenSIPS servers.
keepalived is VRRP.

My question is you'll still have just one keepalived server monitoring
the systems.

I'm trying to understand what others do here. We have for this customer:

DC1:

OpenSIPS - Asterisk...Asterisk...Asterisk


DC2:
OpenSIPS - Asterisk...Asterisk...Asterisk


What do others put in front to switch between the two datacenters but
still avoiding having one keepalived/heartbeat server inbetween these
two DCs?

Do you address this by having a few heartbeat/keepalived servers that
get returned for the DNS records, for example:

sip.mycustomer.com returns a keepalived IP that is running in each
datacentre whereby each VRRP server points to both DCs. Then if anyone
one goes down its points to the other?

Thanks,

Gavin.

-- 
http://www.suretecsystems.com/services/openldap/
http://www.suretectelecom.com

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


Re: [OpenSIPS-Users] keepalived for HA OpenSIPS

2010-03-15 Thread Bogdan-Andrei Iancu
Hi Gavin,

Gavin Henry wrote:
 On 15 March 2010 09:52, Bogdan-Andrei Iancu bog...@voice-system.ro wrote:
   
 Hi Gavin,

 As I understand you try to solve the SPOF issue with the your opensips
 front load balancer, right ? Instead of adding another component to do
 the monitor the LB, why not using a HA system (vrrp, heartbeat, etc) to
 have an active-backup configuration for the LB ?
 

 Hi Bogdan,

 That's what I said:

 We'd like to put a keepalived in front of both OpenSIPS servers.
 keepalived is VRRP.
   
Oh, ok - I thought you meant another fronting app doing the KA to the 
opensips servers (LBs)
 My question is you'll still have just one keepalived server monitoring
 the systems.

 I'm trying to understand what others do here. We have for this customer:

 DC1:

 OpenSIPS - Asterisk...Asterisk...Asterisk


 DC2:
 OpenSIPS - Asterisk...Asterisk...Asterisk


 What do others put in front to switch between the two datacenters but
 still avoiding having one keepalived/heartbeat server inbetween these
 two DCs?
   
The vrrp or heartbeat does not requirement any extra servers - these 
application are run on the same servers are the front-end app (OpenSIPS 
LB in your case).

Here, the concept is of having a floating IP (controlled by vrrp or HB) 
that may be dynamically moved and attached to a server (the opensips 
servers in your case).

These mechanisms require to have the servers (sharing the IP) to be in 
the same network (as ARP pings are used) - and also you cannot simply 
move an IP from a network to other.
 Do you address this by having a few heartbeat/keepalived servers that
 get returned for the DNS records, for example:

 sip.mycustomer.com returns a keepalived IP that is running in each
 datacentre whereby each VRRP server points to both DCs. Then if anyone
 one goes down its points to the other?
   
your DNS will point to a virtual IP, where this IP may be mapped either 
to the opensips in DC1 or in DC2 . VRRP will be running on the opensips 
servers in both DC.

Regards,
Bogdan
 Thanks,

 Gavin.

   


-- 
Bogdan-Andrei Iancu
www.voice-system.ro


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


Re: [OpenSIPS-Users] [Presence] How to receive presence NOTIFY over TCP ?

2010-03-15 Thread Iñaki Baz Castillo
2010/3/11 Pascal Maugeri pascal.maug...@gmail.com:
 Ok, good comment. Yes indeed we have a SIP proxy between the subscriber and
 opensips (which is only acting as presence server in this scenario).
 I thought there were two problems (one at proxy and one at presence server
 side). We will work on proxy side now to solve this issue.

I've the same topology working with no issues (SIP TCP natted client,
a proxy and OpenSIPS as presece-server behind it, using TCP between
client and proxy, and UDP between proxy and OpenSIPS). It just works,
but you need a keepalive system to mantain the TCP connection between
the client and the proxy.
Tipically it's done by the client who keeps it by sending a periodic
TCP message (not a SIP message but anything).

Where is your problem exactly? do you have issues to get the first
NOTFY after sending the initial SUBSCRIBE? or do the issues arise just
for subsequent notifications?


-- 
Iñaki Baz Castillo
i...@aliax.net

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


Re: [OpenSIPS-Users] keepalived for HA OpenSIPS

2010-03-15 Thread Gavin Henry
On 15 March 2010 10:38, Bogdan-Andrei Iancu bog...@voice-system.ro wrote:
 Hi Gavin,

 Gavin Henry wrote:
 On 15 March 2010 09:52, Bogdan-Andrei Iancu bog...@voice-system.ro wrote:

 Hi Gavin,

 As I understand you try to solve the SPOF issue with the your opensips
 front load balancer, right ? Instead of adding another component to do
 the monitor the LB, why not using a HA system (vrrp, heartbeat, etc) to
 have an active-backup configuration for the LB ?


 Hi Bogdan,

 That's what I said:

 We'd like to put a keepalived in front of both OpenSIPS servers.
 keepalived is VRRP.

 Oh, ok - I thought you meant another fronting app doing the KA to the
 opensips servers (LBs)
 My question is you'll still have just one keepalived server monitoring
 the systems.

 I'm trying to understand what others do here. We have for this customer:

 DC1:

 OpenSIPS - Asterisk...Asterisk...Asterisk


 DC2:
 OpenSIPS - Asterisk...Asterisk...Asterisk


 What do others put in front to switch between the two datacenters but
 still avoiding having one keepalived/heartbeat server inbetween these
 two DCs?

 The vrrp or heartbeat does not requirement any extra servers - these
 application are run on the same servers are the front-end app (OpenSIPS
 LB in your case).

Ah, my lack of understanding there.

 Here, the concept is of having a floating IP (controlled by vrrp or HB)
 that may be dynamically moved and attached to a server (the opensips
 servers in your case).

Understood.

 These mechanisms require to have the servers (sharing the IP) to be in
 the same network (as ARP pings are used) - and also you cannot simply
 move an IP from a network to other.

Right, thanks.

 Do you address this by having a few heartbeat/keepalived servers that
 get returned for the DNS records, for example:

 sip.mycustomer.com returns a keepalived IP that is running in each
 datacentre whereby each VRRP server points to both DCs. Then if anyone
 one goes down its points to the other?

 your DNS will point to a virtual IP, where this IP may be mapped either
 to the opensips in DC1 or in DC2 . VRRP will be running on the opensips
 servers in both DC.

Thanks.

 Bogdan-Andrei Iancu
 www.voice-system.ro


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




-- 
http://www.suretecsystems.com/services/openldap/
http://www.suretectelecom.com

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


[OpenSIPS-Users] MediaProxy - multiple dispatchers

2010-03-15 Thread Marco Nesler
hi all,
i'm configuring a mediaproxy setup with a single media relay server and two
media dispatchers (two separate OpenSIPS proxies).
Can I have two dispatchers pointing to the same media relay ? is this one a
supported configuration or should i have a separate set of media relays for
each dispatcher ?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

2010-03-15 Thread Erick Chinchilla Berrocal
Hi
Bogdan
The problem continues

I have these modules

##
/lib/opensips/modules# ls
aaa_radius.so call_control.so  diversion.so load_balancer.so
options.sorr.so  textops.so
acc.socfgutils.so  domainpolicy.so  localcache.so
path.so   seas.sotm.so
alias_db.so   closeddial.sodomain.somangler.sopdt.so
signaling.so   uac_redirect.so
auth_aaa.so   db_flatstore.so  drouting.so  maxfwd.so
peering.sosiptrace.souac.so
auth_db.sodb_mysql.so  enum.so  mediaproxy.so
permissions.sosl.so  uri.so
auth_diameter.so  db_text.so   exec.so  mi_datagram.so
pike.so   sms.so userblacklist.so
auth.so   db_virtual.sogflags.somi_fifo.so
presence_xcapdiff.so  speeddial.so   usrloc.so
avpops.so dialog.sogroup.so msilo.so  qos.so
sst.so xlog.so
b2b_entities.so   dialplan.so  imc.so   nathelper.so
ratelimit.so  statistics.so
benchmark.so  dispatcher.solcr.so   nat_traversal.so
registrar.so  stun.so

##
/etc/opensips/opensips.cfg
/* uncomment next line for MySQL DB support */
loadmodule db_mysql.so
loadmodule signaling.so
loadmodule sl.so
loadmodule tm.so
loadmodule rr.so
loadmodule maxfwd.so
loadmodule usrloc.so
loadmodule registrar.so
loadmodule textops.so
modparam(dialog, db_mode, 1)
loadmodule mi_fifo.so
loadmodule uri.so
loadmodule xlog.so
loadmodule acc.so
loadmodule dialog.so


#--- dialog -
modparam(dialog, db_url,
mysql://(username):(password)@localhost/opensips)
modparam(dialog, dlg_flag, 4)

Reference:
http://www.opensips.org/Resources/PuaDialoinfoConfig

I tried with this options and get the same problem
# DIALOG #
loadmodule dialog.so
modparam(dialog, enable_stats, 1)
modparam(dialog, default_timeout, 21600)
modparam(dialog, db_url, mysql://opensips:opens...@database/opensips)
modparam(dialog, db_mode, 1)
modparam(dialog, dlg_flag, 4)

Reference
http://gventure.wordpress.com/2009/03/30/opensips-installation/


##

opensips -c
Listening on 
 udp: 127.0.0.1 [127.0.0.1]:5060
 udp: 192.168.50.10 [192.168.50.10]:5060
 tcp: 127.0.0.1 [127.0.0.1]:5060
 tcp: 192.168.50.10 [192.168.50.10]:5060
Aliases: 
 tcp: net:5060
 tcp: server.dominio.com:5060
 tcp: localhost:5060
 udp: server:5060
 udp: server.dominio.com:5060
 udp: localhost:5060

Mar 15 13:06:03 [3014] NOTICE:core:main: config file ok, exit

##
# opensipsctl online
database engine 'MYSQL' loaded
Control engine 'FIFO' loaded
1001

##
In the control panel 
Module Diallog = Array ( [0] = sorry -- reply fifo opening error )

Any ideas

Thanks
Erick

-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Monday, March 15, 2010 3:47 AM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

Hi Erick,

For the failing tools, do you have the corresponding opensips modules 
loaded ?

Like, for  Dialog tool, do you have the dialog module loaded ?

Regards,
Bogdan


Erick Chinchilla Berrocal wrote:
 Bodgan 
 I made the following change in the file etc/monit/monitrc
 The manual said insert the line 
 check process opensips with pidfile /var/run/opensips.pid
 and i changed to 
 check process opensips with pidfile /var/run/opensips/opensips.pid
  with this change in the control panel the module MONIT is working well

 with this change in the control panel the module MONIT is working well
 now the problem continues with the following modules, please let me know
if
 you have idea, I read the manual for several times and no 

 - CDRViever = ok 
 - Dialog = Array ( [0] = sorry -- reply fifo opening error )
 - DialPlan = ok
 - Dispatcher = Array ( [0] = sorry -- reply fifo opening error [1] =
sorry
 -- reply fifo opening error )
 - Domain = ok
 - Dymanic Routing = ok
 - Load Balancer = ok
 - MI Comands = /tmp/opensips_fifo
 - Monit = ok
 - Nathelper = ok
 - Permissions = ok
 - Prefix 2 Domain = ok
 - SIP Trace = Array ( [0] = sorry -- reply fifo opening error )
 - Static Monitor = sorry -- reply fifo opening error

 I understand the important for the files db.inc.php and
 boxes.global.inc.php , my current setup is the example in the book
 charpter 6, page 132. the only difference is the password, the primary
name
 server

 This is the log 
 Mar 12 17:44:42 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: 

Re: [OpenSIPS-Users] MediaProxy - multiple dispatchers

2010-03-15 Thread Saúl Ibarra Corretgé
Hi,

On 15/3/10 6:01 PM, Marco Nesler wrote:
 hi all,
 i'm configuring a mediaproxy setup with a single media relay server and
 two media dispatchers (two separate OpenSIPS proxies).
 Can I have two dispatchers pointing to the same media relay ? is this
 one a supported configuration or should i have a separate set of media
 relays for each dispatcher ?


Yes, you may use different dispatchers pointing to a single relay.


Regards,

-- 
Saúl Ibarra Corretgé
AG Projects

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


Re: [OpenSIPS-Users] Users Digest, Vol 20, Issue 27

2010-03-15 Thread Sathyanarayanan R
Hi,

Thanks for your suggestion, Bogdan. 

I looked into the opensips log and found that there were errors on memory
allocation. So we increased the memory pool size to 10 MB from 1 MB and
Shared memory size to 256. Now it is working fine. Is there any recommended
memory pool size?

I require couple of other clarifications:
- What is the maximum CPS it supports on the stateful proxy?
- How do we achieve fault tolerance and redundancy in the opensips?

Regards,
Sat

Message: 3
Date: Tue, 09 Mar 2010 11:17:04 +0200
From: Bogdan-Andrei Iancu bog...@voice-system.ro
Subject: Re: [OpenSIPS-Users] Load Balancer Issue
To: OpenSIPS users mailling list users@lists.opensips.org
Message-ID: 4b961210.7050...@voice-system.ro
Content-Type: text/plain; charset=windows-1252; format=flowed

Hi,

I see here 2 reports:
1) opensips dies - check the log files for error messages to see why 
opensips stopped
2) load not decreasing - this means the BYE is missing or is not 
properly processed by opensips, so it thinks the call is still on. If 
you see that the BYEs are passing through, you could enable debugging 
only for the loose_route() function (use set_debug() function) to see if 
the BYE matches or not. Also you can check via teh dlg_list MI 
function the state of the ongoing calls.

Regards,
Bogdan

Sathyanarayanan R wrote:

 We are using Opensips load balancer module to make outbound calls, 
 when we pump more than 30 CPS, load in the load balancer is not 
 decreased even after the call ends. Beyond certain point opensips 
 service stops with the error ?Opensips dead but subsys locked?. How 
 this problem should be approached and solved?

 Regards,

 Sathya

 

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


-- 
Bogdan-Andrei Iancu
www.voice-system.ro




--


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


Re: [OpenSIPS-Users] Users Digest, Vol 20, Issue 27

2010-03-15 Thread Bogdan-Andrei Iancu
Hi Sat,

the mem error - which memory they were related ? pkg or shm ? and from 
which module?

How much memory to use depends on your script - on what modules you are 
using and what traffic you expect (cps and calls)

According to the latest tests, opensips 1.6 can handle in simple 
stateful proxy mode (no dns, no DB, just proxy) about 10K cps on a 
decent server.

For failover - you are looking for HA of the opensips box, or how to use 
opensips to achieve HA for the boxes behind ?

Regards,
Bogdan


Sathyanarayanan R wrote:
 Hi,

 Thanks for your suggestion, Bogdan. 

 I looked into the opensips log and found that there were errors on memory
 allocation. So we increased the memory pool size to 10 MB from 1 MB and
 Shared memory size to 256. Now it is working fine. Is there any recommended
 memory pool size?

 I require couple of other clarifications:
 - What is the maximum CPS it supports on the stateful proxy?
 - How do we achieve fault tolerance and redundancy in the opensips?

 Regards,
 Sat

 Message: 3
 Date: Tue, 09 Mar 2010 11:17:04 +0200
 From: Bogdan-Andrei Iancu bog...@voice-system.ro
 Subject: Re: [OpenSIPS-Users] Load Balancer Issue
 To: OpenSIPS users mailling list users@lists.opensips.org
 Message-ID: 4b961210.7050...@voice-system.ro
 Content-Type: text/plain; charset=windows-1252; format=flowed

 Hi,

 I see here 2 reports:
 1) opensips dies - check the log files for error messages to see why 
 opensips stopped
 2) load not decreasing - this means the BYE is missing or is not 
 properly processed by opensips, so it thinks the call is still on. If 
 you see that the BYEs are passing through, you could enable debugging 
 only for the loose_route() function (use set_debug() function) to see if 
 the BYE matches or not. Also you can check via teh dlg_list MI 
 function the state of the ongoing calls.

 Regards,
 Bogdan

 Sathyanarayanan R wrote:
   
 We are using Opensips load balancer module to make outbound calls, 
 when we pump more than 30 CPS, load in the load balancer is not 
 decreased even after the call ends. Beyond certain point opensips 
 service stops with the error ?Opensips dead but subsys locked?. How 
 this problem should be approached and solved?

 Regards,

 Sathya

 

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


   


-- 
Bogdan-Andrei Iancu
www.voice-system.ro


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


Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

2010-03-15 Thread Bogdan-Andrei Iancu
Erick,

For the CP error:

##
In the control panel 
Module Diallog = Array ( [0] = sorry -- reply fifo opening error )


what is the corresponding error in opensips logs ?

Regards,
Bogdan

Erick Chinchilla Berrocal wrote:
 Hi
 Bogdan
 The problem continues

 I have these modules

 ##
 /lib/opensips/modules# ls
 aaa_radius.so call_control.so  diversion.so load_balancer.so
 options.sorr.so  textops.so
 acc.socfgutils.so  domainpolicy.so  localcache.so
 path.so   seas.sotm.so
 alias_db.so   closeddial.sodomain.somangler.sopdt.so
 signaling.so   uac_redirect.so
 auth_aaa.so   db_flatstore.so  drouting.so  maxfwd.so
 peering.sosiptrace.souac.so
 auth_db.sodb_mysql.so  enum.so  mediaproxy.so
 permissions.sosl.so  uri.so
 auth_diameter.so  db_text.so   exec.so  mi_datagram.so
 pike.so   sms.so userblacklist.so
 auth.so   db_virtual.sogflags.somi_fifo.so
 presence_xcapdiff.so  speeddial.so   usrloc.so
 avpops.so dialog.sogroup.so msilo.so  qos.so
 sst.so xlog.so
 b2b_entities.so   dialplan.so  imc.so   nathelper.so
 ratelimit.so  statistics.so
 benchmark.so  dispatcher.solcr.so   nat_traversal.so
 registrar.so  stun.so

 ##
 /etc/opensips/opensips.cfg
 /* uncomment next line for MySQL DB support */
 loadmodule db_mysql.so
 loadmodule signaling.so
 loadmodule sl.so
 loadmodule tm.so
 loadmodule rr.so
 loadmodule maxfwd.so
 loadmodule usrloc.so
 loadmodule registrar.so
 loadmodule textops.so
 modparam(dialog, db_mode, 1)
 loadmodule mi_fifo.so
 loadmodule uri.so
 loadmodule xlog.so
 loadmodule acc.so
 loadmodule dialog.so


 #--- dialog -
 modparam(dialog, db_url,
 mysql://(username):(password)@localhost/opensips)
 modparam(dialog, dlg_flag, 4)

 Reference:
 http://www.opensips.org/Resources/PuaDialoinfoConfig

 I tried with this options and get the same problem
 # DIALOG #
 loadmodule dialog.so
 modparam(dialog, enable_stats, 1)
 modparam(dialog, default_timeout, 21600)
 modparam(dialog, db_url, mysql://opensips:opens...@database/opensips)
 modparam(dialog, db_mode, 1)
 modparam(dialog, dlg_flag, 4)

 Reference
 http://gventure.wordpress.com/2009/03/30/opensips-installation/


 ##

 opensips -c
 Listening on 
  udp: 127.0.0.1 [127.0.0.1]:5060
  udp: 192.168.50.10 [192.168.50.10]:5060
  tcp: 127.0.0.1 [127.0.0.1]:5060
  tcp: 192.168.50.10 [192.168.50.10]:5060
 Aliases: 
  tcp: net:5060
  tcp: server.dominio.com:5060
  tcp: localhost:5060
  udp: server:5060
  udp: server.dominio.com:5060
  udp: localhost:5060

 Mar 15 13:06:03 [3014] NOTICE:core:main: config file ok, exit

 ##
 # opensipsctl online
 database engine 'MYSQL' loaded
 Control engine 'FIFO' loaded
 1001

 ##
 In the control panel 
 Module Diallog = Array ( [0] = sorry -- reply fifo opening error )

 Any ideas

 Thanks
 Erick

 -Original Message-
 From: users-boun...@lists.opensips.org
 [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
 Sent: Monday, March 15, 2010 3:47 AM
 To: OpenSIPS users mailling list
 Subject: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

 Hi Erick,

 For the failing tools, do you have the corresponding opensips modules 
 loaded ?

 Like, for  Dialog tool, do you have the dialog module loaded ?

 Regards,
 Bogdan


 Erick Chinchilla Berrocal wrote:
   
 Bodgan 
 I made the following change in the file etc/monit/monitrc
 The manual said insert the line 
 check process opensips with pidfile /var/run/opensips.pid
 and i changed to 
 check process opensips with pidfile /var/run/opensips/opensips.pid
  with this change in the control panel the module MONIT is working well

 with this change in the control panel the module MONIT is working well
 now the problem continues with the following modules, please let me know
 
 if
   
 you have idea, I read the manual for several times and no 

 - CDRViever = ok 
 - Dialog = Array ( [0] = sorry -- reply fifo opening error )
 - DialPlan = ok
 - Dispatcher = Array ( [0] = sorry -- reply fifo opening error [1] =
 
 sorry
   
 -- reply fifo opening error )
 - Domain = ok
 - Dymanic Routing = ok
 - Load Balancer = ok
 - MI Comands = /tmp/opensips_fifo
 - Monit = ok
 - Nathelper = ok
 - Permissions = ok
 - Prefix 2 Domain = ok
 - SIP Trace = Array ( [0] = sorry -- reply fifo opening error )
 - Static Monitor = sorry -- reply fifo opening error

 I understand the important for the files db.inc.php and
 boxes.global.inc.php , my current setup is the example in the book
 charpter 6, page 132. the only difference is the password, the primary
 
 name
   
 server

 This is the log 
 Mar 12 17:44:42 

Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

2010-03-15 Thread Erick Chinchilla Berrocal
Sorry, this is the error /var/log/opensips.log

13:09:06 net /sbin/opensips[2940]: ERROR:mi_fifo:mi_fifo_server: cannot open
reply pipe (null)
(END)

-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Monday, March 15, 2010 11:50 AM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

Erick,

For the CP error:

##
In the control panel 
Module Diallog = Array ( [0] = sorry -- reply fifo opening error )


what is the corresponding error in opensips logs ?

Regards,
Bogdan

Erick Chinchilla Berrocal wrote:
 Hi
 Bogdan
 The problem continues

 I have these modules

 ##
 /lib/opensips/modules# ls
 aaa_radius.so call_control.so  diversion.so load_balancer.so
 options.sorr.so  textops.so
 acc.socfgutils.so  domainpolicy.so  localcache.so
 path.so   seas.sotm.so
 alias_db.so   closeddial.sodomain.somangler.so
pdt.so
 signaling.so   uac_redirect.so
 auth_aaa.so   db_flatstore.so  drouting.so  maxfwd.so
 peering.sosiptrace.souac.so
 auth_db.sodb_mysql.so  enum.so  mediaproxy.so
 permissions.sosl.so  uri.so
 auth_diameter.so  db_text.so   exec.so  mi_datagram.so
 pike.so   sms.so userblacklist.so
 auth.so   db_virtual.sogflags.somi_fifo.so
 presence_xcapdiff.so  speeddial.so   usrloc.so
 avpops.so dialog.sogroup.so msilo.so
qos.so
 sst.so xlog.so
 b2b_entities.so   dialplan.so  imc.so   nathelper.so
 ratelimit.so  statistics.so
 benchmark.so  dispatcher.solcr.so   nat_traversal.so
 registrar.so  stun.so

 ##
 /etc/opensips/opensips.cfg
 /* uncomment next line for MySQL DB support */
 loadmodule db_mysql.so
 loadmodule signaling.so
 loadmodule sl.so
 loadmodule tm.so
 loadmodule rr.so
 loadmodule maxfwd.so
 loadmodule usrloc.so
 loadmodule registrar.so
 loadmodule textops.so
 modparam(dialog, db_mode, 1)
 loadmodule mi_fifo.so
 loadmodule uri.so
 loadmodule xlog.so
 loadmodule acc.so
 loadmodule dialog.so


 #--- dialog -
 modparam(dialog, db_url,
 mysql://(username):(password)@localhost/opensips)
 modparam(dialog, dlg_flag, 4)

 Reference:
 http://www.opensips.org/Resources/PuaDialoinfoConfig

 I tried with this options and get the same problem
 # DIALOG #
 loadmodule dialog.so
 modparam(dialog, enable_stats, 1)
 modparam(dialog, default_timeout, 21600)
 modparam(dialog, db_url,
mysql://opensips:opens...@database/opensips)
 modparam(dialog, db_mode, 1)
 modparam(dialog, dlg_flag, 4)

 Reference
 http://gventure.wordpress.com/2009/03/30/opensips-installation/


 ##

 opensips -c
 Listening on 
  udp: 127.0.0.1 [127.0.0.1]:5060
  udp: 192.168.50.10 [192.168.50.10]:5060
  tcp: 127.0.0.1 [127.0.0.1]:5060
  tcp: 192.168.50.10 [192.168.50.10]:5060
 Aliases: 
  tcp: net:5060
  tcp: server.dominio.com:5060
  tcp: localhost:5060
  udp: server:5060
  udp: server.dominio.com:5060
  udp: localhost:5060

 Mar 15 13:06:03 [3014] NOTICE:core:main: config file ok, exit

 ##
 # opensipsctl online
 database engine 'MYSQL' loaded
 Control engine 'FIFO' loaded
 1001

 ##
 In the control panel 
 Module Diallog = Array ( [0] = sorry -- reply fifo opening error )

 Any ideas

 Thanks
 Erick

 -Original Message-
 From: users-boun...@lists.opensips.org
 [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
 Sent: Monday, March 15, 2010 3:47 AM
 To: OpenSIPS users mailling list
 Subject: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

 Hi Erick,

 For the failing tools, do you have the corresponding opensips modules 
 loaded ?

 Like, for  Dialog tool, do you have the dialog module loaded ?

 Regards,
 Bogdan


 Erick Chinchilla Berrocal wrote:
   
 Bodgan 
 I made the following change in the file etc/monit/monitrc
 The manual said insert the line 
 check process opensips with pidfile /var/run/opensips.pid
 and i changed to 
 check process opensips with pidfile /var/run/opensips/opensips.pid
  with this change in the control panel the module MONIT is working well

 with this change in the control panel the module MONIT is working well
 now the problem continues with the following modules, please let me know
 
 if
   
 you have idea, I read the manual for several times and no 

 - CDRViever = ok 
 - Dialog = Array ( [0] = sorry -- reply fifo opening error )
 - DialPlan = ok
 - Dispatcher = Array ( [0] = sorry -- reply fifo opening error [1] =
 
 sorry
   
 -- reply fifo opening error )
 - Domain = ok
 - Dymanic Routing = ok
 - Load Balancer = ok
 - MI Comands = /tmp/opensips_fifo
 - Monit = ok
 - Nathelper = ok
 - 

Re: [OpenSIPS-Users] Users Digest, Vol 20, Issue 27

2010-03-15 Thread Sathyanarayanan R
Hi Bogdan,

 

They were related to PKG. I am using loadbalancer module and do the outbound
dialing to more than one trunk.

 

Regarding HA, If opensips fails then the opensips in the machine2 to take
over and subsequent requests has to happen through this secondary opensips
machine.

 

Regards,

Sat

 

 

 

Hi Sat,
 
the mem error - which memory they were related ? pkg or shm ? and from 
which module?
 
How much memory to use depends on your script - on what modules you are 
using and what traffic you expect (cps and calls)
 
According to the latest tests, opensips 1.6 can handle in simple 
stateful proxy mode (no dns, no DB, just proxy) about 10K cps on a 
decent server.
 
For failover - you are looking for HA of the opensips box, or how to use 
opensips to achieve HA for the boxes behind ?
 
Regards,
Bogdan
 
 
Sathyanarayanan R wrote:
 Hi,
 
 Thanks for your suggestion, Bogdan. 
 
 I looked into the opensips log and found that there were errors on memory
 allocation. So we increased the memory pool size to 10 MB from 1 MB and
 Shared memory size to 256. Now it is working fine. Is there any
recommended
 memory pool size?
 
 I require couple of other clarifications:
 - What is the maximum CPS it supports on the stateful proxy?
 - How do we achieve fault tolerance and redundancy in the opensips?
 
 Regards,
 Sat
 
 Message: 3
 Date: Tue, 09 Mar 2010 11:17:04 +0200
 From: Bogdan-Andrei Iancu bogdan at voice-system.ro
http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
 Subject: Re: [OpenSIPS-Users] Load Balancer Issue
 To: OpenSIPS users mailling list users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
 Message-ID: 4B961210.7050701 at voice-system.ro
http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
 Content-Type: text/plain; charset=windows-1252; format=flowed
 
 Hi,
 
 I see here 2 reports:
 1) opensips dies - check the log files for error messages to see why 
 opensips stopped
 2) load not decreasing - this means the BYE is missing or is not 
 properly processed by opensips, so it thinks the call is still on. If 
 you see that the BYEs are passing through, you could enable debugging 
 only for the loose_route() function (use set_debug() function) to see if 
 the BYE matches or not. Also you can check via teh dlg_list MI 
 function the state of the ongoing calls.
 
 Regards,
 Bogdan
 
 Sathyanarayanan R wrote:
   
 We are using Opensips load balancer module to make outbound calls, 
 when we pump more than 30 CPS, load in the load balancer is not 
 decreased even after the call ends. Beyond certain point opensips 
 service stops with the error ?Opensips dead but subsys locked?. How 
 this problem should be approached and solved?
 
 Regards,
 
 Sathya
 
 
 
 ___
 Users mailing list
 Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users
   
 
 
 
   
 
 
-- 
Bogdan-Andrei Iancu
www.voice-system.ro

 

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


Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

2010-03-15 Thread erik pepermans
Hi,

Got the same problem :

'opensipsctl fifo dr_reload' returns in syslog :
Mar 15 21:09:22 ns1 /sbin/opensips[22244]: INFO:drouting:dr_reload_cmd:
dr_reload MI command received! 
Mar 15 21:09:22 ns1 /sbin/opensips[22244]:
WARNING:drouting:dr_load_routing_info: using old-style tables for
dr_gateways, probing will be disabled

Via opensips-cp 'fifo dr_reload' returns in syslog : 
Mar 15 21:09:50 ns1 /sbin/opensips[22244]: ERROR:mi_fifo:mi_fifo_server:
command fifo is not available 
Mar 15 21:09:50 ns1 /sbin/opensips[22244]: ERROR:mi_fifo:mi_fifo_server:
cannot open reply pipe (null) 

Via opensips-cp 'ps' returns in syslog :
Mar 15 21:10:27 ns1 /sbin/opensips[22244]: ERROR:mi_fifo:mi_fifo_server:
cannot open reply pipe (null) 

Brgds
Erik

-Oorspronkelijk bericht-
Van: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] Namens Erick Chinchilla Berrocal
Verzonden: maandag 15 maart 2010 19:16
Aan: 'OpenSIPS users mailling list'
Onderwerp: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo


Bodgab
In the syslog I have the error:

opensips-lab /usr/local/sbin/opensips[3047]: ERROR:mi_fifo:mi_fifo_server:
cannot open reply pipe (null)

Instead in the apache2 error.log:

mkfifo: missing operand
Try `mkfifo --help' for more information.

I think that the reply_fifo it was not create

Any idea that can help me to solve this problem?

Thanks
Erick Ch.

-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
Sent: Monday, March 15, 2010 3:47 AM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

Hi Erick,

For the failing tools, do you have the corresponding opensips modules 
loaded ?

Like, for  Dialog tool, do you have the dialog module loaded ?

Regards,
Bogdan


Erick Chinchilla Berrocal wrote:
 Bodgan
 I made the following change in the file etc/monit/monitrc
 The manual said insert the line 
 check process opensips with pidfile /var/run/opensips.pid
 and i changed to 
 check process opensips with pidfile /var/run/opensips/opensips.pid
  with this change in the control panel the module MONIT is working well

 with this change in the control panel the module MONIT is working 
 well now the problem continues with the following modules, please let 
 me know
if
 you have idea, I read the manual for several times and no 

 - CDRViever = ok
 - Dialog = Array ( [0] = sorry -- reply fifo opening error )
 - DialPlan = ok
 - Dispatcher = Array ( [0] = sorry -- reply fifo opening error [1] =
sorry
 -- reply fifo opening error )
 - Domain = ok
 - Dymanic Routing = ok
 - Load Balancer = ok
 - MI Comands = /tmp/opensips_fifo
 - Monit = ok
 - Nathelper = ok
 - Permissions = ok
 - Prefix 2 Domain = ok
 - SIP Trace = Array ( [0] = sorry -- reply fifo opening error )
 - Static Monitor = sorry -- reply fifo opening error

 I understand the important for the files db.inc.php and 
 boxes.global.inc.php , my current setup is the example in the book 
 charpter 6, page 132. the only difference is the password, the 
 primary
name
 server

 This is the log
 Mar 12 17:44:42 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command ds_list is not available
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command ds_reload is not available
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:07:59 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command sip_trace is not available
 Mar 12 18:07:59 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:08:24 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)


 Thanks

 To: 'OpenSIPS users mailling list'
 Subject: RE: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

 Bodgan
 Thanks for your assistant.
 After of change the file opensips.cfg the configuration is # - 
 mi_fifo params - modparam(mi_fifo, fifo_name, 
 /tmp/opensips_fifo) modparam ( mi_fifo, fifo_mode, 0666)

 if only use the line modparam ( mi_fifo, 

Re: [OpenSIPS-Users] Users Digest, Vol 20, Issue 27

2010-03-15 Thread Bogdan-Andrei Iancu
Hi Sat,

Sathyanarayanan R wrote:

 Hi Bogdan,

  

 They were related to PKG. I am using loadbalancer module and do the 
 outbound dialing to more than one trunk.

be sure you are using 1.6.2 - just to eliminate any possible mem leak in 
pkg mem. Usually you should not run out of pkg mem at runtime (except 
re-loads)

  

 Regarding HA, If opensips fails then the opensips in the machine2 to 
 take over and subsequent requests has to happen through this secondary 
 opensips machine.

depends on what HA system you implements (like heartbeat, etc)  - based 
on this, you need to find a solution to replicate data/state between the 
two opensips instances.

Regards,
Bogdan

  

 Regards,

 Sat

  

  

  

 Hi Sat,
  
 the mem error - which memory they were related ? pkg or shm ? and from 
 which module?
  
 How much memory to use depends on your script - on what modules you are 
 using and what traffic you expect (cps and calls)
  
 According to the latest tests, opensips 1.6 can handle in simple 
 stateful proxy mode (no dns, no DB, just proxy) about 10K cps on a 
 decent server.
  
 For failover - you are looking for HA of the opensips box, or how to use 
 opensips to achieve HA for the boxes behind ?
  
 Regards,
 Bogdan
  
  
 Sathyanarayanan R wrote:
 / Hi,/
 / /
 / Thanks for your suggestion, Bogdan. /
 / /
 / I looked into the opensips log and found that there were errors on memory/
 / allocation. So we increased the memory pool size to 10 MB from 1 MB and/
 / Shared memory size to 256. Now it is working fine. Is there any 
 recommended/
 / memory pool size?/
 / /
 / I require couple of other clarifications:/
 / - What is the maximum CPS it supports on the stateful proxy?/
 / - How do we achieve fault tolerance and redundancy in the opensips?/
 / /
 / Regards,/
 / Sat/
 / /
 / Message: 3/
 / Date: Tue, 09 Mar 2010 11:17:04 +0200/
 / From: Bogdan-Andrei Iancu bogdan at voice-system.ro 
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users/
 / Subject: Re: [OpenSIPS-Users] Load Balancer Issue/
 / To: OpenSIPS users mailling list users at lists.opensips.org 
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users/
 / Message-ID: 4B961210.7050701 at voice-system.ro 
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users/
 / Content-Type: text/plain; charset=windows-1252; format=flowed/
 / /
 / Hi,/
 / /
 / I see here 2 reports:/
 / 1) opensips dies - check the log files for error messages to see why /
 / opensips stopped/
 / 2) load not decreasing - this means the BYE is missing or is not /
 / properly processed by opensips, so it thinks the call is still on. If /
 / you see that the BYEs are passing through, you could enable debugging /
 / only for the loose_route() function (use set_debug() function) to see if /
 / the BYE matches or not. Also you can check via teh dlg_list MI /
 / function the state of the ongoing calls./
 / /
 / Regards,/
 / Bogdan/
 / /
 / Sathyanarayanan R wrote:/
 /   /
 / We are using Opensips load balancer module to make outbound calls, /
 / when we pump more than 30 CPS, load in the load balancer is not /
 / decreased even after the call ends. Beyond certain point opensips /
 / service stops with the error ?Opensips dead but subsys locked?. How /
 / this problem should be approached and solved?/
 / /
 / Regards,/
 / /
 / Sathya/
 / /
 / /
 / /
 / ___/
 / Users mailing list/
 / Users at lists.opensips.org 
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users/
 / http://lists.opensips.org/cgi-bin/mailman/listinfo/users/
 /   /
 / /
 / /
 / /
 /   /
  
  
 -- 
 Bogdan-Andrei Iancu
 www.voice-system.ro

  

 

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


-- 
Bogdan-Andrei Iancu
www.voice-system.ro


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


Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

2010-03-15 Thread Bogdan-Andrei Iancu
Hi Erick,

I might have an idea about the error root - it might be related to some 
cfg changes in CP that were done just before the release. Let me ask 
Alex to test it and I will come back to you.

Thanks and regards,
Bogdan

Erick Chinchilla Berrocal wrote:
 Bodgab
 In the syslog I have the error:

 opensips-lab /usr/local/sbin/opensips[3047]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)

 Instead in the apache2 error.log:

 mkfifo: missing operand
 Try `mkfifo --help' for more information.

 I think that the reply_fifo it was not create

 Any idea that can help me to solve this problem?

 Thanks
 Erick Ch.

 -Original Message-
 From: users-boun...@lists.opensips.org
 [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
 Sent: Monday, March 15, 2010 3:47 AM
 To: OpenSIPS users mailling list
 Subject: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

 Hi Erick,

 For the failing tools, do you have the corresponding opensips modules 
 loaded ?

 Like, for  Dialog tool, do you have the dialog module loaded ?

 Regards,
 Bogdan


 Erick Chinchilla Berrocal wrote:
   
 Bodgan 
 I made the following change in the file etc/monit/monitrc
 The manual said insert the line 
 check process opensips with pidfile /var/run/opensips.pid
 and i changed to 
 check process opensips with pidfile /var/run/opensips/opensips.pid
  with this change in the control panel the module MONIT is working well

 with this change in the control panel the module MONIT is working well
 now the problem continues with the following modules, please let me know
 
 if
   
 you have idea, I read the manual for several times and no 

 - CDRViever = ok 
 - Dialog = Array ( [0] = sorry -- reply fifo opening error )
 - DialPlan = ok
 - Dispatcher = Array ( [0] = sorry -- reply fifo opening error [1] =
 
 sorry
   
 -- reply fifo opening error )
 - Domain = ok
 - Dymanic Routing = ok
 - Load Balancer = ok
 - MI Comands = /tmp/opensips_fifo
 - Monit = ok
 - Nathelper = ok
 - Permissions = ok
 - Prefix 2 Domain = ok
 - SIP Trace = Array ( [0] = sorry -- reply fifo opening error )
 - Static Monitor = sorry -- reply fifo opening error

 I understand the important for the files db.inc.php and
 boxes.global.inc.php , my current setup is the example in the book
 charpter 6, page 132. the only difference is the password, the primary
 
 name
   
 server

 This is the log 
 Mar 12 17:44:42 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command ds_list is not available
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command ds_reload is not available
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:07:59 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command sip_trace is not available
 Mar 12 18:07:59 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:08:24 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)


 Thanks

 To: 'OpenSIPS users mailling list'
 Subject: RE: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

 Bodgan
 Thanks for your assistant.
 After of change the file opensips.cfg the configuration is
 # - mi_fifo params -
 modparam(mi_fifo, fifo_name, /tmp/opensips_fifo)
 modparam ( mi_fifo, fifo_mode, 0666)

 if only use the line modparam ( mi_fifo, fifo_mode, 0666) not work

 Now in the Control Panel continues with problems a:
 -Dialog = if only use the line modparam ( mi_fifo, fifo_mode, 0666)
 not work
 -Dispatcher = 
  Array ( [0] = sorry -- reply fifo opening error )
  Array ( [0] = sorry -- reply fifo opening error
 [1] = sorry -- reply fifo opening error )
 -MI Commands = /tmp/opensips_fifo
  sorry -- reply fifo opening error

 -Monit = opensips - Execution Failed

 -SIP trace  = Array ( [0] = sorry -- reply fifo opening error )

 -Static Monitor = sorry --reply fifo opening error

 ###
 The is the email from the server

 Subject: Cron r...@netphp
 

Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

2010-03-15 Thread Bogdan-Andrei Iancu
Here you have 2 errors:
- first you do not have the drouting module loaded in opensips cfg
- second in the generic fifo error (mentioned it the prev email)

Regards,
Bogdan

erik pepermans wrote:
 Hi,

 Got the same problem :

 'opensipsctl fifo dr_reload' returns in syslog :
 Mar 15 21:09:22 ns1 /sbin/opensips[22244]: INFO:drouting:dr_reload_cmd:
 dr_reload MI command received! 
 Mar 15 21:09:22 ns1 /sbin/opensips[22244]:
 WARNING:drouting:dr_load_routing_info: using old-style tables for
 dr_gateways, probing will be disabled

 Via opensips-cp 'fifo dr_reload' returns in syslog : 
 Mar 15 21:09:50 ns1 /sbin/opensips[22244]: ERROR:mi_fifo:mi_fifo_server:
 command fifo is not available 
 Mar 15 21:09:50 ns1 /sbin/opensips[22244]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null) 

 Via opensips-cp 'ps' returns in syslog :
 Mar 15 21:10:27 ns1 /sbin/opensips[22244]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null) 

 Brgds
 Erik

 -Oorspronkelijk bericht-
 Van: users-boun...@lists.opensips.org
 [mailto:users-boun...@lists.opensips.org] Namens Erick Chinchilla Berrocal
 Verzonden: maandag 15 maart 2010 19:16
 Aan: 'OpenSIPS users mailling list'
 Onderwerp: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo


 Bodgab
 In the syslog I have the error:

 opensips-lab /usr/local/sbin/opensips[3047]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)

 Instead in the apache2 error.log:

 mkfifo: missing operand
 Try `mkfifo --help' for more information.

 I think that the reply_fifo it was not create

 Any idea that can help me to solve this problem?

 Thanks
 Erick Ch.

 -Original Message-
 From: users-boun...@lists.opensips.org
 [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
 Sent: Monday, March 15, 2010 3:47 AM
 To: OpenSIPS users mailling list
 Subject: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

 Hi Erick,

 For the failing tools, do you have the corresponding opensips modules 
 loaded ?

 Like, for  Dialog tool, do you have the dialog module loaded ?

 Regards,
 Bogdan


 Erick Chinchilla Berrocal wrote:
   
 Bodgan
 I made the following change in the file etc/monit/monitrc
 The manual said insert the line 
 check process opensips with pidfile /var/run/opensips.pid
 and i changed to 
 check process opensips with pidfile /var/run/opensips/opensips.pid
  with this change in the control panel the module MONIT is working well

 with this change in the control panel the module MONIT is working 
 well now the problem continues with the following modules, please let 
 me know
 
 if
   
 you have idea, I read the manual for several times and no 

 - CDRViever = ok
 - Dialog = Array ( [0] = sorry -- reply fifo opening error )
 - DialPlan = ok
 - Dispatcher = Array ( [0] = sorry -- reply fifo opening error [1] =
 
 sorry
   
 -- reply fifo opening error )
 - Domain = ok
 - Dymanic Routing = ok
 - Load Balancer = ok
 - MI Comands = /tmp/opensips_fifo
 - Monit = ok
 - Nathelper = ok
 - Permissions = ok
 - Prefix 2 Domain = ok
 - SIP Trace = Array ( [0] = sorry -- reply fifo opening error )
 - Static Monitor = sorry -- reply fifo opening error

 I understand the important for the files db.inc.php and 
 boxes.global.inc.php , my current setup is the example in the book 
 charpter 6, page 132. the only difference is the password, the 
 primary
 
 name
   
 server

 This is the log
 Mar 12 17:44:42 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command ds_list is not available
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command ds_reload is not available
 Mar 12 18:04:55 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:07:59 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command sip_trace is not available
 Mar 12 18:07:59 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:08:24 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)


 Thanks

 To: 'OpenSIPS users mailling list'
 Subject: RE: [OpenSIPS-Users] 

Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

2010-03-15 Thread erik pepermans
Hi Bogdan :

The issue is some variables are empty in the function write2fifo_new in
module web/common/mi_comm.php :

function write2fifo_new($command, $errors, $status){

global $config;
global $fifo_file ;

--- missing --
$config-reply_fifo_filename=webfifo_.rand();
--- missing --
$config-reply_fifo_path=/tmp/.$config-reply_fifo_filename;

These variables are used further on this function -

Moreover 'reply_fifo_path' is hardcoded; which should not be the case I
presume.

Brgds
Erik

-Oorspronkelijk bericht-
Van: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] Namens Bogdan-Andrei Iancu
Verzonden: maandag 15 maart 2010 22:17
Aan: OpenSIPS users mailling list
Onderwerp: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo


Here you have 2 errors:
- first you do not have the drouting module loaded in opensips cfg
- second in the generic fifo error (mentioned it the prev email)

Regards,
Bogdan

erik pepermans wrote:
 Hi,

 Got the same problem :

 'opensipsctl fifo dr_reload' returns in syslog :
 Mar 15 21:09:22 ns1 /sbin/opensips[22244]: 
 INFO:drouting:dr_reload_cmd: dr_reload MI command received! Mar 15 
 21:09:22 ns1 /sbin/opensips[22244]:
 WARNING:drouting:dr_load_routing_info: using old-style tables for 
 dr_gateways, probing will be disabled

 Via opensips-cp 'fifo dr_reload' returns in syslog :
 Mar 15 21:09:50 ns1 /sbin/opensips[22244]: ERROR:mi_fifo:mi_fifo_server:
 command fifo is not available 
 Mar 15 21:09:50 ns1 /sbin/opensips[22244]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null) 

 Via opensips-cp 'ps' returns in syslog :
 Mar 15 21:10:27 ns1 /sbin/opensips[22244]: 
 ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe (null)

 Brgds
 Erik

 -Oorspronkelijk bericht-
 Van: users-boun...@lists.opensips.org 
 [mailto:users-boun...@lists.opensips.org] Namens Erick Chinchilla 
 Berrocal
 Verzonden: maandag 15 maart 2010 19:16
 Aan: 'OpenSIPS users mailling list'
 Onderwerp: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo


 Bodgab
 In the syslog I have the error:

 opensips-lab /usr/local/sbin/opensips[3047]: 
 ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe (null)

 Instead in the apache2 error.log:

 mkfifo: missing operand
 Try `mkfifo --help' for more information.

 I think that the reply_fifo it was not create

 Any idea that can help me to solve this problem?

 Thanks
 Erick Ch.

 -Original Message-
 From: users-boun...@lists.opensips.org 
 [mailto:users-boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei 
 Iancu
 Sent: Monday, March 15, 2010 3:47 AM
 To: OpenSIPS users mailling list
 Subject: Re: [OpenSIPS-Users] Problem with /tmp/opensips_fifo

 Hi Erick,

 For the failing tools, do you have the corresponding opensips modules
 loaded ?

 Like, for  Dialog tool, do you have the dialog module loaded ?

 Regards,
 Bogdan


 Erick Chinchilla Berrocal wrote:
   
 Bodgan
 I made the following change in the file etc/monit/monitrc The manual 
 said insert the line check process opensips with pidfile 
 /var/run/opensips.pid and i changed to
 check process opensips with pidfile /var/run/opensips/opensips.pid
  with this change in the control panel the module MONIT is working well

 with this change in the control panel the module MONIT is working
 well now the problem continues with the following modules, please let 
 me know
 
 if
   
 you have idea, I read the manual for several times and no 

 - CDRViever = ok
 - Dialog = Array ( [0] = sorry -- reply fifo opening error )
 - DialPlan = ok
 - Dispatcher = Array ( [0] = sorry -- reply fifo opening error [1] 
 =
 
 sorry
   
 -- reply fifo opening error )
 - Domain = ok
 - Dymanic Routing = ok
 - Load Balancer = ok
 - MI Comands = /tmp/opensips_fifo
 - Monit = ok
 - Nathelper = ok
 - Permissions = ok
 - Prefix 2 Domain = ok
 - SIP Trace = Array ( [0] = sorry -- reply fifo opening error )
 - Static Monitor = sorry -- reply fifo opening error

 I understand the important for the files db.inc.php and
 boxes.global.inc.php , my current setup is the example in the book 
 charpter 6, page 132. the only difference is the password, the 
 primary
 
 name
   
 server

 This is the log
 Mar 12 17:44:42 net /sbin/opensips[2922]: 
 ERROR:mi_fifo:mi_fifo_server: cannot open reply pipe (null) Mar 12 
 18:04:22 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server: 
 command dlg_list is not available Mar 12 18:04:22 net 
 /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server: cannot open reply 
 pipe (null) Mar 12 18:04:32 net /sbin/opensips[2922]: 
 ERROR:mi_fifo:mi_fifo_server: command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open reply pipe (null)
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 command dlg_list is not available
 Mar 12 18:04:32 net /sbin/opensips[2922]: ERROR:mi_fifo:mi_fifo_server:
 cannot open