URL:http://localhost:9091/EchoApp/connect
OBJECT:
{
"nodeId" : "FciyCFgg5kc2WqN1SMlYbdLh7qnkhMH8@192.168.88.59",
"appKey" : "defaultApp",
"sessionId" : "/192.168.88.254:65523/192.168.88.59:8443",
"useWsTunnel" : false,
"useWsTunnelPacketization2" : false,
"useBase64BinaryEncoding" : false,
"mediaProviders" : [ "WebRTC", "MSE", "WSPlayer" ],
"clientVersion" : "0.5.18",
"clientOSVersion" : "5.0 (Windows)",
"clientBrowserVersion" : "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0"
}
enable_extended_logging=true
client_log_level=debug
RTSP stream during audio issues are OK, the problem is with WCS (webrtc). We are using Google Chrome (Windows 10) for testing.Another question,
Where do you play the stream with audio issues. Chrome, Safari, iOS, what is the browser?
Could you send us testing RTSP stream URL too.
We will check if we can reproduce this.
Hello
Please check log
WCS_HOME/logs/flashphoner_manager.log
From this log you can get your sessionId (IP address and port)
Example:
Here sessionId is /192.168.88.254:65523/192.168.88.59:8443.Code:URL:http://localhost:9091/EchoApp/connect OBJECT: { "nodeId" : "FciyCFgg5kc2WqN1SMlYbdLh7qnkhMH8@192.168.88.59", "appKey" : "defaultApp", "sessionId" : "/192.168.88.254:65523/192.168.88.59:8443", "useWsTunnel" : false, "useWsTunnelPacketization2" : false, "useBase64BinaryEncoding" : false, "mediaProviders" : [ "WebRTC", "MSE", "WSPlayer" ], "clientVersion" : "0.5.18", "clientOSVersion" : "5.0 (Windows)", "clientBrowserVersion" : "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0" }
Debug
1. Set logs to debug in flashphoner.properties
2. Monitor flashphoner_manager.log and if the issue happens for your connection, please check what sessionId do you have.Code:enable_extended_logging=true client_log_level=debug
3. Please send to logs@flashphoner.com the following files:
Note, logs are hourly rotated. Make sure you pick up logs for latest hour.
- WCS_HOME/conf
- WCS_HOME/logs/client_logs/2017-06-27
- WCS_HOME/logs/server_logs/flashphoner.log
- WCS_HOME/logs/server_logs/flashphoner.log.
- WCS_HOME/logs/flashphoner_manager.log
- WCS_HOME/logs/flashphoner_manager.log.2017-06-28-09
For example if you tested on 10:01 AM, you may need previous log 9 AM too flashphoner.log.2017-06-28-09
Dear Max,Hello
Please check log
WCS_HOME/logs/flashphoner_manager.log
From this log you can get your sessionId (IP address and port)
Example:
Here sessionId is /192.168.88.254:65523/192.168.88.59:8443.Code:URL:http://localhost:9091/EchoApp/connect OBJECT: { "nodeId" : "FciyCFgg5kc2WqN1SMlYbdLh7qnkhMH8@192.168.88.59", "appKey" : "defaultApp", "sessionId" : "/192.168.88.254:65523/192.168.88.59:8443", "useWsTunnel" : false, "useWsTunnelPacketization2" : false, "useBase64BinaryEncoding" : false, "mediaProviders" : [ "WebRTC", "MSE", "WSPlayer" ], "clientVersion" : "0.5.18", "clientOSVersion" : "5.0 (Windows)", "clientBrowserVersion" : "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0" }
Debug
1. Set logs to debug in flashphoner.properties
2. Monitor flashphoner_manager.log and if the issue happens for your connection, please check what sessionId do you have.Code:enable_extended_logging=true client_log_level=debug
3. Please send to logs@flashphoner.com the following files:
Note, logs are hourly rotated. Make sure you pick up logs for latest hour.
- WCS_HOME/conf
- WCS_HOME/logs/client_logs/2017-06-27
- WCS_HOME/logs/server_logs/flashphoner.log
- WCS_HOME/logs/server_logs/flashphoner.log.
- WCS_HOME/logs/flashphoner_manager.log
- WCS_HOME/logs/flashphoner_manager.log.2017-06-28-09
For example if you tested on 10:01 AM, you may need previous log 9 AM too flashphoner.log.2017-06-28-09
Sounds good.I'll send you all logs you need as soon as the problem will appear again
rootWe have received IP address.
What is username?
could you try again?Unfortunately our key is refused by server.
Please re-check authorized public keys.
#Here you leave just 1 port for SIP because you don't use SIP
port_from=19999
port_to=20000
#Here you provide 10000 ports for media and streaming
media_port_from=20001
media_port_to=30000
netstat -nlp | grep :31
I'm waiting for reply from you.This is port management issue. WCS is trying to use busy ports.
To suppress this you can extend port range in flashphoner.properties:
You can monitor media ports using netstat:Code:#Here you leave just 1 port for SIP because you don't use SIP port_from=19999 port_to=20000 #Here you provide 10000 ports for media and streaming media_port_from=20001 media_port_to=30000
If latest port in the list is close to max value: 30000, for example 29933.Code:netstat -nlp | grep :31
This means that issue will happen soon when the value hits 30000 limit.
So it should work well for about 1 week without issues.
Currently we are trying to fix that. Please do not close SSH access. So we will able to monitor your server and provide an official fix and build for this issue.
I will inform you about progress.