[asterisk-bugs] [Asterisk 0011618]: AST-2007-027 caused a bug with outbound dialing using the SIPPEERS table

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11618 
====================================================================== 
Reported By:                plack
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   11618
Category:                   Channels/chan_sip/DatabaseSupport
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 94593 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-21-2007 17:15 CST
Last Modified:              12-27-2007 05:18 CST
====================================================================== 
Summary:                    AST-2007-027 caused a bug with outbound dialing
using the SIPPEERS table
Description: 
System cannot find the correct peer when the host IP address has been set
and using the name for app_dial.

The system is checking only for sippeers with the host value of dynamic.
====================================================================== 

---------------------------------------------------------------------- 
 sergee - 12-27-07 05:18  
---------------------------------------------------------------------- 
Corydon76,

> If you wanted to take this tack through realtime, then you would have
had to do:

> var = ast_load_realtime("sippeers", "name", newpeername, "host IS NOT
NULL AND '1' =", "1", NULL);


I think this is a dirty hack, don't forget that RT engine is not an SQL
database, it's a general interface. I'm not sure that res_ldap (or any
other future non-sql backend) would like to receive that kind of queries... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-27-07 05:18  sergee         Note Added: 0076009                          
======================================================================