<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-CA" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">12345678[0-9]{<a href="mailto:4%7D@example.com">4}@example.com</a> is a subset of 123[1-9][0-9]{<a href="mailto:8%7D@example.com">8}@example.com</a> so not sure what you mean by it should reject the first but allow the second, if you allow
the second, you allow the first….<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Anyway go back and look at your screenshot from trunk2, you are missing an “@”<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">What I would do is give trunk1 priority over trunk2,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">and the first pattern on trunk1 would be
<o:p></o:p></span></p>
<p class="MsoNormal">12345678[0-9]{<a href="mailto:4%7D@example.com">4}@example.com</a> with the stop flag<o:p></o:p></p>
<p class="MsoNormal">Second pattern on trunk1 <b><span style="mso-fareast-language:EN-US"><o:p></o:p></span></b></p>
<p class="MsoNormal">123[1-9][0-9]{<a href="mailto:8%7D@example.com">8}@example.com</a> no stop flag<o:p></o:p></p>
<p class="MsoNormal">And one pattern on trunk2<o:p></o:p></p>
<p class="MsoNormal">123[1-9][0-9]{<a href="mailto:8%7D@example.com">8}@example.com</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That way whatever match 12345678[0-9]{<a href="mailto:4%7D@example.com">4}@example.com</a> should go out on trunk1 and stop there.<span style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Rickey <rickey58@gmail.com>
<br>
<b>Sent:</b> Thursday, January 4, 2024 5:14 AM<br>
<b>To:</b> spce-user <spce-user@lists.sipwise.com><br>
<b>Subject:</b> [Spce-user] Peer configuration to only accept caller ID range in ougoing traffic<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi,<br>
<br>
Kindly request help with the following setup:<br>
My domain is: <a href="http://example.com">example.com</a><br>
I have 2 peers configured, I would like to:<br>
One of them (trunk1) accepted any callerID in outgoing traffic from the range:<br>
123[1-9][0-9]{<a href="mailto:8%7D@example.com">8}@example.com</a><br>
<br>
and<br>
<br>
The second (trunk2) which should not accept outgoing traffic from the following callerID range:<br>
12345678[0-9]{<a href="mailto:4%7D@example.com">4}@example.com</a><br>
<br>
but accept:<br>
<br>
123[1-9][0-9]{<a href="mailto:8%7D@example.com">8}@example.com</a><br>
or, even better: to prioritize outgoing calls from callerID:<br>
12345678[0-9]{<a href="mailto:4%7D@example.com">4}@example.com</a><br>
were performed by trunk1 and trunk2 was treated as a failover for the above-mentioned callerID.<br>
<br>
I tried in Settings|Peering|trunk2, in the 'Outbound Peering Rules' section, in the 'Caller Pattern' rule, add:<br>
^(?!12345678[0-9]{4}example\.com$).*$<br>
<br>
However, calls to the sample callerID:<br>
123456781234 are still executed by this peer.<br>
<br>
Screenshots of the current configuration are attached.<o:p></o:p></p>
<div>
<p class="MsoNormal"><img border="0" width="1835" height="472" style="width:19.1166in;height:4.9166in" id="Picture_x0020_1" src="cid:image001.png@01DA4210.359E55D0"><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><img border="0" width="1833" height="552" style="width:19.0916in;height:5.75in" id="Picture_x0020_2" src="cid:image002.png@01DA4210.359E55D0"><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">BR,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Rickey<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>