Author: solomax
Date: Wed Jul 13 07:01:25 2016
New Revision: 1752371
URL: http://svn.apache.org/viewvc?rev=1752371&view=rev
Log:
no jira: RTMPS instructions are updated
Modified:
openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
openmeetings/application/trunk/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
Modified:
openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml?rev=1752371&r1=1752370&r2=1752371&view=diff
==============================================================================
---
openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
(original)
+++
openmeetings/application/branches/3.1.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
Wed Jul 13 07:01:25 2016
@@ -21,9 +21,7 @@
</properties>
<body>
-
<section name="Using OpenMeetings with RTMPS and HTTPS">
-
<p>There are 3 ways the client communicates with the
server: </p>
<ul>
<li>The flash-client uses RTMP protocol to
transfer Audio/Video and
@@ -38,33 +36,20 @@
data and remote control to the server
and back
</li>
</ul>
-
</section>
-
<section name="Prerequisites">
-
<ul>
- <li>You need OpenMeetings 1.9.x for this,
OpenMeetings 1.8.x does
- not
- have those options.
- </li>
- <li>Install OpenMeetings according to the
install instructions and
- check that it runs without problems
- </li>
- <li>Rename the existing keystore file
red5/conf/keystore to
- keystore.bak
- </li>
+ <li>You need OpenMeetings 1.9.x or later for
this, OpenMeetings 1.8.x does not have those options.</li>
+ <li>Install OpenMeetings according to the
install instructions and check that it runs without problems</li>
+ <li>Rename the existing keystore file
<tt>red5/conf/keystore.jmx</tt> to <tt>red5/conf/keystore.bak</tt></li>
+ <li>Rename the existing truststore file
<tt>red5/conf/truststore.jmx</tt> to <tt>red5/conf/truststore.bak</tt></li>
</ul>
-
</section>
-
<section name="Configuring RTMPS for the Flash Client">
-
<ol>
<li>
Create a new keystore and key, use the
same password for both:<br/>
- <source>
-<![CDATA[
+ <br/><source><![CDATA[
keytool -keysize 2048 -genkey -alias red5 -keyalg RSA -keystore
red5/conf/keystore
Enter keystore password:
Re-enter new password:
@@ -83,10 +68,8 @@ What is the two-letter country code for
Is CN=demo.openmeetings.de, OU=Dev, O=OpenMeetings, L=Henderson, ST=Nevada,
C=US correct?
[no]: yes
Enter key password for <red5>
-]]>
- </source>
+]]></source>
</li>
-
<li>Generate a CSR: <source><![CDATA[keytool
-certreq -keyalg RSA -alias red5 -file red5.csr -keystore
red5/conf/keystore]]></source>
</li>
<li>Submit CSR to your CA of choice and receive
a signed certificate
@@ -113,34 +96,10 @@ Enter key password for <red5>
screen-sharing web application, you can
copy "main" keystore while testing)
</li>
</ol>
-
- </section>
-
- <section name="Set up RTMPS">
- <ol>
- <li> Default RTMPS port is 8443, you can change
it by editing <tt>red5/conf/red5.properties</tt> and change the port here:
<tt>rtmps.port=8443</tt><br/>
- Please set
<tt>rtmps.keystorepass=password</tt> and <tt>rtmps.truststorepass=password</tt>
- (password = password you set on your
new keystore(s))<br/>
- Additionally you need to set
<tt>rtmps.screen.keystorepass=screenpassword</tt> (screenpassword = password
you set on your keystore for screen-sharing application)
- </li>
- <li>
- Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
-
<tt><rtmpsslport>8443</rtmpsslport></tt>,<br/>
-
<tt><useSSL>yes</useSSL></tt> and<br/>
-
<tt><proxyType>best</proxyType></tt>
- </li>
- <li>Please NOTE https port set in
<tt>red5/conf/red5.properties</tt> should be in sync with the one set in
-
<tt>red5/webapps/openmeetings/public/config.xml</tt>
- </li>
- <li>Restart red5 and try to connect - your
connection should now be
- made via RTMPS (close port 1935 to be
sure)
- </li>
- </ol>
</section>
<section name="SSL for the web interface">
- <p>If you want to use SSL for the web interface in
addition to RTMPS,
- you need to make some further modifications.
This is mainly to secure
- the server against MITM attacks, additionally
some other features
+ <p>Please perform following steps if you want to use
SSL for the web interface.
+ This is mainly to secure the server against
MITM attacks, additionally some other features
like file uploads also use a plain HTTP
connection if this is not
done. The following instructions assume that
you have already set up
RTMPS successfully. </p>
@@ -152,28 +111,65 @@ Enter key password for <red5>
</li>
<li>
Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set
-
<tt><protocol>https</protocol></tt>
- </li>
- <li>
- Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set
-
<tt><red5httpport>5443</red5httpport></tt> port
+ <br/><source><![CDATA[
+ <protocol>https</protocol>
+ <red5httpport>5443</red5httpport>
+]]></source>
</li>
<li>
Restart red5 and try to connect to
<u>https://your.server:5443</u> - you
should be redirected to the OpenMeetings
- app and all access should be via HTTPS
or RTMPS (close port 5080 to be sure).
+ app and all access should be via HTTPS
and/or RTMPS (close port 5080 to be sure).
</li>
</ol>
</section>
-
+ <section name="Set up RTMPS">
+ <h3>Tunneling RTMPS</h3>
+ <ol>
+ <li>HTTPS need to be enabled otherwise
tunneling will not work (it can be set up using frontend nginx/apache as
well)</li>
+ <li>
+ Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
+ <br/><source><![CDATA[
+ <rtmpsslport>5443</rtmpsslport>
+ <useSSL>yes</useSSL>
+ <proxyType>none</proxyType>
+]]></source>
+ </li>
+ <li>Please NOTE <tt>rtmpsslport</tt> port set
in <tt>red5/webapps/openmeetings/public/config.xml</tt> should match
+ <tt>https</tt> port set in
<tt>red5/conf/red5.properties</tt>
+ </li>
+ <li>Restart red5 and try to connect - your
connection should now be made via RTMPS (close port 1935 to be sure)
+ </li>
+ </ol>
+ <h3>Native RTMPS</h3>
+ <ol>
+ <li> Default RTMPS port is 8443, you can change
it by editing <tt>red5/conf/red5.properties</tt> and change the port here:
<tt>rtmps.port=8443</tt><br/>
+ Please set
<tt>rtmps.keystorepass=password</tt> and <tt>rtmps.truststorepass=password</tt>
+ (password = password you set on your
new keystore(s))<br/>
+ Additionally you need to set
<tt>rtmps.screen.keystorepass=screenpassword</tt> (screenpassword = password
you set on your keystore for screen-sharing application)
+ </li>
+ <li>
+ Edit <tt>red5/conf/red5-core.xml</tt>
file:<br/>
+ UNComment <tt>RTMPS</tt> section
+ </li>
+ <li>
+ Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
+ <br/><source><![CDATA[
+ <rtmpsslport>8443</rtmpsslport>
+ <useSSL>yes</useSSL>
+ <proxyType>best</proxyType>
+]]></source>
+ </li>
+ <li>Please NOTE <tt>rtmps</tt> port set in
<tt>red5/conf/red5.properties</tt> should be in sync with the
<tt>rtmpsslport</tt> set in
+
<tt>red5/webapps/openmeetings/public/config.xml</tt>
+ </li>
+ <li>Restart red5 and try to connect - your
connection should now be made via RTMPS (close port 1935 to be sure)
+ </li>
+ </ol>
+ </section>
<section name="Credits">
-
<p>Credits goto: Nexus and Holger Rabbach for their
help and
contribution and configuration documention! </p>
-
</section>
-
-
</body>
-
</document>
Modified:
openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml?rev=1752371&r1=1752370&r2=1752371&view=diff
==============================================================================
---
openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
(original)
+++
openmeetings/application/branches/3.2.x/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
Wed Jul 13 07:01:25 2016
@@ -21,9 +21,7 @@
</properties>
<body>
-
<section name="Using OpenMeetings with RTMPS and HTTPS">
-
<p>There are 3 ways the client communicates with the
server: </p>
<ul>
<li>The flash-client uses RTMP protocol to
transfer Audio/Video and
@@ -38,33 +36,20 @@
data and remote control to the server
and back
</li>
</ul>
-
</section>
-
<section name="Prerequisites">
-
<ul>
- <li>You need OpenMeetings 1.9.x for this,
OpenMeetings 1.8.x does
- not
- have those options.
- </li>
- <li>Install OpenMeetings according to the
install instructions and
- check that it runs without problems
- </li>
- <li>Rename the existing keystore file
red5/conf/keystore to
- keystore.bak
- </li>
+ <li>You need OpenMeetings 1.9.x or later for
this, OpenMeetings 1.8.x does not have those options.</li>
+ <li>Install OpenMeetings according to the
install instructions and check that it runs without problems</li>
+ <li>Rename the existing keystore file
<tt>red5/conf/keystore.jmx</tt> to <tt>red5/conf/keystore.bak</tt></li>
+ <li>Rename the existing truststore file
<tt>red5/conf/truststore.jmx</tt> to <tt>red5/conf/truststore.bak</tt></li>
</ul>
-
</section>
-
<section name="Configuring RTMPS for the Flash Client">
-
<ol>
<li>
Create a new keystore and key, use the
same password for both:<br/>
- <source>
-<![CDATA[
+ <br/><source><![CDATA[
keytool -keysize 2048 -genkey -alias red5 -keyalg RSA -keystore
red5/conf/keystore
Enter keystore password:
Re-enter new password:
@@ -83,10 +68,8 @@ What is the two-letter country code for
Is CN=demo.openmeetings.de, OU=Dev, O=OpenMeetings, L=Henderson, ST=Nevada,
C=US correct?
[no]: yes
Enter key password for <red5>
-]]>
- </source>
+]]></source>
</li>
-
<li>Generate a CSR: <source><![CDATA[keytool
-certreq -keyalg RSA -alias red5 -file red5.csr -keystore
red5/conf/keystore]]></source>
</li>
<li>Submit CSR to your CA of choice and receive
a signed certificate
@@ -113,34 +96,10 @@ Enter key password for <red5>
screen-sharing web application, you can
copy "main" keystore while testing)
</li>
</ol>
-
- </section>
-
- <section name="Set up RTMPS">
- <ol>
- <li> Default RTMPS port is 8443, you can change
it by editing <tt>red5/conf/red5.properties</tt> and change the port here:
<tt>rtmps.port=8443</tt><br/>
- Please set
<tt>rtmps.keystorepass=password</tt> and <tt>rtmps.truststorepass=password</tt>
- (password = password you set on your
new keystore(s))<br/>
- Additionally you need to set
<tt>rtmps.screen.keystorepass=screenpassword</tt> (screenpassword = password
you set on your keystore for screen-sharing application)
- </li>
- <li>
- Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
-
<tt><rtmpsslport>8443</rtmpsslport></tt>,<br/>
-
<tt><useSSL>yes</useSSL></tt> and<br/>
-
<tt><proxyType>best</proxyType></tt>
- </li>
- <li>Please NOTE https port set in
<tt>red5/conf/red5.properties</tt> should be in sync with the one set in
-
<tt>red5/webapps/openmeetings/public/config.xml</tt>
- </li>
- <li>Restart red5 and try to connect - your
connection should now be
- made via RTMPS (close port 1935 to be
sure)
- </li>
- </ol>
</section>
<section name="SSL for the web interface">
- <p>If you want to use SSL for the web interface in
addition to RTMPS,
- you need to make some further modifications.
This is mainly to secure
- the server against MITM attacks, additionally
some other features
+ <p>Please perform following steps if you want to use
SSL for the web interface.
+ This is mainly to secure the server against
MITM attacks, additionally some other features
like file uploads also use a plain HTTP
connection if this is not
done. The following instructions assume that
you have already set up
RTMPS successfully. </p>
@@ -152,28 +111,65 @@ Enter key password for <red5>
</li>
<li>
Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set
-
<tt><protocol>https</protocol></tt>
- </li>
- <li>
- Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set
-
<tt><red5httpport>5443</red5httpport></tt> port
+ <br/><source><![CDATA[
+ <protocol>https</protocol>
+ <red5httpport>5443</red5httpport>
+]]></source>
</li>
<li>
Restart red5 and try to connect to
<u>https://your.server:5443</u> - you
should be redirected to the OpenMeetings
- app and all access should be via HTTPS
or RTMPS (close port 5080 to be sure).
+ app and all access should be via HTTPS
and/or RTMPS (close port 5080 to be sure).
</li>
</ol>
</section>
-
+ <section name="Set up RTMPS">
+ <h3>Tunneling RTMPS</h3>
+ <ol>
+ <li>HTTPS need to be enabled otherwise
tunneling will not work (it can be set up using frontend nginx/apache as
well)</li>
+ <li>
+ Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
+ <br/><source><![CDATA[
+ <rtmpsslport>5443</rtmpsslport>
+ <useSSL>yes</useSSL>
+ <proxyType>none</proxyType>
+]]></source>
+ </li>
+ <li>Please NOTE <tt>rtmpsslport</tt> port set
in <tt>red5/webapps/openmeetings/public/config.xml</tt> should match
+ <tt>https</tt> port set in
<tt>red5/conf/red5.properties</tt>
+ </li>
+ <li>Restart red5 and try to connect - your
connection should now be made via RTMPS (close port 1935 to be sure)
+ </li>
+ </ol>
+ <h3>Native RTMPS</h3>
+ <ol>
+ <li> Default RTMPS port is 8443, you can change
it by editing <tt>red5/conf/red5.properties</tt> and change the port here:
<tt>rtmps.port=8443</tt><br/>
+ Please set
<tt>rtmps.keystorepass=password</tt> and <tt>rtmps.truststorepass=password</tt>
+ (password = password you set on your
new keystore(s))<br/>
+ Additionally you need to set
<tt>rtmps.screen.keystorepass=screenpassword</tt> (screenpassword = password
you set on your keystore for screen-sharing application)
+ </li>
+ <li>
+ Edit <tt>red5/conf/red5-core.xml</tt>
file:<br/>
+ UNComment <tt>RTMPS</tt> section
+ </li>
+ <li>
+ Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
+ <br/><source><![CDATA[
+ <rtmpsslport>8443</rtmpsslport>
+ <useSSL>yes</useSSL>
+ <proxyType>best</proxyType>
+]]></source>
+ </li>
+ <li>Please NOTE <tt>rtmps</tt> port set in
<tt>red5/conf/red5.properties</tt> should be in sync with the
<tt>rtmpsslport</tt> set in
+
<tt>red5/webapps/openmeetings/public/config.xml</tt>
+ </li>
+ <li>Restart red5 and try to connect - your
connection should now be made via RTMPS (close port 1935 to be sure)
+ </li>
+ </ol>
+ </section>
<section name="Credits">
-
<p>Credits goto: Nexus and Holger Rabbach for their
help and
contribution and configuration documention! </p>
-
</section>
-
-
</body>
-
</document>
Modified:
openmeetings/application/trunk/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
URL:
http://svn.apache.org/viewvc/openmeetings/application/trunk/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml?rev=1752371&r1=1752370&r2=1752371&view=diff
==============================================================================
---
openmeetings/application/trunk/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
(original)
+++
openmeetings/application/trunk/openmeetings-server/src/site/xdoc/RTMPSAndHTTPS.xml
Wed Jul 13 07:01:25 2016
@@ -21,9 +21,7 @@
</properties>
<body>
-
<section name="Using OpenMeetings with RTMPS and HTTPS">
-
<p>There are 3 ways the client communicates with the
server: </p>
<ul>
<li>The flash-client uses RTMP protocol to
transfer Audio/Video and
@@ -38,33 +36,20 @@
data and remote control to the server
and back
</li>
</ul>
-
</section>
-
<section name="Prerequisites">
-
<ul>
- <li>You need OpenMeetings 1.9.x for this,
OpenMeetings 1.8.x does
- not
- have those options.
- </li>
- <li>Install OpenMeetings according to the
install instructions and
- check that it runs without problems
- </li>
- <li>Rename the existing keystore file
red5/conf/keystore to
- keystore.bak
- </li>
+ <li>You need OpenMeetings 1.9.x or later for
this, OpenMeetings 1.8.x does not have those options.</li>
+ <li>Install OpenMeetings according to the
install instructions and check that it runs without problems</li>
+ <li>Rename the existing keystore file
<tt>red5/conf/keystore.jmx</tt> to <tt>red5/conf/keystore.bak</tt></li>
+ <li>Rename the existing truststore file
<tt>red5/conf/truststore.jmx</tt> to <tt>red5/conf/truststore.bak</tt></li>
</ul>
-
</section>
-
<section name="Configuring RTMPS for the Flash Client">
-
<ol>
<li>
Create a new keystore and key, use the
same password for both:<br/>
- <source>
-<![CDATA[
+ <br/><source><![CDATA[
keytool -keysize 2048 -genkey -alias red5 -keyalg RSA -keystore
red5/conf/keystore
Enter keystore password:
Re-enter new password:
@@ -83,10 +68,8 @@ What is the two-letter country code for
Is CN=demo.openmeetings.de, OU=Dev, O=OpenMeetings, L=Henderson, ST=Nevada,
C=US correct?
[no]: yes
Enter key password for <red5>
-]]>
- </source>
+]]></source>
</li>
-
<li>Generate a CSR: <source><![CDATA[keytool
-certreq -keyalg RSA -alias red5 -file red5.csr -keystore
red5/conf/keystore]]></source>
</li>
<li>Submit CSR to your CA of choice and receive
a signed certificate
@@ -113,34 +96,10 @@ Enter key password for <red5>
screen-sharing web application, you can
copy "main" keystore while testing)
</li>
</ol>
-
- </section>
-
- <section name="Set up RTMPS">
- <ol>
- <li> Default RTMPS port is 8443, you can change
it by editing <tt>red5/conf/red5.properties</tt> and change the port here:
<tt>rtmps.port=8443</tt><br/>
- Please set
<tt>rtmps.keystorepass=password</tt> and <tt>rtmps.truststorepass=password</tt>
- (password = password you set on your
new keystore(s))<br/>
- Additionally you need to set
<tt>rtmps.screen.keystorepass=screenpassword</tt> (screenpassword = password
you set on your keystore for screen-sharing application)
- </li>
- <li>
- Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
-
<tt><rtmpsslport>8443</rtmpsslport></tt>,<br/>
-
<tt><useSSL>yes</useSSL></tt> and<br/>
-
<tt><proxyType>best</proxyType></tt>
- </li>
- <li>Please NOTE https port set in
<tt>red5/conf/red5.properties</tt> should be in sync with the one set in
-
<tt>red5/webapps/openmeetings/public/config.xml</tt>
- </li>
- <li>Restart red5 and try to connect - your
connection should now be
- made via RTMPS (close port 1935 to be
sure)
- </li>
- </ol>
</section>
<section name="SSL for the web interface">
- <p>If you want to use SSL for the web interface in
addition to RTMPS,
- you need to make some further modifications.
This is mainly to secure
- the server against MITM attacks, additionally
some other features
+ <p>Please perform following steps if you want to use
SSL for the web interface.
+ This is mainly to secure the server against
MITM attacks, additionally some other features
like file uploads also use a plain HTTP
connection if this is not
done. The following instructions assume that
you have already set up
RTMPS successfully. </p>
@@ -152,28 +111,65 @@ Enter key password for <red5>
</li>
<li>
Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set
-
<tt><protocol>https</protocol></tt>
- </li>
- <li>
- Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set
-
<tt><red5httpport>5443</red5httpport></tt> port
+ <br/><source><![CDATA[
+ <protocol>https</protocol>
+ <red5httpport>5443</red5httpport>
+]]></source>
</li>
<li>
Restart red5 and try to connect to
<u>https://your.server:5443</u> - you
should be redirected to the OpenMeetings
- app and all access should be via HTTPS
or RTMPS (close port 5080 to be sure).
+ app and all access should be via HTTPS
and/or RTMPS (close port 5080 to be sure).
</li>
</ol>
</section>
-
+ <section name="Set up RTMPS">
+ <h3>Tunneling RTMPS</h3>
+ <ol>
+ <li>HTTPS need to be enabled otherwise
tunneling will not work (it can be set up using frontend nginx/apache as
well)</li>
+ <li>
+ Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
+ <br/><source><![CDATA[
+ <rtmpsslport>5443</rtmpsslport>
+ <useSSL>yes</useSSL>
+ <proxyType>none</proxyType>
+]]></source>
+ </li>
+ <li>Please NOTE <tt>rtmpsslport</tt> port set
in <tt>red5/webapps/openmeetings/public/config.xml</tt> should match
+ <tt>https</tt> port set in
<tt>red5/conf/red5.properties</tt>
+ </li>
+ <li>Restart red5 and try to connect - your
connection should now be made via RTMPS (close port 1935 to be sure)
+ </li>
+ </ol>
+ <h3>Native RTMPS</h3>
+ <ol>
+ <li> Default RTMPS port is 8443, you can change
it by editing <tt>red5/conf/red5.properties</tt> and change the port here:
<tt>rtmps.port=8443</tt><br/>
+ Please set
<tt>rtmps.keystorepass=password</tt> and <tt>rtmps.truststorepass=password</tt>
+ (password = password you set on your
new keystore(s))<br/>
+ Additionally you need to set
<tt>rtmps.screen.keystorepass=screenpassword</tt> (screenpassword = password
you set on your keystore for screen-sharing application)
+ </li>
+ <li>
+ Edit <tt>red5/conf/red5-core.xml</tt>
file:<br/>
+ UNComment <tt>RTMPS</tt> section
+ </li>
+ <li>
+ Edit
<tt>red5/webapps/openmeetings/public/config.xml</tt> and set<br/>
+ <br/><source><![CDATA[
+ <rtmpsslport>8443</rtmpsslport>
+ <useSSL>yes</useSSL>
+ <proxyType>best</proxyType>
+]]></source>
+ </li>
+ <li>Please NOTE <tt>rtmps</tt> port set in
<tt>red5/conf/red5.properties</tt> should be in sync with the
<tt>rtmpsslport</tt> set in
+
<tt>red5/webapps/openmeetings/public/config.xml</tt>
+ </li>
+ <li>Restart red5 and try to connect - your
connection should now be made via RTMPS (close port 1935 to be sure)
+ </li>
+ </ol>
+ </section>
<section name="Credits">
-
<p>Credits goto: Nexus and Holger Rabbach for their
help and
contribution and configuration documention! </p>
-
</section>
-
-
</body>
-
</document>
