similar to: need a local tech

Hello, We are having issues with a NEW Sangoma A108D: -- Executing [691918892 at pbx1:1] Dial("SIP/xtravoip200-009d24b0", "DAHDI/g0/691918892|30|m") in new stack [Oct 1 10:04:43] WARNING[14171]: channel.c:3170 ast_request: No translator path exists for channel type DAHDI (native 76) to 256 [Oct 1 10:04:43] WARNING[14171]: app_dial.c:1237 dial_exec_full: Unable to create

Hi, Does anybody have an idea as to why dahdi_test results drop to unacceptable levels after doing a wanrouter stop/start using a Sangoma card? See below that it drops from 99.99% to 98.55%: [root at bin]# dahdi_test Opened pseudo dahdi interface, measuring accuracy... 99.999512% 99.992874% --- Results after 2 passes --- Best: 100.000 -- Worst: 99.993 -- Average: 99.996193, Difference:

Hi all I am using asterisk 11.24.1 on a centos 5 machine. kernel 2.6.18 flavor. (x86_64). I have about SIP 150 endpoints on it. when I send a message I'm getting garbled audio. I used to have a single PRI card in the box - but something happened and that connection no longer worked. I removed the card and also removed the system.conf and chan_dahdi entries. I am using ConfBridge in a PA

Hi, I have some servers that are dedicated to do meetme conferencing. From some previous test i concluded that I need to use dahdi_dummy as it is more accurate. If I did use the core timers in dahdi (not loading dahdi_dummy) I got bad quality in the conferences and dahdi_test showed 99.6% as worst. I thought maybe the issue as bad hardware for the timing or something else. But today I

Hi, I am running Fedora 7 VM. On an earlier configuration with zaptel and Asterisk 1.4.21 , meetme worked alright. I upgraded to Dahdi and Asterisk 1.4.26, and the result is choppy sound via Meeme, while a simple Musiconhold works OK with descent audio quality. So I am sure its a Dahdi_dummy problem. Running dahdi_test gave me very poor results. Opened pseudo dahdi interface, measuring

using asterisk 11.6.0-rc1 i just converted my "nat=yes" to "nat=auto_force_rport,auto_comedia" I have my asterisk box on the same subnet as a cisco 1760 (vgw1). a few times per day, Asterisk thinks vgw1 is dead (by qualify/options). A 'sip reload' always fixes the problem. i left 'sip set debug peer vgw1' on the console. but i dont see what's

I am trying to use SoftHangup in my dialplan, but it's either not working or I'm not using it correctly. when i'm on the console, i see: pbx1*CLI> core show channels Channel Location State Application(Data) SIP/vgw1-000000a2 2156181505 at inbound:1 Up AppDial((Outgoing Line)) SIP/143-0000009f s at macro-SaferSIPDial Up Dial(SIP/99302156181505 at vgw1,, 2 active

When I place an outbound call from asterisk 1.6.1.12 to a FXO port on my Cisco 1760V 12.4, the channel changes - seemingly incrementing: e.g., in the first call, below, the channel name is "SIP/vgw1-00000075" -- the second call (on the same FXO port after a soft hangup on the CLI) is "SIP/vgw1-00000077" How can I extract this information in the dialplan so that I can use

Hello, I have following problem with Sangoma A104 card: CLI> pri show span 1 Primary D-channel: 16 Status: Provisioned, Down, Active Switchtype: EuroISDN Type: CPE Window Length: 0/7 Sentrej: 0 SolicitFbit: 0 Retrans: 0 Busy: 0 Overlap Dial: 0 T200 Timer: 1000 T203 Timer: 10000 T305 Timer: 30000 T308 Timer: 4000 T313 Timer: 4000 N200 Counter: 3 NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI

I upgraded from a perfectly working 1.6.2 asterisk installation (including fax via app_fax_digium) to 1.8.0 this evening. All my custom modules (including swift <thanks darren!>) are working fine except for fax. When a caller connects, asterisk switches to the fax context and hangs up the call. i've captured with: core set verbose 10 core set debug 10 fax set debug on sip

I upgraded from Tormenta2 to Sangoma A101. I followed the instructions, and installation was successful. zttool, ztcfg, all show card is installed properly. I copied the parameters from my old working zaptel.conf, zapata.conf and zapata-auto.conf. Verified on Sangoma website that these files are correct. Also configured wanpipe1.conf. But doing all this didn't start the PRI channels. It says

I have used asterisk-1.4.14, zaptel-1.4.7, chan_ss7-1.0.0 on FC7 all went okay. using sangoma a104dx on both machine. I followed the write up on http://www.voip-info.org/wiki/index.php?page=Asterisk+ss7+setup I have the cross over cable between them. however, wanpipe shows connected but the signaling link does not align. i have my configs for host A ##wanpipe1.conf [devices] wanpipe1 =

Hi I wonder if anyone has any sugestions I have had a TDM400 for a couple of years, and I have always had problems with noise on the line, so tonight I have been doing some research and have found that if I load the CPU dahdi_test has almost perfect results and no noise dahdi_test Opened pseudo dahdi interface, measuring accuracy... 99.997% 99.999% 99.998% 99.997% 99.999% 99.998% 99.998%

Hey Guy, I have ubuntu 10.04 64bit and compiled dahdi / wanpipe 3.5.19 /asterisk-1.8.x I didn't understand what is the relation between wanpipe and dahdi ? do i need to start wanrouter service ? I am getting weird errors and my system got kernel panic many time when i restart dahdi service. any idea ? what is the startup sequence of all these service ? root at example:/etc/asterisk#

Trying to install wanpipe 3.5.18. No errors during compile. But when I reach the point where wanpipe and dahdi_cfg is started, I encountered an error. Starting WAN Router... Loading WAN drivers: wanpipe done. Starting up device: wanpipe1 wanconfig: WAN device wanpipe1 driver load failed !! : ioctl(wanpipe1,ROUTER_SETUP) failed: : 22 - Invalid

Hi, I've had problems with MixMonitor recordings. A lot (I'd say almost 50%) of those are corrupted (can`t be opened) or garbled. That is on only one server, which is using the same Asterisk version (1.6.2.18) as the other servers which are mostly fine. What can be the cause? The conversation themselves are reportedly of good quality, only the recording is a problem. Hint:

Hi all, My problem boils down to these errors: ... Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) == Everyone is busy/congested at this time This is triggered by lines in extentions.conf such as: exten => _X.,1,Dial(ZAP/g1/${EXTEN},,W) The system is CentOS v5.2 with Asterisk 1.4.23 (druid-asterisk-1.4.23.1-2), a Sangoma A104

Hi, I have a client who has a system with a Sangoma 1 port PRI card with echo canceling in it. For some reason, when the system comes up the PRI will stay up for about 4-5 hours, then drop. "zap show status" shows everything as ok, but we can't make or receive any calls until the system is rebooted. Just restarting asterisk does not fix the problem. I am going to call

Hi there, we have a problem with dahdi and overlapdial. We are running an E1 in Germany and are in need of overlapdial. The E1 is connected to a Sangoma A101. As soon as overlapdial is set to "yes" we have problems with incoming audio on the dahdi channels. When set to "no" all audio is fine. Basically we can choose between being able to receive calls or to place calls

Hi all, I've done this a few times with other PBX's but swyx has stumped me! I'm having some trouble getting Asterisk connected to a Swyx system using a sangoma A104dx... currently the setup is: BT <-> Swyx The above setup works fine... what i'm trying to achieve is BT & SIP Trunks <-> Asterisk <-> Swyx I have connected to our BT (2 x ISDN30 UK) with