Can anyone explain this one? Sometime when I make a call and the line is busy I get: Oct 7 15:52:00 VERBOSE[20249] logger.c: -- Called g1/3235838 Oct 7 15:52:00 VERBOSE[20249] logger.c: -- Channel 0/1, span 1 got hangup Oct 7 15:52:00 VERBOSE[20249] logger.c: -- Zap/1-1 is busy (which would seem to be the correct behaviour) However, some numbers when they are busy seem to do this: Oct 7 15:51:00 VERBOSE[20249] logger.c: -- Called g1/3212121 Oct 7 15:51:00 DEBUG[20249] chan_zap.c: Queuing frame from PRI_EVENT_PROCEEDING on channel 0/1 span 1 Oct 7 15:51:00 VERBOSE[20249] logger.c: -- Zap/1-1 is proceeding passing it to SIP/5706011080-1906 Oct 7 15:51:01 VERBOSE[20249] logger.c: -- Channel 0/1, span 1 got hangup request Oct 7 15:51:01 VERBOSE[20249] logger.c: -- Zap/1-1 is busy Does anyone have an explination as to why I am getting a PRI_EVENT_PROCEEDING even though the line is actually BUSY? This, of course, totally screws up busy line detection!