bug since update to latest build

[Gabriel T]

hello
i just updated to the latest build, and since then there a few bugs:
when starting publishing, the published event is looping and received every few seconds

there are endless of these errors in server_logs:
03:58:16,183 INFO ManagerApiConnection - StatsSampler-608a5a41-61ee-11e7-94ca-8f0b2359a640 Config for method StreamSampleEvent not found, using defaults
03:58:16,184 INFO ManagerApiConnection - StatsSampler-608a5a41-61ee-11e7-94ca-8f0b2359a640 Config for method StreamSampleEvent not found, using defaults
03:58:16,185 INFO ManagerApiConnection - StatsSampler-608a5a41-61ee-11e7-94ca-8f0b2359a640 Config for method StreamSampleEvent not found, using defaults
03:58:16,185 INFO ManagerApiConnection - StatsSampler-608a5a41-61ee-11e7-94ca-8f0b2359a640 Config for method StreamSampleEvent not found, using defaults
03:58:16,186 INFO ManagerApiConnection - StatsSampler-608a5a41-61ee-11e7-94ca-8f0b2359a640 Config for method StreamSampleEvent not found, using defaults
03:58:16,186 INFO ManagerApiConnection - StatsSampler-608a5a41-61ee-11e7-94ca-8f0b2359a640 Config for method StreamSampleEvent not found, using defaults
03:58:16,187 INFO ManagerApiConnection - StatsSampler-608a5a41-61ee-11e7-94ca-8f0b2359a640 Config for method StreamSampleEvent not found, using defaults

edit: omg and now the sound is terrible !
edit 2: even in the demos (ex: conference), when a new stream is published, it is duplicating itself every 3 seconds

 

[Max]

This issue should be fixed in latest build 2318.
Please do

service webcallserver update

 

[Gabriel T]

i confirm, everything back to normal

 

[Gabriel T]

maybe a new bug: lets say i have 3 windows connected to the same conference app. with one i start publishing. so far its fine, i can see the stream on the 2 other windows. now i stop publishing, and restart publishing (without leaving the room). stream is published but not played (logs says "
"info" : "Session does not exist",
any clue ?

these actions were working fine yesterday before the update

 

[Max]

It was a regression. Should be fixed in 2319. Please check.

service webcallserver update

 

[Gabriel T]

i confirm, its ok now

thank you