Summary:ASTERISK-11930: Bad name when calling between two extensions
Reporter:vicsanca (vicsanca)Labels:
Date Opened:2008-04-28 02:29:59Date Closed:2008-04-29 12:25:44
Versions:Frequency of
Description:When calling between two iax extensions asterisk ask for a bad name. I have this error in log:

[Apr 28 09:22:18] DEBUG[32119] res_config_pgsql.c: 1Postgresql RealTime: Result=0x8711548 Query: SELECT * FROM iax_buddies WHERE name = '102-10' AND host = 'dynamic'
[Apr 28 09:22:18] WARNING[32119] res_config_pgsql.c: Postgresql RealTime: Could not find any rows in table iax_buddies.

When should be:
SELECT * FROM iax_buddies WHERE name = '102' AND host = 'dynamic'


When registering iax extensions asterisk ask with the correct name:
[Apr 28 09:22:08] DEBUG[32137] res_config_pgsql.c: 1Postgresql RealTime: Result=0x87113a0 Query: SELECT * FROM iax_buddies WHERE name = '102' AND host = 'dynamic'
[Apr 28 09:22:08] DEBUG[32137] res_config_pgsql.c: Postgresql RealTime: Found 1 rows.

It asks postgresql in the wrong way only when calling.
Comments:By: Joshua C. Colp (jcolp) 2008-04-28 08:12:19

Is this actually causing an issue? The devicestate core is probably just requesting the device state, and as part of that it passes the full channel name plus it tries to parse out the peer name.

By: vicsanca (vicsanca) 2008-04-29 01:33:03

No. No really. I thinked that this error was causing IAX extensions no to receive calls but was a context problem.
Despite this I don't understand what it's searching for with this name. It's fully documented this module? where?

By: P. Christeas (xrg) 2008-04-29 04:19:20

This behaviour is known due to the devicestate code.
vicsanca: is the erroneous query followed by a second, right one? Or can you confirm that there is only one query for the "102-10" name?

By: Jason Parker (jparker) 2008-04-29 12:25:43

xrg is correct.

To avoid confusion, I've changed the warning to a debug.