[Spce-user] Peering Rule callee pattern NOT allow a number
stephen at belzonicable.net
Sat Oct 28 21:31:10 EDT 2017
An HTML attachment was scrubbed...
-------------- next part --------------
I filter on my pbx servers as well but I have hundreds of residential subscribers registered to sipwise directly.
Sent from my Verizon, Samsung Galaxy smartphone<div>
</div><!-- originalMessage --><div>-------- Original message --------</div><div>From: William Fulton <wfulton at thirdhatch.com> </div><div>Date: 10/28/17 8:00 PM (GMT-06:00) </div><div>To: Stephen Donovan <stephen at belzonicable.net>, Spce-user <spce-user at lists.sipwise.com> </div><div>Subject: RE: Peering Rule callee pattern NOT allow a number </div><div>
We have accomplished this by adding a peering rule to our E911 carrier with blank callee prefix and pattern, and 911 in the caller pattern. We named the rule Emergency Rule.
We also control the ability to dial 911 at the PBX level, by pattern matching on Asterisk.
This has worked for us for a few years now. I am certainly open to other precautions and protection we can put in place since rouge 911 calls can be costly.
From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Stephen Donovan
Sent: Saturday, October 28, 2017 5:36 PM
To: Spce-user <spce-user at lists.sipwise.com>
Subject: [Spce-user] Peering Rule callee pattern NOT allow a number
Is it possible to specifically NOT allow a call to go out a peer? Example, I want to block 911 from going out anywhere but the one trunk that handles E911 for me.
Belzoni Cable, LLC
SIP Solutions, LLC
16014 US Hwy 49
Belzoni, MS 39038
stephen at belzonicable.net<mailto:stephen at belzonicable.net>
More information about the Spce-user