similar to: zapata.conf: recent changes?

Displaying 20 results from an estimated 3000 matches similar to: "zapata.conf: recent changes?"

2011 Feb 18
1
Asterisk with TE 121 DADHI incoming calls fail
Dear Customer Support, i connected the asterisk to a e1 interface of our hipath4000. outgoing calls from a sip peer of my asterisk to an up0 telephone which iss connected to the hipath4000 are working. If you want to dial from an up0 device to the e1 interface where asterisk is connected to, you have to use the prefix 83. But when you enter the 3rd cipher this error appears at the cli
2008 Feb 18
1
PRI dialplan/prefix
hi. could somebody explain how exactly the following parameters in zapata.conf work: pridialplan prilocaldialplan internationalprefix nationalprefix localprefix privateprefix unknownprefix the wiki & comments doesn't quite explain them. and phone companies are absolutely no help. i've setup systems in the US & China with trial & error until it works. now i'm setting up a
2006 Jun 21
1
FW: zapata.conf: recent changes?
And I'll resend this one too. Silly scalix. --Rob -----Original Message----- From: Rob Thomas Sent: Thursday, 22 June 2006 12:19 AM To: 'Asterisk Users Mailing List - Non-Commercial Discussion' Subject: RE: [Asterisk-Users] zapata.conf: recent changes? Looks like you've stopped compiling libpri. All those options that are being ignored, are being ignored because they're
2006 May 09
1
PRI in Shanghai China
hi folks. does any one have experience setting up E1 PRI in Shanghai, China? it works fine when we use SIP phone to dial out, however when using forward function on the same phone, it seems like it's dialing out but there's actually no respond from the phone company (China Telecom) and eventually the dial command will timed out. here's our PRI portion of zapata.conf:
2005 Jan 31
5
Q: PRI leading 0 (area access code) or 00 (country access code) missing on incoming callerid
hi, on our incoming E1-PRI from german telco Arcor the leading 0 for the (area access code in europe) and the 00 (country accescode in europe) are missing on incoming callerids. only prepending a single 0 is not the solution as suggested by some writers on this list, because there is no way to differ between national and international callerids and it's not possible to make the decission
2006 Jan 16
2
Problem with calls starting from a legacy PBX
Hi, I have this setup: E1 PRI PSTN -- Asterisk -- Alcatel PBX - analog phones Can someone tell me what's wrong with this call initiating from an analog phone connected to Alcatel PBX? It dies with NOANSWER but all works if I call other destination numbers. Dialplan is a simple Dial(zap/g1/0984465691) statement. At the end you'll find also zapata.conf.
2005 May 30
2
pridialplan & prilocaldialplan
Hi list! What exactly is the meaning / function of the pridialplan & prilocaldialplan? I've been trying to find out what the different possibilities for these settings are but couldn't find a clear answer. The possible parameters I could find are are : local,unknown,dynamic,national,international and maybe there are more? Thanks!
2009 Apr 03
1
ISDN Timer T309
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> Hi everione,<br> <br> I'm make some test with pri timer T309. I'm using asterisk 1.4.23.1, libpri 1.4.9, dahdi-linux 2.1.0.4 and dahdi-tools 2.1.0.2. But in my tests, the timer fail with a telco
2006 Nov 10
2
Outgoing problem on PRI
Dear All, I have an asterisk server version 1.2.12.1 along with trixbox and I am having this nasty problem, I have a TE200P and have an E1 pri attached to it and zttool says it's OK, I have configured the whole 31 channels into one group as follow: Zapata-auto.conf: callerid=asreceived signalling=pri_cpe switchtype=euroisdn context=from-zaptel group=0 channel=>1-15,17-31
2008 Feb 26
6
[URGENT] Zap channels fail to load
I have spent some time this morning trying to add an Astribank to our current Asterisk, but it failed, so I just removed the hardware, restore the config files to the original setup and started asterisk.; I could see that no Zap channels are started so I did load chan_zap.so: pbx*CLI> module load chan_zap.so [Feb 26 10:32:18] WARNING[3809]: pbx.c:2968 ast_register_application: Already have an
2008 Dec 07
2
International Calls still failing - Confused!
My international calls are not connecting. [general] pridialplan=dynamic ;prilocaldialplan=unknown internationalprefix=00 nationalprefix=0 localprefix= I have the above in my zapta.conf - yet when I dial an international number, I get a ring, then I get the message "the person you are calling, is currently unavailable" This is an ubuntu machine, with a sangoma card, with
2006 Jan 14
1
Problem with just one number!
I have this setup: (PSTN E1 PRI) -- Asterisk -- (crosscable) -- Alcatel PBX --- analog phones and a few of VoIP phones directly connected to Asterisk. Calling a number (just one!) - an automatic responder (IVR) - from VoIP phones works, from analog phones doesn't work: NOANSWER after a few seconds. I'm using no 'r' in dial options (this caused a problem with an IVR some time
2006 Apr 04
2
Fax over 2 bridged TE110P channels
Hi, I have an asterisk installation with 2 E1 cards Software version is Asterisk 1.2.6 Libpri 1.2.2 Zaptel 1.2.5 I'm having problem with fax transmission, let me explain better my setup: My fist TE110P E1 card is connected to the telco line the second TE110P E1 one to an Nexspan PBX so the server is basically sitting between the line, and the pbx. every call coming from the line is
2011 Feb 21
2
calls are not going thru e1 line
I'm curious as to what versions of everything you are using. Reason being this line " -- DAHDI/i1/00256312261627-1 is proceeding passing it to SIP/5000-00000000". It states "DAHDI/i1/00256312261627-1..." and I don't recall seeing that before (my 2.4.0 says " -- DAHDI/1-1 is proceeding passing it to SIP/801-0000000c" [1-1 being the span and channel
2007 Jul 08
3
Zapata, Junghanns Card and a leading 0 on inbound calls
Hi, I'm using a Junghanns Quadbri ISDN card on some lines from the Austrian Telekom. Things are working, the only missing stuff is to add a "0" as a prefix to each incoming call, to make it possible to answer missed call lists. I'm using the 0 as the prefix for outside lines. I've experimented a little with the prefix settings in zapata.conf, but without success:
2007 Jul 26
1
tdm400p fxs module busy
Dear All The setup is te110p with an 8 channels PRI to make and receive all calls. SIP phones throughout the company. TDM400p with 4 FXS modules to send/receive faxes and make credit card transactions. I have an analogue phone on the tdm400p for testing. I can receive calls to the exten. There is a dialing tone. However, when I try to make a call I get a busy signal. Asterisk stated busy then
2013 Jan 06
2
PRI (Primary-NTT)
hi folks. i recently setup an Asterisk system in Hong Kong. their phone company told me that their T1 PRI switch type is Primary-NTT. however in chan_dahdi.conf there's no such option. i have it set to national. it worked fine for a while, but now suddenly stop working. in coming call just keep ringing and didn't even show up on console. out going call hang up immediately with cause code
2010 Sep 15
1
One way audio when overlapdial is set to yes
Hi Group, I am currently facing a dead end and any help will be much appreciated. I have an a104d installed in an asterisk box, two of which is configured on ISDN pri. One is facing pstn and the other one is facing a hipath 300e Siemens. I am getting one way audio when a local on the hipath tries to make a pstn call but no issue on incoming calls from pstn going to the hipath locals. local
2008 Nov 12
4
test OpenVox B400P and junghans card for dahdi BRI wcb4xxp
hello: thanks for Tzafrir Cohen for dahdi testing. I installed dahdi-2.1-r3c svn code and asterisk1-6 for testing OpenVox B400P and junghans card. i fund that there is bug (i think) to dectect NT or TE mode. actually on the board, i set it as TE mode, but after start wcb4xxp, but it show the port is NT mode. to detect the TE mode, I modefy the code in base.c
2010 Apr 10
2
t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED
Hi everyone. We have a problem here... Hope somebody can give us some hints. We have a HP ProLiant DL180 G6 Server with a Debian/Lenny sytem. Asterisk 1.4.21.2 (1.4.21.2~dfsg-3+lenny1) with zaptel (1.4.11) and libpri (1.4.3) is installed. There is a QuadBRI-Card installed: # lspci -vv -s 06:04.0 06:04.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)