Orchid V4, V4+ Programing Tool Support

rkm_hm

These diallers do seem to have their quirks!
I'm using an adapation of Kevin's spreadsheet - modified for my own requirements. I'm using a USB modem to send the programming instructions to the dialler.
When I tried to send the whole routing table at one go, it failed totally, and was only sending 3 or 4 characters for each row instead of the whole string. When I resorted to sending one line at a time, it was much better. Even then, I found it essential to check each code using the little box which I referred to earlier in this thread - so as to see exactly what is being dialled out. For some reason which I can't explain, some lines needed to be sent several times before they got the right message - which sounds a bit like your problem. [Your method of listening for the "x pence per minute" message is ok - but nothing like as good as actually seeing what is being dialled out - particularly if you are using more than one of the 1899/18866/18185-type operators, as I am.

I can't really explain why two different diallers make the same mistake - maybe the quirks are more systematic than I thought!

Incidentally, are you sure that your daytime settings are correct? They may be right for Primus - I don't know - but BT changed to 0700-1900 quite a while ago.

Bigun28

Yes, it is a strange problem because initially I just pulled out my old spreadsheet (as supplied by Kevin) that I used before and just re-entered everything into the dialler via the DTMF coding. I've actually done this a couple of times now and each time gives the same result. I've tried leaving it for a couple of hours after setting it up in case it needed to 'bed in' for some reason, but nothing seemed to help.

In terms of the daytime settings et al, I did think that was initially a problem. So to work around it I set the dialler to send all calls (day, evening and weekend) through 18185 (origonally I had day calls through 18185 and evening and weekend through Primus). But the dialler just won't auto send anything to 18185. The call just connects through the Dialler, straight into Primus for the connection. However, if I manually put 18185 before the number I call, it connects through 18185 as normal (with the tariff message).

rkm_hm

It sounds as if you might have a problem with the carrier code bit of the setup. If 18185 is referred to in the routing table as (say) Carrier #3, have you checked and re-sent the 3rd entry in the carrier table in case it's got corrupted?
[It would need to be something like *#**18185*3 - with the final digit reflecting the actual position in the table].

shilcor

Randal wrote: »

As I programme each step, I pre-dial my phone, then press call and hear the tones being dialled, and also notice the red light light up on the V4 dialler, hang up and then dial the next code, as I've always done before. Sometimes I get 'Number has not been recognised etc.

That definitely isn't right - you shouldn't ever get that if you've entered codes correctly. When I was writing my guide and playing around to test stuff, the only time I got that "number not recognised" was when I tried to program an invalid entry into the Routing Code Table. Some entries, such as call barring for example, will NOT let you enter anything other than zeros for the three Carrier Codes. I know you say you've checked your entries but I know from experience that it's only too easy to look at things you've written yourself and be convinced it's correct. That's why I was grateful to Heinz for sanity checking my guide as I was writing it! If you can post your spreadsheet that you're using as reference (if you are doing that) or send it to me I'm happy to take a look. Just PM me and I'll give you an email address to send it to as I'm not sure you can send files via PM's here. For the record, I use exactly the same method of programming as you using a BT Paragon 500 phone - namely, pre-dial the code and then press the "handsfree" button which gets dialling tone and then dials the code I've punched in. As soon as the tones have stopped I just press "Handsfree" again to hang up.

Heinz

As the only thing you've changed is the Non-Managed Mode, how about trying setting it to Managed Mode again?

IIRC, the sequence is **#0000*1*8

Bigun28

shilcor wrote: »

That definitely isn't right - you shouldn't ever get that if you've entered codes correctly. When I was writing my guide and playing around to test stuff, the only time I got that "number not recognised" was when I tried to program an invalid entry into the Routing Code Table. Some entries, such as call barring for example, will NOT let you enter anything other than zeros for the three Carrier Codes. I know you say you've checked your entries but I know from experience that it's only too easy to look at things you've written yourself and be convinced it's correct. That's why I was grateful to Heinz for sanity checking my guide as I was writing it! If you can post your spreadsheet that you're using as reference (if you are doing that) or send it to me I'm happy to take a look. Just PM me and I'll give you an email address to send it to as I'm not sure you can send files via PM's here. For the record, I use exactly the same method of programming as you using a BT Paragon 500 phone - namely, pre-dial the code and then press the "handsfree" button which gets dialling tone and then dials the code I've punched in. As soon as the tones have stopped I just press "Handsfree" again to hang up.

Just PM'd you.

Equinox1000

Apologies if stating the obvious, but you have cleared the existing program before you re-program with the spreadsheet? As I recall, there is a code to do this in the spreadsheet.

Also, try not listening in to the call because this can cause voltage differentials which scupper the programming.

Finally, another really obvious one - your modem is dialler side of the 'phone line, yes?

shilcor

Randal wrote: »

Just PM'd you.

Replied to your PM (twice!) but nothing back from you - is your email working properly?

Bigun28

All - I really aprpeciate the help and advice thus far.

Shilcor - Apologies but I've been out of the country for a few days and got back today and have just noted your reply in my e-mail Inbox. So I will forward the spreadsheet to you this weekend and would appreciate a sanity check of my entries.

Equinox1000 - You raise some interesting points and thanks for the inputs. I did use the codes (on the spreadsheet) to clear both tables so that I could re-programme from scratch. Did it a few times and I still had the problem.

Not listening in is an interesting thought which I will try. At the moment, I pre-dial the number of my phone, then hit the send button and listen in over the loud speaker. So perhaps try it without the loud speaker?

In terms of the modem, I actually have a satelite broadband system which totally by-passes the phone line and is a stand alone device. I thought there might be some sort of issue in that the V4 would need to operate through a filter, which I did try, but it still made no difference.

shilcor

Randal wrote: »

Not listening in is an interesting thought which I will try. At the moment, I pre-dial the number of my phone, then hit the send button and listen in over the loud speaker. So perhaps try it without the loud speaker?

Should be OK because that's pretty much what I do since my phone has a handsfree mode so I pre-dial the codes, then hit the Handsfree button which effectively does the same as lifting the handset and dialling the number. There is a slight pause between hearing the dialing tone and dialing the codes. I also know for a fact that the phone I use doesn't seem to work as a fully handsfree phone, only as a monitor because if I make a handsfree call, the person the other end can't hear me so it's as if the mocrophone doesn't work. However, I know it does because I can record messages on it handsfree!