similar to: Problem with new sipura firmware 1.0.35a

Displaying 20 results from an estimated 10000 matches similar to: "Problem with new sipura firmware 1.0.35a"

2004 Apr 09
9
small linux distro to run * in old boxes
Has anybody tried to install * in any of these minimalist linux distros like tinylinux? Which linux distro would you use to run * in old P2, P3 boxes? Regards, Victor Perez vperez@mssco.com (469) 221-4189
2004 Dec 15
1
Sipura 2000 intermitent failure to register
I have asterisk 1.0.2 and a Sipura SPA-2000 (firmware 2.0.6(c) ). Today it started to log "registration failed" at intermitent periods. It registers fine, after a few minutes it can no longer register, then after a few minutes it registers fine again. I am wondering if there is a known issue with either asterisk or that sipura firmware. Victor Perez
2004 Mar 16
4
Sipura line 1 outgoing voice problem?
Back in January I started having a problem with my Sipura (and there was at least one other on the list with the same problem) that if I answer an incoming call (via X100P) on line 1 of my Sipura, the caller cannot hear any voice from the internal extension. If the internal user puts the external user on hold (via flash hook) and returns, both directions of audio are fine. Line 2 never has
2004 Apr 15
2
too many arguments to function `ast_queue_hangup' compiling asterisk-oh323
when trying to build asterisk-oh323 I get the following: make[1]: Entering directory `/usr/src/asterisk-oh323-0.5.10/asterisk-driver' gcc -Wall -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declara tions -D_REENTRANT -D_GNU_SOURCE -I/usr/src/asterisk/include -I../wrapper -g -c -o chan_oh323.o chan_oh323.c chan_oh323.c:
2004 Apr 09
0
wcfxo module fail to load (Unable to request IRQ 0)
Hello, just compiled zaptel in mandrake 9.2 and this is what I get when trying modprobe wcfxo: Apr 9 11:35:15 localhost kernel: PCI: No IRQ known for interrupt pin A of devic e 00:05.0. Please try using pci=biosirq. Apr 9 11:35:15 localhost kernel: Setting hook state to 0 (08) Apr 9 11:35:15 localhost kernel: Registered Span 1
2003 Dec 10
4
Sipura SPA2000 & Asterisk & latest firmware (1.0.18)
All, If you currently own a Sipura SPA2000, avoid going to the sipura website and upgrading the firmware. I upgraded my SPA2k a couple of days ago from 1.0.9 (what it came with) to 1.0.18 off the site, and I am having issues with my SPA rebooting itself every 3-10 minutes for no apparent reason. I have been in touch with the *excellent* sipura support folks, and they are working with me to
2007 Jan 16
2
force ulaw passthrough if call from modem extension?
I have Teliax trunk set to ulaw and g729 and I have a modem/fax extension from a sipura forced to ulaw. When the call goes out through Teliax IAX trunk, asterisk transcodes to g729. Is there a way to tell asterisk not to transcode calls from/to a specific extension? I'm running asterisk 1.2.4 and that extension is for my home alarm/dish network and fax calls. Thanks -------------- next part
2011 Jun 21
1
Looking for Sipura-2000 Latest Firmware
Dear Asterisk Users, I have a Sipura 2000 device, and since last few days I have been searching for its latest firmware for upgrade. Googling tells me that Cisco has stopped the support for this device and I dont have definite idea on where would I be able to find the firmware to upgrade my device. Any help in regards to getting the firmware will be helpful. Regards, Amol -------------- next part
2004 Apr 26
1
new sipura firmware
Hello, Has anyone had any good or bad experiences with the new Sipura 2.0 firmware? The 1.0.33 works pretty well but there are a few more features I'd like to have. Regards, Christopher J. Wolff, VP CIO Broadband Laboratories, Inc. http://www.bblabs.com
2005 May 10
4
SIPURA SPA-2000 webserver dead after firmware upgrade
I just got a refurb Sipura SPA-2000 and was able to assign it an IP address with DHCP and ping the device, but then I ran the firmware upgrade utility to bring it up to spa2k-2.0.13g which seemed to work just fine, but after it rebooted I cannot connect to its webserver for configuration. I can still ping the unit. When I use the built in voice menu it reads back the right IP address, webserver
2005 May 31
2
Sipura 2000 behind NAT issue, Vonage is working
Hi, I'm trying to configure Sipura 2000 (behind NAT) which connects to Asterisk (public IP, no NAT) and having interesting results. When Sipura is behind Linux/NAT firewall it works great and no special NAT settings on Sipura are necessary. The issue I'm having is when Sipura is behind Linksys broadband NAT router. Sipura gets registered with Asterisk just fine, but I can't hear
2004 Jan 08
3
Asterisk & Sipura 2000
I have been trying to read everything I can find on Sipura 2000 and Asterisk. I am trying to make the Sipura-2000 act as two analog lines off my asterisk. I have followed (what I believe) the example on http://www.voxilla.com/Article39.phtml and I still can't get my Sipura to register with my Asterisk server. I can re-config my Sipura to talk to fwd, or voice-pulse connect and it works
2005 Jun 16
2
Multiple Sipura 3000
If I have multiple Sipura 3000 device how can I dial out properly? I can receive call without any problem and that's working really well. Caller ID is shown and when someone call he get's the welcome message the same way I have it configure with the X100P card. I don't seem to have any echo problem with the Sipura 3000 (but I do with X100P cards) My main concern is for
2004 Sep 30
3
Sipura-3000 - silent dial out on FXO port
I am trying to configure the FXO port on a Sipura-3000 for use with Asterisk. When I connect to the Sipura to dial out on the PSTN line connected to the Sipura's FXO port, it gives me the dialtone of the PSTN line and then I can hear the DTMF for the number I dialled beforehand. It does work but the customer perceives this delayed second DTMF feedback as "unprofessional" and the
2004 May 22
1
Re: Sipura and STUN (was: rejected NOTIFY re quests)
Sipura does include STUN as an option. It has for quite some time. We are using it with all of our Sipuras behind NAT'd gateways and it works great! Try upgrading to the latest Sipura firmware rev. Darren Nay > -----Original Message----- > From: John Todd [mailto:jtodd@loligo.com] > Sent: Saturday, May 22, 2004 1:57 PM > To: asterisk-users@lists.digium.com > Subject:
2008 Apr 29
1
Annoying Sipura problem?
This may not be the right place to ask, but I have an annoying issue with a Sipura/SPA1000-2.0.10(e) ATA device connected to an Asterisk box. (The system is remote to me, so I've only been able to observe this by dialling into a VoIP phone on-site, then run commands on the box remotely!) First of all it's all working fine connected to an Asterisk box and the user can make/take calls
2005 Sep 29
3
Problems using SIPURA and MFC/R2
We are using MFC/R2 driver successfully in at least three places in Brazil. I have problem with an Asterisk integrated with MFC/R2 with a Siemens Hicom 300. I can get a good audio quality with Grandstream, Polycom, and X-Lite softfones, but SIPURAS and Linksys get a garbled audio, something like a "Darth Vader" voice. We have tried everything in Sipura. The SIPURA 2000 and the Linksys
2005 Sep 10
1
Configuring SIPURA 2002 to work wih Asterisk
I'm setting up Asterisk for the first time. I purchased a SIPURA 2002 ATA to connect with the Asterisk server. In the /var/log/asterisk/messages log I keep getting an error indicating wrong password. Below is the error I am receiving. Note that the IP address and username has been modified for security. Sep 10 15:56:22 NOTICE[24099] chan_sip.c: Registration from 'John Doe
2004 May 22
1
Re: Sipura and STUN (was: rejected NOTIFY requests)
At 7:36 PM +0200 on 5/22/04, Olle E. Johansson wrote: >>[snip] >Sending NOTIFY to Asterisk is an error, but a workaround. Since Asterisk >can handled the NAT traversal all by itself with Qualify (as John points >out) disabling the NOTIFY will not change anything. > >The NOTIFY will in no way affect the status - unreachable/reachable. > >Another problem with the SIPURA is
2005 Jun 02
2
asterisk sipura and g726 codec
With sipura (I tried this with both the 3000 and 841) set to prefer the g726-32 codec, a call from the sipura to asterisk will use g726. Asterisk sip.conf has: disallow=all allow=g726 allow=gsm allow=alaw When the call is from asterisk to the sipura, asterisk will not use g726. It ends up using alaw. I usually use stable but I tried this with head too, and same thing happens. Anybody know how