similar to: DMS-500 CID NAME Problem

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

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

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.

Having a problem w/ not getting CID name from a PRI. CID Name appears in the PRI debug, but even after a Wait(4) it still appears after the phone is ringing. Here is the relevant info from my PRI debug output. Line 4 is a NoOp showing me trying to echo Name and Number. Line 6 dials the extension, and you can see callerid name get presented on line 29. Again, there is a Wait(4) before the

I currrently have Asterisk 1.2.8 with a TE110P Zaptel card tied to our Nortal DMS-10 switch via T1. This T1 trunk is configured for Feature Group D MF. The purpose of this is for LD delivery to a VoIP LD provider as a LD choice for our customers off of the DMS-10. When I sieze a channel on the zaptel, I get a spill of digits from the switch that is the called number, and I can see that in

> > Hello All, > > I have been struggling with this for a long, long time. I came here > looking for answers. So, I have a VM running Debian Lenny. I install > the apt package samba, which installs 3.2.5. I work in a large > university with an extensive Active Directory environment, both forest > and domain running in Win2k native mode. There is a NetApp filer >

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

Hello everyone! I have a little problem: HRH = trusted domain (Samba 3) Hendricks = trusting domain (NT4 sp6a) Trusts are setup between the NT4 and Samba3 + OpenLDAP domain and appear to be working properly. When logged into the HRH domain on a W2k workstation I can view,read, and write on available shares for HRH groups and users on our Windows file servers. Whenever I try to see available

Hi All, We successfully installed MFC/R2, chan_unicall.so with asterisk ver 1.2.6. asterisk is loading properly and we can see US show channels working fine. We are using digium Te120P card. Now we are trying to setup E1 link with Nortel DMS 100, which is resides at one of telco provider in Sri Lanka. But we don't know what is the exact protocol varient to use. Is anyone help us out on this

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

I have not been able to get two B-channel transfer to work on DMS100 PRI. I consistently get the following errors: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ROSE RETURN ERROR: [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: OPERATION: RLT_OPERATION_IND [Nov 6 11:12:49] ERROR[2774]: chan_zap.c:8178 zt_pri_error: ERROR: RLT Not Allowed I have tried on two

I'm having difficulty getting a PRI working between asterisk and a Merlin Legend. I have been attempting to get it going as esf, b8zs & 5ess (although I have tried other switchtypes...). I found the following info in the Legend docs: If the switch type is 5ESS, the protocol MUST be set for ATT Custom. If switch type is DMS-100, the protocol MUST be set for NTNAPRI The README in

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:

The latest libpri is supposed to handle this properly, but doesn't seem to. Here's the debug info. CALLERID(name) is set to empty. < Protocol Discriminator: Q.931 (8) len=66 < TEI=0 Call Ref: len= 2 (reference 256/0x100) (Sent from originator) < Message Type: SETUP (5) < [04 03 80 90 a2] < Bearer Capability (len= 5) [ Ext: 1 Coding-Std: 0 Info transfer capability:

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

Hi, I am running * with E100P board. At least every our I got an Error 500 message and ISDN-PRI restarts: Jan 10 12:53:02 WARNING[98311]: File chan_zap.c, Line 5758 (zt_pri_error): PRI: Read on 27 failed: Unknown error 500 Jan 10 12:54:27 WARNING[98311]: File chan_zap.c, Line 5758 (zt_pri_error): PRI: Read on 27 failed: Unknown error 500 Jan 10 13:33:01 WARNING[98311]: File chan_zap.c, Line

Hi The first step I have to go through when users call into our IVR is to handle the case where users' PBX hides their CID number. In that case, I need to have them type their phone number (ten digits). OTOH, those who call without hiding their CID number are sent directly to the main menu. How would I go about prompting users for their phone number? Here's what I have at this point:

Hi list, For a client I am setting up a system which will use T1 PRI from Primus, who offer only NI-1 and NI-2 protocols for D-Channels. Previousely I have only used switchtypes euroISDN and National. Although the documentation says Asterisk does support NI-1 ans NI-2, but wanted to get your opinion if you have used these protocols on an Asterisk box and if there were any things to consider. If

Hi all, using Skype for Asterisk I have the following problem. In my dialplan I need to have a CID matching (example.skype) over a DID (test.skype) : [example] exten => test.skype/example.skype,1, NoOp(nothing) exten => test.skype/example.skype,n, Hangup() Where test.skype and example.skype are Skype business account. In this case, when I get a : CLI> show dialplan example I get: [