Displaying 20 results from an estimated 9000 matches similar to: "zapata.conf not being parsed by *"
2006 Mar 17
3
Exchange 12 Unified Messaging
Exchange 12 will support "OVA" Outlook Voice Access. It will do this using VOIP. I was wondering if anyone has given any thought as to how Asterisk might interface with Exchange 12. It will do this using a VOIP gateway.
If this could happen it seems to me this could be a really big win for Asterisk. I am going to setup a test server as soon as I can and start digging into this.
2006 Oct 24
10
Meetme... No channel type registered for 'zap'
When I call meetme:
exten => 1000,1,Answer
exten => 1000,n,Meetme(|||d)
Asterisk is complaing with:
-- Executing Answer("IAX2/xxx.yyy.142.204:4569-2", "") in new stack
-- Executing MeetMe("IAX2/xxx.yyy.142.204:4569-2", "|||d") in new stack
-- Playing 'conf-getconfno' (language 'en')
Warning, flexible rate not
2007 Oct 18
4
Issues with making calls
Hi List,
I am from Peru, I have installed an asterisk server in my company with
digium card E1 TE120P, I am having issues when i make calls, here the
error from my server
[Oct 18 09:13:50] WARNING[2377]: channel.c:3232 ast_request: No
channel type registered for 'Zap'
[Oct 18 09:13:50] WARNING[2377]: app_dial.c:1106 dial_exec_full:
Unable to create channel of type 'Zap' (cause
2009 Oct 04
9
Zaptel problems on SUSE 9.3
Hi
My asterisk output is:
chan_sip.so => (Session Initiation Protocol (SIP))
Asterisk Ready.
-- Registered SIP '201' at 192.168.0.55 port 33906
-- Saved useragent "X-Lite release 1011s stamp 41150" for peer 201
-- Executing [907768385144 at default:1] Dial("SIP/201-083e75c0",
"ZAP/g1/907768385144|60") in new stack
[Oct 4 11:54:27]
2004 Sep 28
2
Unable to open pseudo channel
Hi All,
I've had a great time exploring * on & off over the past month and have
had a deal of success, very impressed with this product...
I have an issue on a debian unstable system with the zap interface.
I've compiled and loaded the ztdummy successfully, but when attempting
to connect to a conference room I get failure. I get the error
chan_zap.c:757 zt_open: Unable to open
2004 Sep 27
8
Complete newbie seeks start . . .
Hi ..
I've just received in the post my Wildcard card with a single FXO and
three FXS daughter cards.
I've identified a dedicated PC to function as the * machine and
installed the card. I've installed Fedora Core 2 on that machine.
I've downloaded the * software and the zaptel drivers.
And now, to be quite honest, I haven't got much of a clue what to do next!
I've
2009 Aug 13
1
Autofallthrough delays before hanging up calling channel?
I am seeing some curious behaviour with a 1.2.32 system, which I do not
understand and so can't work out how to fix it.
I have a PRI routed to context default. Here is the complete default
context:
[default]
exten => _9X.,1,Dial(IAX2/m1peer/${EXTEN:1})
exten => _20XX,1,Dial(IAX2/sipeer/${EXTEN})
exten => _X.,1,Dial(IAX2/m1peer/${EXTEN})
exten =>
2004 May 20
4
x100p card + dailing out
I think I have it configured properly. ztcfg -vv shows it as channel 1 and
zttool shows it as OK. But I can't dial out.
When I try, it shows it arrive in teh right stack, but then issues the
following errors:
channel.c:1676 ast_request: No channel type registered for '{PSTN-1}'
app_dial.c:554 dial_exec: Unable to create channel of type '{PSTN-1}'
= = Everyone is busy at
2004 Jul 23
1
No channel type registered for 'ZAP'
Hi,
I'm trying to set up a basic FXO <> SIP gateway. That is, I want calls
from my SIP phone to simply be dumped onto the POTS line. My (entire)
extensions.conf is:
[from-sip]
exten => _9NXXXXXX,1,Dial(ZAP/1/${EXTEN})
and my zaptel.conf is:
fxsks=1
loadzone=us
defaultzone=us
and my zapata.conf is:
context=incoming
signalling=fxs_ks
echocancel=yes
2003 Apr 23
4
Zapata not required??
Hi,
Just browsing through the asterisk.org site and I see in the setup isntructions that only Zaptel, Libpri and Asterisk need to be checked out..
Has Zapata been intergrated into one of the other packages?
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
2004 Oct 05
1
problems with X100P - No channeltyperegisteredfor 'Zap'
Just to make sure this isn't a typo in your original email... Is this
example from your zapata.conf?
Also, the extension you have shown are in extensions.conf not
zapata.conf correct?
Here is an example of a good zapata.conf....
[channels]
language=en
busydetect=yes
faxdetect=both
busycount=7
relaxdtmf=yes
callwaiting=yes
callwaitingcallerid=yes
useincomingcalleridonzaptransfer=yes
2009 Jan 31
3
Zapata.conf
Hi pals,
Pardon me if this question sound basic please. This is the first
installation where I have to use the analogue card and therefore a little
lusty. I have googled a lot, but though there is a lot of information about
the above file, none indicate where the file lives. I have a installed
asterisk and zaptel software on a fresh installation of CentOS 5. This all
from source and following
2007 May 22
3
Dial out issues.
Dear all.
I have what appears to be a configuration error but I cannot for the life of me see what it is. (I am a newbie)
I have searched the wikki and google etc but still none the wiser. Any help would be very gratefully received.
Problem:
Unable to make outgoing calls via E1 euroISDN Digium TE110p card, given congestion signal as per config, unable to open zap channel. All incoming calls work
2003 Jun 01
4
Zapata 3.3v PCI version...
Does anyone know if there are any plans for Zapata or anyone else for that matter to come out with a 3.3v PCI version or PCI-X version of those cards?
Gene
2007 Apr 12
4
Zap failure: cause 66 - Channel not implemented
Hi,
I just compiled and installed Asterisk-1.4.2 along with zaptel-1.4.1
and libpri-1.4.0 on a Debian machine with a TDM400P card.
Everything goes ok but when I try to make a call through the ZAP
channel get an error message about NO ZAP CHANNEL AVAILABLE. Ztcfg and
zttool show the card correctly installed.
When I tried to use the debug command ZAP SHOW, it was not present in
the CLI. My
2004 Oct 01
1
Unable to create Zap channels/IAX Warning
Please can someone help me with the following two error messages:
Error 1. I have loaded the Zaptel dirvers and everything is ok with ztcfg. I
have configured Zapata.conf and everthing looks good but it apears the Zap
channels dont load when starting Asterisk. When I make a call to one of the
fxs port I get the following error message.
-- Executing Dial("SIP/39-b204",
2005 Feb 04
2
zapata.conf ERROR?????? please help
Hi asterisk GURUs I have an issue with a call forwarding setup, I have the
next zapata conf:
-----------------zapata.conf-----------------
[channels]
context=incoming
signalling=fxs_ks
usecallerid=yes
hidecallerid=no
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
channel=1
-----------------zapata.conf-----------------
And in extensions.cof I have a
2007 Apr 26
1
AsteriskNOW generation of zapata.conf file
From: Malcom Kemp Sent: Wednesday, April 25, 2007 11:19 AM
To: 'asterisk-users@lists.digium.com'
Subject: AsteriskNOW generation of zapata.conf file
I am a new user of Asterisk, and an trying to use AsteriskNOW. The test
system is dual processor, so I am using the beta 4 version. I am
currently trying to manually configure, as the GUI does not seem to let
me accomplish what I need.
2003 Jun 08
2
zapata.conf and zaptel.conf
Can anyone explain to me the difference in zaptel.conf and zapata.conf?
I'm trying to get a real clear understanding of them but its getting a
little murky in places. I will be setting up a PBX running asterisk with
2 T100P cards. I will be bringing a 23 channel PRI into one card and
connecting the other card to a Nortell 24 channel FXS channel bank. As I
understand it zapata.conf is
2007 Apr 09
1
zapata.conf
I have a Digium TDM400b11, 1FXO [port2] & 1FXS [port 1]
When I reload the chan_zap I get:
[chan_zap.so] => (Zapata Telephony w/PRI)
== Parsing '/etc/asterisk/zapata.conf': Found
Apr 9 22:39:36 ERROR[3541]: chan_zap.c:10388 setup_zap: Signalling must be specified before any channels are.
Apr 9 22:39:36 WARNING[3541]: loader.c:414 __load_resource: chan_zap.so: load_module