search for: switchtypes

Hi Guys I'm configuring a TE212P card and have the following two entries in my /etc/asterisk/zapata.conf switchtype=dms100 signalling=pri_cpe When I reload asterisk I get the following messages: > -- Reloading module 'chan_zap.so' (Zapata Telephony) > == Parsing '/etc/asterisk/zapata.conf': Found > [Mar 30 17:48:42] WARNING[2985]: chan_zap.c:11072

When I reload the asterisk I get the following warnings: Oct 13 08:29:17 WARNING[10170]: chan_zap.c:10874 setup_zap: Ignoring switchtype Oct 13 08:29:17 WARNING[10170]: chan_zap.c:10874 setup_zap: Ignoring signalling Oct 13 08:29:17 WARNING[10170]: chan_zap.c:10874 setup_zap: Ignoring rxwink Everything works fine as far as I know, I can dial and complete calls. So why am I getting this

Hello Asterisk users. We have a quadBRI card installed and have the following problem. When starting Asterisk, the card is up and works perfect. But if no one uses it for 2-3 hours, the card seems to change status. If I try making a call from my sip phone to an extarnal telephone then asterisk registers that I'm trying to call, i.e. it's not a bridged but a show channels gives this

I'm trying to get a Qwest PRI configured and working with my lab Asterisk server. They said that the switchtype is 5ess and the signaling is pri_cpe. My entries into zaptel.conf are: span=1,0,0,esf,b8zs bchan=1-23 dchan=24 loadzone = us defaultzone=us channels=1-23 And my entries in zapata.conf are: language=en context=telco-incoming switchtype=5ess signalling=pri_cpe

I'm having difficulty getting a PRI working between asterisk and a Merlin Legend. I have been attempting to get it going as esf, b8zs & 5ess (although I have tried other switchtypes...). I found the following info in the Legend docs: If the switch type is 5ESS, the protocol MUST be set for ATT Custom. If switch type is DMS-100, the protocol MUST be set for NTNAPRI The README in libpri implies that switchtype=5ess is ATT Custom from README: ...it has been tested work with...

Hi, I am getting this message on the * console on my first pri span. Pri show span show it is down, and I can't make any calls from the span. Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27

Hi, 1. From chan_dahdi.conf.sample (asterisk 1.6.1.18) : ; Switchtype: Only used for PRI. ; ; national: National ISDN 2 (default) ; dms100: Nortel DMS100 ; 4ess: AT&T 4ESS ; 5ess: Lucent 5ESS ; euroisdn: EuroISDN (common in Europe) ; ni1: Old National ISDN 1 ; qsig: Q.SIG ; ;switchtype=euroisdn At the same time, dahdi_genconf

Dear, I always had one E1 card with one span, so I've never had any problem in set it up through /etc/dahdi/sustem.conf and /etc/asterisk/chan_dahdi.conf because I put span=1. But now I have a PBX with two E1 cards with 4 span (8 span in total). How do I have to define both card in system.conf and chan_dahdi.conf, and how do I have to refer each span to the corresponding card ??? Thanks a

Hello all, I really checked voip-info.org but it still seems to be not very easy and I just hope that there is anybody with a simular config. We have one PRI (euroisdn with 30 channels) coming from the DTAG. The second PRI should be connected to a Siemens Hicom 150E Pro Office PBX (was cheaper than a channel bank :-) Carrier ----S2M------ * -----S2M------Siemens | |

Hi, I've connected Asterisk with 4 PRI to a Siemens HiPath 4000. For CALLERID(name) feature I wanna use Q.SIG as switchtype. Cause Siemens PBX orders Channels logical I need the parameter qsigchannelmapping=logical. Here is my chan_dahdi.conf trunkgroups] [channels] language=de context=default usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes

Did you compile and install libpri *before* Asterisk? I had same problem (among others) b/c I didn't install in the correct order. Try the awesome asterisk_update.sh shell script. Are you trying to emulate CPE or NET? Try signalling=pri_cpe Check for whitespace behind the statement, zapata.conf seems bitchy about whitespace. hth -----Original Message----- From: Steve Totaro

Hi, I've always used dahdi-genconf to just create the dahdi-channels.conf and since our PRI is fairly simple (just dump all the channels into one group) it works with dialing with dahdi/g1/(number). I'm trying to understand the file though for my own reference. It seems the file looks like this: group=0,11 context=from-pstn switchtype = national signalling = pri_cpe channel => 1-23

System: RHv9 cvs-head-11/23/04 with TDM04B and T100P (isdn pri). We've all seen many posts over the last several months regarding the stability of the TDM card. Today, the above system's TDM04B card (4 fxo ports) failed at approx 15:54:49. [root@asterisk asterisk]# cat /proc/zaptel/2 Span 2: WCTDM/0 "Wildcard TDM400P REV E/F Board 1" 25 WCTDM/0/0 FXSKS (In use)

We're rolling out Cisco 7940 phones, linked to *, which is running a TE405p EuroISDN. We have 2 ISDN lines, one we had for testing, and one for general (40+ users) use. During the testing phase, we had 10 phones linked to the second ISDN line, and there were no problems with echo at all. Lucky me. However, since we have started rolling out, we've had quite loud complaints that there is

Any ideas? 51] logger.c: [chan_zap.so] => (Zapata Telephony) Sep 28 00:42:35 VERBOSE[5151] logger.c: == Parsing '/etc/asterisk/zapata.conf': Sep 28 00:42:35 VERBOSE[5151] logger.c: == Parsing '/etc/asterisk/zapata.conf': Found Sep 28 00:42:35 VERBOSE[5151] logger.c: == Parsing '/etc/asterisk/zapata-auto.conf': Sep 28 00:42:35 VERBOSE[5151] logger.c: == Parsing

Hello list i have an issue with my dahdi_channels.conf in span 1 when i use it like below i can do my outband calls without issue ; Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) group=0,11 context=from-pstn switchtype = euroisdn signalling = pri_cpe channel => 17-31 context = default group = 63 but when i add in channel 1-15 like: channel => 1-15,17-31 i receive all

Asterisk 16 latest DAHDI 3.0.0 latest Excerpt from chan_dahdi.conf is shown below. I'm trying to enable fax detection on inbound calls so that I can take appropriate action in the dial plan. "dahdi show channel 1" shows "Fax Handled: no". Does that mean that I don't have it configured correctly? [channels] ; Span 1: WCTE2/0/1 "WCTE23X (PCI) Card 0 Span

This is, hopefully, just a case of brain fade. With zapata.conf and zaptel.conf in place, asterisk loaded, no dial plan and all LEDS on the card lit, I get no dial tone, plugging an analog phone into ports 1 or 2, only a buzz and click. zaptel.conf - defaultzone=us loadzone=us fxoks=1,2 fxsks=3,4 zapata.conf [channels] signalling=fxo_ks language=us context=phones-1 group=0

I have a pretty large setup on one of my customers. Digium TE420B (with echo cancelling module), 3 Xorcom Astribanks with 32 FXS each and 1 Xorcom Astribank with 16 FXO. These FXO ports are NOT used for fax/data transmission, as they are connected to cell phones. Not really related to the issue, but there are also 250 SIP phones. The problem is that fax and dial-up connections are really

Hi all I have a server that has two TE412P (T1/E1+DSP) cards installed. One of them configured as an E1 PRI connected to PSTN and another one configured as a T1 E&M connected to Avaya PBX. Each card only uses two ports, so there are 2 E1 lines and 2 T1 lines connecting to this server. The purpose of this server is as a TDM trunk gateway that gets call from E1/T1 and then forward to an IP-PBX