Anyone got any more csp plugins then this
dcwfilterplugin.jar
provideridentplugin.jar
i*****plugin.jar
LoggingPlugin
If so tell us which plugins you have different so i can add more plugins thanks.
Anyone got any more csp plugins then this
dcwfilterplugin.jar
provideridentplugin.jar
i*****plugin.jar
LoggingPlugin
If so tell us which plugins you have different so i can add more plugins thanks.
Im running latest r224, it's definitely the best imo
and here is couple of suggestions ;)
<plugin class="com.bowman.cardserv.EmmAnalyzerPlugin" enabled="true" jar-file="emmanalyzerplugin.jar"/>
<plugin class="com.bowman.cardserv.CacheCoveragePlugin" enabled="true" jar-file="cachecoverageplugin.jar">
These may not work in an older version, best to upgrade me thinks :)
Thanks sync. Don't suppose you could send me the 2 jar files as i think i may have a hard time getting hold of them. Please :)
Here is the complete plugins folder, don't forget to restart CSP after adding them
What does
<plugin class="com.bowman.cardserv.EmmAnalyzerPlugin" enabled="true" jar-file="emmanalyzerplugin.jar"/>
<plugin class="com.bowman.cardserv.CacheCoveragePlugin" enabled="true" jar-file="cachecoverageplugin.jar">
these plugins do ?
can you explain?
is it smart to install them ?
EmmAnalyzerPlugin
Records emm's received from client sessions, and stores them in memory for inspection.
NOTE: For this to be useful, observe the following:
- The client(s) that is to be monitored must be set to forward all emms, and not perform any local caching.
- The client(s) should probably stay tuned to the same mux/transponder/sid for the duration of the recording.
- Emm's in memory are kept indefinately, until the plugin is restarted or disabled (could grow large).
- Limit the recording to a particular user and profile, if there is a lot of traffic.
Display More
============================================================
CacheCoveragePlugin
This plugin attempts to aid in achieving 100% cache coverage for selected profiles. It monitors the cache contents and
analyzes cw continuity for each service (this can't currently be used with systems that always zero out one cw).
Cache contributions from both local client sessions and remote ClusteredCache nodes are tracked per service.
It can detect (by looking at the cw overlaps) when there a multiple ecm sources for the same service. This typically
occurs when the same exact service is available on different transponders, or different terrestrial transmitters
separated geographically.
Average variance from the expected cw interval is measured (typically amounts to the average ecm processing time), and
continuity errors (gaps) are counted.
Data is collected for all encountered cache contexts (networkid-caid combinations) even if there is no corresponding local
profile, allowing any ClusteredCache setup to be analyzed. Backlogs of all cw's are kept up to 1 minute and can be
viewed manually for each service entry.
Additionally, the time offset for each cw is measured (counted from the first encountered cw in the validity period),
allowing the cw change distribution over time within one period to be estimated. I.e showing which services have cw
switchovers at the same time.
Display More
When you are using CSP you will have to decide what is best for your setup, this includes plugins, some use none at all some use them all when there is no need
I know what works for my setup and have it running very well, depending on the connectors, caid, remote cache and clients each setup has the settings can be very different on each one.
It may seem harsh to say this but try them and see if they work for you or if you really need them, it's the only way to do it as no 2 csp servers will ever be the same.
One bit of advice I'll give to anyone is do not use a friends config, create your own and go from there.
Don’t have an account yet? Register yourself now and be a part of our community!