...
Starting with version 1.13.0, RMR provides the ability to select the endpoint for a message based on the MEID (managed equipment IDentity ID) in the message, rather than selecting the endpoint from the round-robin list for the matching route table entry. To make use of this, there must be one or more route table entries which list the special endpoint name %meid instead of providing a round robin list. As an example, consider the following route table entry:
...
meid_map | start
mme_ar | <owner-endpoint> | <meid> [<meid>...]
mme_del | <meid> [<meid>...]
meid_map | end | <count> [| <md5sum> ]
The mme_ar records are add/update records and allow for the list of MEIDs to be associated with (owned by) the indicated endpoint. The <owner-endpoint> is the hostname:port, or IP address and port, of the application which owns the MEID and thus should receive any messages which are routed based on a route table entry with %meid as the round-robin group. The mme_del records allow for MEIDs to be deleted from RMR's view. Finally, the <count> is the number of add/replace and delete records which were sent; if RMR does not match the <count> value to the number of records, then it will not add the data to the table. Updates only need to list the ownership changes that are necessary; in other words, the Route Manager does not need to supply all of the MEID relationships with each update.
The optional <md5sum> field on the end record should be the MD5 hash of all of the records between the start and end records. This allows for a more precise verification that the transmitted data was correctly received.
If a static seed file is being used for the route table, a second section can be given which supplies the MEID map. The following is a small example of a seed file:
...