Hello,
commit 15b2c21 in sayer/sbc_rtp_relay adds symmetric RTP to the RTP
relay option for the SBC module.
Currently it works like this:
Symmetric RTP (passive mode) is enabled by
- a:direction=active in SDP
- rtprelay_force_symmetric_rtp=yes in sbc profile
- rtprelay_msgflags_symmetric_rtp=yes in sbc profile and
flag 2 set in P-MsgFlags header
In passive mode, the remote RTP address:port is learned by the first
received packet. After the first packet is received, passive mode is
switched off.
This is pretty much how symmetric RTP is implemented for other SEMS
applications, too (only that there is no force_symmetric_rtp option in
sems.conf).
Questions:
- Is this a valid approach?
- Does it work in all situations?
- Is the P-MsgFlags header used by current ser-based proxy
installations at all?
- Would it make sense to add some detection of private IP in SDP as
another option to turn on passive mode?
- Is it useful to have force_symmetric_rtp for each call leg separately?
(I would actually like to avoid featuritis, too.)
Thanks for any hints.
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
