Hi,

as you noticed, currently the TSILO modulo relies on location table to append new branches. While the improvement you propose could be done and may be useful in some cases (when you want to add another branch not tight to the AoR), take in count that simply adding a branch using the contact header may not cover all you scenarios. For example nat-ed clients, clients registering through a proxy adding the Path header to the REGISTER or clients registering using sip.instance contact param. You might have to take in count all of this manually in the script, while using registrar/usrloc all of this would be handled automatically. May I ask you the reason why you don't want to use location table? If the problem is the retention in the location table you could make your client send Expire=1 so that the contact is kept in memory really the time needed to append the new branch.

Best regards,

Federico Cabiddu

On Tue, May 23, 2017 at 3:19 PM, Jayesh Nambiar <jayesh1017@gmail.com> wrote:

Hello,
I see the tsilo module works only with registered contacts using location table. Is there a possibility that the ts_append function can actually take the destination URI as an argument and append branch to respective destination?

Basically I want to avoid maintaining location table. In a typical mobile use case, where the incoming call is suspended and a push notification is generated to the called party; the called party generates a REGISTER request with expires header as 0; kamailio just extracts the contact header and sends the call.
Problem comes in when the same user receives a PUSH on another device; I cannot figure a neat way to append the same call on the new device.

Is there a better alternative to achieve this without looking up the location table. Thanks for any help.

- Jayesh

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users