Currently we are using 1.4.15 which does not have such nasty BUG. When I will be free, I will try to review Asterisk sources to find a problem and submit patch to this.
>From this case I see that not much people are using Asterisk Realtime with >newest Asterisk version. When holidays will end more and more people will start to complain about this. Regards, Mindaugas Kezys http://www.kolmisoft.com MOR - Advanced Billing for Asterisk PBX -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Messina Sent: Sunday, December 30, 2007 12:09 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Realtime logic in Asterisk 1.4.16.1 On Wednesday 19 December 2007 05:48:01 pm Mindaugas Kezys wrote: > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tilghman > Lesher Sent: Thursday, December 20, 2007 1:35 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [asterisk-users] Realtime logic in Asterisk 1.4.16.1 > > On Wednesday 19 December 2007 16:12:27 Mindaugas Kezys wrote: > > [Dec 20 00:04:12] DEBUG[25686]: res_config_mysql.c:138 realtime_mysql: > > MySQL RealTime: Retrieve SQL: SELECT * FROM devices WHERE name = > > 'Provider' AND host = 'dynamic' > > > > Note: host = 'dynamic' > > Correct, that's the FIRST lookup that is done. > > It then checks the IP address and does: > > "SELECT * FROM devices WHERE name = 'Provider' AND host='23.45.67.89'" > where the IP address is what is sent in the SIP INVITE. > > If that fails, it does a lookup only on the name (old behavior). > > If that fails: SELECT * FROM devices WHERE host='23.45.67.89' AND > port='5060' > > If that fails: SELECT * FROM devices WHERE ipaddr='23.45.67.89' AND > port='5060' > > If that fails: SELECT * FROM devices WHERE host='23.45.67.89' and > checks every match for insecure=yes > > If that fails: SELECT * FROM devices WHERE ipaddr='23.45.67.89' and > checks every match for insecure=yes > > And if that fails, then it returns no match. So all of those queries > had to run and fail for you to get no match. were you ever able to get a solution for this? i seem the same problem when storing my sip trunks in mysql, using 1.4.16.2 -- Anthony - http://messinet.com - http://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
