Orchid V4, V4+ Programing Tool Support

Heinz

The 1_8_5 version of Kevin Lawry's Excel spreadsheet (see the first post of this thread) shows the final version of the Heinz program sent out by Orchid last year with amendments since then (the last being in September 2009). As you'll see from Routing Rule 10 (Row 14, columns F to M) thereon, weekend routing of calls to mobiles is slightly different to weekday routing.

It sounds like your Orchid is correctly routing weekday calls to mobiles via 18185 and, because it keeps the cost down to 6p/minute, weekend ones via 18185's freephone gateway number (08081703703).

Something appears to be going wrong with the latter. It will cost you 1p/minute more but I'd suggest manually dialling the 18185 prefix before mobile numbers at weekends (there's no need to override the Orchid, use of the 18185 prefix will do that automatically).

Manually updating your program to route calls to mobiles via 18185 at all times might be an option.

If you want to do that, you need to key:

* # # # 0 7 # 3 1 1 1 # 1 0 #

dosh

Heinz

Tried that, but no joy.

Thanks anyway.

Edit - Would have worked Heinz, if I had entered the code correctly -Thanks

FJSRiDER

dosh wrote: »

Now whenever I 'phone a mobile over the w/e I get a message:
"The number you are trying to dial is incorrect, please check the length of the number and try again."

I noticed the same problem last weekend (although I'm only with 18185 and BT and rarely call mobiles from home at all) I overrode the setting and it called fine.

I wondered if 18185 had changed something and was planning to look at it before the end of the month and the time change..... perhaps it is something else?

dosh

Thanks FJS

I managed to find the original Orchid Default Programming Table and have now manually re-programmed the dialler, it seems to be OK now.
I think my problem could be with Primus CPS not 18185.
Anyway Heinz's solution above (and yours) would have worked if I had entered the code correctly.

Many thanks

Heinz

dosh wrote: »

I managed to find the original Orchid Default Programming Table and have now manually re-programmed the dialler, it seems to be OK now.

There has been one change since Orchid sent out that final update - Kevin Lawry's Excel spreadsheet (see the first post of this thread) is up-to-date.

http://forums.moneysavingexpert.com/showthread.html?p=18598983#post18598983 (you can see that Routing Rule 15 has been amended accordingly).

dosh

Thanks Heinz

Dialler now updated.

Heinz

Orchid dialler clocks need to be updated to take account of the one hour advance of the clocks on Sunday 28th March 2010.

The procedure for doing this is shown HERE.

FJSRiDER

Heinz wrote: »

Orchid dialler clocks need to be updated to take account of the one hour advance of the clocks on Sunday 28th March 2010.

Thanks for your reminder to do this!

Do you know if anyone posted a 'heads up' about reprogramming the dialler for the evening cheap rate time change for BT customers on April 1st - when it is changing from 18:00 - 06:00 to 17:00 - 07:00?

Having just done the clock change and had a quick search for the code for this but not seen it anywhere. I guess it should be ***07001900*5 ? Have I got that right?

Heinz

Yes, but as the Heinz program, on which Kevin's Excel spreadsheet is based, assumes a user who has a BT landline and a CPS calls provider offering free 6pm to 6am 'evening' calls, there is no need to make such a change.

However, I take your point.

For those using Kevin's spreadsheet but using BT's Unlimited Evening & Weekend Calls Plan rather than a CPS calls provider, cell C17 needs to be changed to 07 and cell C19 needs to be changed to 19 on 1 April 2010. Those changes will alter cell D20 to read ***07001900*5 which represents the changes BT has made to its definition of 'evenings'.

Put another way, those using BT's Unlimited Evening & Weekend Calls Plan rather than a CPS calls provider who manually program their Orchid (press the keys on their telephone) by sending DTMF tones, will need to key the sequence ***07001900*5 on or before 1 April 2010.

valmiki

I updated my dialler last week using the spreadsheet, changed the time and also changed the peak hour times in readiness for the BT changes (already widely publicised).

It was the first time I've used the spreadsheet, and just wanted to thank Kevin again, it was really easy and worked a treat.

I managed to check everything (ie. the codes, etc) was all installed by creating a final rule, which was to block the phone number of the line I was connected to. My reasoning was that if I dial my own number I'd get an engaged signal, and with this new rule it just totally ignored the number (in line with other barred numbers all you get is the dial tone as it just disregards the number), and it all worked!