similar to: res_pgsql re-connect on db failure?

Database on a remote machine res_pgsql.conf: [general] dbhost=172.16.0.2 dbport=5432 dbname=ast_config dbuser=pbx dbpass= dbsock=5432 [Nov 28 20:12:02] DEBUG[6581] res_config_pgsql.c: Postgresql RealTime Host: 172.16.0.2 [Nov 28 20:12:02] DEBUG[6581] res_config_pgsql.c: Postgresql RealTime Port: 5432 [Nov 28 20:12:02] DEBUG[6581] res_config_pgsql.c: Postgresql RealTime User: pbx [Nov 28

When I try and start asterisk I get the following, however I have commented out the data the connections in res_mysql.conf and res_pgsql.conf. I am not sure therefore why I am getting these errors. Do I have to change something else to turn this off? Thanks Asterisk 1.4.21.2~dfsg-3, Copyright (C) 1999 - 2008 Digium, Inc. and others. Created by Mark Spencer <markster at digium.com> Asterisk

Hello, How do I use multiple postgresql databases using res_config_pgsql? I tried creating multiple contexts in res_pgsql.conf, but asterisk is only using the 'general' context. My res_pgsq.conf is [general] ;; Connect to mydb on localhost dbport=5432 dbname=mydb dbuser=pgdbuser requirements=warn [pgwritedb] ;; Connect to mydb2 on another host dbhost=<IP

Hi I am having problems with Asterisk 1.4.18 and realtime architecture. I use Postgresql-8.3 as the database. Everything works OK; all sip phones (their configs are in the database) are able to register to the server and I can make calls (dialplan is in the database), but each time Asterisk reads the information from the database it shows me this on the console: [Feb 17 12:32:50] WARNING[620]:

We have several Asterisk servers (1.6.2.15) all configured for Realtime, all backed by the same database. The Asterisk servers are all listed under DNS SRV records, and SIP ATAs find us this way. Normally, no matter which Asterisk server an ATA connects to, we get our database fields filled out correctly, such as "regseconds", "lastms", "ipadr", etc. However, with

Hello, I am using asterisk realtime with a postgresql database on the same server. In res_pgsql.conf I have specified [general] dbhost=localhost dbport=5432 dbname=asteriskdb dbuser=psql dbsock=/tmp/.s.PGSQL.5432 Since both asterisk and db are on same server, I would like asterisk to connect to db using the local unix socket. However asterisk is not using the local unix socket to connect to

Hi, Anybody seen this before? (using a pre-compiled asterisk from the OBS on a sles11sp1) (I mean, i did the same with a 1.6 without any problem, but i need 1.8) after starting: kc3004:~ # /usr/sbin/safe_asterisk: line 145: 16133 Segmentation fault (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY} Asterisk ended with

Good morning, I'm having suddenly cut-offs and I don`t know why. It's been hapenning since I enabled cdr_odbc/func_odbc in my system. We use func_odbc to register some queue member's events (login, pause, etc.) at an external DB ('remoto' connector) and to uptade local tables at a local DB ('local' connector). Currently we are usind cdr_odbc to Postgresql and cdr_addon

If anybody here is a sixTel customer, can you share any tips & tricks for getting in touch with anybody there? They are absurdly hard to get a hold of, particularly when you have a technical issue needing to be resolved. If anyone has any phone numbers other than their main 800 line, I'd sure appreciate it. Thank you, Bryan -------------- next part -------------- An HTML attachment was

We have a script which executes "asterisk -n -r -x ....." periodically against the running server, to check the status of a few things, and pipe the output to a file. With prior versions of Asterisk this worked fine, but having just upgraded to 1.2.9, we are finding that if the output is lengthy, then Asterisk seems to terminate before fully flushing stdout. Is this a known bug, is

Hello. I'm testing the new Asterisk 1.6 beta 5. I'm using realtime to store extensions and sip users. When a user logs on, everything works fine - calls are also fine. But I keep getting these in the console: [Mar 9 16:31:58] WARNING[10284]: res_config_pgsql.c:195 realtime_pgsql: PostgreSQL RealTime: Could not find any rows in table sip_users. Full log: http://rafb.net/p/LO7DEM95.html

Asterisk Project Security Advisory - AST-2007-025 +------------------------------------------------------------------------+ | Product | Asterisk | |----------------------+-------------------------------------------------| | Summary | SQL Injection issue in res_config_pgsql |

Asterisk Project Security Advisory - AST-2007-025 +------------------------------------------------------------------------+ | Product | Asterisk | |----------------------+-------------------------------------------------| | Summary | SQL Injection issue in res_config_pgsql |

Hi, I've just started setting up Dovecot 1.0.1, and made an error in my configuration, which I think has found a potential problem in Dovecot. I'm using PostgreSQL authentication, and set the database host to "localhost", which PostgreSQL doesn't listen on, so libpq is throwing the standard "is the server running?" message. The problem, however, is Dovecot

Hi everybody, I have a Fedora Core 4 x86 32 bit install, which I recently upgraded from asterisk 1.2 to the office 1.4.4 tarball. In the process of doing that I had to upgrade some autoconf/automake stuff, but it worked fine, and my new asterisk works fine. Except that anytime I receive a fax with spandsp and app_rxfax, asterisk seg faults. I have applied the spandsp

I would like to access a Postgresql database directly from my dialplan (to lookup names based on callerid numbers for incoming calls). Based on everywhere I looked - it seems the only way to do this is with func_odbc. Considering that Asterisk seems to be able to access Postgresql databases directly using res_pgsql for the purposes of realtime functionality (without using odbc - if I

(problem encountered on Tru64Unix v4.0f with rsync 2.5.5) A failure to write to stdout or stderr in rwrite (log.c:279) will trigger an endless loop as follows: 0 rprintf calls rwrite 1 rwrite calls fwrite 2 fwrite fails 3 rwrite calls _exit_cleanup 4 _exit_cleanup calls log_exit 5 log_exit calls rprintf 6 rprintf calls rwrite 7

From: Collins Richey <crichey at gmail.com> > It's a little more than that. I find few people who consider RedHat to > be a Demon Evil or that they can't do anything right, but I can > understand the concern about some of their decisions which have made > life difficult for (granted) a few, and it's not really helpful to > demonize those who complain, as Bryan has

Hi, I am a beginner who began to use Asterisk in this July. Last week, I made two addons for PostgreSQL (cdr_addon_postgresql.c and res_config_postgresql.c), because I use not usual MySQL but PostgreSQL. # Of course, not scratch build but modified version 1.4.8. But I don't know how to change configure script, menuselect-xxx, ... etc, and how to merge my sources to addons tar-balls. Anyone

"IT3 Stuart Blake Tener, USNR-R" wrote: > In terms of enterprise reliability, I understand, however, having an > "office recommended journaling filesystem", Some journaling filesystems can be _worse_ than non-journaled. If the recovery mechanism of the JFS is to "aggressively" go to the journal, journal mis-reads can _toast_ a filesystem. I'll take a full