[Spce-user] No rewrite on T.38 INVITE

[Tristan Delsol]

Hi Daniel,

Managed to finally get this to work. The rewrite of the RURI was 
happening too late.
At the moment I have the rewrite directly in the kamailio.cfg here:
else if(!ds_is_from_list("9"))
         {
		# added by Tristan
                 if(uri=~"sip:ngcp-lb;tgrp=9752")
                 {
                  xlog("L_NOTICE", "Rewrite uri for interworking 
fax/T.38 with KPN\n");
 
rewriteuri("sip:ngcp-lb at 87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a35303830");
                 }
		# end

		if($si != "127.0.0.1" )
                 {
                         route(ROUTE_DOS_ATTACK_CHECK);
                 }

I'm not sure how to get this code in where I want it using the 
custom.cfg file.

Thanks for all the patience and help with this!

Cheers,
Tristan

On 27-08-15 12:18, Daniel Grotti wrote:
> Well,
> you should try to do it as first thing, and then let the it through.
> if the client does not change anything else, it should work.
> You have to make sure that the result RURI is equal to the Contact
> header sent by LB in the last 200 OK.
>
>
>
> --
> Daniel Grotti
> VoIP Engineer
>
>
> Sipwise GmbH
> Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
>
> On 08/27/2015 12:13 PM, Tristan Delsol wrote:
>> Not anymore, I was doing that, but as it didn't fix the issue or
>> anything I left it out.
>> I can add it again and create new logs?
>>
>>
>>
>> On 27-08-15 12:11, Daniel Grotti wrote:
>>> Hi,
>>> are you rewriting in LB :
>>>
>>> R=sip:ngcp-lb;tgrp=9752;trunk-context=ipic.imscore.net at 87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a35303830
>>>
>>>
>>> into:
>>>
>>> R=sip:ngcp-lb at 87.239.101.193:5060;ngcpct=7369703a3132372e302e302e313a35303830
>>>
>>>
>>>
>>> as first thing ?
>>> Looks like ALL the in-dialog request (as reinvite, ACK and BYE) coming
>>> from that client has this wrong RURI.
>>>
>>> --
>>>
>>> Daniel Grotti
>>> VoIP Engineer
>>>
>>>
>>> Sipwise GmbH
>>> Europaring F15 | 2345 Brunn am Gebirge, Austria | www.sipwise.com
>>>
>>> On 08/27/2015 12:02 PM, Tristan Delsol wrote:
>>>> @Victor,
>>>> Good to know, saves me alot of time. Thanks.
>>>>
>>>> @Daniel,
>>>> Yeah that log was indeed unreadable until I used geany to read it out
>>>> and then it was do-able.
>>>> I ran the debug your way. I'm sending you the logs while I'm going
>>>> through it myself.
>>>>
>>>> Tristan
>>>>
>>>> On 26-08-15 15:58, Victor Seva wrote:
>>>>> On 08/26/2015 03:21 PM, Lorenzo Mangani wrote:
>>>>>> Tristan,
>>>>>>
>>>>>> Did not look deep but could likely a side effect to the following
>>>>>> error
>>>>>> representing over 50% of your log:
>>>>>>
>>>>>>           ERROR: pv [pv_trans.c:1022]: tr_eval_uri(): invalid uri [0]
>>>>>
>>>>> Known error with the actual config. Not related.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>> _______________________________________________
>> 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
>