[asterisk-dev] Problem with *1.6.0.5; "Skipping dialing interface since it has already been dialed"

[Håkon Nessjøen]

I have investigated the problem further:

Each time I call a queue configured in realtime, and a queue member takes
the call, it makes a new dynamic member in the list, for that call.

In the mysql table queue_members, I have one record for the queue called
"19". This record has a DAHDI/g0/xxxxx number it calls.

But asterisk queue seems to group the channel variable on g0.. Se the
following result after two calls to queue 19:

phone01*CLI> queue show 19
19           has 0 calls (max unlimited) in 'rrmemory' strategy (0s
holdtime), W:0, C:2, A:0, SL:0.0% within 0s
   Members:
      23 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls
(last was 36 secs ago)
      23 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls
(last was 7 secs ago)
      23 (DAHDI/g0/xxxxx) with penalty 1 (realtime) (Unknown) has taken no
calls yet
   No Callers


In the above output, I have replaced the outgoing phone number with the
string "xxxxx" for security reasons.
The name of the member is 23, but each time someone calls the queue, and
gets connected with member 23, it creates a new "(realtime)" member inside
"queue show 19".

Am I the only one with this problem?

Also, if everyone in the queue is busy, i get the following error:
[Nov 30 18:07:53] DEBUG[22988]: app_queue.c:3380 try_calling: Skipping
dialing interface 'DAHDI/g0' since it has already been dialed

And for each "copy" of the new dynamic DAHDI/g0 member, i will get a copy of
the above line. So when a queue has taken 100 calls, i get at least 99 lines
of this.

Should I file it as a bug, or do anyone have a meaning in why this happends?
I can't believe no one else has encountered this.

It's a vanilla Asterisk 1.6.0.5 from asterisk download site. (not using svn)

On a related note, I also sometimes see the following warning:
  [Nov 30 18:40:29] WARNING[25878]: chan_dahdi.c:2661 dahdi_call:
Unrecognized pridialplan NPI modifier: g

Seems like it reacts on me using DAHDI/g0/number... But as far as I know,
thats the only way to call to a specific trunk group(?)

Anyone? Should I post this as a bug/two bugs?

Regards,
Håkon Nessjøen


2009/11/9 Håkon Nessjøen <haakon at avelia.no>

> 2009/10/12 Håkon Nessjøen <haakon at avelia.no>
>
> Hi,
>>
>> I'm getting a bounch of these:
>> [Oct 12 13:26:53] DEBUG[7738]: app_queue.c:3364 try_calling: Skipping
>> dialing interface 'DAHDI/g0' since it has already been dialed
>> [Oct 12 13:26:53] DEBUG[7738]: app_queue.c:3364 try_calling: Skipping
>> dialing interface 'DAHDI/g0' since it has already been dialed
>>
>> Actually every time a user calls into a queue, this message is shown one
>> extra time. So the amount of these messages grow proportionally with the
>> number of calls gone through the system.
>> (after 5 calls, it shows 5 notices when the user enters the queue)
>>
>> So after 2000 calls, you can think the notices are many for each queue
>> call.
>>
>> This didn't seem too critical, since it wass "DEBUG" messages, not
>> warnings. But now the server suddenly died with a lot of calls going on, and
>> the last message it wrote before it segfaulted was indeed the "skipping
>> dialing interface" message.
>>
>> Anyone other than me, that have had problems with this?
>>
>> Regards,
>> Håkon Nessjøen
>>
>
> Seems like this has something to do with Realtime. Have anyone else had
> problems with this?
>
> If I do a "queue show 33" where 33 is a name of one of my queues, i get a
> whole bunch of:
>     40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls
> (last was 5721 secs ago)
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls
> (last was 5523 secs ago)
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls
> yet
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls
> (last was 5362 secs ago)
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls
> yet
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls
> yet
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls
> yet
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls
> (last was 5131 secs ago)
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls
> (last was 4437 secs ago)
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls
> yet
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls
> yet
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken 1 calls
> (last was 3904 secs ago)
>       40 (DAHDI/g0) with penalty 1 (realtime) (Unknown) has taken no calls
> yet
>
> All this (and much more, this was just a snippet) even though member 40 is
> indeed only 1 member, not several. So it seems like each time it tries to
> call the queuemember, it generates a new dynamic member in the queue. Even
> though the member info has not changed.
>
> Håkon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20091130/5b09dd25/attachment-0001.htm