similar to: Send CallerID to PBX via PRI NI2

Okay, now I am really confused. I have two PRI's coming in from two different Carriers (QWEST and ELI), both of them are supposed to be setup to pass name and number on incoming calls. Problem that I am having is that I am not receiving inbound caller id name on either PRI, the only thing that both carriers have in common is that I am terminating into a DMS switch at the carrier.

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.

Maintainer: Express Line Date opened: January 17, 2006 Status: Open Value of bounty: $5000.00 Licensing for code: We retain intellectual rights to the underlying source code. We need Asterisk (stable version) to be able to perform a 2B channel transfer for a NI2 B8ZS PRI line. We can't use a channelized T1 at the time for our work. This feature is commonly called a call transfer on analog

My legacy PBX accepts CID number, but not name. My old PRI vendor never sent the name, so there was never an issue. I have wedged asterisk between the Legacy PBX and PSTN. PSTN - PRI - asterisk - PRI - Legacy. Any calls from asterisk (sip and iax extensions) which have callerID set, will not connect. The legacy PBX hangs up, but asterisk thinks that it is still ringing. I have added

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 all, We we send a server out to a customer with a PRI card I basically tell the PBX person that we want national, NI2, b8zs, D channel is on 24, and we are the CPE and your the NET and us a cross over cable. Allow extensions, local calls and long distance. on the surface I would have thought this would be enough for them to connect the digium card to the PBX and get calls working. The PBX

Hello All, I am getting my first PRI installed in a couple of weeks and I wanted to ask for a little advice. I have a single span Digium card I will be using for the install. Id there a benefit to which protocol I use? When asked, I told them to set it up as NI2. The PRI is through MCI and will be used for local and long distance with DIDs and features like CallerID, etc. Any advice would be

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

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

Following is my scenario to connect back to back PRI of two asterisk server. PRI cards are Sangoma A102D [Asterisk1]------------[PRI]-Cross Cable---------[Asterisk2] Asterisk1 ; Span 1 (MASTER) switchtype = national ; commonly referred to as NI2 context = from-pstn group = 0,24 echocancel = yes signalling = pri_net channel => 1-23 Asterisk2 ; Span 1 switchtype = national ; commonly

I've been working with a telco for the past two days trying to get a PRI span up and running. This is a small-ish telco and I get the feeling they don't do this very often. Anyway, they specified a pretty standard setup: ni2 switchtype, esf framing, b8zs coding, etc. All of my b-channels are up, but we're having a heck of a time getting the d-channel to come up. He finds out that

Looking for someone with a successful experience similar to this; I have a need to cross connect a 3COM NBX PBX PRI interface to asterisk, but over a long distance. We do not need any IP connectivity and the solution requires G.711u audio so there is no benefit to using IP. Has anyone here successfully cross connected any PBX PRI interface expecting NI2 PRI signaling B8ZS/ESF with an

I did some searching to find out what I need to do to get CID&NAME inbound on one of our PRI circuits. Right now, we're only getting number (well, asterisk shows the number in both the name and number portions of CID). Is there anything special I need to do with Asterisk to have it accept the name portion of CID along with the number on a PRI that is provisioned NI2? Thanks, John

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"

We just turned up a PRI with NI2 signaling for callerID & Name. We can see the name in the CDR records but, it doesn't show up when a PSTN -> SIP or PSTN -> IAX2 call is received. The phones only get the number. Where do I look to try to fix this problem? It seems to be timing related. John

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

Outbound calls on my Telus PRI aren't taking the Name portion of the callerID. I've looked at the logs, and it is being set (see below), but the PRI debug output doesn't show the name being sent anywhere. As a result, received calls always display from Unknown (or just the number). Is there some config that I've missed somewhere? I'm running NI-1 (Telus says NI-2 doesn't

Hello, I have written a small function ('JostD' based upon a recent molecular ecology paper) to calculate genetic distance between populations (columns in my data set). As I have it now I have to tell it which 2 columns to use (X, Y). I would like it to automatically calculate 'JostD' for all combinations of columns, perhaps returning a matrix of distances. Thanks for any help

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