118866 rip off

April2

the_devil_made_me_do_it wrote:

The good people at Orchid, set up my dialler for me today, as windows XP dosen't work well with their CW client. I said to them, I was abit worried about this 118866 thing, and they suggested that they programme my dialler with 141 18866 instead, this way, if there was any prroblems, the call wouldn't get routed instead of risking connection to 118866. I'll see how it goes, before I deceide whether to risk it without programming it as 141 18866.
Anyone else doing it this way??

Yes. Have a read of THIS THREAD (post 12 on page 2 is the most relevant).

the_devil_made_me_do_it

so someone is doing it that way then!! Any problems??? I won't know till I get my first bill.

bbb_uk

We've been using the dialler for months now and not once has it dialled the DQ 118866 service. I'm sure this is the case for the majority of other users as well.

With the exception of the thread as pointed out by April2, the other people who have dialled the DQ 118866 service have done it manually by accident. It was only the OP of the thread mentioend by April2 that had this problem even with a dialler which we suspect is due to noise/intereference on the line, or possibly an intermittent faulty dialler.

the_devil_made_me_do_it

well I can't change it at the moment cauce the CW client won't work properly with windows XP. Orchid are looking into it at the moment, to see if they can get their programme to work on XP. So at the moment I can't even check my routing plan.

bbb_uk

the_devil_made_me_do_it wrote:

well I can't change it at the moment cauce the CW client won't work properly with windows XP. Orchid are looking into it at the moment, to see if they can get their programme to work on XP. So at the moment I can't even check my routing plan.

I personally don't think you'll need to change it to 141 18866.

The CW client is an old 16bit programme but it still works on Windows XP (32bit) as I know it works on mine with no problems which means the chances are its your setup.

The most common problem error that may occur on a WinXP setup is:-

16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Winnt\System32\config.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.

This is most likely due to a corrupt config.nt file on your system and if this is the case read the M$ article here.

the_devil_made_me_do_it

The guy at orchid has already set 141 18866 for me, that's what i meant when i said I can't change it.
As for the problem with windows xp, I ain't getting an error message, it just isn't downloading my routing info fully form the server.

Oh does the 121 over ride, only work on the particular telephone call you are making at that time??

bbb_uk

the_devil_made_me_do_it wrote:

The guy at orchid has already set 141 18866 for me, that's what i meant when i said I can't change it.

Oh right.

As for the problem with windows xp, I ain't getting an error message, it just isn't downloading my routing info fully form the server.

I had this problem about a month ago and so has another MSE member that I'm aware of it. It's not related to WinXP though and I believe its the routing table is corrupt or something as it happened since Orchid started having problems with their server just over a month or so ago.

Oh does the 121 over ride, only work on the particular telephone call you are making at that time??

Yes.

the_devil_made_me_do_it

Oh ok thanks. Speaking of routing. The guy at Orchid set up my table, I've forced home, but I don't think it's activated as the dialler isn't recognizing local calls unless i type into the fone the area code.

bbb_uk

the_devil_made_me_do_it wrote:

Oh ok thanks. Speaking of routing. The guy at Orchid set up my table, I've forced home, but I don't think it's activated as the dialler isn't recognizing local calls unless i type into the fone the area code.

This is going off topic a bit but if dialling a number in full routes the call via Call18866 as it should but dialling a local number doesn't then the chances are Orchid have either forgotten to setup the routing for local calls as the same as national calls or the dialler doesn't have your STD (Standard Trunk Dialling) code. For example, for Manchester and the surrounding areas the STD code is 0161 xxx xxxx. The dialler needs this 0161 when you dial a local code as it then puts the STD code in front automatically because the likes of Call18866 will not route a call unless its in the full format.

Does this make sense?

terryrichards

I think that we should all complain about this one, and/or get Martin involved to have a bit of a Rant about this one. Anything I can do?