WCS5.1 on ubuntu 18.04.1 LTS License Activation Issue

S

Stanley

Member
Hi Max,
Something is very wrong with this 5.1 after changing to "-p 2001". I did a fresh install for whole server by formatting and installing WCS v5.1.3578.
Now I notice all of our users connect to this server by calling our custom appkey point to backend server URL did not actually authenticate. WCS will ignore the authentication and allow users to stream all videos. Our backend server did not receive any request from WCS too. I am sending you a new logs
 
Max

Max

Administrator
Staff member
Hello.
After a fresh WCS install, you have not added any REST method to your server application "n2app". So, you should add REST method /connect to your app
Code: 
add app-rest-method n2app connect
 
Max

Max

Administrator
Staff member
I found the issue. app-rest-method "connect" will disappeared after execute "service webcallserver restart".
Click to expand...
We reproduced this issue and will work on it (internal case WCS-1536). We let you know when fix it.
Add REST methods manually to WCS_HOME/conf/database.yml as workaround:
Code: 
...
restMethods:
  flashStreamingApp: [OnMessageEvent, XcapStatusEvent, sendDtmf, DataStatusEvent,
    ConnectionStatusEvent, sessionDebug, pauseStream, playStream, StreamTranscodingGroupEvent,
    hangup, hold, StreamStatusEvent, MessageStatusEvent, OnCallEvent, RecordingStatusEvent,
    ErrorStatusEvent, StreamsStatEvent, OnTransferEvent, availableStream, SessionDebugStatusEvent,
    BugReportStatusEvent, connect, subscribe, CallStatusEvent, sendMessage, publishStream,
    RegistrationStatusEvent, OnDataEvent, sendXcapRequest, unPublishStream, call,
    transfer, answer, stopStream, StreamKeepAliveEvent, SubscriptionStatusEvent, unhold,
    TransferStatusEvent, snapshot, pushLogs, submitBugReport]
  myAppKey: [connect]
 
Last edited:
Max

Max

Administrator
Staff member
Good day, Stanley
We fixed this issue
app-rest-method "connect" will disappeared after execute "service webcallserver restart"
Click to expand...
in version 5.1.3592, please update to this build.
As for backend interaction issue, we added the parameter
Code: 
rest_request_timeout=15
This parameter defines maximum backend server response delay duration (15 seconds by default). The less value, 1 second for example
Code: 
rest_request_timeout=1
may help to prevent WCS from stuck on REST hooks sending to custom backend under high load. Try it, please.
 
Last edited:
S

Stanley

Member
Max said:
Good day, Stanley
We fixed this issue

in version 5.1.3592, please udate to this build.
As for backend interaction issue, we added the parameter
Code: 
rest_request_timeout=15
This parameter defines maximum backend server response delay duration (15 seconds by default). The less value, 1 second for example
Code: 
rest_request_timeout=1
may help to prevent WCS from stuck on REST hooks sending to custom backend under high load. Try it, please.
Click to expand...
Code: 
rest_request_timeout=15
add this in flashphoner.properties?
 
Max

Max

Administrator
Staff member
Try to check for updates with command
Code: 
service webcallserver stop
cd /usr/local/FlashphonerWebCallServer/bin/
./webcallserver update
 
Max

Max

Administrator
Staff member
add this in flashphoner.properties?
Click to expand...
15 seconds is the default value and don't need to be added to config. If you want to check less values, 5 seconds for example, then you should add
Code: 
rest_request_timeout=5
to flashphoner.properties file.
 
S

Stanley

Member
Hi Max, I've sent you the log files thru email. Flashphoner REST Hook did not call our backend server intermittently. I have include our backend server IIS log.
 
Max

Max

Administrator
Staff member
Hello Stanley.
Your backend server log starts at 2018-10-22 02:23:11 and ends at 2018-10-22 02:23:40.
WCS server log in this interval contains no tries to connect, but RTMP publication only:
02:23:06,898 INFO ServerHandler - RTMP-pool-14-thread-52 sending bytes read ack after: 3665984828
02:23:07,000 INFO ServerHandler - RTMP-pool-14-thread-52 sending bytes read ack after: 4590050039
02:23:07,051 INFO ServerHandler - RTMP-pool-14-thread-55 sending bytes read ack after: 3666006203
02:23:08,559 INFO ServerHandler - RTMP-pool-14-thread-57 sending bytes read ack after: 2101050638
02:23:11,276 INFO ServerHandler - RTMP-pool-14-thread-54 sending bytes read ack after: 2011725943
02:23:11,326 INFO ServerHandler - RTMP-pool-14-thread-53 sending bytes read ack after: 2011725841
02:23:11,327 INFO ServerHandler - RTMP-pool-14-thread-55 sending bytes read ack after: 2011725778
02:23:11,377 INFO ServerHandler - RTMP-pool-14-thread-52 sending bytes read ack after: 2011726019
02:23:11,377 INFO ServerHandler - RTMP-pool-14-thread-56 sending bytes read ack after: 2011725778
02:23:11,426 INFO ServerHandler - RTMP-pool-14-thread-56 sending bytes read ack after: 2011725841
02:23:12,886 INFO ServerHandler - RTMP-pool-14-thread-53 sending bytes read ack after: 2179318384
02:23:13,156 INFO ServerHandler - RTMP-pool-14-thread-53 sending bytes read ack after: 2179317387
02:23:19,176 INFO ServerHandler - RTMP-pool-14-thread-57 sending bytes read ack after: 3008375033
02:23:19,326 INFO ServerHandler - RTMP-pool-14-thread-58 sending bytes read ack after: 3008375033
02:23:19,327 INFO ServerHandler - RTMP-pool-14-thread-58 sending bytes read ack after: 3008373547
02:23:21,739 INFO ServerHandler - RTMP-pool-14-thread-59 sending bytes read ack after: 2916926644
02:23:26,399 INFO ServerHandler - RTMP-pool-14-thread-52 sending bytes read ack after: 4592564606
02:23:30,242 INFO ServerHandler - RTMP-pool-14-thread-55 sending bytes read ack after: 1883453277
02:23:33,963 INFO ServerHandler - RTMP-pool-14-thread-58 sending bytes read ack after: 1883568041
02:23:38,092 INFO ServerHandler - RTMP-pool-14-thread-52 sending bytes read ack after: 3668499679
02:23:38,243 INFO ServerHandler - RTMP-pool-14-thread-55 sending bytes read ack after: 3668521042
02:23:46,432 INFO ServerHandler - RTMP-pool-14-thread-52 sending bytes read ack after: 4595069751
02:23:54,640 INFO ServerHandler - RTMP-pool-14-thread-57 sending bytes read ack after: 3010883661
02:23:54,791 INFO ServerHandler - RTMP-pool-14-thread-58 sending bytes read ack after: 3010882163
02:23:54,791 INFO ServerHandler - RTMP-pool-14-thread-58 sending bytes read ack after: 3010883661
02:23:58,209 INFO ServerHandler - RTMP-pool-14-thread-59 sending bytes read ack after: 2919431181
02:23:59,903 INFO ServerHandler - RTMP-pool-14-thread-52 sending bytes read ack after: 1143422682
Click to expand...
So we cannot correspond server logs with backend logs.
For futher help please provide us SSH access to your server, our engineers will check.
 
You must log in or register to reply here.
Top