similar to: AG4000C and T100P

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

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

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

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:

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

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

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

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

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

I have DAHDI 2.2.1 my system.conf file is : span=1,0,0,esf,b8zs bchan=1-23 dchan=24 echocanceller=mg2,1-23 loadzone = us defaultzone = us Its telling me: Running dahdi_cfg: DAHDI_SPANCONFIG failed on span 1: Invalid argument (22) [FAILED] What am I missing. Its straight PRI NI2.

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

Hi, i have the following code: define internal %"struct.dexter::ConditionConstant"* @_ZN6dexter18BinaryConditionAdd8evaluateEv5(%"class.dexter::BinaryConditionAdd"*) { entry: %1 = getelementptr inbounds %"class.dexter::BinaryConditionAdd"* %0, i32 0, i32 0, i32 1 %2 = load %"class.dexter::BaseCondition"** %1, align 8 %3 = bitcast

Hi llvm-dev@, This is a proposal for LLVM to adopt Sony's Dexter tool [0], import it into the debuginfo-tests repo, and use it to run integration tests between debuggers and clang/llvms debuginfo. (Sony has approved donating Dexter to LLVM). Background ---------- The debuginfo-tests repo contains an integration test suite for debug data, which builds each test case from its source code

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.

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

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