Re: [SR-Users] TSILO question

[Federico Cabiddu]

Hi,
about your questions:

Q1: yes it's feasible as long as the two Registrars (Kamailio) have the
location information. Please see my reply on a thread on this topic:
http://lists.sip-router.org/pipermail/sr-users/2016-February/091612.html

Q2: given that TSILO depends on the users' location you have to put it in
the Registrar.

Best regards,

Federico

On Wed, Nov 30, 2016 at 5:32 AM, C. J Hsu (徐熙杰)  wrote:

> hi Federico
>
> i'm stuck at TSILO and wondering if you could give me some advises.
>
> Q1:
>
> in lab1, I'm having two Kamailios with proxy and registrar together, UA1
> and UA2.
> UAs go thru hardware load-balancing device (F5) to register themselves in
> Kamailio,
>
> I wonder, UA1 calling to UA2, invite suspended in Kamailio 1, waiting for
> UA2;
> and when UA2 come to register in Kamailio 2, TSILO in Kamailio 1 resumes
> the invite and sending it to Kamailio 2, is this a no problem scenario?
>
> Q2:
>
> if we decide to separate Proxy and Registrar in different Kamailio, when
> should I put TSILO in?
>
>
> RGDS
>
> C J
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] tsilo question

[Federico Cabiddu]

Hi,
currently the module depends on registrar module to append new branches:
basically it forces a lookup and update the dset for the transaction. So
adding the Contact(s) of the 302 (if I understand correctly what you want
to do) is not possible, maybe it could be a feature to add. As Daniel
suggested I would handle this in branch_failure_route with get_redirects
from the uac_redirect module.

Regards,

Federico


On Tue, Dec 2, 2014 at 4:16 PM, Daniel-Constantin Mierla 
wrote:

> Hello,
>
> Might work easier via failue_branch_route than reply route, as there it
> gets the request for processing.
>
> Cheers,
> Daniel
>
>
> On Tuesday, December 2, 2014, Klaus Darilion 
> wrote:
>
>> Hi!
>>
>> Currently tsilo allows to add branches in failure route or request route
>> (e.g. on REGISTER).
>>
>> would be be possible to allow this function also in reply routes? E.g.
>> if one branch replies with 3xx, to add a new branch to the CFWD target
>> but still have the other branches ringing.
>>
>> regards
>> Klaus
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
> --
> Daniel-Constantin Mierla - http://www.asipto.com
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond
> 
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] tsilo question

[Daniel-Constantin Mierla]

Hello,

Might work easier via failue_branch_route than reply route, as there
it gets the
request for processing.

Cheers,
Daniel

On Tuesday, December 2, 2014, Klaus Darilion 
wrote:

> Hi!
>
> Currently tsilo allows to add branches in failure route or request route
> (e.g. on REGISTER).
>
> would be be possible to allow this function also in reply routes? E.g.
> if one branch replies with 3xx, to add a new branch to the CFWD target
> but still have the other branches ringing.
>
> regards
> Klaus
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org 
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>


-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] tsilo question

[Klaus Darilion]

Hi!

Currently tsilo allows to add branches in failure route or request route
(e.g. on REGISTER).

would be be possible to allow this function also in reply routes? E.g.
if one branch replies with 3xx, to add a new branch to the CFWD target
but still have the other branches ringing.

regards
Klaus

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users