[Spce-user] Spce-user Digest, Vol 61, Issue 4
Edo
edo.ekunwe at gmail.com
Thu Jul 11 12:06:03 EDT 2024
Solved.
*^(99888)([0-9]+)$ worked*. The issue I had was that I was using this and
replacement pattern 99888\2 at the same time not realizing that I was
stripping and adding the 99888 at the same time.
Thanks
On Thu, Jul 11, 2024 at 11:00 AM <spce-user-request at lists.sipwise.com>
wrote:
> Send Spce-user mailing list submissions to
> spce-user at lists.sipwise.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
> or, via email, send a message with subject or body 'help' to
> spce-user-request at lists.sipwise.com
>
> You can reach the person managing the list at
> spce-user-owner at lists.sipwise.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Spce-user digest..."
>
>
> Today's Topics:
>
> 1. Rewrite Rule Set number manipulation question (Edo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 10 Jul 2024 11:37:01 -0500
> From: Edo <edo.ekunwe at gmail.com>
> To: spce-user at lists.sipwise.com
> Subject: [Spce-user] Rewrite Rule Set number manipulation question
> Message-ID:
> <CAFkRdGuaYL6d_HGLn2NBxNe86k1SrM9Vsr-bV2GMWeSgC=
> 0YgQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi All,
>
> I am looking for examples on the scenario below
>
> *********************
>
> I am trying to configure the system to implement tech prefixes for
> different products. This is essentially a routing implementation.
>
>
> Scenario:
>
>
> I have 3 flavors of products that can be accessed using peer-specific
> prefixes, eg 99222 to product 1, 99555 to product 2 and 99888 to product 3
>
>
> A call comes in from Peer A with 99222e164 number, the incoming filter for
> the peer has a line item to accept this call, a fee is applied to this call
> then routed to another Peer B for termination. Before it is sent off to
> Peer B, the product prefix is stripped off then sent to the terminating
> Peer B (who does not know anything about the 99222 prefix but it may also
> request a prefix as well) e.g. change 99222e164 to 2114e164 before sending
> it to Peer B or just send e164 to Peer B ? I will like to have the
> configuration example for both scenarios for sending to Peer B.
>
> ********************
>
> I know the Rewrite Rule Sets can help me do the number manipulations but
> the examples they have are just too overly permissive for me e.g.
> ^([0-9]+)$ masks for ALL numbers....
>
> I tried using ^(99888[0-9]+)$ to mask for that particular prefix but do not
> know how to strip the first 5 numbers before sending it out. The only
> example I have is how to ADD numbers before sending it out like Replacement
> pattern "XXXXX\1" adds XXXXX to the front of the number and sends out.. If
> I wanted to add the XXXXX to the end of the e164 I do not know how to do
> that or if I wanted to strip 99888 from the number then add XXXXX to the
> front, I don't know how to do that..
>
> I also tried ^(99888)([0-9]+)$ with a Replacement pattern of "\2" with no
> success, also tried replacement pattern of "99888\2" with no success as
> well.
>
> Any ideas?
>
> Thanks
>
> --
> -----
> Ekunwe
> Tel: 601.497.3932
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240710/d1b5a1ea/attachment-0001.htm
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>
>
> ------------------------------
>
> End of Spce-user Digest, Vol 61, Issue 4
> ****************************************
>
--
-----
Ekunwe
Tel: 601.497.3932
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20240711/ce8c0560/attachment.htm>
More information about the Spce-user
mailing list