According to the 1.5.x docs, force_rtp_proxy() is deprecated and rtpproxy_offer() and rtpproxy_answer() should be used instead.
Does that mean unforce_rtp_proxy() is also deprecated? If so, how should calls be cleaned up once a BYE is received? Is the orthodox approach to simply let the streams time out on their own, or should unforce_rtp_proxy() still be used here? What about when a CANCEL is received while the dialog is an early state -- should unforce_rtp_proxy() be used there too?
Thanks!
2009/7/6 Alex Balashov abalashov@evaristesys.com:
According to the 1.5.x docs, force_rtp_proxy() is deprecated and rtpproxy_offer() and rtpproxy_answer() should be used instead.
Does that mean unforce_rtp_proxy() is also deprecated?
I don't understand it. I expect that unforce_rtp_proxy() is still required.
Iñaki Baz Castillo schrieb:
2009/7/6 Alex Balashov abalashov@evaristesys.com:
According to the 1.5.x docs, force_rtp_proxy() is deprecated and rtpproxy_offer() and rtpproxy_answer() should be used instead.
Does that mean unforce_rtp_proxy() is also deprecated?
I don't understand it. I expect that unforce_rtp_proxy() is still required.
As there is no other function it is probably still unforce_rtp_proxy() to stop the session.
klaus
-
Alex Balashov -
Iñaki Baz Castillo -
Klaus Darilion