[Spce-user] Route One Phone Number (CN or DID)

Robert Cuaresma rcuaresma at telcon.es
Fri Apr 27 04:48:35 EDT 2018


Hi list!

I solved the issue using pipe symbol on the sentence, like this:

Caller pattern: ^sips?:(?!(34123456789|34987654321)).+$

Now, all specified CLI on this sentence, be routed through the next 
priority peering group.

I hope this can help you too.

Saludos,
Robert Cuaresma


El 24/04/2018 a las 9:39, Robert Cuaresma escribió:
>
> 	
> 	Comentarios <http://aka.ms/SafetyTipsFeedback>
>
> Hi!
>
> ¿Anyone knows how to create a peering rule with two or more negative 
> patterns? Actually I have 2 rules created but doesn't works because 
> all calls go through first rule.
>
> Thanks!
>
> Saludos,
> Robert Cuaresma
>
> El 19/04/2018 a las 16:04, Robert Cuaresma escribió:
>>
>> 	
>> Este remitente no superó nuestras comprobaciones de detección de fraude y es posible que no sea quien parece ser. Obtenga información acerca de la 
>> suplantación de identidad <http://aka.ms/LearnAboutSpoofing>.
>> 	Comentarios <http://aka.ms/SafetyTipsFeedback>
>>
>> Hi!,
>>
>> I had the same question (but with caller pattern), and I had applied 
>> the regex that you say and works fine, but if I add another rule with 
>> other caller pattern it don't works. How can I add two negative 
>> rules? I have spce 4.5.6.
>>
>> The rules that i have created are this:
>>
>> Calle prefix: 34902
>> Caller pattern: ^sips?:(?!(34123456789)).+$
>>
>> Calle prefix: 34902
>> Caller pattern: ^sips?:(?!(34987654321)).+$
>>
>> Thanks a lot!
>>
>> Saludos,
>> Robert Cuaresma
>>
>> El 16/04/2018 a las 9:38, Hohl Matthias escribió:
>>>
>>> Yes, this is normal beavior.
>>>
>>> Read this 6.6.2.3 => 
>>> https://www.sipwise.org/doc/mr5.5.3/spce/ar01s06.html#_creating_peerings
>>>
>>> If you on version 5.x.x use negative lookahead to disallow this 
>>> number on your higher priority peering, so it will fallback to your 
>>> lower priority peering.
>>>
>>> Callee Prefix: .
>>>
>>> Callee Pattern: ^sips?:(?!(431234567)).+$
>>>
>>> Caller Pattern: .
>>>
>>> This means: allow every Callee number expect of 431234567 from every 
>>> subscriber.
>>>
>>> *Von:*Spce-user <spce-user-bounces at lists.sipwise.com> *Im Auftrag 
>>> von *Matt Schwinn
>>> *Gesendet:* Sonntag, 15. April 2018 19:49
>>> *An:* Daniel Grotti <dgrotti at sipwise.com>
>>> *Cc:* spce-user at lists.sipwise.com
>>> *Betreff:* Re: [Spce-user] Route One Phone Number (CN or DID)
>>>
>>> I have finally gotten around to testing this and I believe this is 
>>> incorrect, however I am using the caller pattern in this instance.  
>>> If I have the peer set at priority 9, then the pattern never 
>>> matches.  I can only get it to match if I change the priority to 1 
>>> (higher than my other peers).  Can someone verify?
>>>
>>> On Thu, Mar 1, 2018 at 10:36 AM, Daniel Grotti <dgrotti at sipwise.com 
>>> <mailto:dgrotti at sipwise.com>> wrote:
>>>
>>>     Priority does not matter, cause callee prefix match will win as
>>>     best match to the callee number.
>>>
>>>
>>>     -- 
>>>
>>>     Daniel Grotti
>>>
>>>     Head of Customer Support
>>>
>>>     Sipwise GmbH, Campus 21/Europaring F15
>>>
>>>     AT-2345 Brunn am Gebirge
>>>
>>>     Office: +43(0)130120332
>>>
>>>     Email:dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
>>>
>>>     Website:https://www.sipwise.com
>>>
>>>     On 03/01/2018 07:27 PM, Matt Schwinn wrote:
>>>
>>>         Ok excellent.  Will this simply work, or does the peering
>>>         group need to be higher priority than my default? Currently
>>>         the peer I would like it to go out is priority 2.  Also, how
>>>         would I specify several Callee numbers?  Comma separated?
>>>
>>>         Thank you again!
>>>
>>>         On Thu, Mar 1, 2018 at 9:18 AM, Daniel Grotti
>>>         <dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>> wrote:
>>>
>>>             Hi,
>>>             then specify the Callee number in teh peering rule of
>>>             peering group you want to engage.
>>>
>>>             Cheers,
>>>
>>>             -- 
>>>
>>>             Daniel Grotti
>>>
>>>             Head of Customer Support
>>>
>>>             Sipwise GmbH, Campus 21/Europaring F15
>>>
>>>             AT-2345 Brunn am Gebirge
>>>
>>>             Office: +43(0)130120332
>>>
>>>             Email: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
>>>
>>>             Website: https://www.sipwise.com
>>>
>>>             On 03/01/2018 06:14 PM, Matt Schwinn wrote:
>>>
>>>                 Callee... from one of my callers.
>>>
>>>                 On Wed, Feb 28, 2018 at 10:28 PM, Daniel Grotti
>>>                 <dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>>
>>>                 wrote:
>>>
>>>                     Hi,
>>>
>>>                     Which number is rejected? Caller number or
>>>                     callee number?
>>>
>>>                     Daniel
>>>
>>>                     Sent from my iPhone
>>>
>>>
>>>                     On 01.03.2018, at 00:41, Matt Schwinn
>>>                     <winwithschwinn at gmail.com
>>>                     <mailto:winwithschwinn at gmail.com>> wrote:
>>>
>>>                         My main provider is rejecting a phone number
>>>                         that another provider is not.  I'd like to
>>>                         route the one number to my secondary
>>>                         provider. What is the best way for me to do
>>>                         this?  I have some ideas, but I'd like
>>>                         advice from someone who has done this
>>>                         before. Thanks all!
>>>
>>>
>>>                         -- 
>>>
>>>                         Enjoy the day!
>>>                         Matt Schwinn
>>>                         TCG Technologies LLC
>>>
>>>                         and
>>>
>>>                         Company B
>>>
>>>                         209-202-3329
>>>
>>>                         www.TCGTechLLC.com <http://www.TCGTechLLC.com>
>>>
>>>                         _______________________________________________
>>>                         Spce-user mailing list
>>>                         Spce-user at lists.sipwise.com
>>>                         <mailto:Spce-user at lists.sipwise.com>
>>>                         https://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>>
>>>
>>>                 -- 
>>>
>>>                 Enjoy the day!
>>>                 Matt Schwinn
>>>                 TCG Technologies LLC
>>>
>>>                 and
>>>
>>>                 Company B
>>>
>>>                 209-202-3329
>>>
>>>                 www.TCGTechLLC.com <http://www.TCGTechLLC.com>
>>>
>>>
>>>
>>>
>>>         -- 
>>>
>>>         Enjoy the day!
>>>         Matt Schwinn
>>>         TCG Technologies LLC
>>>
>>>         and
>>>
>>>         Company B
>>>
>>>         209-202-3329
>>>
>>>         www.TCGTechLLC.com <http://www.TCGTechLLC.com>
>>>
>>>
>>>
>>>
>>> -- 
>>>
>>> Enjoy the day!
>>> Matt Schwinn
>>> TCG Technologies LLC
>>>
>>>       and
>>>
>>> Company B
>>>
>>> 209-202-3329
>>>
>>> www.TCGTechLLC.com <http://www.TCGTechLLC.com>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
>
> _______________________________________________
> 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/20180427/a094b457/attachment-0001.html>


More information about the Spce-user mailing list