similar to: Channel Bank Frustrations

Folks, I'm experimenting with bringing multiple (8) analog lines from our local telco into a Carrier Access ADIT 600 channel bank with an FXO module, then having this talk to Asterisk via the T1 TDM controller on the ADIT and a TE405P card. I don't know if this will work well (ie: give me decent echo cancellation, call disconnect supervision, caller ID etc) but I haven't had much

What kind of channelbank/FXS port are you connecting to? I've seen problems connecting to some of the older versions of the Adtran Total Access 750's. I wouldn't doubt there would be problems on other channelbanks with older firmwares. Of course, no firmware on CAC AB1's I have the AAstra 480, Adtran 750 Channelbank (updated firmware), T100P card, and it worked fine on the

In my * server I have a T100P, connected with a T1 crossover cable to an Adtran TA750 with 2 FXO cards. After I do 'modprobe wct1xxp;ztcfg' the alarm on the card starts blinking red. Running zttool confirmed that yes, it is a red alarm. I've read a few previous posts on this type of setup and I'm not too much closer. What should I be checking next? A different cable? The

List, I have a TE410P (T1 mode, all PRI) and a T100P (fxoks, for fxs channel bank). I cannot seem to get the T100P to send any clock to the channel bank. I prefer that it use the same clock source as the TE410P, but it doesn't matter if it's not in sync just as long as it's there. The TE410P is configured 3x pri_cpe, 1x pri_net. The three cpe go to XO Sonus switch, the net to

I just purchased a T100p from digium and a Carrier Access Access Bank 1 channel bank (12fxs/12fxo). I have the setup partially working thanks to some help from IRC. However I still have the following issues I can't seem to resolve 1. When calling into the system from the PSTN call hangup is not detected. * leaves line in use until it is shutdown. 2. When calling an analog phone connected to

I am having some difficulty getting a T100P card to work with my PRI. When I attempt to make an outbound call via: exten => 1004,1,Dial(Zap/g1/NPANXXXXXX) I see the following on the asterisk console: -- Executing Dial("SIP/sbruton-b8ce", "Zap/g1/NPANXXXXXX") in new stack Apr 21 08:18:48 NOTICE[16401]: app_dial.c:554 dial_exec: Unable to create channel of type

Due to some failed hardware on another platform, I've had to move a T100P card to a different chassis. After this move was completed, I am seeing some strange results on the T100P card that do not display to me any failure mode with which I am familiar. The card comes up, and shows "good" carrier and status, but Asterisk refuses to bring the D-channel up. Calls of course do

I have about a dozen SIP phones up and working, now I want to connect the asterisk box to our Fujitsu 9600 PBX. I currently have two dial-up servers conencted to the Fujitsu PBX that I built with mgetty/pppd and have the lines provisioned the same way as those dial-up server, ESF, B8ZS, and E&M wink start, so I have confidence in the guys who set up the PBX. I've built a loop back plug

Hi, Maybe someone has seen this before... I've installed a new T100P, but it doesn't seem to work. I've attached the T100P to an Adtran 750 using a crossover cable. The Adtran shows a red alarm on the T1 interface. The Adtran has been set to factory defaults with FXS cards in 1-3 and an FXO card in 5. The T100P shows no signs of life--the leds are not lit. Should I be seeing

I am having trouble getting my T100P and ADIT 600 talking. I have 2 FXO 8 port cards in the ADIT and a T1 controller card. I have a T1 x-over cable connecting two together. Here are copies of the relevant bits of my zaptel.conf and Zapata.conf Zaptel.conf span=1,0,0,esf,b8zs loadzone=us defaultzone=us Zapata.cfg context=default signalling=fxs_ks group=1 channel => 1-24 My

Hello all, I've got a T100P connected to an Adtran TA750 with a T1 crossover... This connects to a patch panel with phone ports. The Adtran is fully populated with FXS cards. All I get on any phone port is a fast clicking noise... No dialtone. Asterisk 'sees' the card, (the channels show up in /proc/zaptel). Incoming calls are routed to the zap/x channel, but no ring. I'm

I run a SIP-only shop with a 23 channel PRI and single T100P. Here are my configs: /etc/zaptel.conf: span=1,0,0,esf,b8zs bchan=1-23 dchan=24 loadzone = us defaultzone=us /etc/asterisk/zapata.conf [channels] context=default switchtype=dms100 signalling=pri_cpe pridialplan=unknown rxwink=300 ; Atlas seems to use long (250ms) winks usecallerid=no hidecallerid=no callwaiting=no

Folks, I've been following recent discussions regarding echo and echo training with much interest, since it's a problem we've never been able to eliminate here. We're facing two challenges presently, and they may be related (or not): a) Cisco 7960s in the office here echo back to our staff, but the customer hears decent sound. b) We've yet to be able to pass faxes through

In the next week or so, we'll be turning up a new T1 Pri from Cox Cable in Omaha using a T100P (installed but not yet configured). While discussing the interface parameters with a very knowledgable Cox engineer, we decided on some of the basics including b8zs, esf, dchan=24, callerid, 5 digits of called number forwarded to *, and switchtype=national (NI2). They indicated their CO switch is a

My PRI is being reset at least once a day with the following errors in the logs. zaptel, zapata, libpri, and asterisk are from CVS this morning.. This has been happening for weeks on all versions (including -stable). the T100P card appears to NOT be sharing an IRQ. xenon# cat /proc/interupts CPU0 0: 1203977 XT-PIC timer 1: 3 XT-PIC keyboard 2:

To recap: T100P card wouldn't sync with the telco using line side clocking ( span=1,1,0.........) Had to use internal clocking (span=1,0,0.......) zttool showed Tx/Rx Levels as 0/ 1 For the grins of it I replaced the T100P card with another newer card from inventory. This newer card has the same rev on the ASIC / FPGA but doesn't have any of the various jumper headers installed

An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040913/52b2ac04/attachment.htm -------------- next part -------------- hi all, can anyone give solution for this. ?wct1xxp - Digium Wildcard T100P T1/PRI Card 0 zttool gives RED Digium Wildcard T100P T1/PRI Card 0 my zaptel.conf look like this span=1,1,0,esf,b8zs

An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040913/22b214e9/attachment.htm -------------- next part -------------- hi all, can anyone give solution for this. ?wct1xxp - Digium Wildcard T100P T1/PRI Card 0 zttool gives RED Digium Wildcard T100P T1/PRI Card 0 my zaptel.conf look like this span=1,1,0,esf,b8zs

Has anyone gotten CID from Bell Canada to work properly with *? We have our * box down at our datacentre in St Louis, and whenever we call it from a Bell Canada Telephone line, all we see is '' for the CID. I did some digging on google and the mailing lists and couldn't find anything pertaining directly to Bell-Canada and * CID, but didn't find much. I did however find :

Hi, I have two t100p cards installed. One card connected to the PSTN, the other card is hooked to the Definity PBX with a T1 cross over cable. The card connected to the PSTN works fine. The problem is with the card hooked up to the PBX. The light behind the card is green, but when I dial from this card I get an error. Its says it could start the D-Channel. Could someone help me out with this