Sipura 3000 Firmware



3000

  1. Sipura 3000 Firmware List
  2. Sipura Spa-3000 Firmware

Sipura SPA-1001: Sipura SPA-3000: Note: The SPA-1000, SPA1001, SPA-2000, & SPA-3000 use the same firmware. The problem with Firmware for these things started when Sipura sold out to Cisco. Cisco keeps all Firmware close to the heart and it's darn near impossible to find it on any of Cisco's sites.

LinkSys (who bought out Sipura) have released version 3.1.18 of the firmware for their SPA-3000 analogue telephone adapter. The comments in reply to my post on Whirlpool seem to indicate that this improves quality and reduces echo. I've just updated my box, so it will be interested to see if any difference is noted. Download Sipura VoIP Dial Plan Tester for free. Dial plan tester/manager for Sipura 3000 Voice Over IP (VoIP) devices. Validates the dial plan syntax, preconfigured test templates of numbers to test (e.g.

Sipura (3000) does not register with V23 (any version)

Firmware
DD-WRT Forum Forum Index ->Broadcom SoC based Hardware

Sipura 3000 Firmware List

View previous topic :: View next topic
AuthorMessage
bloukos
DD-WRT Novice
Joined: 10 Jun 2006
Posts: 3
Location: Athens, Greece
Posted: Sat Sep 09, 2006 11:42 Post subject: Sipura (3000) does not register with V23 (any version)
Hello,
After trying with several versions of V23 (including SP1, SP2) the Sipura SPA-3000 does not register with my VoIP service. I am currently using V22 final with which it works with no problems.
With V23, I've tried changing several options to debug (disabled firewall, opened ports which I normally not need, put ATA in DMZ, enabled/disabled QoS) with no success. Enabling syslog, I get lots of 'ip_mangle_packet' messages (or something like that).
I remember others have reported similar problems. I've tried altering my configuration on the ATA again with no success.
Anyone with a solution?
Thanks in advance,
Alex.
_________________
Alexandros Bagos
Sponsor
<=' td='>
xciton
DD-WRT User
Joined: 07 Jun 2006
Posts: 50

Posted: Mon Sep 11, 2006 21:18 Post subject:
The SPA-3000 works for me no problems (dd-wrt vpn 08/30/06).
Make sure there are no other sip devices on your network (that perhaps are using port 5060 as well)
Are you sure you're not using the voip version of dd-wrt?
Also, you should be using a outside STUN server to let the SPA-3000 discover what ports it has available to use.
dino2006
DD-WRT Novice
Joined: 19 Jun 2006
Posts: 7

Posted: Tue Sep 12, 2006 6:55 Post subject:
I couldn't get it to work with 2.3 without changing the SIP port, worked fine with 2.2. This was with the non VOIP firmware.
pixeljuice
DD-WRT Novice
Joined: 21 Sep 2006
Posts: 14

Posted: Sat Sep 23, 2006 14:03 Post subject:
I was having the same issue. I have a SPA3000 and a Cisco ATA 188 - both were working great sitting behind my router (previously with Alchemy firmware) and connecting to my external Asterisk server. Once I upgraded to DD-WRT v23.sp2 my SPA3000 stopped working properly - it did register fine and I could receive and make calls - but I would get no sound in or out, not even the ringing tone (i.e. I noticed on my Asterisk that the call is established and the person I called got a call from me - but I couldn't hear nor be heard). My Cisco ATA phone worked just as usual.
I made sure my port forwarding was identical to the alchemy (I obviously reset the setting when upgrading and manually entered them again), and nothing else changed.
I tried several things, disabling Qos, enabling / disabling port forwarding etc... The only solution I managed was to change the ports from 5060 to something else both on the Cisco ATA (changed to 5062) and on SPA 3000 (under Line1 - changed to 5064 and PSTN Line to 5066).
Really strange but at least now it works. I wonder why DD-WRT doesn't like port 5060
pixeljuice
DD-WRT Novice
Joined: 21 Sep 2006
Posts: 14

Posted: Sat Sep 23, 2006 15:48 Post subject:
Perhaps I was too quick to be happy... For some bizarre reason after a while (can't exactly say how long, but probably less than 10 minutes), it goes back to the way it was before - i.e. no ringing tone / audio but call is taking place and registration+progress on asterisk looks ok.
The funny thing - changing the ports again (say to 5068) would make it work, but then changing back (to 5066) wouldn't. I tried restarting the SPA3000, Asterisk box and DD-WRT but nothing seems to help. It's as if those ports are marked as unusable somewhere - or am I simply missing something out??
I ended up changing both PSTN and Line1 ports to 5065 and it is working for about 30 minutes now... will wait and see if the situation changes (perhaps something to do with re-registering with the asterisk box? Although changing the ports should initiate a re-registerion anyway...)
xciton
DD-WRT User
Joined: 07 Jun 2006
Posts: 50

Posted: Sat Sep 23, 2006 16:42 Post subject:
Have you guys configured your ATA's for STUN? It's under the SIP tab, near the very bottom. You can use 'stun.fwdnet.net' and enable both the 'Test' and 'Enable' settings.
If that doesn't work, you should probably read up one of the following forums:
http://forum.voxilla.com/
http://www.dslreports.com/forum/voip
http://forums.whirlpool.net.au/forum-threads.cfm?f=107
pixeljuice
DD-WRT Novice
Joined: 21 Sep 2006
Posts: 14

Posted: Sat Sep 23, 2006 23:22 Post subject:
I didn't have STUN configured originally because I had port forwarding in place, but I added the STUN settings just in case. Still - it doesn't explain how come some ports seem to work and others don't even when port forwarding is in place properly, and also how come it did work just fine when using a different firmware?
A few hours later my spa3000 seems to still work fine with port 5065 set to both PSTN and line1... I wonder if it would though changing back to (say) port 5060
bloukos
DD-WRT Novice
Joined: 10 Jun 2006
Posts: 3
Location: Athens, Greece
Posted: Tue Sep 26, 2006 5:33 Post subject:
I have STUN enabled anyway. The same configuration on the Sipura that works with V.22, doesn't work with V.23. I remember a similar behavior when changing ports, but eventually that didn't work for me either.
_________________
Alexandros Bagos
airton
DD-WRT Novice
Joined: 05 Oct 2006
Posts: 5

Posted: Thu Oct 05, 2006 8:15 Post subject: SIP error 479 (We dont accept private IP contacts)
I'm trying dd-wrt v23 SP2 on WRT54GL (i'm interested in QOS for better voice quality).
Problem: my ATA cannot register on SIP registrar (error 479). My configuration:
ADSL - IP public dynamic
|
|
MODEM/ROUTER Netgear DG834, NAT enabled, DMZ on 192.168.1.1
| IP 192.168.1.254
|
| IP 192.168.1.1
WRT54GL dd-wrt v23 SP2, port used by SIP/RTP forwarded on 192.168.0.253, no QOS enabled
| IP 192.168.0.254
|
| IP 192.168.0.253
ATA HT-496 grandstream, gateway 192.168.0.254
|
|
Phone
I read ATA's log and i think dd-wrt re-write IP address in SIP message header putting 192.168.1.1 (its internet IP address) and overwriting the real public IP address discovered by ATA (using STUN).
If i exclude WRT54GL everything work.
Any idea to solve this serious problem?
downgrade to v22?
Return to thibor15c firmware?
Thanks.
BrainSlayer
Site Admin
Joined: 06 Jun 2006
Posts: 7031
Location: Dresden, Germany
Posted: Fri Oct 06, 2006 13:45 Post subject:
dd-wrt rewrites it only using sipath. if you dont want this. dont use the voip version
_________________
'So you tried to use the computer and it started smoking? Sounds like a Mac to me..' - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
airton
DD-WRT Novice
Joined: 05 Oct 2006
Posts: 5

Posted: Fri Oct 06, 2006 14:32 Post subject:
BrainSlayer wrote:
dd-wrt rewrites it only using sipath. if you dont want this. dont use the voip version

more info...
The SIP error 479 is reported using mini or standard version and Grandstream ATA or SJ-phone and using STUN (with dd-wrt v23sp2 in gateway or router mode).
Instead X-lite (with STUN) works.
Everything work using linksys firmware v4.30.5.
Perhaps dd-wrt v23sp2 is not fully sip-enabled or has some bug...
airton
DD-WRT Novice
Joined: 05 Oct 2006
Posts: 5

Posted: Mon Oct 09, 2006 22:01 Post subject: More test about sip register failure
I make some other test to collect more info:
Configuration:
------------------------------------------------------------
ADSL Modem/Router
- public IP address: 81.174.xxx.yyy
- LAN IP Address: 192.168.0.254
- NAT enabled
- static route 192.168.1.0/255.255.255.0 to 192.168.0.100
DD-WRT Router (v23 sp2 - mini)
- internet port IP Address: 192.168.0.100
- internet gateway: 192.168.0.254
- LAN IP Address: 192.168.1.254
- Mode: Gateway/Router
- IP packets captured with tcpdump
SIP Client (pjsua) on LAN PC
- IP Address: 192.168.1.10
- stun enabled: stun.fwdnet.net
Results
------------------------------------------------------------
[1] - capture at br0 (LAN) of ddwrt - ddwrt Mode Gateway
/tmp # /tmp/tcpdump -v -n -s 0 -i br0
23:20:53.916949 IP (tos 0x0, ttl 128, id 24931, offset 0, flags [none], proto: UDP (17), length: 105) 192.168.1.10.5060 > 195.62.aaa.bbb.5060: SIP, length: 458
REGISTER sip:myvoip.provider.it SIP/2.0
Via: SIP/2.0/UDP 81.174.xxx.yyy:5060;rport;branch=z9hG4bKPj91c11ffd21c24bb69f405c6481f5e6c4
Max-Forwards: 70
From: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=83ba2fc693eb412187b16d95246d5e3c
To: <sip:nnnnnnnnnn@myvoip.provider.it>
Call-ID: 43d26f1580384fe09e7845a653cc4905
CSeq: 48445 REGISTER
Contact: <sip:nnnnnnnnnn@81.174.xxx.yyy:5060;transport=UDP>
Expires: 55
User-Agent: PJSUA v0.5.8/win32
Content-Length: 0
23:21:14.787209 IP (tos 0x10, ttl 53, id 0, offset 0, flags [DF], proto: UDP (17), length: 660) 195.62.aaa.bbb.5060 > 192.168.1.10.5060: SIP, length: 632
SIP/2.0 479 Please don't use private IP addresses
Via: SIP/2.0/UDP 192.168.0.100:5060;rport=1026;branch=z9hG4bKPj91c11ffd21c24bb69f405c6481f5e6c4;received=81.174.xxx.yyy
From: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=83ba2fc693eb412187b16d95246d5e3c
To: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=88f80658fec2aee552096ea46e92568d.1d0a
Call-ID: 43d26f1580384fe09e7845a653cc4905
CSeq: 48445 REGISTER
Server: SPS01EUT(0.9.6 (i386/linux))
Content-Length: 0
Warning: 392 195.62.aaa.bbb:5060 'Noisy feedback tells: pid=16917 req_src_ip=81.174.xxx.yyy req_src_port=1026 in_uri=sip:myvoip.provider.it out_uri=sip:myvoip.provider.it via_cnt1'
[2] - capture at vlan1 (WAN) of ddwrt - ddwrt Mode Gateway
/tmp # /tmp/tcpdump -v -n -s 0 -i vlan1 not port 22
23:19:01.993106 IP (tos 0x0, ttl 127, id 24925, offset 0, flags [none], proto: UDP (17), length: 486) 192.168.0.100.5060 > 195.62.aaa.bbb.5060: SIP, length: 458
REGISTER sip:myvoip.provider.it SIP/2.0
Via: SIP/2.0/UDP 192.168.0.100:5060;rport;branch=z9hG4bKPjc1611ca4848245d49f33af9148cd4427
Max-Forwards: 70
From: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=abf5c595befb447e994d0816ce46705d
To: <sip:nnnnnnnnnn@myvoip.provider.it>
Call-ID: 5ef6f995d301458aa1a654f2a26ebaa8
CSeq: 34757 REGISTER
Contact: <sip:nnnnnnnnnn@192.168.0.100:5060;transport=UDP>
Expires: 55
User-Agent: PJSUA v0.5.8/win32
Content-Length: 0
23:19:02.035392 IP (tos 0x10, ttl 54, id 0, offset 0, flags [DF], proto: UDP (17), length: 660) 195.62.aaa.bbb.5060 > 192.168.0.100.5060: SIP, length: 632
SIP/2.0 479 Please don't use private IP addresses
Via: SIP/2.0/UDP 192.168.0.100:5060;rport=1026;branch=z9hG4bKPjc1611ca4848245d49f33af9148cd4427;received=81.174.xxx.yyy
From: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=abf5c595befb447e994d0816ce46705d
To: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=88f80658fec2aee552096ea46e92568d.716c
Call-ID: 5ef6f995d301458aa1a654f2a26ebaa8
CSeq: 34757 REGISTER
Server: SPS01EUT(0.9.6 (i386/linux))
Content-Length: 0
Warning: 392 195.62.aaa.bbb:5060 'Noisy feedback tells: pid=16913 req_src_ip=81.174.xxx.yyy req_src_port=1026 in_uri=sip:myvoip.provider.it out_uri=sip:myvoip.provider.it via_cnt1'
[3] - capture at vlan1 (WAN) of ddwrt - ddwrt Mode Router (OSPF)
/tmp # /tmp/tcpdump -v -n -s 0 -i vlan1 not port 22
23:36:22.266045 IP (tos 0x0, ttl 127, id 25775, offset 0, flags [none], proto: UDP (17), length: 484) 192.168.1.10.5060 > 195.62.aaa.bbb.5060: SIP, length: 456
REGISTER sip:myvoip.provider.it SIP/2.0
Via: SIP/2.0/UDP 192.168.1.10:5060;rport;branch=z9hG4bKPj880f72c9787846f3843a8a42753cee04
Max-Forwards: 70
From: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=743e99908e074fc7ac2ca4f0c411f607
To: <sip:nnnnnnnnnn@myvoip.provider.it>
Call-ID: d2c6d30219234f9ebd6ca4288c9a95af
CSeq: 39616 REGISTER
Contact: <sip:nnnnnnnnnn@192.168.1.10:5060;transport=UDP>
Expires: 55
User-Agent: PJSUA v0.5.8/win32
Content-Length: 0
23:36:22.309328 IP (tos 0x10, ttl 54, id 0, offset 0, flags [DF], proto: UDP (17), length: 659) 195.62.aaa.bbb.5060 > 192.168.1.10.5060: SIP, length: 631
SIP/2.0 479 Please don't use private IP addresses
Via: SIP/2.0/UDP 192.168.1.10:5060;rport=1026;branch=z9hG4bKPj880f72c9787846f3843a8a42753cee04;received=81.174.22.179
From: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=743e99908e074fc7ac2ca4f0c411f607
To: <sip:nnnnnnnnnn@myvoip.provider.it>;tag=88f80658fec2aee552096ea46e92568d.3486
Call-ID: d2c6d30219234f9ebd6ca4288c9a95af
CSeq: 39616 REGISTER
Server: SPS01EUT(0.9.6 (i386/linux))
Content-Length: 0
Warning: 392 195.62.aaa.bbb:5060 'Noisy feedback tells: pid=16917 req_src_ip=81.174.22.179 req_src_port=1026 in_uri=sip:myvoip.provider.it out_uri=sip:myvoip.provider.it via_cnt1'
Comments
------------------------------------------------------------
1. SIP REGISTER message captured on ddwrt LAN interface (result [1]) has header Via: SIP/2.0/UDP 81.174.xxx.yyy:5060. The internet public IP address discovered by stun is present, but the registrar answer with 'SIP/2.0 479 Please don't use private IP addresses'...
2. In fact the same SIP REGISTER message captured on ddwrt WAN interface (result [2]) has header Via: SIP/2.0/UDP 192.168.0.100:5060. The internet public IP address has been replaced with ddwrt WAP IP (ddwrt is working as gateway)
3. And the same SIP REGISTER message captured on ddwrt WAN interface (result [3]) has header Via: SIP/2.0/UDP 192.168.1.10:5060 (SIP client IP) if ddwrt is working as router (doesn't perform NAT)
It's clear ddwrt rewrite IP address in SIP headers!!!
I think this is a bug!
bye, Airton.
paped
DD-WRT Novice
Joined: 10 Oct 2006
Posts: 11
Location: UK
Posted: Thu Oct 12, 2006 12:48 Post subject:
This worked for me with a WRT54GL, SPA3000 and using sipgate on port 5060 might help you but can't promise......
Make sure that you are using any version of DD-wrt other then the VoIP one.... I use the standard version
Set-up STUN on your sipura but ensure that the stun test option is off...
Set-up port forwards for stun (speak to your voip supplier for the port number), sip (port 5060 normally) and RTP (port 5004 normally) also setup a port range forward for your voice ports that are used, on my sipura it was something like ports 16384 to 16482. All forwarding to your sipura's IP address.
Then the key one that I found was on your QOS settings, set both the upload and download speeds to around 75 to 78% of the connection speeds. Then power cycle your sipura and wrt54 for the QOS setting to pickup, do not soft reboot the unit as I have notice that sometimes this seem to screw up QOS on mine.
The stun and port forwards seem to get over various f/w issues with voip and by changing the QOS setting on my 1mbps adsl connection it seem to allow the connection/registration to take place....
Hope this helps.....
tk
DD-WRT Novice
Joined: 05 Jul 2006
Posts: 19

Posted: Thu Oct 19, 2006 5:03 Post subject:
I have the same issue with the v23sp2. In addition when I go to the SIPatH tab on my router and select phone book or status sub-tab the router freezes. Well, not quite: it appears that connections opened before clicking on the tab continue to run, but I can't open any new connections and the router does not display any web interface, i.e. the SIPatH phone book and status pages never load and I can't load any other page.
v22 allowed registrations with no problems and I don't recall freezing issues per se. Although I do have to admit that clicking on those pages made the router awfully slow for a minute or so until the pages loaded. Looks like a very possible bug that is somehow exaggerated by the new version.
DD-WRT Forum Forum Index ->Broadcom SoC based HardwareAll times are GMT

Navigation

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum

spaconf is a tool which can be used with an analog phone adapter (ATA) such as the Sipura SPA 3000 and Linksys PAP2. These devices are normallyconfigured via a web interface, but this tool allows you to read theconfiguration from the device and store it in a text file, or take atext file and copy the configuration to the device.

Why would you want to use this?

  • you can back up your configuration to a computer
  • you can more easily swap configurations with other users
  • you can compare configurations easily (using diff)
  • you can use this tool to update your configuration programmatically(for different times of day, etc.)
  • you can store your configuration in a source control system
  • you prefer editing text files to using web interfaces

spaconf is written in python and should run anywhere python runs (Unix, Windows, Mac, etc.).

It requires Python 2.3 or newer.

Home page:
http://www.opensky.ca/~jdhildeb/software/spaconf/
Download:

spaconf is available as source code in .tar.gz format (requires python to run) and as a Windows standalone executable (choose the .zip file).

All downloads are available from:
http://www.opensky.ca/~jdhildeb/software/spaconf/downloads/
Sample config file:
http://www.opensky.ca/~jdhildeb/software/spaconf/spa3000.txt

usage: spaconf.py [-nq] <src> [<dest>]

spaconf.py can read the active configuration from a Sipura SPA or Linksys PAP2 analog telephone adapter (ATA) and store it in a text file, or can take an existing text file and write that configuration to the ATA.Configuration options are stored as key-value pairs.

One of <src> or <dest> should be a local file path, and the other should be a URL to your ATA with the username and password embedded.If <src> or <dest> is a hyphen (-), standard input or output is used.<src> can also be a key-value pair (i.e., key = value).

Options:

-n, --nobootDo not reboot the ATA after configuring it.
-q, --quietDo not print informational messages.

Examples:

Write ATA config to standard output:
spaconf.py http://admin:mypassword@myata/
Sipura 3000 firmware manual

System Message: WARNING/2 (README.txt, line 61)

Definition list ends without a blank line; unexpected unindent.

or spaconf.py http://admin:mypassword@myata/ -

Copy ATA config into a config file:
spaconf.py http://admin:mypassword@myata/ ata.config
Or use an explicit IP if necessary:
spaconf.py http://admin:mypassword@192.168.0.5/ ata.config
Copy a config file to the ATA device (no reboot afterward):
spaconf.py --noboot ata.config http://admin:mypassword@192.168.0.5/
Copy config options from standard input to the ATA device:
spaconf.py - http://admin:mypassword@myata/
Set a single option (key/value pair):
spaconf.py key = value http://admin:mypassword@myata/

System Message: WARNING/2 (README.txt, line 77)

Definition list ends without a blank line; unexpected unindent.

or spaconf.py key value http://admin:mypassword@myata/

Sipura 3000 firmware list
Notes:

When reading a config from an ATA, this script unfortunatelycannot retrieve the passwords. They appear as stars ('****'). It is however safe to write such a configuration back to the device; such passwords will be ignored, and the passwords in the device will be left unchanged. If you edit a config file tocontain a (non-star) password, however, it will be changed.

Sipura Spa-3000 Firmware

System Message: WARNING/2 (README.txt, line 80); backlink

Inline strong start-string without end-string.

System Message: WARNING/2 (README.txt, line 80); backlink

Inline strong start-string without end-string.

It is not necessary that a config file contain key-value pairsfor every option supported by the ATA. Any options not present will not be changed.

Lines beginning with # in a config file are taken as comments andignored. Lines beginning with ! are printed to standard out whenthe config file is restored to an ATA.

Single and double quotes are permitted around option values (singlequotes are used in generated files) but may be omitted. When usinga key-value pair in the command, it is good practice to use singlequotes around the value to keep the shell from munging it.

This program has been tested with the Sipura SPA 3000 (firmwareversions 2.0.13g and 3.1.3), and with the Linksys PAP2 (firmware 3.1.9 and 5.1.5). Your mileage may vary.

Changelog:
2008-01-02

Release 0.3.

Huge thanks to Jerry Kindall for patches which:
  • add better support for Linksys PAP2 devices
  • fixed bug where spaconf couldn't handle values containing '='
  • allow stdin/stdout to be used for config files
  • allow the reboot to be suppressed
  • more verbose output (and --quiet option)
  • script returns an error code (0 is success)
  • allow you to set a single configuration value from command line

Sorry, no windows executable for this version yet.

2006-04-11

Release 0.2.

Added alternate URLs for compatibility with Linksys PAP devices.

2005-12-29
Initial release (0.1).
Feedback:
Please send me comments, bug reports, etc.jason@opensky.ca(better yet, please send patches!)