similar to: DMS-500 CID name not in CDR

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

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.

We have just had an ISDN PRI service commissioned here in AU (using Powertel as provider). I have called them and ensured that we have the ability to set Caller ID on our service to any number in our 100 number block, and I have been assured that everything is OK from their end (unlikely). Every time I drop a sample.call in to /var/spool/asterisk/outgoing with the Callerid: option set, the

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

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

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, I have a Cisco 2600 PRI gateway being hosted on an Asterisk server. The PRI on the cisco is pointing to a customer legacy PBX, the SIP VoIP side of the cisco is pointing to an Asterisk server (1.2.X). In Asterisk, the SIP peer is setup with callerid="some name"<5551212> In a SIP call from the cisco to asterisk, there is no CID name info in SIP debug, so Asterisk

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

I managed to get Asterisk working with my PBX using T1, now I am moving on to trying to make PRI work. I have my zaptel.conf and zapata.conf configured as follows: Zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone=us defaultzone=us Zapata.conf: [channels] transfer=yes immediate=yes callprogress=yes language=en context=default switchtype=national signalling=pri_net group=1

Hey all, It such a shame that BRI technology is such a flop in the USA. For a small office such as mine it would be a great product. So her goes my question.... What is a known asterisk working BRI card that will operate in the USA. I need to weigh price/quality. I need to do DID/DDI (or what ever you want to call it). Asterisk will do everything else I need. The ILEC has at the other

??? Usually phone companies set the outgoing CallerID for you but recently we got control over that and are now setting the outgoing Calleir ID ourselves.? My problem now is that the CDR will put the outgoing CID in the CDR instead of the extension that dialed and that causes problems for reports.? What is the proper way to set outgoing CID and keeping the original extension number in the

Hi all- HELP! This is actually a revisit of a problem that I had earlier with E400P's at a customer site. Customer still gets locked up channel problem, but has learned to live with it (channels clear themselves after several minutes). The symptoms, which I believe are directly related: I'm having problems with tons of framing and "read" errors on my E1 connections (and

On 2/22/18 1:07 PM, Antony Stone wrote: > On Thursday 22 February 2018 at 19:10:51, Carlos Chavez wrote: > >> Usually phone companies set the outgoing CallerID for you but >> recently we got control over that and are now setting the outgoing >> Calleir ID ourselves. My problem now is that the CDR will put the >> outgoing CID in the CDR instead of the extension

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

On 2/22/18 3:46 PM, Antony Stone wrote: > On Thursday 22 February 2018 at 21:41:41, Carlos Chavez wrote: > >> On 2/22/18 1:07 PM, Antony Stone wrote: >>> On Thursday 22 February 2018 at 19:10:51, Carlos Chavez wrote: >>>> Usually phone companies set the outgoing CallerID for you but >>>> >>>> recently we got control over that and are