asterisk users - Dec 2007 - Iax and ZAP

I have a working system with two fxo and two fxs channels.  I recenlty got an
IAX2 account I would like to use also.

While I have gotten the IAX2 channel to "register", it remains non
functional, as the incoming calls, go nowhere and the outgoing calls attempt to
go out over the ZAP channel.  I can see this, via the CLI, with debugs on.

I strongly suspect this is a dial plan/config problem with my setup, but I am
currently at a loss.  I've found no examples (that make sense) via google.

On incoming calls, I get a "no such context/extension".  I do not have
trunk defined for IAX. Outgoing did not work when I did, either.

joe a.

>>> On 12/11/2007 at 7:22 AM, Joe Acquisto wrote:
> I have a working system with two fxo and two fxs channels.  I recenlty got
an
> IAX2 account I would like to use also.
> 
> While I have gotten the IAX2 channel to "register", it remains
non
> functional, as the incoming calls, go nowhere and the outgoing calls
attempt
> to go out over the ZAP channel.  I can see this, via the CLI, with debugs
on.
> 
> I strongly suspect this is a dial plan/config problem with my setup, but I 
> am currently at a loss.  I've found no examples (that make sense) via
google.
> 
> On incoming calls, I get a "no such context/extension".  I do not
have trunk
> defined for IAX. Outgoing did not work when I did, either.
> 
> joe a.
Managed to get calls to answer (no more "no such context/extension"),
but they just hangup immediately.

Below is a sanitized snippet of the debug output:
------------------------------
tel1*CLI>
    -- Accepting AUTHENTICATED call from nn.nnn.nnn.nnn
       > requested format = ulaw,
       > requested prefs = (g729|ulaw|g726|gsm),
       > actual format = ulaw,
       > host prefs = (ulaw|alaw|gsm),
       > priority = mine
    -- Executing [xxxxxxxxxx at incoming-iaxprovider:1]
Answer("IAX2/iaxprovider-3", "") in new stack
    -- Executing [xxxxxxxxxx at incoming-iaxprovider:2]
Dial("IAX2/iaxprovider-3", "SIP/200|20") in new stack
Tx-Frame Retry[000] -- OSeqno: 001 ISeqno: 002 Type: IAX     Subclass: ACCEPT
   Timestamp: 00070ms  SCall: 00003  DCall: 00247 [nn.nnn.nnn.nnn:4569]
   FORMAT          : 4

Tx-Frame Retry[000] -- OSeqno: 002 ISeqno: 002 Type: CONTROL Subclass: ANSWER
   Timestamp: 00073ms  SCall: 00003  DCall: 00247 [nn.nnn.nnn.nnn:4569]
  == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing [xxxxxxxxxx at incoming-iaxprovider:3]
Goto("IAX2/iaxprovider-3", "aa_menu3|s|2") in new stack
    -- Goto (aa_menu3,s,2)
    -- Hungup 'IAX2/iaxprovider-3'
Tx-Frame Retry[000] -- OSeqno: 003 ISeqno: 002 Type: IAX     Subclass: HANGUP
   Timestamp: 00084ms  SCall: 00003  DCall: 00247 [nn.nnn.nnn.nnn:4569]
   CAUSE CODE      : 3
------------------------------

A snippet of the dial plan.

------------------------------

[incoming-iaxprovider]

exten => xxxxxxxxxx,1,Answer()
exten => xxxxxxxxxx,2,Dial(SIP/200,20)
exten => xxxxxxxxxx,3,goto(aa_menu3,s,2)
exten => s,n, Hangup

-------------------------


joe a.

>>> On 12/12/2007 at 8:35 AM, Joe Acquisto wrote:
 I have a working system with two fxo and two fxs channels.  I recenlty got
> an 
> > IAX2 account I would like to use also. . . .
> > 
. . . the outgoing calls  attempt 
> > to go out over the ZAP channel.  I can see this, via the CLI, with
debugs
> on.
> > 
After correcting my errors, I can receive calls.

Outgoing calls remain non functional, insisting on going out over the ZAP
channel.

I think I would like to maintain the ZAP channels and use iax on occasion.  How
about something like pressing *99 (or something), presenting a dial tone (or
some noise) that would signal to enter the intended number?

I am not getting how to "direct" which channel/trunk to use.

joe a.