Get OpenNMS
Get Involved
Get to Know Us
From OpenNMS
Contents |
Overview
A mobile sequence monitor often involves exchanging SMS messages with or more phone numbers or network short-codes (generically, numbers). This specification covers the case where a message must be sent to a number that is unknown at the time the sequence is specified and can be discovered only by receiving a message from that number.
User Story
An SMS stock symbol lookup and quote service
The user wishes to create a mobile sequence that tests an SMS-based service as described in the following table.
| Step | Direction | Message Type | Far Number | Message Content |
|---|---|---|---|---|
| 1 | TX | SMS | 78625 | Red Hat |
| 2 | RX | 7862501 or 7862502 (load-balanced) | SMS | Red Hat Inc. symbol: RHT. Respond with 1 to get a quote for this symbol. |
| 3 | TX | 7862501 or 7862502 - depending on far number from step 2 | SMS | 1 |
| 4 | RX | 7862501 or 7862502 | SMS | Red Hat Inc. last traded at $30.12 |
Strategy
Since the validate-source element respects the convention of a leading tilde indicating regular expression syntax, one potential strategy is to create a way to use matching groups within a sequence.
Acceptance Criteria
- Any sms-request or ussd-request must be able to use a source number from earlier in the same sequence as part of its destination number or message content.
- There should exist a way to assign a source number to a session variable. This capability could be important for sequences involving several transactions.
