Orchid V4, V4+ and Ranger 400 phone users - Discussion

Heinz

farci wrote: »

I'm not sure why it should be more expensive to route via an 0808 number than a short code. 0800/8 is free to the caller so is the net cost not still the same as short code?

Taking into account that 18185 has to pay for your call to their 0808 number (that's the way freephone numbers work), it's not surprising that, for some types of call, their charges are higher for those going via that route.

For example, calls to 01/02/03 numbers cost 5p connection and 0p/minute via the 18185 prefix (if you can use it) whereas those calls cost 5p connection and 1p/minute via the 0808 1 703 703 freephone gateway number.

Compare their charges for 18185 dialling and for 0808 1 703 703 dialling and you'll see what I mean.

cazian

I'm having a problem with my Version 4 dialler. When dialling a certain local Reading (0118) number, the number is dialled correctly, except that the last number of the seven-digit number is dialled as a 6 and not as a 9, as it should be. I know it's the dialler, as when its taken out of circuit, the number is dialled correctly. The problem occurs even when the dialler does not use low-cost routing (as the number can be called for free on our network, Virgin Media).

Any ideas if it is a hardware fault or a problem that might be sorted by a reset of the dialler?

If the dialler is most likely faulty, does anyone have a spare version 4 dialler they can spare, as I note Orchid no longer sell them?

Heinz

Now that's a strange one and, as it's the last digit and only the last digit being dialled incorrectly, I cannot think of a reason.

However, a V4 is just a computer and, as we all know, they have a habit of getting their knickers in a twist from time to time and need a swift re-boot - so a full reset before you admit defeat cannot do any harm.

There are 3 procedures:

Lift Handset & dial
**# 0000 * 1 * 8
Replace handset

Lift Handset & dial
**# 0000 * 0 * *
Replace handset

Lift Handset & dial
**# 0000 * 0 * 7
Replace handset

As to anyone having a spare, I'm afraid they're like hens' teeth now (I've had a search running on eBay for months without a single hit).

cazian

Thanks for the advice Heinz. I have just tried the reset advice, though not sure it worked. Should the reset clear out all the routing as well? When I tried to dial my mobile number after inputting all the codes quoted, it still dialled via 18899. Does that mean the reset didn't work?

Also, I have vaugue memories of having to use a wired phone to programme the dialler, though not sure. We now only have access to cordless phones - do I need to get hold of a wired phone and plug that straight into the dialler to effect the reset?

Heinz

cazian wrote: »

Thanks for the advice Heinz. I have just tried the reset advice, though not sure it worked. Should the reset clear out all the routing as well? When I tried to dial my mobile number after inputting all the codes quoted, it still dialled via 18899. Does that mean the reset didn't work?

Also, I have vaugue memories of having to use a wired phone to programme the dialler, though not sure. We now only have access to cordless phones - do I need to get hold of a wired phone and plug that straight into the dialler to effect the reset?

AFAIK, using those reset codes should not clear the V4's carrier and routing programming (although manually updating the time/day/date afterwards would be prudent).

I use my laptop's modem and Kevin Lawry's MS Excel spreadsheet to program my V4 now but use a DECT handset for the time/day/date programming so, as long as your DECT base station is plugged into the V4, using a DECT handset for manually proramming carrier and routing codes should not be a problem. In fact, it'll probably be easier because you could 'predial' each string before sending to the V4.

cazian

Thanks for the feedback Heinz. The reset and time reset appears to have worked - the problem number is now dialled correctly through the dialler.

I have used Kevin Lawry's MS Excel spreadsheet and laptop modem as well to program the dialler but for some reason that doesn't seem to work anymore - I keep getting an error message that says COM3 is already in use. I'm not sure what else in the laptop could possibly be using the same port.

cazian

Further to the last message, the dialler has resumed misdialling, so a false dawn. The hunt for a replacement dialler is on (you were right about them being like hen's teeth, Heinz!)

Lplates

Heinz wrote: »

As to anyone having a spare, I'm afraid they're like hens' teeth now (I've had a search running on eBay for months without a single hit).

You might like to make sure that your search is still active. One sold on eBay, after seven days on sale, the same day as you posted - see

http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=350371611986

cazian

I found the same item, in my quest for a replacement dialler. Unfortunately, as far as I could gather from some Googling, the dialler in that auction is a Version 2, as opposed to a Version 4. Unfortunately, I understand that the Version 2 does not have the ability to programme an internal clock, so that a different carrier can be called, dependant on the time of day, which is an essential feature for me. The search goes on...

Lplates

cazian wrote: »

I found the same item, in my quest for a replacement dialler. Unfortunately, as far as I could gather from some Googling, the dialler in that auction is a Version 2, as opposed to a Version 4. Unfortunately, I understand that the Version 2 does not have the ability to programme an internal clock, so that a different carrier can be called, dependant on the time of day, which is an essential feature for me. The search goes on...

It was in fact a V4 – although regrettably it’s too late for you to use this information now.