I have a case where we have to use RTPProxy rather than Mediaproxy because bridging mode is required as well as far-end NAT traversal.
However, calls from some mobile SIP clients are getting 1-way audio and I think this is because the client requires the "direction:active" attribute to be present in the SDP to make it use symmetric RTP. (I have some SIP packet captures for other sites where Mediaproxy was used and they show this directive is present, but with RTPProxy it is not). I think it may need the s/w flag to be used in rtpproxy_offer, but the documentation does not explain these flags properly. Does anyone have experience of these flags or know how else it is possible to get the "direction" attribute added? Thanks. John Quick Smartvox Limited Web: www.smartvox.co.uk _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
