Orchid V4, V4+ Programing Tool Support

Heinz

It should be possible. Do you have a printout of your V4's program?

It's more likely that your V4's clock is wrong though.

Try updating that first http://forums.moneysavingexpert.com/showpost.php?p=1830574&postcount=2

the_devil_made_me_do_it

I've checked my table & it seems calls are routed via BT evening & weekends, so your probably right about the clock being wrong. I have manually updated it using your link. Hopefully that will solve the problem.

scope

Heinz wrote: »

Use a 121 prefix.

121 doesnt work for me, either on its own (to give new dial tone) or as part og the number 1210208123455678.. Any idea?

I too would like to make a couple of quick calls through BT to stop these silly caller ID charges.

Heinz

121 is the Orchid dialler override code but all it does is override the Orchid's programmed routing of an individual call (e.g. if your program would normally add a 18185 prefix to any UK 01/02/03 or mobile call, prefixing the number with 121 would prevent the 18185 prefix being added and send that particular call via your default calls provider instead.

If you have BT line rental and a CPS calls provider the prefix to send an individual call via BT is 1280 (you don't need to separately override the Orchid with 121 prefix, the 1280 prefix effectively does that job by forcing the call onto BT).

However, a number of former CPS calls providers have now changed how they provide they calls and, in the case of Sky Talk for example, that prefix no longer works and it is imposible for subscribers to make any calls via their BT account even if they use the 1280 prefix.

Who is your default calls provider?

scope

Heinz wrote: »

Who is your default calls provider?

Im with BT, with any additional routing taking place using the Orchid.. So in that case should 121 in front of the call always send it through BT? Or have i misunderstood you?

Heinz

Yes. If you don't use a CPS calls provider (i.e. your line/calls provider is BT and your Orchid just routes certain calls via 18185), a 121 prefix should override all programming in the Orchid and route that call via BT.

Equinox1000

Remember though that the 121 is itself programmable. If it doesn't work it may have been changed inadvertently.

Heinz

Equinox1000 wrote: »

Remember though that the 121 is itself programmable. If it doesn't work it may have been changed inadvertently.

Good point. Hadn't thought of that.

121 is, indeed, included as a Routing Rule (it's Rule 23 in Kevin's spreadsheet in post 1 of this thread) and, if you left it out because you didn't recognise it or didn't think it was necessary, keying 121 will do nothing at all.

Assuming Rule 23 fits in with your program, the manual keying sequence is:

*###121#5000#23#

shaungjones

I am a new user of the V4 Plus Orchid Dialler and thanks very much for the support through this forum in getting my unit up and running.

I have one observation that I would like confirming. Is it possible to make one call, hang up and then another but the second misses the LCR table ? I can recreate this and wonder if there is a rule of thumb that the dialler needs a break between calls - 20 or 30 secs ?

Heinz

shaungjones wrote: »

I am a new user of the V4 Plus Orchid Dialler and thanks very much for the support through this forum in getting my unit up and running.

I have one observation that I would like confirming. Is it possible to make one call, hang up and then another but the second misses the LCR table ? I can recreate this and wonder if there is a rule of thumb that the dialler needs a break between calls - 20 or 30 secs ?

I do remember such an occurrence being mentioned at some stage in the past but have not experienced it myself.

Pausing for a 'rest period' to allow the Orchid to return to its 'ready' state appears a sensible option but what that period should be can only be conjecture or decided upon by experience.