Clearing Speed dial fixed in the latest firmware?

(1/2) > >>

davidgomez79:
I had reported a bug with clearing speed dials via the phone using *74 and it seems to have been known about for a while now. I for sure thought it would be fixed this F/W release.. any ETA.. is it not fixable? (yes i know that ron guy posted a *76 code for it but it really should be fixed by official firmware)

another odd quirk is that *7500 (being an invalid speed dial) gives you this read out:

"The value is 45BBM"

I sure hope that setting a speed dial using *7400 wont overwrite code in firmware ala overflow?

RonR:
That Ron guy was also disappointed that *76 or something similar wasn't added in 2283.

I get the same result for *7500.

I haven't gotten brave enough yet to try *7400.   :)

obi-support2:
Please change *74 and *75 to avoid dialing 00 accidentally.

*74([1-9]|[1-9]x), Set Speed Dial, coll($Spd[$Code]
*75([1-9]|[1-9]x), Check Speed Dial, say($Spd[$Code])

Leading 0 should not be allowed for speed dial also.
We will modify our default *74 and *75 as above
in next release, and protect against illegal speed dial number.

I can't think of a better solution than the *76 suggested by RonR to clear speed dial.

RonR:
I think

[1-9]x?

is a little sexier loking.   :)


*74([1-9]x?), Set Speed Dial, coll($Spd[$Code])

*75([1-9]x?), Check Speed Dial, say($Spd[$Code])

*76([1-9]x?), Clear Speed Dial, set($Spd[$code],)

obi-support2:
Not exactly equivalent. Your syntax may not be what most expected because the ?
element will make the OBi wait for a long timer after a single digit (10s).
whereas (x|xx) will wait for only a short timer (2s)

BTW, please do not attempt to use more complex digit map syntax in this context, such as
S1, S2, .... We only use it to map speed dial numbers.

Navigation

[0] Message Index

[#] Next page