Cannot create user defined digit map

<< < (2/2)

drgeoff:
Quote from: suyog on August 28, 2020, 03:15:46 pm

Thanks, drgeoff.  You are very helpful.

I have defined a digit map called "blk" as follows:
(140859xxxxx | 1630322xxxx)

So the following setting should drop all calls from all 11 digit phone numbers starting with 1408859 and 1630322, but allow everything else.  Am I right?
X_InBoundCallRoute {(Mblk):},{ph}
Note that before I edited the X_InBoundCallRoute field, its value was just "ph" (without double quotes).
Regards,
Suyog

Correct.

azrobert:
Is this working for you? GV sends an 11 digit callerid preceded by a plus, so your digit map should look like this:
(+140859xxxxx | +1630322xxxx)

drgeoff:
Quote from: Dustins on September 05, 2020, 04:22:42 am

A digit map can be used to match digits to ensure a complete number is dialed, transform dialed digits, and block numbers from being dialed. Its structure is a series of rules that read from left to right.

What are you trying to say by that "read from left to right"?

The order of the rules (the parts between the | separators) in a Digit Map does not matter.  All the rules are evaluated and considered.  Unlike the {rule} parts of an InboundCallRoute or OutboundCallRoute which are evaluated in turn, left to right and the first one found to match is acted upon and thus the order is critical.

See "Matching Against Multiple Rules in Digit Map" on page 199 of https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdf

suyog:
Quote from: azrobert on September 01, 2020, 11:56:10 am

Is this working for you? GV sends an 11 digit callerid preceded by a plus, so your digit map should look like this:
(+140859xxxxx | +1630322xxxx)


Thanks azrobert.  No it was not working because I was getting calls from the numbers I blocked.  Now I know why.  I have added the "+" and we will see how it goes.  Thanks again.

Navigation

[0] Message Index

[*] Previous page