similar to: how to answer a Panasonic PBX extension with Asterisk?

Hi, Continuing with the saga of Digium vs MTNL Mumbai, looking for suggestions on handling incoming Caller-ID issues. The card manages to grab a couple of (random) digits of the incoming CID, but they're more or less useless. Is there any way to fix this? Asterisk 1.8.13, Dahdi 2.5.0.1 on Debian Testing (Wheezy), MTNL Mumbai. Digium, Inc. Wildcard AEX410 4-port analog card (PCI-Express)

hi all, i have an asterisk install with a digium 4 port fxo card and cisco 7960 sip phones -- running on a compaq Pentium III (Coppermine) at 800Mhz 256KB cache and 1GB of ram. when a call comes in on zap/1-1 for example, the delay between when zap sees the line going to ring state, and when the desktop telephone rings can be as long as 7000 milliseconds (or about 3 or 4 rings on an ear piece).

Hi all, I am seeing on my logs this message: Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 on channel 3 Jun 13 09:14:51 DEBUG[4944] chan_zap.c: Monitor doohicky got event Event 160 on channel 3 (repeated much more then what I will show here). I see that it comes from static void* do_monitor(void *data) in chan_zap.c, but I do not understand what does it

Hi everyone! I have a Digium Card TDM410 But, it appear for me this massege chan_dahdi.c:8061 handle_alarms: Detected alarm on channel 3: Red Alarm But my line is ok! But sometimes it back sig_analog.c:3807 analog_handle_init_event: Alarm cleared on channel 2 But it again back to red alarm. What can be happen? My lines is all ok! But when I put on Digium Card TDM410 is very inconsistent

Humm, if I put a filter in this lines, maybe back? 2016-01-05 12:36 GMT-02:00, Ryan, Travis <RyanT at oscarwinski.com>: > >> -----Original Message----- >> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users- >> bounces at lists.digium.com] On Behalf Of Vitor Mazuco >> Sent: Tuesday, January 05, 2016 9:21 AM >> To: Asterisk Users Mailing

hi,all i have just set up asterisk 1.6.0.7 rc1 with spandsp 0.0.5 pre4 to ReceiveFAX, link to a E1 (DE410P) using dahdi this can receive the fax from E1 successfully, but i see many error message in the log like this: [Mar 16 09:24:38] ERROR[23540] channel.c: ast_read() called with no recorded file descriptor. when i receive a 5 pages fax, i will see this error message over 200 lines..... it

Hi, I have a problem that is biting at all my customer sites where they have PRIs taking heavy load. This happens both with the stable code stream and with the current CVS. What happens is that after some running, Asterisk starts reporting strange errors on the PRI, eventually calling the PRI down Starts with this sort of thing: Feb 21 09:39:23 DEBUG[18095]: Didn't get a frame from

Upgrading an ancient customer installation... was running 1.4.23.1 (Trixbox) with Zaptel 1.4.12.9 and a Sangoma A102D, which has been running fine for 5+ years. Customer getting anxious about hardware failure, so we built a new box and installed 1.8.24.0, Dahdi 2.7.0.1, and a new Sangoma A104D. The single active span is an RBS T1 B8ZS/ESF/E&M Wink. I tried to move one span over one

Hi list, Just installed spandsp. In my limiting testing, I have an issue on a Philips fax machine (HFC21) directly connected to my * server through TDM400, reception with rxfax works fine, but txfax always fails. Below is a transcript of failed transmit. This is with asterisk-1.0.3 (with native moh patch but I don't think it is the source of the problem). I already tried libtiff 3.5.7,

In Asterisk 1.8, I used the following line in extensions.conf to allow me to pass "*82" in front of a dialed number, to disable the callerid block that's normally on that POTS line: ; disable callerid block exten => _*82.,1,Dial(${POTS}/${EXTEN}) But this seems to have stopped working when I upgraded to Asterisk 11.7. I get the following debug output, with a "no

The Asterisk Development Team would like to announce the release of asterisk-18.20.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/18.20.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-18.20.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/18.20.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-20.5.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/20.5.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-20.5.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/20.5.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

Hi all, I must admit that I am stuck. I have a TDM400P card with two FXS and two FXO modules which I had set up and configured so that it was working beautifully. The only problem was that occasionally it would get itself into a state where outgoing calls would simply be met with a very loud static. A reboot would fix this issue and everything would work fine for a while. Recently however,

Hello, CVS 07/31/03. Test with 130+ PSTN-to-SIP calls. Asterisk gets locked ... grep -e "Error" -e "eventually" p-console chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or resource busy chan_sip.c line 1453 (sip_alloc): Got it eventually... chan_sip.c line 1453 (sip_alloc): Error obtaining mutex: Device or resource busy chan_sip.c line 1453 (sip_alloc): Got

I have an extension defined like this: exten => do_monitor,1,Answer() exten => do_monitor,n,NoOp(Just got '${CfMC_ActionID}') exten => do_monitor,n,ChanSpy(${CfMC_WhoHear},qX) exten => do_monitor,n,Hangup() I use an AMI packet like this: Action: Originate Channel: Agent/1001 Exten: do_monitor Context: cfmc_cdi_private Priority: 1 Variable: CfMC_ActionID=callE1334 Variable:

The Asterisk Development Team would like to announce the release of Asterisk 18.19.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/18.19.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of Asterisk 18.19.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/18.19.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of Asterisk 20.4.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/20.4.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!