Hello Daniel,
thank's for your help... I was thinking to use $fs (forced socket) variable
in branch_route to know what interface packet will be sending and set the
correct rtpproxy parameters (I don't know if is a better solution). I will
test your solution too.
Best Regards
2013/5/10 Daniel-Constantin Mierla <miconda(a)gmail.com>
Hello,
On 5/8/13 8:24 PM, Bruno Bresciani wrote:
Hi all,
currently I have been used kamailio and rtpproxy to listen on two
different network (bridge mode), and the register of sip users are saved on
different locations ("aliases" and "location") according the
interface
where register is received. When there is a call to a user registered, I
use the registered() function of module registrar on my route[ ] block, to
discover the network where sip user is connected and use the correct
parameters in rtpproxy functions.
From now, I need that my plataform has forking call support and when the
same sip user is registered on both networks, I have to use the
branch_route[ ] block to process every branch separately because is
necessary different rtpproxy parameters.
I am with difficult in branch_route to set the correct rtpproxy
parameters because I can't find a way to know the network that the branch
will be send. Could anybody tell me if exist a form to solve my problem?
one solution is to use a branch flag that you set at registration time
based on the network is coming on. Then in branch route you can test for
this flag.
Cheers,
Daniel
--
Daniel-Constantin Mierla -
http://www.asipto.com
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/**miconda<http://www.linkedin.com/in/miconda&…
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
*
http://asipto.com/u/katu *
______________________________**_________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http:/…