On Jan 11, 2007, at 11:08 PM, Jarek Jarzebowski wrote:
Dnia 31-12-2006 o 18:05:00 Jarek Jarzebowski [EMAIL PROTECTED]
napisał(a):
Dnia 31-12-2006 o 17:39:10 Tzafrir Cohen
[EMAIL PROTECTED] napisał(a):
On Sun, Dec 31, 2006 at 05:08:26PM +0100, Jarek Jarzebowski wrote:
Dnia 31-12-2006 o 16:17:19 Tzafrir Cohen [EMAIL PROTECTED]
napisał(a):
On Sun, Dec 31, 2006 at 03:59:14PM +0100, Jarek Jarzebowski wrote:
Hi All,
is anybody using Sangoma A102d card with Asterisk on Debian 3.1?
I configure and install Sangoma wanpipe step by step based on
Sangoma
Wiki
and manuals but can not get success results. I suppose that it
may be
some
Debian specific case.
AFAIK, that procedure has been tested on Debian Sarge before.
What specific problems you have?
I use wanpipe-2.3.4-3. I run ./Setup install. After standard 2
frist
question (answer 'y') I got:
Please specify absolute path name of your linux directory
(Press Enter for Default: /lib/modules/2.4.27-3-686-smp/
build)
I press Enter. And got:
Upgrading WANPIPE kernel documentation ...Done.
Upgrading WANPIPE kernel headers ...Done.
Upgrading WANPIPE kernel drivers ...Done.
cp: cannot stat `drivers/net/wan/Makefile': No such file or
directory
grep: drivers/net/wan/Makefile: No such file or directory
Updating T1/E1 in
/lib/modules/2.4.27-3-686-smp/build/drivers/net/wan/Makefile
./Setup: line 895: drivers/net/wan/Makefile.nex: No such file or
directory
cat: drivers/net/wan/Makefile: No such file or directory
drivers/net/wan/Makefile does not exist in the kernel-headers
package of
2.4 (e.g: your 2.4.27-3-686-smp) . It does seem to exist in the
kernel-headers packagers of 2.6 .
So one thing to try: use kernel 2.6:
apt-get install kernel-image-2.6-686-smp kernel-headers-2.6-686-
smp
and reboot to that kernel.
Note, however that this is just one educated guess of me.
OK. I will try that and give an answer.
I install wanpipe on Debian (kernel 2.6.8). Wanrouter seems to work
OK. But I am affraid that I do something wrong with asterisk
config. On asterisk I can see:
*CLI pri show span 1
Primary D-channel: 16
Status: Provisioned, Down, Active
Switchtype: EuroISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 1
T305 Timer: 3
T308 Timer: 4000
T313 Timer: 4000
N200 Counter: 3
*CLI pri show span 2
Primary D-channel: 47
Status: Provisioned, Down, Active
Switchtype: EuroISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 1
T305 Timer: 3
T308 Timer: 4000
T313 Timer: 4000
N200 Counter: 3
*CLI pri show intense debug span 1
[ 00 01 7f ]
Unnumbered frame:
SAPI: 00 C/R: 0 EA: 0
TEI: 000EA: 1
M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced
mode extended) ]
0 bytes of data
Sending Set Asynchronous Balanced Mode Extended
[ 00 01 7f ]
Unnumbered frame:
SAPI: 00 C/R: 0 EA: 0
TEI: 000EA: 1
M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced
mode extended) ]
0 bytes of data
It looks to me like some config misunderstunding between A102d
and Aterisk.
I am total newbe to sangoma cards, Digium like Tor2 cards have no
such a problem.
Looking forward to any ideas...
Regards,
--
Jarek
Hi Jarek!
Did you find any solution to this problem? I have the exact same
problem with a Sangoma A102d card on debian 3.1, 2.6.19 and wanpipe
2.3.4-4. I've followed several different guides, including the one on
sangoma's wiki. When I try to make a call out, I get this error:
Jan 16 13:17:28] WARNING[18084]: app_dial.c:1081 dial_exec_full:
Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel
congestion)
Also got the same SABME errors as you do.
Best regards,
Erik Haider Forsén
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users