[Spce-user] do NOT match a string in peering rules

Gmail leightonbrennan at gmail.com
Wed May 18 02:45:50 EDT 2016


I think I read on a previous topic that a regular expression takes precedence over exact pattern matches. 
You probably have a reg expr matching the rule which is taking priority. 

Try creating the number using a reg expr and retest. 

Best Regards
Leighton Brennan

> On 18 May 2016, at 05:08, Raúl Alexis Betancor Santana <rabs at dimension-virtual.com> wrote:
> 
> Do te 'inverse match' ... that means, create a peering rule that matchs the calls from that susbscriber to the failing destination, and force it to goes to the specific peer group you want.
> 
> De: "Stephen Donovan" <stephen at belzonicable.net>
> Para: "spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com>
> Enviados: Miércoles, 18 de Mayo 2016 0:38:43
> Asunto: [Spce-user] do NOT match a string in peering rules
> Hello,
>  
>  
> Is it possible to NOT match a certain number in a peering rule?  I have a customer that is having trouble completing calls to one prefix out one peer.  I want to send calls to 1662836xxxx out the next available peer but all other calls to go out this peer.
>  
>  
> Stephen
>  
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160518/4c6b6eea/attachment-0001.html>


More information about the Spce-user mailing list