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

wygde3

Heinz wrote: »

Don't use Carrier No.9 - it may appear to be there, but it isn't.

The retail price of the products probably has quite an impact on whether 10+ year old software will be updated!

Sorry? 9 isn't there? :mad: Is this documented somewhere? Or just a feature? Bill Gates legacy lives on ...

On the update ... I'd love to design a new interface but just don;t know how the updating of the phone works ... is there any documentation anywhere which explains this ... may be a niche there!

Heinz

wygde3 wrote: »

Sorry? 9 isn't there? :mad: Is this documented somewhere?

See the first paragraph in the right column of Page 19 of the the Quick Start User Guide

wygde3 wrote: »

On the update ... I'd love to design a new interface but just don;t know how the updating of the phone works ... is there any documentation anywhere which explains this ... may be a niche there!

Speak to Toby. You never know, you may get a trip to China out of it!

wygde3

Thanks for your help, Heinz. Another (!) question ...

In your program I see that you have 08 calls going via 1280 (carrier entry 3). I have added some low cast carriers (e.g. 0844 200 1515 as carrier entry 5 for New Zealand which starts 00 64).

How does the routing table work in terms of precedents? So if I dial 00 64 xxxxxxx does it just use entry 5? Or does it use 5 then realise that it starts 08 (from 0844 200 1515) and so use 1280 first? In other words if I ring NZ does it end up doing 1280 and then 0844 200 1515 or does it just dial 0844 200 1515?

P.S. I'm using Primus Option 2 on a BT supplied line.

Heinz

Yes, that used to have me wondering but I then discovered that Orchid LCRs route on longest string.

Hence, although there's a routing rule which specifies ALL 08 calls should always be associated with the carrier rule which inserts a 1280 prefix, the routing rule which specifies that 0845 calls should be associated with different carrier rules (i.e. routed differently) takes precedence and is the one which is actioned.

In any case, in you 0064 example, you will dial 0064 - so the program will find the routing rule which relates to the dialling of 00 (or 0064 if you have specified a different routing for NZ specifically) and apply that carrier rule. The fact that the carrier rule associated with the 00 routing rule dials 08xx is irrelevant.

For example:

I have a routing rule which associates dialling 00 with a carrier rule which dials a 18185 prefix;

However, for Spanish landlines, I have another routing rule which associates the dialling of 0034 with the use of a carrier rule which dials an 0844 gateway provider's access number (½p/minute instead of 18185's 1p/minute);

BUT, for Spanish mobiles I have another routing rule which associates the dialling of 00346 with the use of a carrier rule which dials a 18866 prefix.

wygde3

Heinz wrote: »

Yes, that used to have me wondering but I then discovered that Orchid LCRs route on longest string.

Hence, although the program specifies ALL 08 calls should be routed via 1280, the rule which specifies that 0845 calls should be routed differently (BT-18185-18185) takes precedence and is the one which is actioned.

Ah, OK. So in my example only carrier 5 is used.

Also, I assume that when a routing code like 001 is used that even though it says this is America it will also direct calls to Canada (which start 001). I assume that there's nothing clever under the bonnet which distinguishes between an 001 to the US v an 001 to Canada?

Added to this why is there an '001 - 001' and an '001 - America' entry in the routing codes drop down list? Aren't they exactly the same?

Heinz

Have another read of post #85 - I was adding to that whilst you were posting #86.

No, there's no differentiation between USA and Canada numbers (AFAIAA, the vast majority of alternative providers charge the same for all call which start with the country code 1).

The presence of the 001 - 001 and 001 - America routing rules (both with Attribute 'A') in the drop down list is purely historical. Someone probably unnecessarily added whichever was the 'almost duplicate' but neither can now be deleted in case there's a router out there somewhere using it/them.

wygde3

Heinz wrote: »

Yes, that used to have me wondering but I then discovered that Orchid LCRs route on longest string.

Hence, although there's a routing rule which specifies ALL 08 calls should always be associated with the carrier rule which inserts a 1280 prefix, the routing rule which specifies that 0845 calls should be associated with different carrier rules (i.e. routed differently) takes precedence and is the one which is actioned.

In any case, in you 0064 example, you will dial 0064 - so the program will find the routing rule which relates to the dialling of 00 (or 0064 if you have specified a different routing for NZ specifically) and apply that carrier rule. The fact that the carrier rule associated with the 00 routing rule dials 08xx is irrelevant.

For example:

I have a routing rule which associates dialling 00 with a carrier rule which dials a 18185 prefix;

However, for Spanish landlines, I have another routing rule which associates the dialling of 0034 with the use of a carrier rule which dials an 0844 gateway provider's access number (½p/minute instead of 18185's 1p/minute);

BUT, for Spanish mobiles I have another routing rule which associates the dialing of 00346 with the use of a carrier rule which dials a 18866 prefix.

OK. I remember a few months ago that you advised that we should always flip back to BT using 1280 before using an 0844 number to guarantee the cheap rate as it's possible that some like Primus might actually charge a different rate for the 0844 numbers than published by teh low cost carriers (though highly unlikely). So it seems that the only way to do this is to ask Orchid to set up a carrier code like 128008442050505. Unfortunately this would mean a whole parallel set of numbers! (Back to my point on a previous post about redesigning CWClient to make it much more intuitive and allowing functionality such as 'and' rules as opposed to its current 'or' rules.)

Heinz

Nearly 50 of the many 0844 gateway numbers are in the Carrier rule drop down menu already. 0844 200 1515 and 0844 200 8585 are both there (both also ½p/minute).

A quick e-mail to ask for another to be added should cover it though.

wygde3

Heinz wrote: »

Nearly 50 of the many 0844 gateway numbers are in the Carrier rule drop down menu already. 0844 200 1515 and 0844 200 8585 are both there (both also ½p/minute).

A quick e-mail to ask for another to be added should cover it though.

I've been having a think and am going to try and provide some more facilities in deciding how to set up CWClient ... more in the sphere of 'which 8 carrier codes are optimal to use if you have local, mobile and several internation landline and mobile numbers you want to ring'. Don;t know if I can do it but am on my way!

are the results which go into teh UK and International CallCheckers available in some organised form? Maybe Excel or Access or such like? These will clearly be input into my idea.

Anyone know? And if they are, how do I get them?

Snapelover

Heinz, as per my recent problem I tried to do a complete reset (as per your post #862) but when I try to do the first step before I finish dialling the sequence I am told to please hang up and try again. Why is this?