diff --git a/doc/Configure-Sems-OpenSER-HOWTO b/doc/Configure-Sems-OpenSER-HOWTO
index 21628afb..cb76eb90 100644
--- a/doc/Configure-Sems-OpenSER-HOWTO
+++ b/doc/Configure-Sems-OpenSER-HOWTO
@@ -2,34 +2,15 @@
 *  Sems + OpenSER mini-HOWTO  *
 *******************************
 
-1. Introduction
-
-This document applies to OpenSER version 1.3 or higher.  For earlier
-versions, refer to Sems + Ser mini-HOWTO.
-
-2. Compilation
-
-Before compiling Sems for OpenSER, uncomment
-
-#          -DOpenSER
-
-lines in Makefile.defs.
-
-3. OpenSER Configuration
-
-In openser.cfg, load module mi_datafgram.so, for example:
-
-mpath="/usr/lib/openser/modules"
-loadmodule "mi_datagram.so"
-
-Define mi_datagram module parameters, for example:
-
-# -- mi_datagram params
-modparam("mi_datagram", "socket_name", "/tmp/sems_openser_sock")
-modparam("mi_datagram", "unix_socket_mode", 0600)
-modparam("mi_datagram", "unix_socket_user", "root")
-modparam("mi_datagram", "unix_socket_group", "root")
-
-4. Other Instructions
-
-Refer to Sems + Ser mini-HOWTO.
+Sems 1.0 includes plugin sipctrl.so, which turns Sems into a regular,
+RFC3261 compliant SIP user agent.  No special interaction is thus
+anymore needed between Sems and OpenSER.  Just follow the general Sems
+instructions on how to configure the user agent and how to select an
+application that Sems executes upon receiving initial INVITE.
+
+In version 1.0 of Sems, it is still possible to use the old Unix socket
+interface between Sems and OpenSER by loading plugin unixsockctrl.so
+instead of plugin sipctrl.so.  If you decide to do that, then follow the
+instructions in Configure-Sems-OpenSER-HOWTO of version 0.10.0 of Sems.
+Note, however, that this old interface is not anymore supported and will
+be completely removed in the next version of Sems.