search for: ni2

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 the CID name doesn't get populated in the * CDR. The only variance in the PRI debug outputs is this, from the DMS switch: Jun 9 16:41:15...

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 am terminating a PRI, NI2 signaling into a PBX (My company's PBX not the PSTN) from an Asterisk server. Caller ID number appears to be transmitted caller id name is not being transmitted is their a compile time flag on libpri that I need to un-comment to enable this feature or is this is unsupported for now? Thanks...

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 appreciated. Thanks! Wiley -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/att...

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 phone lines. On an analog phone line, the incoming call is answered, a hook-flash is performed to get stutter dialtone, the telephone number to transfer to is dialed,...

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

...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 or suggestions. Cheers Colin Function: JostD <- function(DF, X, Y) { Ni1 <- DF[,X] Ni2 <- DF[,Y] N1 <- sum(Ni1) N2 <- sum(Ni2) pi1 <-Ni1/N1 pi2 <-Ni2/N2 pisqr <- ((pi1+pi2)/2)^2 H1 <- 1 - sum(pi1^2) H2 <- 1 - sum(pi2^2) Ha <- 0.5*(H1+H2) Da <- 1/(1-Ha) Dg <- 1/sum(pisqr) Db <- Dg/Da...

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 comes out to provision our new trunks. Regards, /rg

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.

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. Thanks Gene Kochanowsky

...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 asterisk box providing PRI_Network signaling on a T1 interface card using a long haul point to point ESF/B8ZS T1? I do not need the technical details on how to set up asterisk or the remote PBX, just need a sanity check on the idea of using the PTP T1 as a cross c...

We are in the process of ordering a Voice PRI to plug into Asterisk. Of course we will be buying a card from Digium for this. Question is this, there seem to be MANY options technically when ordering this PRI (in the US) but since this is the first time ordering a voice circuit I am clueless as to what options we need. Any clues would be helpful or maybe something has already been written

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 referred to as NI2 context = from-pstn group = 0,24 echocancel = yes signalling = pri_cpe channel => 1-23 Following is my extensions.conf stuff on b...

...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 DMS500 that is compatible with several different switchtypes including 5ess, dms100, etc. * will clock sync from this pri. This system also has a tdm04b (4-port fxo) installed and working, and is expected to remain after the t100p is implemented. Zttool can s...

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

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 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 this is an asterisk system and says that to get this working, I'm going to need to turn on "call-by-call" trunking. Have...

...s complaining about having no caller ID. I tried this, but it still would not complete the call. hidecallerid=no ;fix for no answer restrictcid=yes usecallingpres=no I have also tried to make the callerid name null, but asterisk still tries to send the data. I have also tried to dumb it down from NI2 to NI1, but asterisk still tries to send the callerID name in the PRI debug. Is there a way to send callerid number and not the name? ref. zapata.conf: context=panasonic swichtype=national pridialplan=unknown prilocaldialplan=unknown signalling=pri_net usecallerid=yes facilityenable=no hidecalle...

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" signals to my system, to which he's getting an "establish remote" response from my asterisk box. I've been running a packet dump (wa...