Allow endpoint selection based on meid in message
This change allows the route table to specify message types which
should route based on the MEID (managed equipment ID) in the message
buffer rather than a round-robin list. The special group entry of
%meid in the routing table causes this, and requires the route
generator to suppy RMR with a map of endpoints which currently
manage each ME.
Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I6023cc0363222c85b1b7893c573d6e3f65edd221
diff --git a/docs/config-deploy.rst b/docs/config-deploy.rst
index 1b56489..d6ae082 100644
--- a/docs/config-deploy.rst
+++ b/docs/config-deploy.rst
@@ -71,7 +71,10 @@
used for debugging, testing, or if no route table
generator process is being used to supply the route table.
If not defined, no static table is used and RMr will not
- report *ready* until a table is received.
+ report *ready* until a table is received. The static route
+ table may contain both the route table (between newrt
+ start and end records), and the MEID map (between meid_map
+ start and end records)
RMR_SRC_ID