Orchid Dialler Discount

wygde3

Thanks for the last series of posts on the extra # needed ... I was going loopy for the last 24 hours as I tried to work out what was going on. I (unfortunately) happened to add my mother's details so that I could manage her routing table myself and thought I'd screwed something up. Have now tried extra # and found that it works a treat ...

Have also emailed Orchid support and asked what was happening. By the way it must be something to do with 1899 because the routing for international calls (which was not via 1899) was fine.

If you find out what is/was happening with 1899 and when we can not do the extra # please post. Thanks for your help.

Woby_Tide

I didn't realise that it was just taking an age to connect I thought something was wrong with 1899 when my wife started complaining. I was just hitting # either after hearing the Orchid had replayed my number to 1899 or as wakey said, now just adding it to the number. My original thoughts were maybe the 1899 servers were being overloaded with all the unhappy bunnies at 18866 being distraught about the xtra 1p connection fee increase and had all switched, but as said, looks to be a change by 1899.

fbrj

Woby_Tide wrote:

I didn't realise that it was just taking an age to connect I thought something was wrong with 1899 when my wife started complaining. I was just hitting # either after hearing the Orchid had replayed my number to 1899 or as wakey said, now just adding it to the number. My original thoughts were maybe the 1899 servers were being overloaded with all the unhappy bunnies at 18866 being distraught about the xtra 1p connection fee increase and had all switched, but as said, looks to be a change by 1899.

I wonder if this "delay" affects all the 1899/18866 family? While experimenting yesterday, I changed a 1889 routing to a 18866 (then force dialled etc). It definitely used 18866 as the message changed to "half a p a minute" from the "this is a free call" message. The delay was more or less the same...ie 30 secs+. This recent problem for cable users was probably most noticed on 1899 as very few will have set a dialler to route to 18866 (maybe some international calls).

Incidentally, I am not a cable user, have an Orchid dialler and route through 18866 and 1899 and have noticed no change at all.....seems to be a cable user specific problem!

Woby_Tide

cable users have a different access number to use so it may route differently, plus we need a delay inserting in numbers dialled so gues sthe process is different

fbrj

fbrj wrote:

Many thanks. I'll call them in the morning and let them know re dialling the hash. I'll report back....hopefully with good news!

Yep - good news......dialling the hash at the end of the number has done the trick!!

timbouk

fbrj wrote:

Yep - good news......dialling the hash at the end of the number has done the trick!!

Can the orchid be programmed to add a hash at the end?

April2

timbouk wrote:

Can the orchid be programmed to add a hash at the end?

Can't think why not - it's only another 'digit' on the telephone keypad.

timbouk

April2 wrote:

Can't think why not - it's only another 'digit' on the telephone keypad.

Because family need it to be idiot proof and totally transparent?

fbrj

April2 wrote:

Can't think why not - it's only another 'digit' on the telephone keypad.

If this is possible - I'd be interested to know how...basically it means that any No that routes through 1899 automatically needs a # added onto the end of the number...the question is..how?????

Woby_Tide

if your are dialling 01234 567890 just dial 01234 567890# or store them in the phones memory like that?