by

Sipura 3000 Firmware



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

DD-WRT Forum Forum Index ->Broadcom SoC based Hardware
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.

Analog Calls Routed Over the Internet. Internet telephone service is now more accessible than before. Part of Cisco Small Business Voice Gateways and ATAs, the SPA3102 Voice Gateway allows automatic routing of local calls from mobile phones and land lines to Voice over Internet Protocol (VoIP) service providers, and vice versa.

DD-WRT Forum Forum Index ->Broadcom SoC based HardwareAll times are GMT
  • Sipura 3000 – This ATA is discontinued and has been superseded by the. The only documentation publicly accessible is the Sipura ATA User guide for firmware v2.0.
  • Sipura 3000 Dial Plan Manager is a small, simple and easy-to-use program designed to be a dial plan tester/manager for Sipura 3000 Voice Over IP (VoIP) devices.

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

Configuration Tools - Data Sheets - Installation, User and Admin Guides - Firmware - Factory Reset

Aastra | Atcom | AVM | Axtan | AYC | Boscom | Cisco | Digium | Draytek | Edgewater | Eicon | Elmeg | Epygi | Grandstream | Hitachi | Intertex | Linksys | Mediatrix | Multitech | Pika | Pirelli | Polycom | Quintum | Ranch Networks | Rhino | Sangoma | Siemens | Sipura | Snom | swissvoice | UTStarcom | Vegastream | VXI | Zultys | ZyXEL

Aastra Firmware
Default Admin Username = admin
Default Admin password = 22222

Model

Language Pack
Release Notes
Aastra 53i2.0.2Rev002.0.2June 2007
Aastra 57i2.0.2Rev002.0.2June 2007
Aastra 57i2.0.2Rev002.0.2June 2007
Aastra 480i Generic SIP1.4.2June 2007
Aastra 480i Broadsoft SIPNovember 2005
Aastra 9112i Generic SIP1.4.21.4.2June 2007
Aastra 9112i Broadsoft SIPNovember 2005
Aastra 9133i Generic SIP1.4.21.4.2June 2007
Aastra 9133i Broadsoft SIPNovember 2005

Atcom Firmware
Default Admin Username =
Default Admin password = 12345678
Default User password = 1234

ModelCurrent Firmware
Atcom AT-320PD FirmwareH.3231.54.004
Atcom AT-320PD FirmwareIAX21.54.004
Atcom AT-320PD FirmwareMGCP1.54.004
Atcom AT-320PD FirmwareNet2Phone1.53.006
Atcom AT-320PD FirmwareSIP1.54.004
Atcom Admin & Debug ToolPalm Tool1.5.1

AYC Firmware
The current release version for the AYC IPcts and IPcts-E is version 1.05 and is only available to AYC Accredited Engineers directly from AYC.
End users should contact their AYC installer for updates.

3000

Grandstream Firmware
Default Admin Username =
Default Admin password =Admin

Model

Release Notes
Release Date

Grandstream HT-286 Hardware Revision 2 Firmware

1.0.8.33
168.75.215.189
December 2005

Grandstream HT-286 Hardware Revision 3 Firmware

1.0.8.33
168.75.215.189
October 2006

Grandstream HT-386 Firmware

1.0.3.64
168.75.215.190
December 2006

Grandstream HT-486 Hardware Revision 1 Firmware

1.0.6.7
168.75.215.189
June 2005

Grandstream HT-486 Hardware Revision 2 Firmware

October 2006

Grandstream HT-488 Firmware

1.0.3.64168.75.215.190December 2006
Grandstream HT-496 Firmware1.0.3.64168.75.215.190December 2006

Grandstream HT-502 Firmware

1.0.0.44168.75.215.189June 2007

Grandstream BudgeTone 101 Firmware

1.0.8.33
168.75.215.189
October 2006

Grandstream BudgeTone 102 Firmware

1.0.8.33
168.75.215.189
October 2006

Grandstream BudgeTone 200 Firmware

1.1.1.14
168.75.215.189
October 2006

Grandstream GXP-2000 Firmware

1.1.1.14
168.75.215.189
October 2006
Grandstream GXV-3000 Firmware1.0.1.7
168.75.215.189
March 2007
Grandstream GXW-4004 Firmware1.0.0.441.0.0.44168.75.215.189June 2007
Grandstream GXW-4008 Firmware1.0.0.441.0.0.44168.75.215.189June 2007
Grandstream GXW-410x Firmware1.0.0.55168.75.215.189May 2007

Grandstream ATAs can only be updated via the WAN port.For firmware upgrades for HT-386, HT-488 & HT-496 use TFTP server 168.75.215.190.
For firmware upgrades for all other devices use TFTP server 168.75.215.189.
Please be aware that the firmware upgrade may take up to 10 minutes.Due to a TCP reliability bug (for HT286/HT486/BT100 only) that exists before 1.0.8.16 releases, it is strongly recommended to use TFTP for firmware upgrade (instead of using HTTP), if you are upgrading firmware from any firmware prior 1.0.8.x. This bug is fixed in the 1.0.8.16 release. Firmware 1.0.8.33 (HT286/HT486/BT100) is available at TFTP server 168.75.215.189
Once upgraded to this release, the firmware can NOT be downgraded to firmware versions prior to 1.0.8.16. Therefore, it is STRONGLY recommended that you fully test this version before committing to massive upgrade in production network. Warning: Before upgrading your telephone or adapter, please verify with your service provider if the firmware change will affect your service.

If you are using TFTP to update do NOT enable the 'Check for Updates' option as this applies to http only and disables TFTP updates.
TFTP checks for updates at every reboot


After upgrade, please power cycle the phone to enable all the new features.EdgewaterHitachi Firmware
Default Admin Username = admin
Default Admin password = 000000Hitachi WIP-3000 Firmware Boot ROM v 1.1.2
Boot ROM v 1.1.4
Firmware Version 2.4.2 LA1 Multi-language and 802.11g Support !Hitachi WIP-5000E Firmware (The back of the phone looks like this with NO 'asterisk')
Boot ROM v 1.04
Firmware Version 2.1.11 - Latest stable versionFirmware Version 2.2.1 - Do NOT use if you are using Asterisk
Firmware Version 2.2.6 - Known bug when using STUNHitachi WIP-5000E-A Firmware (The back of the phone looks like this with an 'asterisk')
Boot ROM v 1.14
Firmware Version 2.4.2 LA1 Multi-language and 802.11g Support !

Hitachi Management Software for version 2.1.11 and earlier
Hitachi Management Software for version 2.2.x and later

Linksys Firmware
Linksys WIP330 Admin Username and Password
admin/admin, admin/0000 or administrator/0000
All other Linksys Phones and ATAs
Default Admin Username =
Default Admin password =

SPA Firmware with Upgrade Utility Program
Download the firmware file to a local PC to upgrade your SPA.
NOTE: The SPA2100 and SPA2102 use different firmware ensure you use the correct firmware for your model
NOTE: The SPA3000 and SPA3102 use different firmware ensure you use the correct firmware for your model

Linksys Analogue Telephone Adapters (ATAs) Firmware

Model

Release Notes
Linksys PAP2T Firmware5.1.3December 2006
Linksys SPA1001 FirmwareJanuary 2007
Linksys SPA2002 Firmware3.1.18January 2007
Linksys SPA2100 Firmware3.3.8aMarch 2007
Linksys SPA2102 Firmware5.1.95.1.9April 2007
Linksys SPA3000 Firmware3.1.10d
Linksys SPA3102 Firmware5.1.75.1.7April 2007
Linksys VoIP Phones Firmware

Model

Release Notes
Linksys SPA901 Firmware5.1.5December 2006
Linksys SPA921 Firmware5.1.55.1.5January 2007
Linksys SPA922 Firmware5.1.75.1.7April 2007
Linksys SPA941 Firmware5.1.55.1.5January 2007
Linksys SPA942 Firmware5.1.75.1.7April 2007
Linksys SPA962 Firmware5.1.75.1.7April 2007
Linksys SPA 9x2 Display Language Localisations (SPA 922, SPA942, SPA962 only) - requires v5 firmware

Language

Release Date
Administrator Guide for SPA9x2 LocalisationDecember 2006
EnglishDecember 2006
CzechDecember 2006
Danish
1.00
December 2006
DutchDecember 2006
French
1.00
December 2006
German1.00December 2006
Italian1.00December 2006
Portuguese1.00December 2006
Slovak1.00December 2006
Spanish1.00December 2006
Swedish1.00December 2006

Linksys Wi-Fi VoIP Phones Firmware

WIP330 ONLY Firmware Update Routine

  • 1. Only if Firmware version is 1.00.06A or earlier
    • a. Access Phone Settings -> Upgrade
    • b. Set
      • i. Download URL: http://www.myphonecall.co.uk/support/firmware/linksys/wip330
      • ii. OS Image File: wip330_sbe.bin
    • c. Select Upgrade Softkey.
    • d. After completing the upgrade above the phone will reboot, and you will observe a smaller GUI Selection for Upgrade.
    • e. In the Upgrade path you enter
      • i. Download URL: http://www.myphonecall.co.uk/support/firmware/linksys/wip330
      • ii. OS Image File: wip330_v1_02_12S.bin
    • f. Select Upgrade Softkey.
    • g. After this upgrade completes, the phone is up to date with latest firmware
  • 2. Only if Firmware version is higher than 1.00.06A
    • a. Access Phone Settings -> Upgrade
    • b. Set
      • i. Download URL: http://www.myphonecall.co.uk/support/firmware/linksys/wip330
      • ii. OS Image File: wip330_v1_02_12S.bin
    • c. Select Upgrade Softkey.
    • d. After this upgrade completes, the phone is up to date with latest firmware.

Model

Release Notes
Linksys WIP330 Firmware
1.02.12
January 2007

Linksys IP PBX Firmware

Model

Release Notes
SPA9000 v1April 2007
SPA9000 v25.1.17April 2007
SPA400April 2007
SPA9000 Setup WizardJanuary 2007

Linksys SPA9000 v1 - LEDS at the back
Linksys SPA9000 v2 - LEDS at the front

Linksys SPA9000 Localisations

Auto Attendant Language

Release Date
EnglishDecember 2006
DanishDecember 2006
DutchDecember 2006
FrenchDecember 2006
GermanDecember 2006
ItalianDecember 2006
PortugueseDecember 2006
SpanishDecember 2006
SwedishDecember 2006


Alternative Upgrade mechanisms:-

Sipura 3000 Firmware Vs

Via TFTP
  • If necessary, install a TFTP server on a PC on the same local subnet as the SPA device.
  • Place the firmware upgrade 'spa_whatever.bin' file in the tftp root directory of the active TFTP server.
  • Determine the IP address of the powered-up SPA (IVR menu ****#110#).
  • Request the upgrade from a web browser:-
  • If the TFTP server is running on the same computer:-
    ie if 192.168.1.1 is the SPA's IP address then
    http://192.168.1.1/upgrade?/spa.bin.
  • If the tftp server is on a remote computer:-
    ie if 192.168.1.1 is the SPA address and 172.16.1.1 is the tftp server address then
    http://192.168.1.1/upgrade?tftp://172.16.1.1/spa.bin
  • The SPA should then get the new firmware from the TFTP server and reboot.

Via HTTP

  • Upload this file to directory on your webserver. (Example http://192.168.80.80/spa.bin)
  • Assuming 192.168.1.2 is the SPA's IP address then enter http://192.168.1.2/upgrade?http://192.168.80.80/spa.bin into your browser
  • Now you should be redirected to a wait screen and your device should be upgrading its firmware which may take some time.

Pirelli DP-L10 Firmware
###520# Show Firmware Version

Polycom SoundPoint and SoundStation Firmware
Default Admin Username = Polycom
Default Admin password = 456

Only available via support (Sorry - Polycom's rules not ours)Boot ROM 3.2.2 Release Notes
Boot ROM 3.2.2
SIP 2.0.3 Release Notes
SIP 2.0.3

UPGRADE REQUIREMENTS FOR BOOTROM 3.2.2/SIP 2.0.3
SoundPoint IP 300 2.6.1 or greater
SoundPoint IP 301 2.6.1 or greater
SoundPoint IP 430 3.1.3 or greater
SoundPoint IP 500 2.6.1 or greater
SoundPoint IP 501 2.6.1 or greater
SoundPoint IP 600 2.6.1 or greater
SoundPoint IP 601 3.1.0 or greater
SoundStation IP 4000 3.1.2 or greater

DOWNGRADE LIMITATIONS
Phones with BootROM 3.2.2 / SIP 2.0.3 may be downgraded as far back as the following software revisions:
BootROM:
IP 301, 501 – BootROM 3.0.0
IP 430 – BootROM 3.1.3RevB
IP 601 – BootROM 3.1.0
IP 4000 – BootROM 3.1.2
SIP Software:
IP 301, 501 – SIP 1.5.3
IP 430 – SIP 1.6.6RevB
IP 601 – SIP 1.6.1
IP 4000 – SIP 1.5.3

Publicly Available
Boot ROM 3.1.3 rev D Release Notes
Boot ROM 3.2.1 Release NotesBoot ROM 3.1.3 rev D
Boot ROM 3.2.1
SIP 1.6.7 Release NotesSIP 1.6.7

Latest Stable Sangoma Drivers 2.3.4-2 (30 Nov 2006)

Sangoma A101 & A102 with serial number format 10101u0-xxxxx - Firmware Version 25
Sangoma A101 & A102 with serial number format 10101u10-xxxxx - Firmware Version 25
Sangoma A102D - Firmware Version 28
Sangoma A102DX (A102DM) - Firmware Version 28
Sangoma A102X (A102M) - Firmware Version 28
Sangoma A104 - Firmware Version 24
Sangoma A104D - Firmware Version 24
Sangoma A104DX (A104DM) - Firmware Version 28
Sangoma A104X (A104M) - Firmware Version 28
Sangoma A108 - Firmware Version 28
Sangoma A108D - Firmware Version 28
Sangoma A108DX (A108DM) - Firmware Version 28
Sangoma A108X (A108M) - Firmware Version 28
Sangoma A200 - Firmware Version 07
Sangoma A301 - Firmware Version 05

Sipura Firmware
Default Admin Username =
Default Admin password =

SPA Firmware with Upgrade Utility Program
Download the firmware file to a local PC to upgrade your SPA with currently supported release(s).

Sipura 3000 Firmware Pc

Model2.03.0
Sipura SPA-1000 Firmware

N/A

Sipura SPA-1001 Firmware

2.0.13gRelease Notes
2.0.13_SEg (¹) Release Notes

Sipura SPA-2000 Firmware
Sipura SPA-2002 Firmware

N/A

Sipura SPA-2100 Firmware
Sipura SPA-3000 Firmware
Sipura SPA-841 Firmware

N/A

3.1.4Release Notes, Ring tone Generator

(¹) SPA-1001 SE firmware supports 2 service providers. Read more.
We have included the SPA Upgrade Utility Program as well as the binary upgrade file in the download. The binary file is useful for those customers who do not have a WindowsTM based PC or use remote provisioning to upgrade units via TFTP, HTTP or HTTPS.

Sipura Spa-3000 Firmware

Please note: It is not necessary to upgrade your SPA if your device is remotely provisioned by a service provider.
Click here to use our SPA-2000 web-based configuration wizard
Click here to use our SPA-3000 web-based configuration wizard

Example of US-style Dial-Plan
(011,xx.|*xx|[3469]11|0|00|<:1408>[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx)
The example dial-plan above is for US-style dialling, where it will allow you to dial 7-digit with 1408 automatically appended.
You can also dial 1 followed by 10-digit for long distance.

Snom Firmware
Default Admin Username =
Default Admin password = 0000

Download from http://www.Snom.com/
or use
The Snom Automatic Update Service
The telephone(s) to be updated need to have one of the following URLs set as the 'Setting Server'

Choose the following URL if you wish to update your phone to the current stable firmware release and then not update to new releases automatically:-
http://provisioning.Snom.com/release/update_once.php

Choose the following URL if you wish to update your phone to the current stable firmware release and then have it keep updating automatically to new releases:-
http://provisioning.Snom.com/release/update.php
This version will keep your phone firmware automatically up-to-date and you will not have to pay any further attention to it.

Sipura 3000 Firmware List

Choose the following URL if you wish to update your phone to the current Beta firmware and then have it keep updating automatically to new Beta versions:-
http://provisioning.Snom.com/beta/update.php
This version will keep your phone firmware automatically up-to-date with the latest BETA firmware and you will not have to pay any further attention to it.

swissvoice IP10S Firmware
Default Admin Username = admin
Default Admin password = admin

Swissvoice IP10S H.323 Firmware - v1.1.0.B1 - FK2 - Release Notes
Swissvoice IP10S MGCP Firmware - v1.0.5.B8 - Release Notes
Swissvoice IP10S SIP Firmware - v1.0.1.B4 - Release Notes

If you are using TFTP to upgrade the firmware you need to edit swupdate_ip10.inf and change
<APPLICATION server=ftp
to
<APPLICATION server=tftp

and

<BOOT version=v107 server=ftp>
to
<BOOT version=v107 server=tftp>

To swap from one protocol to another one (MGCP to SIP for example), it's mandatory to add, inside file swupdate_ip10.inf contained inside the zip file, option 'update=forced clean-data=all' inside tag <APPLICATION>, and option 'update=forced' inside tag <BOOT>.

Default Admin Username = admin
Default Admin Password = psw

Default User Username = User
Default User Password = 888888

UTStarcom F1000 Firmware v4.50 - DO NOT USE ON F1000G !!!
UTStarcom F1000G Firmware v2.7 - DO NOT USE ON F1000 !!!
UTStarcom F3000 - Firmware v5.90 (Jan 2007)

To identify whether you have the UTStarcom F1000 or F1000G remove the battery and look at the model number listed inside.

Sipura 3000 Firmware

Default Admin Username =
Default Admin Password = 895897

ZIP 2x2 v 1.0.14

ZyXEL Firmware
http://www.zyxel.com/web/support_download_list.php