Re: [SR-Users] tsilo ts_append problem

Thx for your great help Federico! Regards Giovanni From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Federico Cabiddu Sent: vendredi 8 juillet 2016 08:49 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] tsilo ts_append problem Hi Giovanni, thanks for

Re: [SR-Users] tsilo ts_append problem

Hi Giovanni, thanks for testing and reporting. I will prepare a PR for this. About your solution I do agree with it, simple and effective :) Regards, Federico On Fri, Jul 8, 2016 at 8:20 AM, gmele wrote: > Hello Federico, > > your patch seems to work for us. Thx. > > For the 2 registrars needi

Re: [SR-Users] tsilo ts_append problem

Hello Federico, your patch seems to work for us. Thx. For the 2 registrars needing the transaction information, we have found another way to solve it: in our previous config, the dispatcher ds_select_dst was using algo 1 (from URI) for INVITE and REGISTER, meaning that the INVITE may be done on f

Re: [SR-Users] tsilo ts_append problem

Hi Giovanni, glad that I could help you :) About your questions: sip.instance: I've pushed in a branch ( https://github.com/kamailio/kamailio/tree/grumvalski/ts_append-instance) a change in tm t_append_branches function. Can you give it a try and let me know how it works for you? The change is rea

Re: [SR-Users] tsilo ts_append problem

Hello Federico, the dirty patch on the TM module was just for test as we are implementing our own softphone application (like yours @ Orange) based on Linphone, but in another team, so asking for changes takes time. Like you suggested, the Path module resolved our INVITE problem. Thx :-) Now, ab

Re: [SR-Users] tsilo ts_append problem

Hi Giovanni, when I suggested to disable sip.instance, really I meant in the client, since I know that linphone has an option for this. Anyway the problem is not due to your patch. If your registrar is behind a proxy, you have to enable the support for the Path header in the registrar module ( http

Re: [SR-Users] tsilo ts_append problem

Hello Federico, yes, we use the sip.instance as it is sent by our softphone. To validate it is the sip.instance that is causing the error, I patched the tm module to ignore the sip.instance in the contact info when it is written in the location table. In our system, we have a kamailio proxy and a

Re: [SR-Users] tsilo ts_append problem

Hi Giovanni, are you using sip instances and the client reconnecting is the same? There is currently a limitation in the module which prevent it from working with sip.instance, I had in mind to fix it since a while but I still haven't found the time to work on it. If it's the case, try not using si

Re: [SR-Users] tsilo ts_append problem

Hello Federico, thanks for your answer. We applied the parameter and set it to 1. we also change some of our config: Transaction store: === route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if

Re: [SR-Users] tsilo ts_append problem

Hi Giovanni, tsilo module has a parameter to specify if store the transaction with or without the domain part of the ruri: http://www.kamailio.org/docs/modules/devel/modules/tsilo.html#idp45289468. By default is disable so it will use the user part only. Regards, Federico On Wed, Jul 6, 2016 at

[SR-Users] tsilo ts_append problem

Hello, we are using tsilo to achieve mobile push notification in kamailio. In tsilo module documentation, ts_append() function is used with the pseudo variable “$tU” holding the username of the to-uri. Our config looks like : route[PUSHJOIN] { $var(hjoin) = 0; lock("$tu");