[Spce-user] Peer configuration to only accept caller ID range in ougoing traffic

[Vincent Dubois]

12345678[0-9]{4}@example.com<mailto:4%7D at example.com> is a subset of 123[1-9][0-9]{8}@example.com<mailto:8%7D at example.com> 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….

Anyway go back and look at your screenshot from trunk2, you are missing an “@”

What I would do is give trunk1 priority over trunk2,
and the first pattern on trunk1 would be
12345678[0-9]{4}@example.com<mailto:4%7D at example.com>  with the stop flag
Second pattern on trunk1
123[1-9][0-9]{8}@example.com<mailto:8%7D at example.com>  no stop flag
And one pattern on trunk2
123[1-9][0-9]{8}@example.com<mailto:8%7D at example.com>

That way whatever match 12345678[0-9]{4}@example.com<mailto:4%7D at example.com>  should go out on trunk1 and stop there.


From: Rickey <rickey58 at gmail.com>
Sent: Thursday, January 4, 2024 5:14 AM
To: spce-user <spce-user at lists.sipwise.com>
Subject: [Spce-user] Peer configuration to only accept caller ID range in ougoing traffic

Hi,

Kindly request help with the following setup:
My domain is: example.com<http://example.com>
I have 2 peers configured, I would like to:
One of them (trunk1) accepted any callerID in outgoing traffic from the range:
123[1-9][0-9]{8}@example.com<mailto:8%7D at example.com>

and

The second (trunk2) which should not accept outgoing traffic from the following callerID range:
12345678[0-9]{4}@example.com<mailto:4%7D at example.com>

but accept:

123[1-9][0-9]{8}@example.com<mailto:8%7D at example.com>
or, even better: to prioritize outgoing calls from callerID:
12345678[0-9]{4}@example.com<mailto:4%7D at example.com>
were performed by trunk1 and trunk2 was treated as a failover for the above-mentioned callerID.

I tried in Settings|Peering|trunk2, in the 'Outbound Peering Rules' section, in the 'Caller Pattern' rule, add:
^(?!12345678[0-9]{4}example\.com$).*$

However, calls to the sample callerID:
123456781234 are still executed by this peer.

Screenshots of the current configuration are attached.
[cid:image001.png at 01DA4210.359E55D0]
[cid:image002.png at 01DA4210.359E55D0]

BR,
Rickey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240108/f593bc06/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 84416 bytes
Desc: image001.png
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240108/f593bc06/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 98580 bytes
Desc: image002.png
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240108/f593bc06/attachment-0003.png>