Hi,
o Mikko Lehto on 01/30/2011 10:56 PM:
Hi and greetings from passive follower :)
nice to hear from you :)
I think folks of mediaproxy project just recently discussed somewhat similar
scenario Juha is referring to, here is a link to discussion:
http://lists.opensips.org/pipermail/users/2011-January/016347.html
It is not exactly the same as there is no actual forked SIP branch, just
changing media source endpoint.
Is that leaky media case also handled correctly by SEMS (allthough no
parallel branch exist)?
as we are (currently) handling RTP relay in user space, we can
implement the following solutions
- stay in 'passive' mode, i.e. switch destination address any time
RTP is received from a different port
- stay in 'passive' mode for e.g. 1 second after call is
established, which should be enough to get over 'leaked' RTP, and
still does not mean we need to compare addresses every time a packet
is received
Stefan
--
Stefan Sayer
VoIP Services Consulting and Development
Warschauer Str. 24
10243 Berlin
tel:+491621366449
sip:[email protected]
email/xmpp:[email protected]
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
