similar to: compatibility of PRI Two B channel transfers TBTC/2BTC

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'm trying to get "blind transfer" from an incoming DAHDI line to an external number to work on an * 1.6 install using a T1 from XO. The documentation is very "distributed" and incomplete, so while it's not working, it's definitely more likely my error somehow. Couple questions if anybody is out there who even knows what TBCT is. 1) Is this even

Although in a bugtracker posting with a patch from over two years ago, Matt Fredrickson from Digium says that it works with 5ESS under Asterisk 1.2.X: http://bugs.digium.com/view.php?id=3554 There are also bounties and claims of this feature working on NI2 protocol(although no patches posted) on the voip-info.org Wiki:

Hello, We currently have a scenario where a large percentage of inbound calls on a telco PRI are intended for professors who aren't currently in their offices/at their desks. My question is, is anyone actively using the Asterisk "RLT" (Release Link Trunking) feature to bounce these sorts of calls back to the telco? The idea being to forward the call to their mobile phone without

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

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

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

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

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"

Hi- A customer of mine running asterisk has inquired if asterisk currently supports TBCT, that is the ability of asterisk to transfer a call back up to the carrier's switch to complete a connection, freeing up the B-channels on the asterisk box. I saw a reference to this feature in the asterisk "bounties" section on the Wiki, and someone added a note saying that this might be

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 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

Hi Guys, I am sorry if my issue is not related to this but I think it is. I have a PRI with Bell Canada and when I dial in and have the call transfered to a context to dial out and then have those two channels bridged, the call disconnects with cause 16 just exactly as Jay R. Ashworth shows in his CLI output. Bell Canada support RLT or know as 2BCT or TBCT to some but we have not requested that

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

Hello List We are trying to redirect calls directly, instead of opening a new channel and dialing out. Etc: A calls B on our asterisk, and is directly redirected to C We have been told that this feature should be available on a PRI level, and is called Partial re-routing. Anybody has an idea of whether this is supported in Asterisk? Kind Regards Jon Sch?pzinsky Detele. No virus found in

Does anyone know of a way to simulate the signaling of a PRI trunk for testing/setup purposes? I realize this may be a rather naive question, but I was wondering if you could take a TE110, for example, and using a crossover cable (or not?) and some means of emulating the NI2 signaling protocol connect it to another TE110 on another machine to test and verify an installation before the telco

Hi all, I have seen the term E1 and PRI used interchangably when referring to a voice service with 30B channels and 1 D channel. Are they just different terms for the same thing or is there some technical difference. Even Newton's telco dictonary seemed a bit fuzzy on this topic. I have seen it said the PRi is a protocol that runs on top of E1. Is this true?

We are connecting a new device to our voice system, and the vendor has a whole list of "supported" network devices and associated parameters for the Telco to adjust... Yes, it's the telcos issue... Anyway, out of all of the swtich types that dahdi can emulate, what is the most complete/tunable solution? The premise for those interested is a PRI connection to a Dialogic card,

I managed to get Asterisk working with my PBX using T1, now I am moving on to trying to make PRI work. I have my zaptel.conf and zapata.conf configured as follows: Zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone=us defaultzone=us Zapata.conf: [channels] transfer=yes immediate=yes callprogress=yes language=en context=default switchtype=national signalling=pri_net group=1