[Asterisk-Users] DIALSTATUS weirdness (CHANUNAVAIL instead of BUSY, NOANSWER instead of CHANUNAVAIL)

[Andrew Kohlsmith]

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 at 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 at 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.