VoIP Mailing List Archives

jkinard at closeup.org · Guest

Hi all,

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'
-- Executing [s at fax-in: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
-- Executing [s at fax-in: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 [s at fax-in: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 [s at fax-in: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'
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).

Here's my configuration for asterisk. Is anything amiss by chance?

Standard T1
Signalling is E&M Wink, 200ms wink time (as far as I can tell)
Mode is ESF and format is B8ZS

/etc/zaptel.conf is:
span=1,1,0,esf,b8zs
e&m=1-4
loadzone = us
defaultzone=us

/etc/asterisk/zapata.conf is:
[trunkgroups]

[channels]
language=en
context=default
switchtype=national
signalling=em_w
wink=200
channel => 1-4
usecallerid=yes
callerid=asreceived
cidsignalling=bell
hidecallerid=no
callwaiting=no
usecallingpres=yes
callwaitingcallerid=no
threewaycalling=no
transfer=no
canpark=no
cancallforward=no
callreturn=no
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
busydetect=yes
busycount=6
faxdetect=incoming

/etc/asterisk/extensions.conf is:
[general]
static=yes
writeprotect=no
clearglobalvars=no

[globals]
CONSOLE=Console/dsp ; Console interface for demo
TRUNK=Zap/g0 ; Trunk interface
TRUNKMSD=1 ; MSD digits to strip (usually 1 or 0)

[fax-in]
exten => s,1,Dial(IAX2/iaxmodem0/${EXTEN},10,r)

Thoughts?

Thanks!,

--Josh

faxguy at howardsilvan... · Guest

Joshua Kinard wrote:

jkinard at closeup.org · Guest

-----Original Message-----
From: Lee Howard

faxguy at howardsilvan... · Guest

Joshua Kinard wrote:

jkinard at closeup.org · Guest

Okay, so I've been toying around on the Rolm side, and still getting nothing. Took another look on Asterisk, finally figured out where the debugging could be enabled on the console, and finding a lot of interesting things.

Running 'dmesg' simply shows the entire buffer is flooded with 'PCI Master Aborts', and they appear as soon as the zaptel driver tries to do anything in conjunction with asterisk. Further more, there seems to be a problem with chan_zap and the my_zt_write function, in that it gets a -1 return code, "Resource temporarily unavailable" (which comprised the bulk of the asterisk debugging output).

I've attached a snipped version of that output, notably removing about 2000 lines of chan_zap repeating the "Resource temporarily unavailable" error. Do I need to look at downgrading asterisk and zaptel to 1.2.x, or might this be some conflict with the Proliant DL385 hardware that currently hosts the T1 Card?

FYI, asterisk-1.4.18 and zaptel-1.4.8.
Thanks!,

--jkinard
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: asterisk-zap-debug.txt
Url: http://lists.digium.com/pipermail/asterisk-users/attachments/20080219/2a696a90/attachment.txt

jkinard at closeup.org · Guest

Okay, some more interesting tidbits to throw out incase someone has run into this before.

I've found out that th D100P has been EOL'ed by Digium due to it being a bit weird with certain systems, and I suspect my HP Proliant DL385 server may be one of those. Anyone used this card on such a system, running Suse (or at minimum, kernel 2.6.16.5x), and seen either PCI Master Aborts or NMI Errors being fired around in dmesg?

I moved the the D110P card out of what was a 100MHz PCI Slot and into a 133MHz PCI slot. The PCI Master Aborts vanish, but get replaced by this:

Do you have a strange power saving mode enabled?
Uhhuh. NMI received for unknown reason 00 on CPU 1.
Uhhuh. NMI received for unknown reason 21 on CPU 0.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?

Ad infinium.

The interesting part of all of this? The whole T1-PRI Bridge setup works now. I dial my test extension, and a fax modem comes screaming back at me a few seconds later. That timing oddity with my Rolm system vanished with moving this to the PCI 133MHz slot I guess. The downside is my server locked up a few times until I passed a couple of options given to me by Digium's tech support.

I'm going to go run some hardware diagnostics on the server itself to make sure it's not going all emo on me or something, and then see what Digium can maybe help with. But I thought I'd see if anyone's had similar or other odd cases on DL385 hardware.

Cheers!,

--jkinard

-----Original Message-----

Okay, so I've been toying around on the Rolm side, and still getting nothing. Took another look on Asterisk, finally figured out where the debugging could be enabled on the console, and finding a lot of interesting things.

Running 'dmesg' simply shows the entire buffer is flooded with 'PCI Master Aborts', and they appear as soon as the zaptel driver tries to do anything in conjunction with asterisk. Further more, there seems to be a problem with chan_zap and the my_zt_write function, in that it gets a -1 return code, "Resource temporarily unavailable" (which comprised the bulk of the asterisk debugging output).

I've attached a snipped version of that output, notably removing about 2000 lines of chan_zap repeating the "Resource temporarily unavailable" error. Do I need to look at downgrading asterisk and zaptel to 1.2.x, or might this be some conflict with the Proliant DL385 hardware that currently hosts the T1 Card?

FYI, asterisk-1.4.18 and zaptel-1.4.8.

asterisk-list at puzzl... · Guest

Joshua,

On Tue, 2008-02-19 at 17:22 -0500, Joshua Kinard wrote:

jkinard at closeup.org · Guest

-----Original Message-----
Joshua,

jparker at digium.com · Guest

Joshua Kinard wrote:

jkinard at closeup.org · Guest

-----Original Message-----

support at drdos.info · Guest

Joshua Kinard wrote:

jkinard at closeup.org · Guest

-----Original Message-----