VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
| View previous topic :: View next topic |
| Author |
Message |
pezhman_lali at yahoo.com
Guest
|
 Posted: Sun Apr 27, 2008 1:46 am Post subject: [asterisk-users] psql |
 |
|
Dear
I am using ast 1.4.19 with postgres.
the realtime extension was done properly, but the two
following warning was reported,
1)realtime_pgsql: Postgresql RealTime: Could not find
any rows in table extensions.
2)realtime_multi_pgsql: Postgresql RealTime: Could not
find any rows in table extensions.
the interesting part is, the asterisk executes the
dial for incoming calls via extensions ,thru database,
it means , the asterisk can find a row in table
the following is the asterisk output:
best
Mani
Connected to Asterisk 1.4.19 currently running on
IS-4377 (pid = 17670)
Verbosity is at least 3
-- Executing Dial("SIP/11.11.11.11-09feed30",
"SIP/202188590963 at 33.33.33.33|60")
-- Called 202188590963 at 33.33.33.33
[Apr 27 08:06:28] WARNING[17712]:
res_config_pgsql.c:207 realtime_pgsql: Postgresql
RealTime: Could not find any rows in table extensions.
[Apr 27 08:06:28] WARNING[17712]:
res_config_pgsql.c:370 realtime_multi_pgsql:
Postgresql RealTime: Could not find any rows in table
extensions.
-- SIP/91.186.198.18-09ff42d8 is making progress
passing it to SIP/11.11.11.11-09feed30
[Apr 27 08:06:31] NOTICE[17712]: rtp.c:788
process_rfc3389: Comfort noise support incomplete in
Asterisk (RFC 3389). Please turn off on client if
possible. Client IP: 33.33.33.33
== Spawn extension (DID, 202188590963, 1) exited
non-zero on 'SIP/11.11.11.11-09feed30'
[Apr 27 08:06:32] WARNING[17712]:
res_config_pgsql.c:207 realtime_pgsql: Postgresql
RealTime: Could not find any rows in table extensions.
[Apr 27 08:06:32] WARNING[17712]:
res_config_pgsql.c:370 realtime_multi_pgsql:
Postgresql RealTime: Could not find any rows in table
extensions.
IS-4377*CLI>
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ |
|
| Back to top |
|
 |
tilghman at mail.jeffa...
Guest
|
| Posted: Sun Apr 27, 2008 11:05 am Post subject: [asterisk-users] psql |
|
|
On Sunday 27 April 2008 01:46:23 Pezhman Lali wrote:
| Quote: | I am using ast 1.4.19 with postgres.
the realtime extension was done properly, but the two
following warning was reported,
1)realtime_pgsql: Postgresql RealTime: Could not find
any rows in table extensions.
2)realtime_multi_pgsql: Postgresql RealTime: Could not
find any rows in table extensions.
|
Those warnings are safe to ignore. They really should be at log level DEBUG,
not WARNING, because queries will fail to retrieve any results much of the
time. This is due to our searching for matches, which starts at the most
specific match first and falls back to more general matches. So any match for
extensions that employs a pattern match will always generate one query which
succeeds, but fails to return any results.
--
Tilghman |
|
| Back to top |
|
|
stotaro at totarotechn...
Guest
|
| Posted: Sun Apr 27, 2008 11:11 am Post subject: [asterisk-users] psql |
|
|
On Sun, Apr 27, 2008 at 12:05 PM, Tilghman Lesher
<tilghman at mail.jeffandtilghman.com> wrote:
| Quote: | On Sunday 27 April 2008 01:46:23 Pezhman Lali wrote:
| Quote: | I am using ast 1.4.19 with postgres.
the realtime extension was done properly, but the two
following warning was reported,
1)realtime_pgsql: Postgresql RealTime: Could not find
any rows in table extensions.
2)realtime_multi_pgsql: Postgresql RealTime: Could not
find any rows in table extensions.
|
Those warnings are safe to ignore. They really should be at log level DEBUG,
not WARNING, because queries will fail to retrieve any results much of the
time. This is due to our searching for matches, which starts at the most
specific match first and falls back to more general matches. So any match for
extensions that employs a pattern match will always generate one query which
succeeds, but fails to return any results.
--
Tilghman
|
Not to start any huge debate, but what is the best (most tested and
stable) database setup? I am under the impression that MySQL plus the
ODBC driver is "the best".
Thanks,
Steve Totaro |
|
| Back to top |
|
|
tilghman at mail.jeffa...
Guest
|
| Posted: Sun Apr 27, 2008 11:42 am Post subject: [asterisk-users] psql |
|
|
On Sunday 27 April 2008 11:11:28 Steve Totaro wrote:
| Quote: | On Sun, Apr 27, 2008 at 12:05 PM, Tilghman Lesher
<tilghman at mail.jeffandtilghman.com> wrote:
| Quote: | On Sunday 27 April 2008 01:46:23 Pezhman Lali wrote:
| Quote: | I am using ast 1.4.19 with postgres.
the realtime extension was done properly, but the two
following warning was reported,
1)realtime_pgsql: Postgresql RealTime: Could not find
any rows in table extensions.
2)realtime_multi_pgsql: Postgresql RealTime: Could not
find any rows in table extensions.
|
Those warnings are safe to ignore. They really should be at log level
DEBUG, not WARNING, because queries will fail to retrieve any results
much of the time. This is due to our searching for matches, which starts
at the most specific match first and falls back to more general matches.
So any match for extensions that employs a pattern match will always
generate one query which succeeds, but fails to return any results.
|
Not to start any huge debate, but what is the best (most tested and
stable) database setup? I am under the impression that MySQL plus the
ODBC driver is "the best".
|
That's fine, but I have had the most horrid results using any distribution-
supplied ODBC drivers. The best results are obtained by source-compiling
the latest ODBC drivers, whether they be the MySQL ODBC Connector 3.51 or
PsqlODBC. UnixODBC is fairly safe to use from distribution channels, however.
--
Tilghman |
|
| Back to top |
|
|
stotaro at totarotechn...
Guest
|
| Posted: Sun Apr 27, 2008 12:19 pm Post subject: [asterisk-users] psql |
|
|
On Sun, Apr 27, 2008 at 12:42 PM, Tilghman Lesher
<tilghman at mail.jeffandtilghman.com> wrote:
| Quote: | On Sunday 27 April 2008 11:11:28 Steve Totaro wrote:
| Quote: | On Sun, Apr 27, 2008 at 12:05 PM, Tilghman Lesher
<tilghman at mail.jeffandtilghman.com> wrote:
| Quote: | On Sunday 27 April 2008 01:46:23 Pezhman Lali wrote:
| Quote: | I am using ast 1.4.19 with postgres.
the realtime extension was done properly, but the two
following warning was reported,
1)realtime_pgsql: Postgresql RealTime: Could not find
any rows in table extensions.
2)realtime_multi_pgsql: Postgresql RealTime: Could not
find any rows in table extensions.
|
Those warnings are safe to ignore. They really should be at log level
DEBUG, not WARNING, because queries will fail to retrieve any results
much of the time. This is due to our searching for matches, which starts
at the most specific match first and falls back to more general matches.
So any match for extensions that employs a pattern match will always
generate one query which succeeds, but fails to return any results.
|
|
| Quote: | Not to start any huge debate, but what is the best (most tested and
stable) database setup? I am under the impression that MySQL plus the
ODBC driver is "the best".
|
That's fine, but I have had the most horrid results using any distribution-
supplied ODBC drivers. The best results are obtained by source-compiling
the latest ODBC drivers, whether they be the MySQL ODBC Connector 3.51 or
PsqlODBC. UnixODBC is fairly safe to use from distribution channels, however.
|
I use UnixODBC. You say "fairly safe". Is the MySQL ODBC 3.51 your top choice?
Thanks,
Steve Totaro |
|
| Back to top |
|
|
tilghman at mail.jeffa...
Guest
|
| Posted: Mon Apr 28, 2008 11:49 am Post subject: [asterisk-users] psql |
|
|
On Sunday 27 April 2008 12:19, Steve Totaro wrote:
| Quote: | On Sun, Apr 27, 2008 at 12:42 PM, Tilghman Lesher
<tilghman at mail.jeffandtilghman.com> wrote:
| Quote: | On Sunday 27 April 2008 11:11:28 Steve Totaro wrote:
| Quote: | On Sun, Apr 27, 2008 at 12:05 PM, Tilghman Lesher
<tilghman at mail.jeffandtilghman.com> wrote:
| Quote: | On Sunday 27 April 2008 01:46:23 Pezhman Lali wrote:
| Quote: | I am using ast 1.4.19 with postgres.
the realtime extension was done properly, but the two
following warning was reported,
1)realtime_pgsql: Postgresql RealTime: Could not find
any rows in table extensions.
2)realtime_multi_pgsql: Postgresql RealTime: Could not
find any rows in table extensions.
|
Those warnings are safe to ignore. They really should be at log
level DEBUG, not WARNING, because queries will fail to retrieve any
results much of the time. This is due to our searching for matches,
which starts at the most specific match first and falls back to more
general matches. So any match for extensions that employs a pattern
match will always generate one query which succeeds, but fails to
return any results.
|
Not to start any huge debate, but what is the best (most tested and
stable) database setup? I am under the impression that MySQL plus the
ODBC driver is "the best".
|
That's fine, but I have had the most horrid results using any
distribution- supplied ODBC drivers. The best results are obtained by
source-compiling the latest ODBC drivers, whether they be the MySQL ODBC
Connector 3.51 or PsqlODBC. UnixODBC is fairly safe to use from
distribution channels, however.
|
I use UnixODBC. You say "fairly safe". Is the MySQL ODBC 3.51 your top
choice?
|
I wouldn't call it my top choice, but it is a fairly typical choice, given
that the data stored there tends to be rather static. If I was needed a
database where I was a bit more paranoid about data integrity (like if I was
interfacing with a billing backend), I might use Postgres. However, that's
not typically the case.
--
Tilghman |
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Search
