[Spce-user] CLIR and Rewrite Rules
Daniel Grotti
dgrotti at sipwise.com
Thu Oct 22 06:00:10 EDT 2015
Hi Jon,
we will improve that.
Idea is to add stoppers in Rewriting rules, so you can decide to stop
after a certain rewrite rules or instead to go ahead by matching the
next rewrite rules, so you can perform changes is one shot.
This needs to be investigated and implemented though.
--
Daniel Grotti
VoIP Engineer
Sipwise GmbH
Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
On 10/22/2015 11:46 AM, Jon Bonilla (Manwe) wrote:
> El Thu, 22 Oct 2015 11:10:43 +0200
> "Jon Bonilla (Manwe)" <manwe at sipdoc.net> escribió:
>
>> El Thu, 22 Oct 2015 10:40:12 +0200
>> Daniel Grotti <dgrotti at sipwise.com> escribió:
>>
>>> Hi Jon!
>>> well, the reason is that in this way we can let the customer able to
>>> change the format of VSC (*XX*) with rewrite rules as well, if they want.
>>>
>>
>> Makes sense. I will have to modify all the rewrite rules though.
>>
>> thanks Daniel
>
>
> What about in this only case if we call dialplan functions twice? One before
> ROUTE_CLIR as it is now and the other one inside ROUTE_CLIR. That way you can
> get both: Code rewrite and number normalization without having to put *31* in
> your callee_in rewrite rules.
>
> That should work IMHO and would make thing easier.
>
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
More information about the Spce-user
mailing list