search for: pcislots

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 =

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

On 02/12/2018 03:27 PM, Gerd Hoffmann wrote: > On Mon, Feb 12, 2018 at 03:00:24PM +0100, Tomeu Vizoso wrote: >> On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: >>> Hi, >>> >>>> can we reach agreement on whether vsock should be involved in this? >>> >>> I think the best approach would be to have guest proxy and host proxy >>> use

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

On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: > Hi, > >> can we reach agreement on whether vsock should be involved in this? > > I think the best approach would be to have guest proxy and host proxy > use vsock for the wayland protocol. Use a wayland protocol extension to > reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two > proxies need to

On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: > Hi, > >> can we reach agreement on whether vsock should be involved in this? > > I think the best approach would be to have guest proxy and host proxy > use vsock for the wayland protocol. Use a wayland protocol extension to > reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two > proxies need to

I have a system that I am trying to get a port on a Sangoma A104d card connected to an Adtran 850 with 5 FXS modules and 1 FXO module. A problem I am having is figuring out what cable should be used from the port on the Sangoma to the JP2 port on the Adtran. Tried was a cross-over T1 (1->4, 2->5, 4->1, 5->2) as well as a straight T1 (1->1, 2->2, 4->4, 5->5). Neither one

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, Please post any comments or questions if you get around to testing them. Your comments are very welcome! Best regards, -Gonglei > > >>> On 22.10.13 at 06:08, "Gonglei (Arei)" <arei.gonglei@huawei.com> > wrote: > > > Hi, guys. The new patch has been modified based on the principles you > > > suggested, thank you so much. > > >

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:

I have a hardware here with 9 NICs (8 of them on-board) and I want to set up 8 NICs as real network interfaces, one for each xen domain. The 9th NIC should be Domain-0 which is working well. Currently I have only set up one domain which is running in bridged mode at the moment. I am currently trying to set up a second domain which uses eth2 but I didn''t succeed. I want to get the

On Mon, Feb 12, 2018 at 03:00:24PM +0100, Tomeu Vizoso wrote: > On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: > > Hi, > > > > > can we reach agreement on whether vsock should be involved in this? > > > > I think the best approach would be to have guest proxy and host proxy > > use vsock for the wayland protocol. Use a wayland protocol extension to

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

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 i'm using sangoma card. connected to E1, my wanpipe file as #================================================ # WANPIPE1 Configuration File #================================================ # # Date: Fri May 27 00:25:04 GMT+7 2005 # # Note: This file was generated automatically # by /usr/sbin/wancfg program. # # If you want to edit this file, it is # recommended