[Spce-user] mr6.5.5 - block list based on Caller-ID

Henk henk at voipdigit.nl
Fri Feb 7 03:33:53 EST 2020

Hi Walter,

Just as a coincidence I had the same issue last month. I tested two 

1. Make a dummy trunk and add outbound CLI rules to 'capture' the 
disallowed traffic. The dummy trunk can just be a default Kamailio 
instance with the line

sl_send_reply("403","CLI not allowed");

I tested with another system, but you can also add a Kamailio instance 
locally on a different port.

2. Make a list of rewrite rules and rewrite all forbidden CLI's to a 
special like 'forbidden'. Then you can add some custom code in the proxy 
to reply with 403.

I'm using the last one, but I've added the custom code in another 
(Kamailio) proxy that handles my traffic to this provider:

             if ($fU=="forbidden")
                 # Illegal CLI, determined with rewrite rules
                 sl_send_reply("403","This CLI is not allowed");

I've imported the rules directly in provisioning.voip_rewrite_rules as 
the UI is not suited to add around 100 rules I have.

Hope this helps,


Henk Plessius


On 07-Feb-20 08:12, Walter Klomp via Spce-user wrote:
> Hi,
> We need to block inbound calls based on CallerID.  Is there a "global" 
> version, or a list which I can apply to multiple peers and subscribers 
> (some sip trunk customers have wildcard caller-id).
> I was hoping on Admin NCOS, but that only blocks on outgoing calls. 
> (on called number).
> Hope some of you have some idea?
> Thanks
> Walter.
> The contents of this email and any attachments are confidential and 
> may also be privileged. You must not disseminate the contents of this 
> email and any attachments without permission of the sender. If you 
> have received this email by mistake, please delete all copies and 
> inform the sender immediately. You may refer to our company's Privacy 
> Policy here 
> <https://myrepublic.net/sg/legal/terms-of-use-policies/privacy-policy/>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20200207/bf7513b1/attachment-0002.html>

More information about the Spce-user mailing list