similar to: Fail to detect DTMF over direct ISDN pri lin k

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,

Hello, I'm having a problem with significant audio dropouts occurring in voicemail messages left via an ISDN-BRI trunk. Dropout durations are as short as 15ms and as long as 200-300ms. The audio that is recorded, appears to be otherwise complete, just with frequent holes punched in it. The same trunk has no problems with audio files played toward it from voicemail, nor interacting with

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

Hello- Has anyone had experience connecting to a Marconi switch (in the UK) using E1-PRI connections (TE410P)? In a new installation, my customer is getting yellow alarms on every channel about every 30 seconds. These alarms clear themselves immediately and then re-occur in another 30 seconds, ad infinitum. I used the same configuration that I've used successfully in the past while talking

All good information, thanks. However this is private network between Asterisk and a Norstar MICS about six feet away. So I'm holding both 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

Hello, Quick Diagram: Telco-PRI -> Asterisk <- Norstar PRI -> Norstar PBX (DMS100) (TE405P) (DMS100) | | V Cisco 7960G (SIP) I'm trying to change the Origination Number on my outgoing PRI, and running into a weird problem. If I make a call from a SIP extension off asterisk using the following context:

Hi everyone, I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI (Megalink) circuit and having some trouble getting it to handshake. Thanks for any help or suggestions to diagnose this problem. The problem is that Asterisk has trouble bringing up the link. I see the following lines every couple of minutes: == Primary D-Channel on span 1 up == Primary D-Channel on

Dear all, Can someone help me about DTMF in ISDNPRI. I'm seting up E1 PRI found problem 90% Hangup when put digit. my E1 card work well with other telco. for this telco it's first time to use (telco in Thailand but i don;t know about equipment they use) I try to debug and got message below. Please let's me know if you can help Regards, Dome C.

At the same site, DTMF recognition is functioning badly, sometimes duplicating digits and sometimes totally missing others. We have checked already /proc/interrups, there is no interrupt being shared. Our zaptel has .. span=1,1,0,ccs,hdb3 On zapata we have ... switchtype=euroisdn signalling=pri_cpe relaxdtmf=no (yes doesn't seem to help) -----Original Message----- From:

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.

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

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

Hi, I dropped an asterisk server with a TE405P between a Norstar Meridian PBX and it's PRI PSTN connection. Everything seemed to work fine using a pass-thru-type dialplan configuration... except now we've realised that outbound calls to celphones get dropped upon connect, but not on every call (almost always the first try, but not the second). All other calls to non-celphones had no

So I reached the point where my PRI is accepting incoming calls, but I cannot dialout. I must be doing something stupid, but I can't figure it out. The Asterisk box is sitting between the Mitel and the phone company, and has PRI lines to each. Asterisk was built from CVS r1-0 Log for a call from mitel heading outbound: ------------------------- -- Accepting call from '' to

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"

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

I am having a problem with a new PRI turn-up on dahdi 2.5.0 and asterisk 1.8.5 that I have not seen before. The PRI is setup as B8ZS, ESF and the span shows up and ok. This PRI is merely a crossover T1 going into an old DC0 class 5 switch. I am getting the following errors over and over again [Aug 16 10:26:10] NOTICE[8002]: chan_dahdi.c:3043 my_handle_dchan_exception: PRI got event: HDLC Bad FCS

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

I am in the process of implementing a new ISDN pri and have a couple of questions. This is a full 24 channels (23 B and 1 D) delivered over a T1 interface. The interface looks good and is not showing any errors. Any help that you can provide would be greatly appreciated. 1) What switchtype should be configured in the zapata.conf file when AT&T is using CUSTOM? My understanding is that

Hi, I am about to pull my hair out after trying to get our PRI up and working. We are switching from a Cisco gateway to an Asterisk box which provides the 23 phone lines for our office. So, because the Cisco gateway is working I can assume I have all the settings right (b8zs, esf, dms100, etc) and the PRI is live (because we are switching over). When dialing from PSTN, I get busy signal. When