similar to: NI2 signaling with * for CID&NAME?

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 Chris. -------------- next part -------------- An HTML attachment

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

Hi All, Sorry for the double post, but I'm in a real bind. 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 CVS-v1-0-11/09/04-12:27:27. When connected to 5ESS Switches, using the NI2 (national) PRI protocol, the CID name and number come across fine and

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

I there, I have some trouble to do working caller id name for outgoing calls on the PRI we just installed. Caller id name work on incoming calls only. Caller id number work on incoming and outgoing calls. The provider, Goup Telecom, said that's in what i'm sending. They said that I send the cid name in ascii code and to do it working, I need to send it in hex. So I take some traces

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

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

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

I'm having trouble getting outbound calls going with aah 1.3 and a tdm400p w/ 4 FXO. Incoming calls work fine, outbound I get this: -- Executing SetVar("SIP/231-af2b", "OUTNUM=6643955") in new stack -- Executing Cut("SIP/231-af2b", "custom=OUT_1|:|1") in new stack -- Executing GotoIf("SIP/231-af2b", "0?19") in new stack

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

Ok, I'm about to take the plunge, and am trying to decide between Channelized T1 E&M and PRI. I'm getting an "Integrated T1" which will have data and voice capability, all plugged directly into my digium single T1 card. In either case the data piece looks pretty straighforward, just setup the channel properly, hand it off to the linux hdlc layer, and route away.... the

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

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

We have a setup running Asterisk interconnected to a Panasonic TDA200. The Asterisk server has a two port E1 card, one connected to the phone company and the other to the Panasonic. Everything is running fine and we can send and receive calls from the Panasonic and phone company. We are using MFC/R2 for both links on Asterisk 1.4.4 and Zaptel 1.4.3. The only detail we have is that we cannot

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

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

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: