diff --git a/doc/Configure-Sems-Ser-HOWTO b/doc/Configure-Sems-Ser-HOWTO
index f4f16055..108df54e 100644
--- a/doc/Configure-Sems-Ser-HOWTO
+++ b/doc/Configure-Sems-Ser-HOWTO
@@ -1,3 +1,14 @@
+
+******* IMPORTANT ***************************************************************************
+ This is only needed if SER, the SIP Express Router, is used as SIP stack for SEMS. Since 1.0
+ you can simply use the sipctrl module, which provides a SIP stack for SEMS. sipctrl is set
+ as the default control plugin, so usually there need not be any changes in that regard.
+
+ But, if you need more functionality from the SIP stack, e.g. TLS, TCP, filtering of inbound
+ requests etc., you can use ser2 with the binrpcctl module, and the SASI SER application server
+ interface, and then parts of the information below apply.
+*********************************************************************************************
+
***************************
* Sems + Ser mini-HOWTO *
***************************
diff --git a/doc/doxyref.h b/doc/doxyref.h
index 212c5e3b..f4a3adb0 100644
--- a/doc/doxyref.h
+++ b/doc/doxyref.h
@@ -59,6 +59,15 @@
/*! \page Configure-Sems-Ser-HOWTO mini-Howto on how to configure SER and SEMS to work together
*
+ *
+ * This is only needed if SER, the SIP Express Router, is used as SIP stack for SEMS. Since 1.0
+ * you can simply use the sipctrl module, which provides a SIP stack for SEMS. sipctrl is set
+ * as the default control plugin, so usually there need not be any changes in that regard.
+ * But, if you need more functionality from the SIP stack, e.g. TLS, TCP, filtering of inbound
+ * requests etc., you can use ser2 with the binrpcctl module, and the SASI SER application server
+ * interface, and then parts of the information below apply.
+ *
+ *
* Be sure to also check the instructions that are on the page with the
*
* application development tutorial, there is step by step instructions including