<div dir="ltr">Cool, I think I am starting to understand it a little better. Thanks a lot - will test it<div><br></div><div style>The second question that was in the initial post (or maybe I should have made it two posts?) was with regards to dealing with literally millions of numbers that need be specified for the various peers - how would one handle that?</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 17, 2013 at 5:14 PM, Daniel Grotti <span dir="ltr"><<a href="mailto:dgrotti@sipwise.com" target="_blank">dgrotti@sipwise.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Theo,<br>
<br>
Here it is how the priority works:<br>
<br>
<br>
>From the Handbook:<br>
"The selection of peering servers for outbound calls is done in the<br>
following order:<br>
1. length of the matching peering rules for a call.<br>
2. priority of the peering group.<br>
3. weight of the peering servers in the selected peering group.<br>
After one or more peering group(s) is matched for an outbound call, all<br>
servers in this group are tried, according to their weight (lower weight<br>
has more precedence). If a peering server replies with SIP codes 408,<br>
500 or 503, or if a peering server doesn’t respond at all, the next<br>
peering server in the current peering group is used as a fallback, one<br>
after the other until the call succeeds. If no more servers are left in<br>
the current peering group, the next group which matches the peering<br>
rules is going to be used"<br>
<br>
<br>
I think you can try the following solution:<br>
<br>
<br>
Peer 1 - priority 1<br>
<br>
Peeing rule 1<br>
Callee Prefix: null<br>
Caller pattern: XXX<br>
Callee pattern: null<br>
<br>
Peeing rule 2<br>
Callee Prefix: null<br>
Caller pattern: null<br>
Callee pattern: null<br>
<br>
<br>
<br>
Peer 2 - priority 1<br>
<br>
Peeing rule 1<br>
Callee Prefix: null<br>
Caller pattern: YYY<br>
Callee pattern: null<br>
<br>
Peeing rule 2<br>
Callee Prefix: null<br>
Caller pattern: null<br>
Callee pattern: null<br>
<br>
<br>
<br>
In this configuration all calls from domain XXX will match Peer 1/Peeing<br>
rule 1.<br>
If it fails, the system should try and match to Peer 2/Peeing rule 2.<br>
<br>
Same for domain YYY. It will match first Peer 2/Peeing rule 1.<br>
If it fails, the system should try and match to Peer 1/Peeing rule 2.<br>
<br>
<br>
<br>
br,<br>
Daniel<br>
<div class="im"><br>
<br>
<br>
<br>
On 04/17/2013 05:01 PM, Theo wrote:<br>
> HI Daniel<br>
><br>
> Thanks for that. I have used that part already but I don't think it<br>
> solves this?<br>
><br>
> domain xxx uses peer 1 and MUST try that peer first irrespective of<br>
> number dialed. If it fails on peer 1, it needs to go to peer 2.<br>
> domain yyy needs to go to peer 2, and MUST try that peer first<br>
> irrespective of number dialed. If it fails on peer 2, it must go to peer 1.<br>
><br>
> My understanding is that it will try a peer in the priority order that<br>
> peers have been given. But what happens when priorities are dependent on<br>
> the subscriber/domain?<br>
><br>
><br>
> On Wed, Apr 17, 2013 at 4:16 PM, Daniel Grotti <<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>>> wrote:<br>
><br>
> Hello Theo,<br>
><br>
> Under peering rules you can use 'Callee Pattern' and 'Caller Pattern'<br>
> fields.<br>
><br>
> Under Caller Pattern you can set:<br>
> "A POSIX regex matching against the full Request-URI (e.g.<br>
> '^sip:.+@example\.org$' or '^sip:431')"<br>
><br>
><br>
> Under Caller Pattern you can set:<br>
> "A POSIX regex matching against 'sip:user@domain' (e.g.<br>
> '^sip:.+@example\.org$' matching the whole URI, or '999' matching if the<br>
> URI contains '999')"<br>
><br>
> In this way you can route your calls to a specific peer based - for<br>
> example - on caller domain.<br>
><br>
><br>
> br,<br>
> Daniel<br>
><br>
><br>
><br>
><br>
> On 04/16/2013 02:02 PM, Theo wrote:<br>
> > Hi<br>
> ><br>
> > Couple questions about peering rules. My understanding is that you set<br>
> > peering rules for numbers. Is it possible to also specify a peer for a<br>
> > specific subscriber or domain? I know you can specify a domain in a<br>
> > peering rule, but what I would like to see is to simply state<br>
> somewhere<br>
> > for a domain "use this peer irrespective of number dialled"?<br>
> ><br>
> > Still on peering rules - we'd need millions of rules. Because of<br>
> number<br>
> > porting across providers, the prefix is no longer a sure way to<br>
> indicate<br>
> > to which carrier we must send the call. We have a base with<br>
> prefixes and<br>
> > an ever growing list of individual numbers that need to be routed to<br>
> > various carriers. How would we deal with this?<br>
> ><br>
> > Cheers<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Spce-user mailing list<br>
</div></div>> > <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a> <mailto:<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>><br>
<div class="im">> > <a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
> ><br>
><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
</div>> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a> <mailto:<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>><br>
<div class="HOEnZb"><div class="h5">> <a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
><br>
><br>
<br>
_______________________________________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
<a href="http://lists.sipwise.com/listinfo/spce-user" target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
</div></div></blockquote></div><br></div>