How to set the outgoing rule?

[Paul32]

If you will simply put  "Action2: Do nothing", it will authomatically pass on to the next rule (if it exists). So what´s the point in implementing something that is already there?????

That's simply not true. After the first rule matching the filter MagiCall exits from rule processing.
BTW: If it wasn't like that it needed an Action2 "Exit from rule processing". Either way a very important option is missing.

Paul

Really??? Even if it was like you think it would haven´t needed  "exit from rule processing" as it does exit by itself after the last rule was processed. I have a complex set of rules (almost 11) set up, and it wors like charm.  Obviously "call to" ends all rule processing, so if your first rule will end with "call to" it won´t drop to the second rule. Don´t you see a logical contradiction in what you are trying to do. How would you expect any rules to be executed AFTER the call has been placed?!

The use of "exit from rule processing" was to avoid having all (further) rules processed. Exiting is what's happening today after the first rule that matched (try it yourself by setting up 2 rules where each adds 00 to the beginning of the phone number).
For what I'm trying to do please see Post#5 from November 13, 2009, 04:46:02 am.
I cannot write that in 1 rule as phone numbers are not uniquely formatted (some start with +43, some with 0043, some w/o country code). And as soon as I use a rule 'match category' and that rule matched it exits from rule processing.

Best regards, Paul

[telleuno]

If you will simply put  "Action2: Do nothing", it will authomatically pass on to the next rule (if it exists). So what´s the point in implementing something that is already there?????

That's simply not true. After the first rule matching the filter MagiCall exits from rule processing.
BTW: If it wasn't like that it needed an Action2 "Exit from rule processing". Either way a very important option is missing.

Paul

Really??? Even if it was like you think it would haven´t needed  "exit from rule processing" as it does exit by itself after the last rule was processed. I have a complex set of rules (almost 11) set up, and it wors like charm.  Obviously "call to" ends all rule processing, so if your first rule will end with "call to" it won´t drop to the second rule. Don´t you see a logical contradiction in what you are trying to do. How would you expect any rules to be executed AFTER the call has been placed?!

The use of "exit from rule processing" was to avoid having all (further) rules processed. Exiting is what's happening today after the first rule that matched (try it yourself by setting up 2 rules where each adds 00 to the beginning of the phone number).
For what I'm trying to do please see Post#5 from November 13, 2009, 04:46:02 am.
I cannot write that in 1 rule as phone numbers are not uniquely formatted (some start with +43, some with 0043, some w/o country code). And as soon as I use a rule 'match category' and that rule matched it exits from rule processing.

Best regards, Paul

I´ve actually added a reply belowto my original message. My mess (I am in Brazil) is actually bigger than yours, as I am forced to introduce a long distance call company prefix on long distance calls,  and I have to identify which calls are long distance and which are not, as any move from one area code to another means entering into a a roaming mode. And + for international dialing doesn´t work here either.

So first thing you have to do is to check if there is a + and replace it to 00 (that would be your first rule)
Second rule - check if there is 00 in front of number - if yes - don´t change
Third rule - check length of the number and add 00 and country code (assuming it is always the same)

If there was no + in the number you were going to dial the rule will drop to the next one
If there was no 00 it will drop to the third rule

etc.

So, there IS already  an implied "if" in the rules system. And you have to realise that what ends the rule processing is the "call to" directive. You can´t keep on processing the rules after the call is placed.

Now back to your problem (which I think have a solution).  Let me ask you why do you issue USSD CID command before every call? Do you want to show your ID only to a certain calling parties and after this change the dialed number into a necessary format? Did I get it right? Is that your issue?

[Paul32]

Could you tell me how you do it?
When I configure only two rules (to keep it pretty simple)
Rule 1:
General: Outgoing | Apply always | Always
Filter: All
Operation: Change dialed number | Call to 00{phone}
Rule 2:
General: Outgoing | Apply always | Always
Filter: All
Operation: Change dialed number | Call to 99{phone}

and then dial 1234 it doesn't dial 99001234 but only 001234.

How would you have Rule2 processed after Rule1 was applied?


Paul

[telleuno]

Could you tell me how you do it?
When I configure only two rules (to keep it pretty simple)
Rule 1:
General: Outgoing | Apply always | Always
Filter: All
Operation: Change dialed number | Call to 00{phone}
Rule 2:
General: Outgoing | Apply always | Always
Filter: All
Operation: Change dialed number | Call to 99{phone}

and then dial 1234 it doesn't dial 99001234 but only 001234.

How would you have Rule2 processed after Rule1 was applied?


Paul

Paul, sure your second rule will never be processed, as the criteria for filter in the first filter is too broad. There is no number which will not pass the first rule. Let me show how it works. Let´s assume you have a database with numbers starting with +43 and 043 and you will want to dial all of them as 0043

Rule 1:
General: Outgoing | Apply always | Always
Filter: +43*
Operation: Change dialed number | Call to 00{phone}[-1,0]

After this rule if the number was starting from +43 it will be changed to 0043 and called (exit rule processing)
All other numbers (not starting from +43) will slip to the next rule

Rule 2:
General: Outgoing | Apply always | Always
Filter: 043*
Operation: Change dialed number | Call to 0{phone}

After this rule if the number was starting from 043 it will be changed to 0043 and called (exit rule processing)
All other numbers (not starting from 043 and not starting from +43, as it was processed in the first rule) will slip to the next rule, if it exists.

And so on. So you have to be VERY specific when you set filter criteria. Broad  filter criteria are good for example if you want to drop all of your calls to the voicemail int the night time and send and SMS asking not to bother you when you sleep.

[Paul32]

 

Tha'ts what I said. After the first rule matching / being applied it exits. There's no way to have following rules applied as in "Action2: Continue with next rule".

Now how would you a) match an outlook category AND b) change the nummer depending on 0043/+43/043 prefix?
IMHO that's impossible today. Your rules may work because you only work with numbers, not categories.

Paul

[telleuno]

Tha'ts what I said. After the first rule matching / being applied it exits. There's no way to have following rules applied as in "Action2: Continue with next rule".

Now how would you a) match an outlook category AND b) change the nummer depending on 0043/+43/043 prefix?
IMHO that's impossible today. Your rules may work because you only work with numbers, not categories.

Paul

Why, of course you can!

Set up a set of rules:

Rule 1:
General: Outgoing | Apply always | Always
Filter: Outlook Category
Category: Business (or whatever)
Action1: Pass on to the next rule

After this rule only "Business" outlook category numbers will slip to the next rule. The rest will be dropped

Rule 2:
General: Outgoing | Apply always | Always
Filter: 043*
Action1: Change dialed number | Call to 0{phone}

and so on.

PS Actually if they will add Action2 - Pass on to the next rule it will not change anything in your case, as "call to" directive in Action1 will always prevent slipping to the next rule since your filtering criteria are too broad.

[Paul32]

Mate, thanks for all your effort!
That is what I was looking for!

Paul

[telleuno]

Mate, thanks for all your effort!
That is what I was looking for!

Paul

I am happy it worked for you!

[yorkhoh]

I believe I'm interested in this "Action 2 = continue to next rule" option also!

Unless someone can come up with a suitable workaround.

I'm in Australia using PennySIM with Pennytel.

I use a calling card access number for pretty much ALL numbers dialed, bar a few numbers (emergency, home, specific other mobile numbers).
13 and 1800 numbers MUST include the country code or it won't work. ie. {AccessNumber},+61{phone}

Some of my contacts in the address book have the country code - most do not. Although ALL have the area code. (I've been caught out in different cities wondering why my call wouldn't go through - so I always input area code into contacts now).
So the last rule in my list catches everything and plain "Change dialed number" and Call to: {AccessNumber},{phone}

My problem is, the {AccessNumber} can be different. Sometimes the main number is down so I revert to a different {AccessNumber2}. I have made different rules for these circumstances. When one doesn't work - I simply go into MagiCall and deactivate Rule_AccessNumber1 and activate Rule_AccessNumber2. For Rule_AccessNumber[option] I currently have 4 options (in other words, 4 different access numbers).

The issue now is the 13 and 1800 numbers that I need to "Change dialed number" for.
I want to be able to have Action1 = "Change dialed number" and then Call to = +61{phone} then have Action2 = "pass on to next rule"

Why?
Because I don't know which Rule_AccessNumber[option] I will be using.

My current rule for 13 and 1800 numbers (2 separate rules) to "Change dialed number" for Action1 and have it
Call to = {AccessNumber1},+61{phone}

Obviously, when AccessNumber1 was down for a whole day - I was unable to dial 13 or 1800 numbers easily.

There's already 9 rules in my list. I can add 2x4 = 8 more rules for 13 and 1800 numbers when the {AccessNumber} goes down and I need to switch. This would add in extra fiddling around when I'm already a bit peeved that {AccessNumber1} went down already.

Having an Action2 to continue the rule list would be great - so that I can prepend the "+61" to 13 and 1800 numbers and continue to the catch-all rule to dial the working {AccessNumber}.

Any work arounds?
and yes, I realise I can just dial +61 manually in front of all my 13 and 1800 numbers - but that's not useful for say, someone else borrowing my phone.

[telleuno]

Any "Call to" directive ends rule processing. What I would have done in your case is I would have created a second profile with the same set of rules but using a backup calling card number. In case you primary number is down just switch the profile and keep on using secondary number.

[admin]

Hi yorkhoh,

I agree with telleuno, profiles are the best solution for you.
It is not possible to execute multiple Action1 and then go to next rules, because of technical reasons.

[yorkhoh]

Hey, thanks for that!

That's so simple and effective I cannot believe I didn't think of it.

For my particular case scenario, I would still need to make multiple entries for each different "calling card numbers" for both the 13 and 18 prefixes. But at least when a "calling card number" fails, instead of pressing about 12 different items, it'd be a simple change of profile...what's that? 2 clicks?

Thanks again.