my outgoing tab has 16 rows now. For some reason having a lot of trouble with adding new "exact" matching entries for speed dials. Is there a limit to how many rows the wizard can handle?
My priority column is set as 6.100, 10.100, 11.200, 11.250, etc. When entries dialed via the ATA, the dial plan does not even kick in. No logs on the console. I tried many different patterns.
Could be bugs in Simple Wizard ?
Re: Could be bugs in Simple Wizard ?
Strange that it only happens for some speedials like *91, *93, etc. I tried deleting whole rows and recreating several times.
Re: Could be bugs in Simple Wizard ?
There's no limit on the number of rows. I've checked that exact matches like *1 and *93 work correctly for me.
What I suspect is happening is that your ATA is not passing through the call. Some ATAs, such as the Sipura/Linksys ones, treat * prefixed numbers as special codes to perform actions on the ATA. You can turn that behaviour off somewhere in the ATA's settings.
What I suspect is happening is that your ATA is not passing through the call. Some ATAs, such as the Sipura/Linksys ones, treat * prefixed numbers as special codes to perform actions on the ATA. You can turn that behaviour off somewhere in the ATA's settings.
Re: Could be bugs in Simple Wizard ?
You are so good
On my Sipura SPA3000, found them under Regional->Vertical Service Activation Codes . There are a bunch of them. Could not find a single toggle to disable them all. So maybe easier is to use a different schema for speedials on ss.
Maybe **1, **25, etc. Any suggestions?
On my Sipura SPA3000, found them under Regional->Vertical Service Activation Codes . There are a bunch of them. Could not find a single toggle to disable them all. So maybe easier is to use a different schema for speedials on ss.
Maybe **1, **25, etc. Any suggestions?
Re: Could be bugs in Simple Wizard ?
Personally I just use 100, 101, 102 etc. The other non-numeric key you've got is # but that's also typically used for control purposes.