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

[Stephen Donovan]

I took a different approach, rather than a Caller Pattern that matched the subscriber and forced all of their calls to that peer, I removed those rules, I have the preferred peer overall catching anything not defined, then I have the peer for the calls that have trouble completing set at a higher priority, I match Callee Pattern as 1662xxx for the handful of prefixes that I want to go to that peer, seems to work as I intend so far.

From: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Raúl Alexis Betancor Santana
Sent: Tuesday, May 17, 2016 11:08 PM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] do NOT match a string in peering rules

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<mailto:stephen at belzonicable.net>>
Para: "spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>" <spce-user at lists.sipwise.com<mailto: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<mailto: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/f4cd78da/attachment-0001.html>