| * | templatename | The SMS Template containing the record, sent in the SMS/800 tmpltnm field. Note that a template name must begin with a * followed by the two alphabetic characters representing your SMS/800 Entity. |
| * | dateTime |
The effective date/time of the record. The format of
this value is:
mm/dd/yy hh:mmX/Y
where X is the meridiem (A or P), and Y is the SMS/800 timezone
indicator. An example of a valid date/time would be:
07/01/98 10:15A/C.
Be aware that Somos only allows schedule date/times
where the minute on the quarter hour
:00,
:15,
:30,
or
:45.
Any other value for minute will cause the record to fail validation. This field may also contain the value NOW to request an immediate change. |
| * | resporg | The RespOrg, sent in the SMS/800 tro field. This field also identifies the SMS/800 Entity to which this SMS Template will belong. |
| interLATACarrier | The numeric CIC code of the primary InterLATA carrier, sent in the SMS/800 iec field. | |
| intraLATACarrier | The numeric CIC code of the primary IntraLATA carrier, sent in the SMS/800 iac field. | |
| planDN | The dialed number serving as the source of the complex routing plan. Also see complexRecord below. | |
| planTemplatename | The SMS Template serving as the source of the complex routing plan. Also see complexRecord below. | |
| complexRecord | The name of the entry in the RPLAN or TRPLAN table that contains the complex routing for this record. If planDN was specified, then this value and complexRecord are used as an index into RPLAN. If planTemplatename was specified, then this value and complexRecord are used as an index into TRPLAN. If neither planDN nor planTemplatename are specified then complexRecord is assumed to be a local SMS Template plan and that value alone is used as an index into TRPLAN. | |
| notes | Commentary to be sent in the SMS/800 note field. Can be up to 151 characters. | |
| description | SMS Template description to be sent in the SMS/800 descrip field. Can be up to 40 characters. | |
| lns | The number of terminating lines sent in the SMS/800 lns field. Format is 1 to 4 decimal numerals. | |
| contactName | The name of the contact person, sent in the SMS/800 ncon field. Maximum of 30 characters. | |
| contactPhone | The Contact Phone Number, sent in the SMS/800 ctel field. Must be 10 decimal numerals. | |
| network | Network Area of Service, sent in the SMS/800 anet field. The value is a comma-separated list of valid SMS/800 network codes. | |
| state | State Area of Service, sent in the SMS/800 asta field. The value is a comma-separated list of valid SMS/800 state codes. | |
| areacode | Area Code Area of Service, sent in the SMS/800 aac field. The value is a comma-separated list of valid area codes. | |
| lata | LATA Area of Service, sent in the SMS/800 alat field. The value is a comma-separated list of valid LATAs. | |
| labels | Label Area of Service, sent in the SMS/800 albl field. The value is a comma-separated list of valid SMS/800 AOS label names. The SMS/800 MGI provides no means to define AOS labels; they must previously exist. | |
| highpriority | This parameter provides access to the SMS/800 High Priority Update feature. Setting it to 1 will tell SMS to place this customer record at the front of the SCP queue. Only a small number of these updates can be done each day. After that, if this parameter is set to 1 the message will fail. You may check the Activity Log to see how many such updates remain for the current day. |