similar to: Zap Outgoing

I noticed a problem this morning with our cdr logging. We have a cron job that places a call file into the spool directory having asterisk call itself to check to make sure its still handling incoming calls correctly, then queries the CDR database in mysql and makes sure that appropriate records exist. I can confirm that the call is happening correctly, but I'm missing records in the

I'm trying to use Jeremy's suggestion of dialling using just the peer name instead of user:pass@peer but I'm running into some really funky issues. It does the same thing with both VoicePulse and another * server I have. [voicepulse] type=peer host=gw5.voicepulse.com trunk=yes user=USERNAME pass=PASSWORD and in my dialplan: Dial(IAX2/voicepulse/${EXTEN:2}@VPWS,90,r) The log shows

Every so often, and it seems that it happens only when a call is in progress, all 24 Zap channels get reset. All channels are opened and then timeout. This causes the in-progress calls to terminate. There are no corresponding Red/Yellow alarms on wither the PBX or Asterisk although we do receive a fair amount of Blue Alarms. The Asterisk server is connected to a legacy PBX through a Digium

I have a problem that is probably so "doh" I will be embarrassed. However, I have spent all evening on this with no success: I have the following setup (asterisk cvshead as of today) 10 Channel EuroISDN<=>Asterisk<=>Meridian What I can do: Call from outside into the asterisk, dial an extension, and pass through to the meridian. WooHoo. What I can't do: Call from

Hello, When I receive calls in one FXO port (TDM400 or A200, occurs in both) and it dial to one invalid SIP extension, the call never hangup. The call would have to be dropped, but it seems that "Starting simple switch on 'Zap/1-1'" and "Hungup 'Zap/1-1'" occurs almost at the same time. If the dial is made to a valid SIP extension, the call is

Due to management concerns our asterisk system has been setup to record all phone calls for some time now (before the 1.0 release). Everything was working fine until we upgraded 1.0.5 where all calls are recorded except those that pass through a queue (we are not using the queue record functionality because there are some minor issues with using it in our scenario). Specifically, the

Calling out on PSTN over a TDM400P seems to generate a Red Alarm - whatever that is. I have another extension on the PSTN, and I can dial out over that. zttool shows no alarms. asterisk*CLI> zap show status Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO Wildcard TDM400P REV I Board 1 OK 0 0 0 CAS Unk YEL 0 db

Hi, I have installed a quadBri card, with Asterisk-1.0.10 and the bristuff-0.2.0-RC8s (* 1.0.10) When calling 0207654321 the following happens: -- Executing Goto("Zap/1-1 ", " salsa-helpdesk-day|s|1 ") in new stack -- Goto (salsa-helpdesk-day,s,1) -- Executing Dial ("Zap/1-1 ", "Zap/g1/0201234567|30 ") in new stack -- Requested transfer capability:

A call is placed via IAX2 from one asterisk to another, to a TDM400 channel whose extensions.conf entry is exten => 502,1,Dial(${COLIN}) exten => 502,2,Congestion If this channel is already busy when called, the call is instantly hungup, without the caller hearing the congestion tone. The log from the callers asterisk shows: -- Executing Dial("Zap/1-1",

On 1.2.x I have a random problem when a Zap/x channel flashes to transfer or make a three way call. The Zap/x-2 channel is created and the transfer or three way proceeds, but on hangup the Zap/x-1 channel fails to destroy the old bridge and asterisk goes crazy logging the problem. Here is an example debug log. This happens only once a day or so, with 100 or so users transfering and three

Hi, I'm trying to use ChanIsAvail to build a resilient 'dialout' macro. The logic is simple; try Zap/g1 (a group of two E1s), and if that fails, try locating a channel via DUNDi. Here's a massively cut down version to illustrate the problem I'm having. macro dialout ( dest ) { ChanIsAvail(Zap/g1); noop(Value of AVAILCHAN is ${AVAILCHAN});

Hi, A most peculiar and vexing problem for you all. I hope I have been verbose enough without being a firehose ;) The set up: I have a channel bank, using the r1t1 rhino driver with a rhino T1 card (the channel bank itself is a very legacy piece of equipment)- this supplies FXS for all the house phones. Also, a Wildcard TDM400P, using the wctdm module with 1 FXO module, this supplies FXO to the

Hi all, I have an Astribank connected to Asterisk 1.4. I'm setting up extensions and I have a problem with inbound calls to zap extensions. The phone at 65 rings once and then the line gets hung up. If I pick up the phone really fast, it works. Any suggestions? I have the following setup: [from-pstn] exten => 207582401,1,Dial(Zap/65,30) CLI shows me this: -- Accepting call from

I am installing one asterisk, to establish connection with my PABX Siemens, in ISDN, link went up normally, also I obtain to internally call the branches the PABX, normally, but when I try to dial for the PSTN, through pabx with the command exten = _ 19xxxxxxxx, 1, dial(zap/g2/${EXTEN}, 30) asterisk, reports me the following error: -- Executing Dial("SIP/8110-a729",

Ok, I've seen discussion before on doing transfers (attended and unattended), there seems to be much confusion over it. As things sit, I've been trying (unsuccessfully) to do transfers with a zap channel (analog phone attached to TDM400). I have no idea what I'm missing. My current understanding is that I need to have transfer=yes in zapata.conf, do a flash hook, dial the 2nd

All, I upgraded my asterisk setup from CVS on or about 12/15. Suddenly, *all* of my incoming calls are coming up as FAXes. I had to disable my fax extension because every call to my POTS line was getting redirected to my FAX machine. After removing the FAX extension, if I call my POTS line from my cell phone, I get the following: *CLI> -- Starting simple switch on 'Zap/1-1'

Hi, i was able to fix this problem when i added the line pridialplan=local in the zapata.conf but it depends on your telco, i think. marcus -----Urspr?ngliche Nachricht----- Von: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] Gesendet: Donnerstag, 6. April 2006 11:50 An: asterisk-users@lists.digium.com Betreff: [Asterisk-Users] Dial out on Zap Hi,

Hi, I'm trying to test my dial out function so I did something like this in extensions.conf exten => 999,1,Dial(Zap/g1/02601591) exten => 999,102,Congestion() My Zapata.conf looks something like this [channels] context=from-pstn group=0 switchtype=euroisdn overlapdial=yes faxdetect=no ; PRI port 1 (E1) ; context=1 group=1 signalling=pri_cpe channel=>1-15,17-31 I am able to

I'm trying the latest bri 0.1.0 RC2 drivers. In announce I see implementation of so long waited Transfer feature. But I can't make it work. When the person who is making transfer after talking with second party press "R" second time to establish 3 way call the person to which call supposed to be transfered being disconnected. Any ideas whats wrong? Thanks, Dmitry

I have a system with two 4 port T1 cards, with 5 PRI's configured. Each PRI is configured as an individual PRI and belongs to it's own group (groups 1-5) This system is handling roll-over from another system, where any error in processing the call on that system results in it being sent here. This mainly results in all calls resulting in a busy being sent for retry here. I then