LINE Port=>InboundCallRoute max length
karog:
Getting no response, I decided to experiment. The answer is complicated.
First, it appears that trying to submit a too long value will simply fail and not alter the device. You don't get an error of any kind but you also don't get the "successful" message and the request to reboot.
I did a binary search on length for InboundCallRoute trying various lengths. Too long failed and short enough succeeded after which I also verified the saved value. In my case the max length was 1433. I didn't know then if that was all extra available memory of just that field. I tried similar in User Defined Digit Maps field. They too came in around 1433 or so.
I then tried to put long values in several Digit Maps fields and this failed at first. But then I discovered I could put in several long values as long as I submitted (but not rebooted) after each one individually. I have tested up to four long values in Digit Maps fields and now have a vague recollection that a fifth failed.
My purpose was to create a long block list. I now define 4 Digit Maps fields as ignore0, ignore1, ignore2, and ignore3. I reference all of these in the InboundCallRoute. I have chosen to store at most 100 10 digit numbers plus |'s and enclosing () for a total of 1101 chars per map. This allows me to block up to 400 numbers. I could probably increase the number per map to 125 giving me 500 blocked numbers. Of course I could look for patterns and capture redundancy but I find no real need.
Right now I have about 120 blocked numbers so I have plenty of head room and use only ignore0 and ignore1. In ignore2 and ignore3 I use a default value of (0000000000) until my list grows that long.
It seems to work pretty well and the block list can be shared among trunks so I reference it in the InboundCallRoute of both the Line port and SP1.
giqcass:
A user defined macro could replace
"ignore0, ignore1, ignore2, and ignore3" in the InboundCallRoute.
What you have done has got me wondering if the process of adding blocked number could be refined.
karog:
Quote from: giqcass on December 17, 2014, 07:29:37 am
A user defined macro could replace
"ignore0, ignore1, ignore2, and ignore3" in the InboundCallRoute.
What you have done has got me wondering if the process of adding blocked number could be refined.
I am not familiar with user defined macros in this context. Would you elaborate? Give an example?
giqcass:
A user defined macro is like a variable. It can be used to pull data from a system variable or it can contain static data. It's useful if you want to use the same value in many places. I haven't used one in the InboundCallRoute however it should work if you set "ExpandIn = ALL". It would only be worth the added fuss if you mess with the InboundCallRoute a lot.
System Management
>>>>>>>>>>>>>>>Auto Provisioning
>>>>>>>>>>>>>>>>>>>>>>>>>>Set User Defined Macro 0 as follows.
Value = whatever you want
ExpandIn = ALL
Now $UDM0 = whatever you want
EDIT: I'm trying to work out if it is possible to add numbers to the blocked list from the phone keypad.
karog:
Quote from: giqcass on December 17, 2014, 09:18:51 am
A user defined macro is like a variable. It can be used to pull data from a system variable or it can contain static data. It's useful if you want to use the same value in many places. I haven't used one in the InboundCallRoute however it should work if you set "ExpandIn = ALL". It would only be worth the added fuss if you mess with the InboundCallRoute a lot.
System Management>>>Auto Provisioning>>>Set User Defined Macro 0 as follows.
Value = whatever you want
ExpandIn = ALL
Now $UDM0 = whatever you want
EDIT: I'm trying to work out if it is possible to add numbers to the blocked list from the phone keypad.
Thanks for the response.
I keep a txt file with the numbers I block, one per line. And I allow comments so I can include numbers I don't want to block but want to notate because they contain poor callerID info so that I don't accidentally block them in the future eg amazon help callback, google voice verification callback, etc.
I actually keep two copies of the file. One is what is currently stored on the OBi and one is a copy that I edit. Then I run a bash script I wrote that compares the two files and constructs the changed Digit Maps and writes out the the modified ones with their names so that I can easily copy and paste them in.
That is certainly more work than pushing a quick phone keypad combo but works for me. If you come up with something along that line, I would appreciate hearing about it.
EDIT: Now that I think about it, rather than using a User Defined Macro to consolidate the ignore references, I could just use another Digit Map for that. But I don't change that part of the InboundCallRoutes anyway so it is not really worth it. The main changes I make to the InboundCallRoutes is what to do with calls that pass the block filter. Right now I send them to both PH and out SP1 (a GV number) to a different GV number that rings in Hangouts on my Moto X. I might change that to send the Moto X just specific numbers rather than all non-blocked calls. I haven't decided that yet.
Navigation
[0] Message Index
[#] Next page
[*] Previous page