[Spce-user] Peer configuration to only accept caller ID range in ougoing traffic
Rickey
rickey58 at gmail.com
Thu Jan 4 05:14:21 EST 2024
Hi,
Kindly request help with the following setup:
My domain is: 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
and
The second (trunk2) which should not accept outgoing traffic from the
following callerID range:
12345678[0-9]{4}@example.com
but accept:
123[1-9][0-9]{8}@example.com
or, even better: to prioritize outgoing calls from callerID:
12345678[0-9]{4}@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.
[image: image.png]
[image: image.png]
BR,
Rickey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240104/3108c65c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 84416 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240104/3108c65c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 98580 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240104/3108c65c/attachment-0003.png>
More information about the Spce-user
mailing list