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

Daniel Grotti dgrotti at sipwise.com
Thu Aug 27 06:11:56 EDT 2015


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
> 



More information about the Spce-user mailing list