similar to: Re: Asterisk-Users Digest, Vol 10, Issue 215

Hello All I'm using asterisk 1.1.X and MFCR2 lib version 0.03pre2. when i call to E1 (connected with asterisk), chan_unicall don't detected event incoming call and show error. error messages: *CLI> Warning, flexibel rate not heavily tested! Rx CAS bits 0x9 [ 10000/ 0/ 0] Line unblocked -- R2 Channel 4 unblocked Rx CAS bits 0x9 [ 10000/ 0/ 0] Line unblocked -- R2

Hello All Any body used sangoma card A101. I have problem with this card. My system are: Linux Redhat 8.0. asterisk 1.07 and libpri, zaptel,... i connected E1 and MF/R2 signalling. i configure HDLC and TDM Voice. this is my configure as belows: #================================================ # WANPIPE1 Configuration File #================================================ # # Date: Sun May

Hi All I have problem with LIBMFCR2 for once Exchange I using Sangoma card, the firstly. my ssystem run successful with MFCR2, connected to E10 (Acatel Exchange), after that, i move connection connect to EWSD (Siemens), my system don't work. error protocol R2. my system: Asterisk CVS 1.1.X LibMFCR2 pre.005 and unicall-pre.005 this's my setting and my setting wanpipe1.conf

I'm using Asterisk 1.4.5 (will try 1.4.6 on Thursday, but I don't see anything in the changelog after the 1.4.5 release dealing with distinctive ring), zaptel 1.4.3, and wanpipe 2.3.4-10 with a Sangoma A200 card. I enabled usedistinctiveringdetection in zapata.conf. However, on the Asterisk console, the output I get is: -- Detected ring pattern: 0,0,0 It would appear that Asterisk is

Hi, after many issues we finally managed to make our system do outgoing calls with perfect quality. However I cannot detect *any* form of incoming call. when I use an outside phone to call the E1 connected to the sangoma a102, I instantly get a fast busy tone. My /etc/zaptel.conf is: loadzone=us defaultzone=us #Sangoma A102 port 1 [slot:1 bus:4 span: 1] span=1,0,0,ccs,hdb3 bchan=1-15,17-31

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 =

I am having a problem trying to get a Sangoma A101 to work with Unicall. I have installed the sangoma drivers and everything seems to be well but when I try to run ztcfg I get the following error: CAS signalling on span 1 conflicts with HDLC with FCS check on channel 16. Here is my /etc/zaptel.conf # MFC/R2 normalmente no usa CRC4 span=1,0,0,cas,hdb3 cas=1-15:1101 dchan=16 cas=17-31:1101

Do you have any extension in default context of your extensions.conf file to accept incoming calls ? It must be something like; exten => 12345678,1,Answer() exten => 12345678,2,Playback(Welcome) ... 12345678 = The DID number you are calling to reach E1 Idris -----Original Message----- From: Erick Perez [mailto:eaperezh at gmail.com] Sent: Thursday, July 26, 2007 7:03 AM To:

Hello, We have an Asterisk 1.0.9 machine with a Sangoma A101 card fitted, it is connected to a Telstra OnRamp E1 in Melbourne, Australia. The problem we are experiencing is extreme echo and clicking noises. These are only audible to the calling party, e.g. the person calling in from the PSTN to Asterisk via the E1, the person on the SIP handset cannot hear any echo or clicking, only the

I've replaced 2XTE110 with an A102 with echo cancellation specifically to deal with echo problems. However, user feedback has indicated to me that on some calls (not a lot, but some) the call is unusable, with audio artifiacts, described by one user, as: "very bad phasing reverb & feedback (from my rock & roll days)". This is quite intermittent, as in most cases, the user

Hi, I am trying to validate a setup with a sangoma A116 card (16PRI in one card). I currently have two machines set up, each with a sangoma A116 card. Those are interconnected with crossed PRI cables. One of them is in NT mode, the other in TE. The ports are configured in E1 mode, asterisk is all set up and I can make calls between them, filling up all 480 (16 * 30) channels. Now, I learned

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

Hi Folks, I'm have Asterisk version 1.2.1 with a A101 PRI card. I'm working with the CLEC to bring up the PRI and inbound calls are hanging up at his end after a few seconds. I ran PRI debug but it only gives me minimal insight. " Ext: 1 Cause: Unknown (16), class = Normal Event (1)" He ran a trace and the only difference he is seeing is a "ISDN interface explicitly

Hi all, Can somebody help me out, to get the call going through to my provider? I connected my A104D Sangoma card to E1/isdn and each I tried to make call I get the errors below. My protocol analyzer can see only setup info and release complete. WIRELESS2*CLI> set debug 9 Core debug was 0 and is now 9 WIRELESS2*CLI> pri intense debug span 1 Enabled EXTENSIVE debugging on span 1 T203

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 a problem with a Sangoma card. It worked until yesterday. Now I keep getting this error: Jul 29 17:45:17 pbxacura kernel: wanpipe1: Enable E1 CAS signalling mode! Jul 29 17:45:17 pbxacura kernel: wanpipe1:w1g1: Rx Error: No 'DeviceSelect' from target: pci fatal error! (0x000FA000) Jul 29 17:45:48 pbxacura last message repeated 30946 times It is using Wanpipe 3.5.6 and Zaptel

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

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#

Hi, executing the reload command on Asterisk make the Unicall channel unblock all Unicall channels dropping active calls. Is this just a local error (maybe in the other end of my E1 ?), an option in the source (maybe a debugging option ?) or it must be this way ? Asterisk: 1.0.9 unicall: 0.0.3-pre4 protocolvariant: br Thanks, Leonardo Aug 31 15:00:55 WARNING[28411]: Already have a