search for: dms100

We have a DMS100 that does not have PRI. So we're using a channelized T1 using WU-LAW, ESF and B8ZS coming from the DMS100 that's plugged into a Tormenta2 Quad T1 Card on my Asterisk Box running Debian 3.01(woody) with Kernel 2.4.22. The Link is up but according to the DMS100, Channel_1 goes into RMB (Rem...

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

Hello all, I have Asterisk 1.2.1 and a TE110P connected to a Nortel Meridian Option 81C system. The PRI line is currently setup as DMS100. Here are the relevant lines from zaptel.conf and zapata.conf: zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone = us defaultzone = us zapata.conf: [channels] language=en context=from-internal musiconhold=default switchtype=dms100 resetinterval=72000 signalling=pri_net ch...

Hi Folks, I'm trying to send CallerID Name information out to the PSTN via a PRI with Bell Canada with no success. With inbound calls (originating from the PSTN) CNAM is received successfully, and we've not had any similar problems with other Telco PRIs, so I'm stumped.

----- Original Message ----- > Message: 3 > Date: Thu, 16 Sep 2004 07:57:15 -0400 (EDT) > From: David Troy <dave@popvox.com> > Subject: Re: [Asterisk-Users] No Caller Name sent from Asterisk over > National or DMS100 PRI to a Norstar MICS? > snip> > > I have a PRI link up and running between Asterisk and a Nortel Norstar MICS > > v4.1 . I'm having a problem getting the textual Caller Name across the link > > from Ast to Ns, however numeric Caller ID arrives and displays fine. >Fro...

...th ends of the link. :-) > -----Original Message----- > From: David Troy [mailto:dave@popvox.com] > Sent: September 16, 2004 4:57 AM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [Asterisk-Users] No Caller Name sent from Asterisk over > National or DMS100 PRI to a Norstar MICS? > > > > Bill Lohr, et al: > > I can say from personal experience that with a PRI in MD (Verizon or > Verizon-CLEC) territory, it is possible to inject CALLER ID > NUMBER on a > per call basis regardless of what channel the call originates >...

...r numeric Caller ID arrives and displays fine. From Ns to Ast both elements come through fine. I'm forcing dummy values for testing using: exten => s,1,SetCIDName(Test) exten => s,2,SetCallerID(1234561234) exten => s,3,Dial(zap/g1/${ARG1},15) I've tried switchtype=national and dms100 (adjusting accordingly on Ns) with no change. zapata.conf is currently: ; Norstar #2 (Wharf Road) context=in-t1nstar group=1 usecallerid=yes hidecallerid=no usecallingpres=no switchtype=dms100 pridialplan=local signalling=pri_net channel => 1-23 The SETUP frame from Ast contains: &g...

...I seen this was done with HylaFax. Any help would be great!! Here is my configs cat zaptel.conf #PRI to Telco span=1,1,0,esf,b8zs bchan=1-23 dchan=24 # PRI to Fax server span=2,0,0,esf,b8zs bchan=25-47 dchan=48 zapata.conf [channels] context=from-analog signalling=pri_cpe switchtype=dms100 group=1 usecallerid=yes hidecallerid=no restrictcid=no usecallingpres=no useincomingcalleridonzaptransfer=yes callerid=asreceived faxdetect=no musiconhold=default channel => 1-23 context=from-sip-internal switchtype=dms100 signalling=pri_net group=2 overlapdial=yes usecallerid=yes hidecallerid...

...zone=us ======================== zapata.conf ; ; Zapata telephony interface ; ; Configuration file [channels] busydetect=1 busycount=7 relaxdtmf=yes callerid=asreceived context=default signalling=pri_cpe usecallerid=yes transfer=yes echocancel=yes echocancelwhenbridged=yes switchtype=dms100 rxgain=0.0 txgain=0.0 immediate=no signalling=pri_cpe group=1 context=default channel => 1-23 busydetect=1 busycount=7 relaxdtmf=yes callerid=asreceived context=default signalling=pri_cpe usecallerid=yes transfer=yes echocancel=yes echocancelwhenbridged=yes switchtype=dms100 rxgain=0.0 txg...

Hi all, I'm trying to insert a Rhino Ceros box equipped with a Rhino R2T1 dual-T1 card and running the latest version of Trixbox (2.4.2) between the central office and a Nortel Option 11. The switch at the CO is a DMS100. Basically, I'm taking the T1, connecting it to port 0 on the R2T1 card, and then connecting port 1 to the Nortel. (Actually a CSU and then the Nortel) We're running PRI over T1... Channels 1-23 are B and channel 24 is D. So I configured the system ahead of time with line encoding, line l...

Hi Guys I'm configuring a TE212P card and have the following two entries in my /etc/asterisk/zapata.conf switchtype=dms100 signalling=pri_cpe When I reload asterisk I get the following messages: > -- Reloading module 'chan_zap.so' (Zapata Telephony) > == Parsing '/etc/asterisk/zapata.conf': Found > [Mar 30 17:48:42] WARNING[2985]: chan_zap.c:11072 process_zap: > Ignoring switchtype &...

Hello, I'm using Asterisk (latest CVS head) to perform outbound call as robot/testing tool for an IVR platform, with a Wildcard T100P configure as ISDN Pri. For develop the exten context script I was using a real PSTN ISDN Megalink (DMS100) to reach the platform and my script was able to correctly detected the DTMF tone send back by the platform to synchronize the script. But for load test, I want to used a direct ISDN link with the platform, without to change anything at the Asterix side, I configure the platform to be the ISDN Net...

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" signals to my system, to which he's getting an "establish remote" response from my asterisk box. I've been running a packet dump (wanpipemon -i w1g1 -c tr...

...NOTICE[23988]: chan_zap.c:8202 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 cur...

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.

...pan=1,1,1,ccs,hdb3,crc4,yellow span=2,0,1,ccs,hdb3,crc4,yellow bchan=1-15,32-46 dchan=16,47 bchan=17-31,48-62 ------------------------------------------- where span 1 is to the provider and span 2 is to the PBX zapata.conf --------------------------------------------- context=from-pstn switchtype=dms100 signalling=pri_cpe callerid=asreceived group=1 callgroup=1 pickupgroup=1 rxgain=0.0 txgain=0.0 channel=>1-15,17-31 context=from-pstn switchtype=dms100 signalling=pri_cpe callerid=asreceived group=2 callgroup=2 pickupgroup=2 rxgain=0.0 txgain=0.0 channel=>32-46,48-62 -------------------------...

...en => _NXXNXXXXXX,1,CallingPres(32) exten => _NXXNXXXXXX,2,SetCallerID(2125551234) exten => _NXXNXXXXXX,3,Dial(${TRUNK_LO}/${EXTEN}) zapata.conf [channels] usecallerid=yes cidsignalling=bell cidstart=ring hidecallerid=no restrictcid=no usecallingpres=yes callerid=asreceived switchtype = dms100 signalling = em_w group = 1 context=inbound callerid=asreceived channel => 1-24 Does anyone have any suggestions? Thanks, Waldo

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. Thanks Gene Kochanowsky

...Asterisk -> TE110P ->Kentrox (csu/dsu) -> Mitel T1 Card. All I get is a blinking yellow on my TE110P card and an alarm on my Mitel. T1 card. Any advice would be great. Zaptel.conf span=1,0,1,d4,ami e&m=1-23 dchan=24 Zapata.conf signalling=em_w switchtype=dms100 echocancel=yes echocancelwhenbridged=yes echotraining=400 callerid=asreceived group=1 context=default channel => 1-23 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050422/a116dd2d/attachm...

...elcos issue... Anyway, out of all of the swtich types that dahdi can emulate, what is the most complete/tunable solution? The premise for those interested is a PRI connection to a Dialogic card, channels 1-10 inbound, the rest outbound. The vendor states that their point of view, if the CO has a DMS100 that is the easiest (PRI, 1-23, NI1, B8ZS, 10 channel choke for inbound). I won't type the two pages of "CO tweaks" for a 5ess... I also don't want the monthly reoccurring when we have multiple PRIs to tie into as it is. Thanks for the input! -Jonathan