similar to: What type of PRI setup is best

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

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

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

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.

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

Dovecot (1.1.1) criticises a sql user_query that's working on the sql console and thats correct. DOVECOT-LOG: "dovecot: Jul 06 22:58:29 Error: auth(default): sql(nti): User query failed: ERROR: syntax error at or near "mbox" dovecot: Jul 06 22:58:29 Error: auth(default): LINE 1: ...gid, home, (CASE WHEN smtp like '/var/pop3/ THEN 'mbox:' || ..." QUERY:

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.

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

--- Hi, this is still WIP, but already passes piglit's s3tc-teximage, s3tc-texsubimage and fbo-generatemipmap-formats(s3tc tests) and even Wolfenstein:Enemy-Territory works on my nv25. It's based on Ben's newlib branch. I have few issues though: 1) So far it needs libtxc_dxtn, but I might expose the s3tc extensions even without encoder using driconf option - Is that desirable? 2)

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

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

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

-----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of nik600 Sent: Saturday, February 18, 2006 2:00 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] problem with outgoingcallsUnabletocreatechannelof type 'ZAP' (cause 34 -Circuit/channelcongestion) On 2/17/06,

#dsync -D -vv -u stak at nti.uff.br mirror maildir:/CX4/vdomains/ nti.uff.br/stak/mail dsync(root): Fatal: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) My mail.conf *mail_location = mbox:/CX4/vdomains/%d/home/%n/mail:INBOX=/CX4/vdomains/%d/var/spool/mail/%n:INDEX=/tmp/imap-index/%d/%n *What that error means ? Before when i