Summary:ASTERISK-04044: DNID is not always set on incoming BRI calls with HFC driver bristuff-0.2.0-RC8
Reporter:Thomas (thomas andrews)Labels:
Date Opened:2005-05-03 09:24:20Date Closed:2011-06-07 14:05:30
Versions:Frequency of
Description:DNID is sometimes correctly set, and sometimes null depending on some of the following factors: If I use one b-channel to call out and back in again, the DNID of the incoming call is always null. If I make an incoming call on the BRI immediately after starting asterisk, the DNID is also null. If I start asterisk, make an outgoing call which comes back in again (ie phone my own number), and then hang up, the subsequent incoming call from an outside party will correctly display DNID consistently. If there is a call busy on b1 then incoming calls on b2 will have DNID null.

In all cases DNID is only seen if an outgoing call has been made.

It looks to me like p->pri is not being set when there is an incoming call, but rather only when there is an outgoing call.


Using asterisk 1.07, Libpri 1.07, Zaptel 1.07, bristuff-0.2.0-RC8
(The patches in bristuff have been applied)
Hardware: 2xTDM cards with 8 FXS modules and 2xBillion HFC cards.
Comments:By: Kevin P. Fleming (kpfleming) 2005-05-03 20:41:20

bristuff is not part of the Asterisk source tree, and is not supported by this bug tracking system. You'll have to report your issue to the bristuff maintainer.