How is everyone handling global CLI blocking in Multi-tenant?

[simcard]

Call Blocking... The approach for Per-domain on a multi-tenant is straightforward, but how is everyone handling global block list(s) across all domains? We've got the numbers to go into the lists, but want to block them at a global level

 

[Adrian Fretwell]

My first thought would be to move the call_block dial plan into the global context, but doing this may require some work with the SQL in /usr/share/freeswitch/scripts/app/call_block/index.lua.

Maybe the answer is to write a global call block lua script that does not reference the domain. Of course if you only have a few numbers to block, you could do this in the dialplan in the global or public context.

 

[simcard]

Thanks, Adrian. That gives me some food for thought.

We don't know what the volume will look like, so we'd like a pathway that's as simple and repeatable as possible.

So as to leave as much of the existing fusion code intact, one idea we're now looking at is duplicating the call_block dial plan and lua script, but modifying them to hard code to look up against our 'management tenant/domain' and just enter CLIs via the normal Call Block app under that tenant. We have nothing configured in the management tenant, so we can't think of anything at this stage it would cause an issue with.

The other option is writing a new app completely, but we think that's going overboard when there is already something that gets us halfway there.

 

[Adrian Fretwell]

So as to leave as much of the existing fusion code intact, one idea we're now looking at is duplicating the call_block dial plan and lua script

Sounds like a good plan...