[asterisk-bugs] [Asterisk 0012416]: gratuitous, incorrect database lookups when loading a realtime SIP peer/user

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=12416 
====================================================================== 
Reported By:                _brent_
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12416
Category:                   Resources/res_config_pgsql
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             04-10-2008 18:32 CDT
Last Modified:              04-11-2008 10:12 CDT
====================================================================== 
Summary:                    gratuitous, incorrect database lookups when loading
a realtime SIP peer/user
Description: 
With debugging turned way up, I noticed a warning in the CLI when placing a
call between two extensions on an instance of Asterisk (my
sippeers/sipusers table is user_agent_client_assignment):

[Apr 10 23:36:00] WARNING[32014] res_config_pgsql.c: Postgresql RealTime:
Could not find any rows in table user_agent_client_assignment.

Examining the PostgreSQL logs and more Asterisk debugging shows that
Asterisk makes one correct, successful query and several badly-formed,
unsuccessful queries.

See the attachments for output from Asterisk and PostgreSQL.


====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 04-11-08 10:12  
---------------------------------------------------------------------- 
No, those queries are correct.  You're simply seeing the order in which
Asterisk tries to do matching.  We try to keep the behavior identical, in
terms of matching, whether you're using static or realtime configs. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-11-08 10:12  Corydon76      Note Added: 0085347                          
04-11-08 10:12  Corydon76      Status                   new => closed       
04-11-08 10:12  Corydon76      Resolution               open => no change
required
======================================================================