How to set the outgoing rule?

[phoenix510]

I am using version 2.2.2 of the magicall.
May I  know how to set the outgoing rule & the contacts list format in any place?
If my contacts list all the phone number have area code example : 852XXXXXXXX , 65XXXXXXXX , 86XXXXXXXXXX , 853XXXXXXXX . When I calling 65XXXXXXXX at singapore I don't need the 65 area code but when I calling 852XXXXXXXX i needto add 001 at front (001852XXXXXXXX)?
help me, please

[admin]

I think you need a number of rules for each location and you can enable/disable rules for your need. Here are some examples:

Rule name: In Singapore
Rule type: Outgoing Call
Filter type: Specific Number
Phone #: 852*; 86*; 853*
Action1: Change dialed number
Call to: 001{phone}

Rule name: In China
Rule type: Outgoing Call
Filter type: Specific Number
Phone #: 65*; 852*; 853*
Action1: Change dialed number
Call to: 00{phone}

[phoenix510]

thanks for your reply


Rule name: In Singapore
Rule type: Outgoing Call
Filter type: Specific Number
Phone #: 852*; 86*; 853*
Action1: Change dialed number
Call to: 001{phone}

BTW when I calling this number 65XXXXXXXX in my contacts at singapore this rule can cut the 65 area code right?

[admin]

No, those rules will not cut the area code. You need two rules for each location to do that. Here are new examples.

Rule name: In Singapore 1
Rule type: Outgoing Call
Filter type: Specific Number
Phone #: 65*
Action1: Change dialed number
Call to: {phone}[-2,0]

Rule name: In Singapore 2
Rule type: Outgoing Call
Filter type: Specific Number
Phone #: 852*; 86*; 853*
Action1: Change dialed number
Call to: 001{phone}

Rule name: In China 1
Rule type: Outgoing Call
Filter type: Specific Number
Phone #: 86*
Action1: Change dialed number
Call to: {phone}[-2,0]

Rule name: In China 2
Rule type: Outgoing Call
Filter type: Specific Number
Phone #: 65*; 852*; 853*
Action1: Change dialed number
Call to: 00{phone}

Hope these rules can help you.

[phoenix510]

thanks

[Paul32]

Hi,

how would I nest rules? I am looking for an Action2 like "Pass on to next rule" (don't stop rule processing).

Overe here *31# is the code to show caller ID (per call), #31# to hide it.
When using
Rule name: Show CID
Rule type: Outgoing Call
Filter type: Outlook Category
Category: ShowCallerID
Action1: Change dialed number
Call to: *31#{phone}
calls to numbers starting with + do not work (network problem over here).

But I cannot filter for Category AND numbers starting with + to set
Call to: *31#00-{phone}


Thats what I liked to do:
Rule name: Show CID
Rule type: Outgoing Call
Filter type: Outlook Category
Category: ShowCallerID
Action1: Change dialed number
Call to: *31#{phone}
Action2: Pass on to next rule

Rule name: Reformat numbers for ShowCID
Rule type: Outgoing Call
Filter type: Specific Number
Phone #: *31#+43*
Action1: Change dialed number
Call to: *31#00-{phone}[-5,0]



So what was really helpful were Action2 "Pass on to next rule".
 
 
 Thank you, Paul

P.S. Formatting all (thousands!) of the phone number to same format is not an option because
a) 00xxx numbers do not work in all countries whilst +xxx numbers do
b) most numbers are sunchronized with the companies address book and my boss decides what is done

[admin]

This looks like a feature for improving, because at present, using Category is not able to attach a phone number filter. Maybe we may add an additional filter option to rules, in future versions.

Thanks for the suggestion.

[Paul32]

Dear admin,

I hope you don't missunderstand the possibilities: "attach a phone number filter" was an idea.
But "Action2: Pass on to next rule" was much more versatile and would help even with the present possibilities of your software.

Also, "Action2: Pass on to next rule" was pretty easy to implement, it should be possible to make that feature available with the next version.


Thanks. Paul

[Paul32]

There's a new version but w/o that feature (according to your "wahts new").
Why? It would have been SO easy!

Paul

[admin]

Hi Paul, we didn't say we would implement that feature.

[Paul32]

well, that was the most stupid of all possible answers. 

[telleuno]

Dear admin,

I hope you don't missunderstand the possibilities: "attach a phone number filter" was an idea.
But "Action2: Pass on to next rule" was much more versatile and would help even with the present possibilities of your software.

Also, "Action2: Pass on to next rule" was pretty easy to implement, it should be possible to make that feature available with the next version.


Thanks. Paul

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?????

[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

[Paul32]

well, that was the most stupid of all possible answers. 

What is especially disappointing about you not implementing that feature: Besides its huge usability improvement it would have been a very tiny effort to implement.
Just 1 new menu item and a simple {if} clause causing to jump to next rule instead of exiting .

I sincerely do not understand the point of mobiion.

[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?!

For example,

I keep absolutely all numbers in the international format (+55 11 5555-2222)
First rule checks if number begins with +5511 (if yes it changes it to 011) - a local number
Second rule checks if number begins with 00 (in case the CID identified an inbound international call number) and changes it to (00...)
Third rule checks if the number begins with + (if it was +55, it was already processed by the first rule) and replaces + with 00 for international dialing.

Etc.