similar to: New T100P Pri install suggestions?

We are in the process of installing a PRI line and we are going to connect it to an Asterisk Box. Verizon called us today to find out some information. I am surprised that they have never heard of Asterisk or Digium. But anyways, they needed some information in order to set up the circuit. Does the TE110P support NI1 or NI2? (I think the answer is both) What is the number of digits

Greetings, This may be a bit arcane but does anyone know what the contents of a facility message should be for initiating a TBCT on an NI2 ISDN. I've been trying to get it to work on a DMS100 for the last four months to no avail. The message I am currently sending makes it to the switch but is returned with unknown message. Perhaps someone here has done it before and can help me out.

I have not been able to get two B-channel transfer to work on DMS100 PRI. I consistently get the following errors: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ROSE RETURN ERROR: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: OPERATION: RLT_OPERATION_IND [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ERROR: RLT Not Allowed I have tried on two

Hi I am interested in setting up an Asterisk PBX in my office with digium hardware, and I just have a few questions in regards to what I would need. It is my understanding that an FXO card is used to interface with an incoming/outgoing phone line, and an FXS card is used for interfacing with a phone within the system. Currently we have 4 incoming/outgoing phone lines and would like to have

Hi Last week I installed Asterisk (release1) with digium t100p single span T1 (wct1xxp) board on Dell GX270 pc configured for PRI. Asterisk/t100p is currently the only user of the t1 line. All worked well for about a half a day, PSTN to SIP phones to non-SIP IP phones etc. Alas, since then I consistently get multitudes of blue alarms on all b-channels followed by a loss of d-channel: Aug 31

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

I am having my colo set up 2 PRI's for my new asterisk implementation. They asked the following... ##SNIP## What type (NI2, NTI, 4ESS, or 5ESS) and whether they want to be USER or NETWORK. If the equipment is flexible, NI2, with us as NETWORK is preferred. ##SNIP## We are using a digium quad span T1 card. What is the recommended setup? Thanks, Chris

I have an NI2 PRI connection to a 5ESS switch. I am explicitly told to use NI2 as the protocol, not 5ESS. I am running Asterisk 1.2.4. When making calls to the PSTN, Asterisk sends the calling name as part of the display information element in the SETUP message. I need to be able to send the calling name as part of the facility information element in the SETUP message. I've seen that work

Hi Guys, I have several * servers connected to T1 PRI's from various service providers in multiple locations the US. All the * servers use the same hardware with the same OS and * version. When connected to 5ESS Switches, using the NI2 (national) PRI protocol, the CID name and number come across fine and populate into the * CDR fine. I connected to a DMS-500, NI2 (national) protocol and

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

My CLEC just called and asked if we will support the "MI2" protocol on our proposed T1 circuit. I think this is for CallerID name. Will the T100P support this? Thanks, Mike

I have just received a T100P and an Adtran TSU 600 in the mail. I seem to be having a problem with the T100P card. So far I have done the following: vi zaptel.conf fxoks=1-22 fxsks=23-24 ... vi zapata.conf ... signalling=fxo_ks ... channel => 1-22 ... signalling=fxs_ks ... channel => 23-24 I then run modprobe zaptel modprobe wct1xxp ztcfg -vv There are no errors to report. In

Hi Everyone. I have a client that uses an Altigen system. I am really new to PBX systems so all this is totally foreign to me. They currently have 5 inbound trunk lines and about 20 analog phones. >From what I can gather they are using the Altigen Quantum cards that support 8 extensions and 4 trunks. >From what I can gather the solution is a TDM04B and TDM01B to bring in the lines from

Hello, A client has asked for Two B channel Transfer capability (known as TBCT or 2BCT, similar to other features such as ECT, RTL and Q,SIG Path Replacement) in a new Asterisk system and so I researched the capability and came up with quite a few gaps in documentation.

I've been going back and forth with my telco for several days, trying different configurations to get a new PRI to come up. The bchannels are all up and the T1 is not in alarm status. The dchannel refuses to come up however. We've tried ni2, qsig, and now dms100 for the switchtype. The telco tech I've been working with says that he's been sending "reset all channels"

Hello I am struggling to get my TDM04B working. Just to rule out a hardware problem how can I check that the hardware works? How can I then check that the drivers are loaded correctly? Angus -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050620/470458c6/attachment.htm

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

Hi, I'm currently working on a * server connected to an. ahem. "Wireless Communication Server". The HWCS has an NMS AG 4000C. I'm using NI2, net side on the * box. The D-Channel comes up. The B-Channels come up. The first call to the * box goes through. After which, the HWCS with the AG4000 seems to either get a state-machine screwed up, or * does not send the correct

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)

Hello all, I have Asterisk 1.2.1 and a TE110P connected to a Nortel Meridian Option 81C system. The PRI line is currently setup as DMS100. Here are the relevant lines from zaptel.conf and zapata.conf: zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone = us defaultzone = us zapata.conf: [channels] language=en context=from-internal musiconhold=default switchtype=dms100