[Spce-user] rewrite rule

[Daniel Grotti]

Hi,
I don't understand what do you mean here.
Please enable debug 2 (ngcp-kamctl proxy fifo debug 2) and redo the
call, then checks the log and share kamailio-proxy.log.
Also, please, describer what do you want to achieve.

Daniel



On 11/25/2014 05:10 PM, Tóth Csaba wrote:
> Hi,
> thanks, now its clearer.
>
> Please see the log i linked, there are these lines:
>
> Nov 25 14:09:05 sip proxy[31192]: NOTICE: <script>: Rewriting called
> party '88' to '88' - R=sip:88 at 11.22.33.44:5060
> ID=M2U0MTk1NDlhNzdlNTRlOGY4YzhmM2NmNzlkOTU1MmM.
> ....
> Nov 25 14:09:05 sip proxy[31192]: NOTICE: <script>: Rewriting called
> party '88' to '_13' - R=sip:88 at sip.peer.hu
> ID=M2U0MTk1NDlhNzdlNTRlOGY4YzhmM2NmNzlkOTU1MmM.
>
>
> This log is generated from the rules test case i described above.
> I guess the first is the callee's inbound rules *not* match, the second
> is the peer rules match.
>
> I guess not this is the working behavior from the system what we wait.
> Do you think this is a bug in 3.4.2?
>
> Thanks,
> Csaba
>
>
>
> 2014.11.25. 15:24 keltezéssel, Daniel Grotti írta:
>> Hi,
>> this is how it works:
>>
>> 1) Local subscriber calls another local subscriber"
>>
>> Inbound rewrite rules of the caller's Domain (or the caller's subscriber
>> if it's set) takes place
>> Outbound rewrite rules of the callee's Domain (or the callee's
>> subscriber if it's set) takes place
>>
>> 2) Local subscriber calls outbound
>>
>> Inbound rewrite rules of the caller's Domain (or the caller's subscriber
>> if it's set) takes place
>> Outbound rewrite rules of the peer
>>
>> 3) Incoming call for local subscriber
>>
>> Inbound rewrite rules of the peer
>> Outbound rewrite rules of the callee's Domain (or the callee's
>> subscriber if it's set) takes place
>>
>>
>>
>>
>> Daniel
>>
>>
>>
>> On 11/25/2014 02:30 PM, Tóth Csaba wrote:
>>> Hi,
>>>
>>> i have a problem with rewrite-rules.
>>>
>>> I setted up three different rules sets: Rule3 to the subscriber, Rule2
>>> to the domain and Rule1 to the peer.
>>>
>>> Setted a ^88 match to every slot of the rules, but with different output:
>>>
>>> Rule1 In Callee match:^88 to:_11
>>> Rule1 In Caller match:^88 to:_12
>>> Rule1 Out Callee match:^88 to:_13
>>> Rule1 Out Caller match:^88 to:_14
>>>
>>> Rule2 In Callee match:^88 to:_15
>>> Rule2 In Caller match:^88 to:_16
>>> Rule2 Out Callee match:^88 to:_17
>>> Rule2 Out Caller match:^88 to:_18
>>>
>>> Rule3 In Callee match:^88 to:_19
>>> Rule3 In Caller match:^88 to:_20
>>> Rule3 Out Callee match:^88 to:_21
>>> Rule3 Out Caller match:^88 to:_22
>>>
>>>
>>> And when i place a call to 88, it is converted just to _13 at peer. This is
>>> the log: http://pastebin.com/Nk9yyrqy
>>>
>>> Why is that? None of the subscriber and the domain catches the 88?
>>>
>>> I believe this work like this:
>>> if the call comes in, either the domain or the subscriber rewrite rule
>>> evaluated (if one is setted up in the subscriber, domain priority
>>> order), than when the call goes out at peer it again evaluated by the
>>> peer's rewrite rule set.
>>>
>>> I use the latest 3.4.2 version.
>>>
>>> Thanks in advance,
>>> Csaba
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user