Joshua Kinard wrote:
> So I'm trying to work on this complex fax server setup, and part of it 
> involves connecting my asterisk server to my Rolm CBX switch, via a T1 line.  
> I plan on using Asterisk simply as a T1-PRI Bridge to IAXmodem (which in 
> turn, activates HylaFax+ to handle the faxing).  So far, though, I don't 
> think I'm getting 100% of the way there.  When dialing the fax extension from 
> my Rolm phone, I get several seconds of silence followed by error tone.  But 
> on asterisk's CLI, I see this:
>
>     -- Starting simple switch on 'Zap/2-1'
>     -- Starting simple switch on 'Zap/3-1'
>     -- Starting simple switch on 'Zap/4-1'
>     -- Starting simple switch on 'Zap/1-1'
>   

So, okay, there are four calls coming in on the Zap (strange, but...)

>     -- Executing [EMAIL PROTECTED]:1] Dial("Zap/2-1", 
> "IAX2/iaxmodem0/s|10|r") in new stack
>     -- Called iaxmodem0/s
>     -- Call accepted by 127.0.0.1 (format ulaw)
>     -- Format for call is ulaw
>     -- IAX2/iaxmodem0-5 is ringing
>     -- IAX2/iaxmodem0-5 answered Zap/2-1
>   

iaxmodem0 correctly takes the first call...

>     -- Executing [EMAIL PROTECTED]:1] Dial("Zap/3-1", 
> "IAX2/iaxmodem0/s|10|r") in new stack
>     -- Called iaxmodem0/s
> [Feb 15 15:40:22] WARNING[24329]: chan_iax2.c:7542 socket_process: Call 
> rejected by 127.0.0.1: Busy
>     -- Hungup 'IAX2/iaxmodem0-1'
>   == Everyone is busy/congested at this time (1:0/0/1)
>   == Auto fallthrough, channel 'Zap/3-1' status is 'CHANUNAVAIL'
>     -- Executing [EMAIL PROTECTED]:1] Dial("Zap/4-1", 
> "IAX2/iaxmodem0/s|10|r") in new stack
>     -- Called iaxmodem0/s
> [Feb 15 15:40:30] WARNING[24327]: chan_iax2.c:7542 socket_process: Call 
> rejected by 127.0.0.1: Busy
>     -- Hungup 'IAX2/iaxmodem0-3'
>   == Everyone is busy/congested at this time (1:0/0/1)
>   == Auto fallthrough, channel 'Zap/4-1' status is 'CHANUNAVAIL'
>     -- Hungup 'Zap/3-1'
>     -- Executing [EMAIL PROTECTED]:1] Dial("Zap/1-1", 
> "IAX2/iaxmodem0/s|10|r") in new stack
>     -- Called iaxmodem0/s
> [Feb 15 15:40:35] WARNING[24327]: chan_iax2.c:7542 socket_process: Call 
> rejected by 127.0.0.1: Busy
>     -- Hungup 'IAX2/iaxmodem0-4'
>   == Everyone is busy/congested at this time (1:0/0/1)
>   == Auto fallthrough, channel 'Zap/1-1' status is 'CHANUNAVAIL'
>     -- Hungup 'Zap/4-1'
>   

And the other calls get busy and improperly run through the auto 
fallthrough process (you *need* a Hangup in your dialplan fax-in context).

> The Rolm gives me error tone just before the "Starting simple switch" 
> messages begin to appear, so it's almost like the Rolm is not waiting around 
> long enough for the asterisk server to answer, before it jumps to the next 
> configured T1 channel, runs out of channels (I only configured four in the 
> Rolm and on asterisk).
>   

I think that your zaptel/zapata configuration between the Rolm and 
Asterisk on that T1 is misconfigured.  Set it up for PRI if you can... 
it'll be a lot easier, is my guess.

Thanks,

Lee.



_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to