8MS User Guide |
Terminology |
Main Help Page |
This section of the user guide defines terms and values necessary to understand 8MS, the 8MS user interface and the SMS/800 Toll-Free service.
Select a letter to quickly jump to terms beginning with that letter.
8MS Routing Sets are automatically created. When a new Toll-Free Number CAD Record is created, 8MS analyzes on the record. If an 8MS Routing Set already exists that matches this Record, then the Toll-Free Number Record is associated with the existing 8MS Routing Set. If an 8MS Routing Set is not found that matches this Record, then a new 8MS Routing Set is created and this Record is associated with that new 8MS Routing Set. Thus, 8MS Routing Sets are not explicitly created in 8MS; they are created by activating a record in SMS/800.
When an 8MS Routing Set is created, it is given a system-defined name consisting of a vertical bar (|) symbol followed by a series of digits, for example |000058362. 8MS Routing Set names can be changed using the 8MS Routing Set Mgmt screen, allowing users to give their 8MS Routing Sets more meaningful names.
An 8MS Routing Set can be used as the Source or Destination of a Copy Record or other Batch operation. The routing associated with the selected 8MS Routing Set is copied to the destination number or numbers. An 8MS Routing Set can also be used for populating the Record Management: SMS CAD, Record Management: SMS PAD, or SMS Template Management screens when creating a new Record.
8MS Routing Sets also provide a user-friendly way to identify how a set of Toll-Free Numbers are routing, using the Search Local Records screen.
The set of numbers targeted for a Batch operation is known as the Destination.
Each Entity has a limited number of SMS Templates they may create. BR Templates are not counted as part of that number.
On 8MS, a CPR is associated with a CAD on the Record Management: SMS CAD screen. Alternate names for a CPR are Routing Plan and Complex Record.
A Branch has a limited length, allowing only a few values to be stored directly on a branch. When the contents of a Branch will exceed the maximum length of the Branch, the Branch contents are stored in a Label and the Label name is shown on the Branch.
Beginning with 8MS 17.1, 8MS is capable of using either the Registry API or the MGI.
A Number List can be used as the Destination of a Copy Record or other Batch operation.
A Toll-Free Number Record may be
An SMS Template Record is a TAD record.
Every Record has a specific Effective Date/Time that indicates when this Record will go Active.
All records have an associated date/time. For records stored at Somos, the minutes portion of this date/time must be on the quarter hour (:00, :15, :30, :45). Rejected records are only stored on 8MS and may have a time other than quarter hour. This time indicates when the record was sent to Somos.
Beginning with 8MS 17.1, 8MS is capable of using either the Registry API or the MGI.
Also known as an Area of Service or AOS.
SMS/800 can refer to either the legacy system or the new TFNR system.
Every Working Toll-Free Number has a set of routing data associated with the number. This set of data defines how calls are routed to a carrier for that number and what areas may dial the number. This routing data is typically bound to the specified number via the CAD, LAD and CPR.
As an alternative to binding the routing data to a number, an SMS Template (also known as a TAD record) may be defined which contains the routing data. When this is done, the SMS Template is pointed at by the number using a Pointer record (also known as a PAD record). Multiple numbers may point at a single SMS Template.
By allowing multiple numbers to reference one SMS Template, it is no longer necessary to update the routing data of of each individual number when changing the routing. Instead, the single SMS Template is modified. Since all these number reference the SMS Template, the routing is automatically updated.
An SMS Template can be used as the Source or Destination of a Copy Record or other Batch operation.
Every Resp Org is assigned 2 test numbers from each of the active 8YY NPA's for testing purposes; these numbers are given an Unavailable status to prevent another Resp Org from reserving them in the event that the owning Resp Org accidentally spares them.
This status is used when a user searches on the Search Local Numbers screen using a Number List. Any numbers shown in the results with a status of Unknown are not on the 8MS platform.
Unsolicited Messages are designed to keep 8MS data in sync with SMS/800. If a user performs an action on another 8MS platform (i.e., another MGI client) or on the SMS/800 user interface, SMS/800 will notify 8MS that this action was taken.
The most important unsolicited messages sent from SMS/800 are notifications of number reservations, scheduling of CAD, PAD and TAD records and Resp Org changes. When 8MS receives an Unsolicited Message from SMS/800 regarding one of these items, 8MS will then send retrieve requests to SMS/800 asking for the new data. In this way, 8MS keeps it's data in sync with SMS/800.
8MS customers always have the option to turn off one or more Unsolicited Messages by submitting a request to 8MS. This is most often requested when an 8MS customer wants to avoid exceeding their number limits by disabling RespOrg changes and number reservations. This prevents 8MS from ever downloading numbers from SMS/800 without explicit user requests to do so.
Modern browsers may support additional keyword colors.