Orchid V4, V4+ Programing Tool Support

Equinox1000

Randal - I thought you were using the spreadsheet to program but now I understand you are doing it manually so you don't have a modem in the equation. Worth trying a different phone because it is possible the diallers have difficulty hearing the tones.

Is your dialler line or mains powered? Either way, it could be there isn't quite enough power to fully operate the dialler? If line powered, try a different line at another location.

digital

I've just spent a happy (?) few minutes manually reprogramming my V4 with 35 codes of varying types generated by Kevin's (thanks) spreadsheet. Two, however, elicited a 'number not recognised' response. They were:
*###056#1111#08# and
*###118*1*9#1111#22#
Can anyone spot why these codes are not accepted and escape the V4 to produce the recorded message?

rkm_hm

What exactly are you trying to achieve? Are you trying to block 056 numbers? If so, you need 1000 instead of 1111.

What's the 118 line supposed to do?

digital

I'm trying to block both 056 and 118 numbers. The odd thing is that both codes are generated by Kevin's spreadsheet.

However, changing the 1111 to 1000 in each one, as you suggest, fixes the problem. Thanks!

rkm_hm

Well, the version of Kevin's spreadsheet which I've got (but don't use in the original form) doesn't block 056 calls - it routes them via Carrier 1 (18185) at all times, hence: *###056#3111#08#
All his examples of blocking have 1000 rather than 3111.

Similarly, Kevin isn't blocking 118 - he's "translating" it so that it doesn't matter what digit you dial after 118, you'll always get 118226.

shilcor

digital wrote: »

I'm trying to block both 056 and 118 numbers. The odd thing is that both codes are generated by Kevin's spreadsheet.

However, changing the 1111 to 1000 in each one, as you suggest, fixes the problem. Thanks!

That's because the "Barring" call handling type only works when the three carrier code entries are all zeros. You cannot bar calls during certain times (daytime for example) and allow them the rest of the time.

digital

Ah! Thanks for that. I've changed them and all (appears) to work now. Just a pity this computer doesn't have a modem and I had to enter everything manually.

nigelbeans

I have recently bought one of these diallers, but I can't get it to work!

When I attempt to make a call there is a dialling tone, then the sound of the phone dialling the phone number I want to call, then the dialling tone continues until I get cut off with the "Please hang up and try again" message from BT.

I have programmed it manually with a DECT handset, following these steps:

• Set Non-Managed mode (**#0000*0*8)
• Set Daytime time band (***07001900*5)
• Set Weekend time band (***6000172359*6)
• Set the internal clock (**#0000*17197010712*2)
• Set local STD code (***01438*4)
• Clear the Carrier Code Table (**#0000*2222*6)
• Clear the Routing Code Table (**#0000*1111*6)
• Program entries into the Carrier Code Table (*#**18185*1)etc.
• Program entries into the Routing Code Table (*###*2*9#4110#01#) for local etc.

It is labelled as a V4 Plus, but came with no power adapter.
I first tried programming and making calls with no power.
Then I tried programming it and making calls with an adapter (input: 100-240VAC 50/60Hz 0.3A, Output:+12V 0.8A).

The red light comes on in both cases when the line is active with a dialling tone, but when power is connected there is a click from the dialler as the light comes on and goes out (the click sounds like a switch).

Is the dialler faulty?
What should happen when a call is sucessfully made through one of these diallers, (i.e. what should be heard over the handset or from the dialler etc.)?

Any help would be appreciated, because I've never experienced one working correctly, so I don't know what I should be looking out for.

rkm_hm

If you're getting a dialling tone back as soon as it's finished dialling, it sounds as if you've somehow succeeded in blocking that class of call - which would require the first digit after the *###{code}# to be a 1 (=block) rather than a 3 (=allow) or 4 (=local), etc.

When using a DECT phone to insert each sequence, did you first dial it into the DECT with the phone on hook, and then take the phone off hook to dial it in one go into the Orchid, and go on-hook again as soon as it had finished dialling? That is the most reliable method.

There's nothing obviously (to me, at any rate) wrong with the sequences you have shown. The problem with the Orchid is that there's no easy way of verifying that they have been accepted. [But see below].

Who is your default carrier - is it BT? If so, please be aware that datetime peak rate is between 0700 and 1900 not 0600-1800. Also, don't you get (at least) free weekend calls? If so, why use 18185 all the time and not just when BT charge an arm and a leg?

If your default carrier is NOT BT, are you sure that they allow you to use indirect operators such as 18185?

I program mine using a modified version of Kevin Lawry's spreadsheet in conjunction with a USB fax/modem, and even then, not all sequences are accepted first time. I have aquired a device which I mentioned earlier in the thread which enables me to see what is being dialled out to the line, to make sure that the Orchid is behaving as expected. If you're anywhere near Warwick, I may be able to connect my device to your dialler to see exactly what it's doing.

shilcor

nigelbeans wrote: »

I have recently bought one of these diallers, but I can't get it to work!

When I attempt to make a call there is a dialling tone, then the sound of the phone dialling the phone number I want to call, then the dialling tone continues until I get cut off with the "Please hang up and try again" message from BT.

Just a thought but when you are trying to make a call through the dialler, are you adding the STD code or just dialling the local number? I see that you have only programmed just a single rule for local calls in the routing table and haven't added a rule for 01 and 02 numbers. That should be OK because in theory, any call that doesn't find a match in the routing code table should be ignored and passed straight through but it might be worth trying to add a few more of the standard routing codes in case your local processing isn't working properly. I assume you didn't get any "number not recognised" recorded messages back after any of the steps you went through when you were programming your dialler? As the other Roger has said, getting dialling tone back when you try to make a call suggests call barring but as long as your steps to clear any previous routing tabel entried worked OK, then that shouldn't be the case.
I can't see anything wrong with the steps you went through or the codes you used and assume you've seen my programming guide ? (link to it in a previous post #630 in this thread).