RTP session create restriction!

Wowza Streaming Engine
1

we’ve a live Stream running in our wowza server. Now, if user access the stream from vlc player, We get the user agent information from wowza_access log. and if user access the stream from browser, then the stream is played by vlc player too and we get the user agent information is same! we actually want to restrict the access from vlc player directly. But if the two user agent information is same, the how can we differentiate the access and block the direct access?? the access_logger information is given below:

2015-02-15 17:33:19 BDT comment server INFO 200 - trueAccessLog: onRTPSessionCreate: 2025882039 - - - 16416.324 – - - - - - - - - - - - - - - - - - - - - – -

2015-02-15 17:33:19 BDT comment server INFO 200 - trueAccessLog: onRTPSessionCreate: ipAddress192.168.56.1 - - - 16416.332 - - - - - - - - - - - - - - - - - - - – - - - -

2015-02-15 17:33:19 BDT comment server INFO 200 - trueAccessLog: onRTPSessionCreate: queryStrnull - - - 16416.333 – - - - - - - - - - - - - - - - - - - - - – -

2015-02-15 17:33:19 BDT comment server INFO 200 - trueAccessLog: onRTPSessionCreate: referrernull - - - 16416.334 – - - - - - - - - - - - - - - - - - - - - – -

2015-02-15 17:33:19 BDT comment server INFO 200 - trueAccessLog: onRTPSessionCreate: userAgentLibVLC/2.1.5 (LIVE555 Streaming Media v2014.05.27) - - - 16416.334 - - - - - - - - - - - - - - - – - - - - - - - -

2015-02-15 17:33:19 BDT comment server INFO 200 - trueAccessLog: onRTPSessionCreate: uriStrrtsp://192.168.56.101:1935/live/mystream – - 16416.338 - - - - - - - - - - - - - - - - - – - - - - - -

2

Hi,

The guide given here shows how you would block the user agent.

I don’t think there is a way through userAgent you can tell the difference, and the information is easily changed/faked.

Daren

3

daren_j, Yes, you are right. The useragent information is not enough to block! then, what can we do to detect direct access to our streaam from vlc player??