[markd]

Hi Any news on this one in 3K v 3.1.0

Speed dials do not accept " nnnn@sipProxyort " syntax anymore,
where "nnnn" is desired number to call. The feature was working well in firmware 3.1.3

Any chance of a fix / work around?

Thanks

Mark

[jcgalvezv]

I guess you need to enable IP dialing. From some firmware version (I don'r remember which one) the speed dial is validated against the dial plan.

Juan C.

[markd]

Thanks.

Can you tell me how to do it.

Mark

[DracoFelis]

Originally Posted by markd

Speed dials do not accept " nnnn@sipProxyort " syntax anymore,
where "nnnn" is desired number to call. The feature was working well in firmware 3.1.3

Any chance of a fix / work around?

I think I saw in at least one of the firmware version notes, that they do consider this a bug, and had fixed the problem. But, of course, they might have reintroduced the bug in whatever the current version is.

Edit/Added:
And don't forget to make sure you have a single "x" (by itself) somewhere in your "dial plan". That is sometimes needed to allow you to use "Speed Dials", as the dial plan checks digits BEFORE the Sipura decides that you only entered a single digit (and therefore wanted a speed dial). So, if it's not already in your dial plan, make sure to add "x |" to the dial plan (so that you can enter the single digit that the speed dials want)!

But if you are still having probems, the "work around" is pretty trivial. Just put things that you would otherwise put into your "speed dials" into your "dial plan" directly. For example, lets say I like to listen to test recordings, and want to call the SIP Broker test number: sip:*011188888@sipbroker.com

Then if I added this to my dialing plan, I could just dial that SIP URI by entering #7 on my adapter:
<#7:*011188888@sipbroker.com>S0 |

NOTE:
Don't forget about "rebooting" your adapter after making changes. While often times the adapter takes the changes after pressing "Submit All Changes", there are times when the adapter gets "stuck" (a bug in the firmware, I suspect). I learned this fact "the hard way" after spending HOURS trying to debug settings that were right (and showing as updated in the web interface), but which didn't "take" until after I "power cycled" (reboot) the adapter! So just "play it safe" and reboot your adapter after making config changes.

BTW: You can "soft reboot" (restart, without power cycling) your adapter by simply calling the following URL from your web browser:
http://YOUR_ADAPTER_IP/admin/reboot
(where "YOUR_ADAPTER_IP" is the LAN address of your LinkSys/Sipura adapter)

[a.d]

@DracoFelis:

No, it is not dial plan related. The "speed dial" in 3.1.10 works with nnnn Syntax, where nnnn is an ID on the Proxy that "line1" is registred with.
But doesn't metter. I found out (after almost 2 weeks) this firmware can take PSTN line "off hook" and stay like that forever. A "soft" reboot doesn't help, and the "line" LED is off. The "info" page shows the status corectly (-7V/30mA) and all lines are engaged (Line1, PSTN and VOIP line registered to be used for PSTN gateway).
So I am back to 3.1.3 that still rings at random in some nights.

Does anybody know how to fix this problem? It is not hardware,since 3.1.10 does not have this issue.
There are 2 long threads about this: one here, about "ghost" rings and one on Whirlpool forum about "prank" calls, but no conclusion. Maybe there are some particular settings that just work. I mention I have no "caller ID" service on my PSTN line so I can't use that trick.

Thank you

[DracoFelis]

Originally Posted by a.d

Does anybody know how to fix this problem? It is not hardware,since 3.1.10 does not have this issue.
There are 2 long threads about this: one here, about "ghost" rings and one on Whirlpool forum about "prank" calls, but no conclusion.

My "fix", such as it is, is to just run with the older "2.0.13(GWg)" firmware on my SPA3000.

Remember, Sipura (which later got bought out by LinkSys/Cisco) apparently rewrote some key code when they switched to the v3 firmwares. But while the newer v3 firmwares may have a few more features (and are still being actively developed, unlike the v2 code), reports like yours seem to show that the v3 firmwares have never gotten as "stable" as the older v2 code. So until the v3 code "matures" to the point I think it's less trouble then the v2 code, I'll stick with the latest v2 code in my VoIP adapter...

[markd]

Thanks Draco. Yes your sample does work but i can't get it to work with any of the others. I thing it can not cope with a user name ie the bit before the @ with alpha characters.

As for ghost rings I have them with 2.0.1(99e2) firware. Should I therefore upgrade to "2.0.13(GWg)" and if so how?

Thanks

Mark

[DracoFelis]

Originally Posted by markd

As for ghost rings I have them with 2.0.1(99e2) firware. Should I therefore upgrade to "2.0.13(GWg)" and if so how?

Don't promise it will help, but IMHO it's unlikely to hurt.

I just checked, and it looks like the latest v2 firmwares are still available for download from this web page (under the 2.0 column):
http://www.sipura.com/support/index.htm