asterisk users - Dec 2004 - DIALSTATUS weirdness (CHANUNAVAIL instead of BUSY, NOANSWER instead of CHANUNAVAIL)

Just throwing this out here, hopefully someone can tell me why.

*CLI> show version
Asterisk CVS-HEAD-11/17/04-10:16:38 built by root@wanderer on a i686 running 
Linux

Zap/g1 is pri_cpe to Bell Canada
5551234 is a normal POTS line I have busied out (handset offhook)

exten => 1234,1,Dial(Zap/g1/5551234,,g)
exten => 1234,n,NoOp(HANGUPCAUSE is ${HANGUPCAUSE} and DIALSTATUS is 
${DIALSTATUS})

Why, if 5551234 is busy, is DIALSTATUS set to CHANUNAVAIL?  Should it not be 
BUSY?

And now with IAX2 (I am using a user:pass that is purposely invalid):

exten => 1234,1,Dial(IAX2/user:WRONGpassword@peer/${EXTEN})
exten => 1234,n,NoOp(HANGUPCAUSE is ${HANGUPCAUSE} and DIALSTATUS is 
${DIALSTATUS})

DIALSTATUS is NOANSWER instead of CHANUNAVAIL ... huh??

Is there a logical reasoning for this?

-A.

All,

I've got a problem here. We are using a Digium 4 T-1 board in our * server. 
The T-1's are ISDN.  The problem I'm having is that we have an ivr setup
so
that when someone dials our DID it goes to the s extension and starts 
playing the ivr which is fine, but if someone dials an extension for example 
extension 200, it doesnt go to 200 it goes to extension 2.  Seems like our 
server doesn't even wait for the rest of the digits dialed. soon as it sees 
2 it goes straight to exten 2 and ignores the last two zeros therefore never 
reaching extension 200. any suggestions?  i've enclosed a snipet below.

TIA,
-Jon


exten=>s,1,Answer
exten=>s,2,Wait(1)
exten=>s,3,Background(intro)
exten=>s,4,Background(ivrmenu)
exten=>i,1,Playback(invalid)
exten=>i,2,Goto(s|4)
exten=>200,Goto(office,102,1);forward to 102 in office context
exten=>201,Goto(office,110,1);forward to 110 in office context
exten=>1,1,Goto(office,102,1)
exten=>2,1,Goto(office,103,1)
exten=>3,1,Goto(office,104,1)
exten=>4,1,Goto(office,105,1)
exten=>5,1,Goto(office,106,1)
exten=>0,1,Goto(office,107,1)
exten=>t,1,Goto(office,108,1)

On December 3, 2004 03:36 pm, Andrew Kohlsmith wrote:
> exten => 1234,1,Dial(Zap/g1/5551234,,g)
> exten => 1234,n,NoOp(HANGUPCAUSE is ${HANGUPCAUSE} and DIALSTATUS is
> ${DIALSTATUS})
>
> Why, if 5551234 is busy, is DIALSTATUS set to CHANUNAVAIL?  Should it not
> be BUSY?
Brian West pointed me at chan_zap.c where there is a configuration parameter 
called "priindication" which can be used to set the pri indication to
inband
or out of band, defaulting to out of band.

I have set priindication=outofband in zapata.conf, now I will test this later 
but it looks like it will work.

Posting a new thread now in -dev as to why the blue f*ck there is a pri inband 
configuration option that is 

a) undocumented and 
b) defaults to inband

The mind boggles -- PRI is *always* out of band.

-A.