We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It's important, with several providers, establish some rules for send SMS. Based on the usual rules we can provide:
Also we can add support to use a caller id or presentation id depending on the same rules.
An example of configuration could be:
{routes, [ {time, {from, {0, 0, 0}}, {until, {6, 59, 59}}, {prefixes, ["33", "34", "35", "36"]}, {prov, lleida} } }, {default, lleida} ]}.
The rules are recursive so, you can combine as much as you want. The format is:
{time, {from, time()}, {until, time()}, rule()}
{days, [0..6], rule()}
{date, date(), rule()}
{prefixes, [string()], rule()}
{prov, provider()}
{default, provider()}
When a full rule (with all of their children match, the rules is applied. Else the system check the next rule. default match with everything.
default
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It's important, with several providers, establish some rules for send SMS. Based on the usual rules we can provide:
Also we can add support to use a caller id or presentation id depending on the same rules.
An example of configuration could be:
The rules are recursive so, you can combine as much as you want. The format is:
{time, {from, time()}, {until, time()}, rule()}
{days, [0..6], rule()}
{date, date(), rule()}
{prefixes, [string()], rule()}
{prov, provider()}
{default, provider()}
When a full rule (with all of their children match, the rules is applied. Else the system check the next rule.
default
match with everything.The text was updated successfully, but these errors were encountered: