RE: [Asterisk-Users] zapata.conf not being parsed by *

2004-12-29 Thread Jerry Rasmussen
: RE: [Asterisk-Users] zapata.conf not being parsed by * You know I think the I compiled them in the wrong order. I bet you that is it. I will give it a try and let you know. From: [EMAIL PROTECTED] on behalf of Eric Wieling aka ManxPower Sent: Wed 12/29/2004 3

RE: [Asterisk-Users] zapata.conf not being parsed by *

2004-12-29 Thread Jerry Rasmussen
Discussion Subject: Re: [Asterisk-Users] zapata.conf not being parsed by * Jerry Rasmussen wrote: > Also when I try to dial outbound I get the following errors > channel.c:1920 ast_request: No channel type registered for 'Zap' and > Unable to create channel of type &#

Re: [Asterisk-Users] zapata.conf not being parsed by *

2004-12-29 Thread Eric Wieling aka ManxPower
Jerry Rasmussen wrote: Also when I try to dial outbound I get the following errors channel.c:1920 ast_request: No channel type registered for 'Zap' and Unable to create channel of type 'Zap' (cause 66). My assumption is I am getting these errors because Zapata.conf is not being parsed Or you have

RE: [Asterisk-Users] zapata.conf not being parsed by *

2004-12-29 Thread Jim Van Meggelen
You need two files to make the zapata stuff work: /etc/zaptel.conf /etc/asterisk/zapata.conf The first one (/etc/zaptel.conf), configures the Linux driver for the hardware. In theory, you could have another application other than Asterisk using the zaptel driver. The second one (/etc/asterisk/za

RE: [Asterisk-Users] zapata.conf not being parsed by *

2004-12-29 Thread Jerry Rasmussen
is not being parsed From: [EMAIL PROTECTED] on behalf of Leif Madsen Sent: Wed 12/29/2004 2:16 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] zapata.conf not being parsed by * On Wed, 29 Dec 2004 13:59:19 -0500, Jerry Rasmussen <[EMAIL PR

Re: [Asterisk-Users] zapata.conf not being parsed by *

2004-12-29 Thread Leif Madsen
On Wed, 29 Dec 2004 13:59:19 -0500, Jerry Rasmussen <[EMAIL PROTECTED]> wrote: > I am running * 1.0.3 for some reason when I start * is does not appear to be > parsing my zapata.conf file. I do not see any errors * just does not seem to > know to look for zapata.conf. I am unable to use my FXO