search for: 4ess

...pri_dchannel: PRI got event: HDLC Overrun (7) on Primary D-channel of span 1 This is my zapata.conf [channels] ; ; Default language ; language=en ; ; Default context ; context=demo ; ; Switchtype: Only used for PRI. ; ; national: National ISDN 2 (default) ; dms100: Nortel DMS100 ; 4ess: AT&T 4ESS ; 5ess: Lucent 5ESS ; euroisdn: EuroISDN ; ni1: Old National ISDN 1 ; qsig: Q.SIG ; switchtype=national ; ; Some switches (AT&T especially) require network specific facility IE ; supported values are currently 'none', 'sd...

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

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.

...le echo.<br> <br> Here is my chan_dahdi.conf:<br> <br> [channels]<br> ; configuration for T1 card as PRI<br> language = en<br> <br> group = 1<br> echocancel = yes<br> echotraining = yes<br> signalling = pri_cpe<br> switchtype = 4ess<br> usecallerid = yes<br> context = incoming<br> channel => 1-23<br> <br> Someone has to have had some experience with these hardware echo cancellers, any ideas? Should I adjust my rx and tx gains? Any advice would be very helpful. Thank you.<br> <div class...

...onfig files. /etc/zaptel.conf span=1,1,1,esf,b8zs bchan=1-23 dchan=24 loadzone=us defaultzone=us relevant portions of zapata.conf: [trunkgroups] [channels] language=en context=from-pstn pridialplan=unknown signalling=pri_cpe ; pri_cpe = PRI slave ; pri_net = PRI master ;signaling=em_w switchtype=4ess group=0 channel => 1-23 debug info: -- Executing Dial("SIP/202-2d92", "zap/g0/18005551212") in new stack -- Making new call for cr 32771 -- Requested transfer capability: 0x00 - SPEECH > Protocol Discriminator: Q.931 (8) len=48 > Call Ref: len= 2 (referen...

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

Anyone configured a E1 PRI in Kuala Lampur, Malaysia with TM Malaysia? What signaling did they provide, framing, formatting? primary-4ess Lucent 4ESS switch type for the U.S. primary-5ess Lucent 5ESS switch type for the U.S. primary-dms100 Northern Telecom DMS-100 switch type for the U.S. primary-dpnss DPNSS switch type for Europe primary-net5 NET5 switch type for UK, Europe, Asia and Australia primary-ni...

Hi, 1. From chan_dahdi.conf.sample (asterisk 1.6.1.18) : ; Switchtype: Only used for PRI. ; ; national: National ISDN 2 (default) ; dms100: Nortel DMS100 ; 4ess: AT&T 4ESS ; 5ess: Lucent 5ESS ; euroisdn: EuroISDN (common in Europe) ; ni1: Old National ISDN 1 ; qsig: Q.SIG ; ;switchtype=euroisdn At the same time, dahdi_genconf generates files in which there is: ; Span 1: B4/0/1 "B4XXP (PCI) Card 0 Spa...

...ne. I move a client from ccm to Asterisk keeping the 2811 gateway. Set up is complete, outgoing and incoming calls are sended to the 2811. The problem is that in 90% of the time I get a 500server error back from 2811 when placing a call. Incoming calls are OK. The 2811 was configured in primary-4ess (?) for ccm. I changed it to primary-net5. The ios is c2800nm-spservicesk9-mz.123-11.T5.bin If someone had any hint, would be great to share. -- Daniel

You should run the 4ESS protocol ("a" on the Definity command "change DS1 board#) as the Definity may not send Display Name for the NI-2 protocol (settings "b" or "d") Remember to make the Asterisk zapata settings consistent with the Definity. On the Definity trunk group form Page 1, c...

...-96 #dchan=96 span=5,1,0,esf,b8zs bchan=97-120 #dchan=120 span=6,1,0,esf,b8zs bchan=121-144 #dchan=144 zapata.conf [trunkgroups] trunkgroup => 1,24,48 spanmap => 1,1,0 spanmap => 2,1,1 spanmap => 3,1,2 spanmap => 4,1,3 spanmap => 5,1,6 spanmap => 6,1,7 [channels] switchtype=4ess signalling=pri_cpe context=trunkinbound group = 0 channel => 1-23 channel => 25-47 channel => 49-144 ;,25-47,49-144 ;,25-47,48-288 ;channel => 1-23,25-47,49-144 ;,49-71,73-95,97-119,121-143 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.dig...

...they are set for NI2 or "National" then perhaps there's something going on within their equipment. Hard to say without doing some testing. I've had some strange occurrences with my telephone carriers here in California. For example, I had the telco set their equipment to "4ess" and I set mine to the same - it would NOT work, no matter what. I had them leave theirs on "4ess" and I set mine to "5ess" and it worked perfectly! Go figure. Are you in a position to have one of the carrier's engineers do some debugging? You can call them and let...

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

I am having problems sending and receiving calls over the T1. They never seem to connect - outbound keeps ringing, inbound gets busy. The T1 looks ok - no errors on the line. Any ideas on what is wrong? I have tried a variety of fxsks and fxoks configurations without avail. This is a single asterisk@home system with a single T1 card. Robbed Bit T1 ami, d4. ------------------inbound call

...: <br> <br> ********chan_dahdi.conf********* <br> <br> [channels]<br> ; configuration for T1 card as PRI<br> language = en<br> <br> group = 1<br> echocancel = yes<br> echotraining = yes<br> signalling = pri_cpe<br> switchtype = 4ess<br> usecallerid = yes<br> context = incoming<br> channel => 1-23<br> <br> <br> ***********/etc/dahdi/system.conf************* <br> loadzone=us <br> defaultzone=us <br> span=1,0,0,esf,b8zs <br> bchan=1-23 <br> dchan=24 <br> &...

...help me isolate the problem. Chad Hendren ; ; Zapata telephony interface ; ; Configuration file [channels] ; ; Default language ; ;language=en ; ; Default context ; context=default ; ; Switchtype: Only used for PRI. ; ; national: National ISDN 2 (default) ; dms100: Nortel DMS100 ; 4ess: AT&T 4ESS ; 5ess: Lucent 5ESS ; euroisdn: EuroISDN ; ni1: Old National ISDN 1 ; switchtype=5ess ; ; PRI Dialplan: Only RARELY used for PRI. ; ; unknown: Unknown ; private: Private ISDN ; local: Local ISDN ; national: National I...

...Is this an Asterisk bug, or do I have it configured improperly. Below is how I have it configured zaptel.conf span=1,1,0,esf,b8zs span=2,2,0,esf,b8zs span=3,3,0,esf,b8zs zapata.conf [trunkgroup] trunkgroup=>1,24,48 spanmap=>1,1,1 spanmap=>1,2,2 spanmap=>1,3,3 [channels] switchtype=4ess context=default signalling=pri_cpe nsf=sdn group=1 channel => 1-23,25-47,49-72 Thanks for any help. Mark

...ers-bounces@lists.digium.com [mailto:asterisk- > users-bounces@lists.digium.com] On Behalf Of mavince@optonline.net > Sent: Sunday, November 05, 2006 6:09 PM > To: asterisk-users@lists.digium.com > Subject: [asterisk-users] Definity Asterisk Caller ID Issue > > You should run the 4ESS protocol ("a" on the Definity command > "change DS1 board#) as the Definity may not send Display Name > for the NI-2 protocol (settings "b" or "d") > ? > Remember to?make the Asterisk zapata settings consistent with > the Definity. > ? > On...

I just tried to go from CAS to PRI on my T1 (Sangoma), and failed pretty badly. Seemingly everything worked -- Asterisk would see the incoming call (including CID and DID info), try to route it, and fail -- giving me a telco (not Asterisk) call failure message. My zapata.conf and zaptel.conf files are at http://pastebin.com/558349 Below's the log dump. Note that, because I was simply going

...anmap => 4,1,4 [channels] ; ; Default language ; ;language=en ; ; Default context ; context=default ; ; Switchtype: Only used for PRI. ; ; national: National ISDN 2 (default) ; dms100: Nortel DMS100 ; 4ess: AT&T 4ESS ; 5ess: Lucent 5ESS ; euroisdn: EuroISDN ; ni1: Old National ISDN 1 ; switchtype=national ; ; Some switches (AT&T especially) require network specific facility IE ; supported values are currently 'none', 'sdn', 'megacom'...