Orchid dialler occasionally not routing calls

DeeCee

The call logger is a ER-4000.
You can see it at....
http://www.unitone.com.tw/ESD/PhoneManager.htm

It "reads" the outgoing dial tones and logs the numbers dialled together with time and date.
..... Got it in USA.

Steve.W_2

Had the same problems when I first got my Orchid, I emailed Orchid support who checked my routing set up & confirmed it was correct. They replaced the dialler with a new one & its been fine since...

bbb_uk

Just made a call and I couldn't hear the orchid dialler dial the '18866' prefix like it should. Have you had a reply back Jem?

jem16

bbb_uk wrote:

Just made a call and I couldn't hear the orchid dialler dial the '18866' prefix like it should. Have you had a reply back Jem?

Just got a reply today and was just reading it when you posted. Here it is;

"Sorry for the delay in getting back to you, i have just looked at the thread, it is not something new, we used to have two call loggers travelling around various parts of the country for some of our corporate customers. The usual culprit was 1471 3, this is a BT service and you cannot reroute 1471'd calls to a low cost network. Other possible causes are as mentioned in the thread, dialling 121 or 141, unplugging the dialler, as was mentioned it is possible to dial to quickly straight after another call, but in reality this is unlikely, i think the timeout is about 40ms!!! Parallel phones not connected to a dialler is another cause of misdials, this again is because the phone is not connected to the dialler, failing that the dialler could be faulty, we have no problem swapping the dialler if it is faulty, but i can assure you that the dialler will not work intermittently (unless faulty of course). Let me know if any of this is a likely cause or if you would like to swap the dialler out."

None of what they suggest is happening in my case but I've just emailed back about one thing - what's the problem with 121 or 141? The reason I'm asking is my local STD code is 0141 and my problem has only happened with 0141 numbers. Now we haven't missed out the 0 in the 0141 as the call logs show them correctly dialled and we have got through to the person but I'm wondering if the dialler hasn't picked up on the 0.

bbb_uk

jem16 wrote:

The reason I'm asking is my local STD code is 0141 and my problem has only happened with 0141 numbers. Now we haven't missed out the 0 in the 0141 as the call logs show them correctly dialled and we have got through to the person but I'm wondering if the dialler hasn't picked up on the 0.

Ours are local STD as well but to be honest most calls we make are generally local (without the full STD) anyhow. Having just rung Orchid and spoke with a pleasant lady we discovered that my local area code wasn't programmed into the dialler (not listed on CWClient). I've now entered our number on the CWClient and programmed the dialler with our area code via our phone using the code: *** area code *4. I'm going to give that a try.

DeeCee

My miss-dialled calls were to numbers that had been dialled many times from a DECT phonebook. Some numbers had been dialled 30-40 times without error !
For example one number had been routed incorrectly at 11:01 and routed at 11:25 correctly. The logger showed that the dialler had failed to insert the service prefix number.

Calls are set up to route through 1899 & 18866 at all times and were to local, national and USA numbers.

No further problems to date with the new dialler, but still logging calls. About 90+ to date.

apwood

Just a note, doesn't apply to the above cases, but a similar problem happened to me - but quite a few calls were mis-dialled. I found it was because the clock on the dialler had lost its time setting (despite being a v4plus with power supply). After doing a force home the clock was set correctly and the problem went away.

ginger_nuts

I remember it been posted on here some time ago where orchid had said you should leave 5 seconds between calls ,otherwise call may not be routed correctly .

Heinz

My daughter had the same problem and was on the verge of sending the Orchid back when, by chance, she had no dialtone one blustery day.

Reporting the fault to BT resulted, eventually (the diialtone returned before the first engineer arrived - on a Friday - and he just signed the job off as NFF), in them discovering the wiring from the pole outside was circa 1921 and there was an intermittent connection if the wind blew! It was almost unnoticeable in calm weather but the slightest gust was sufficient to interrupt dialling.