You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This
setting(http://sipml5.org/docgen/symbols/SIPml.Stack.Configuration.html#enable_m
edia_stream_cache) does not work over http.
In sipml v1.4.217 it could possible to use this setting after patching
tsip_dialog_invite.prototype.new_msession_mgr function, like this - change
a.set(tmedia_session_mgr.prototype.SetParamSession(a.e_type, "ice-servers",
this.get_stack().network.ao_ice_servers),
tmedia_session_mgr.prototype.SetParamSession(a.e_type, "cache-stream",
this.get_stack().network.b_cache_stream),
tmedia_session_mgr.prototype.SetParamSession(a.e_type, "bandwidth",
this.get_session().media.o_bandwidth),
tmedia_session_mgr.prototype.SetParamSession(a.e_type, "video-size",
this.get_session().media.o_video_size));
on
a.set(tmedia_session_mgr.prototype.SetParamSession(a.e_type, "ice-servers",
this.get_stack().network.ao_ice_servers),
tmedia_session_mgr.prototype.SetParamSession(a.e_type, "cache-stream",
this.get_stack().media.b_cache_stream),
tmedia_session_mgr.prototype.SetParamSession(a.e_type, "bandwidth",
this.get_session().media.o_bandwidth),
tmedia_session_mgr.prototype.SetParamSession(a.e_type, "video-size",
this.get_session().media.o_video_size));
But in sipml5 v 1.5.222 you added handler this.o_pc.onsignalingstatechange,
which is the reason of "Failed to set local answer sdp: Called in wrong state:
STATE_SENTACCEPT" error, which I get on incoming call.
If remove this handler everything is work as well.
Original issue reported on code.google.com by d.sols...@gmail.com on 14 Jan 2015 at 1:09
The text was updated successfully, but these errors were encountered:
It's seems this issue related with my problem in
https://code.google.com/p/sipml5/issues/detail?id=209.
if you set enable_media_stream_cache to false, do you have any problem with
incoming calls?
Thanks,
Alexander.
Original comment by AP.Rol...@gmail.com on 11 Feb 2015 at 3:17
Original issue reported on code.google.com by
d.sols...@gmail.com
on 14 Jan 2015 at 1:09The text was updated successfully, but these errors were encountered: