The following table lists the Smart Alert errors for the GLENAYRE module.
|Parity error - incoming data failed the automatic parity check. Framing error - bad/missing front porch, start/stop bits. Request from billing computer longer than maximum allowed. Overrun error - characters lost by serial port.
|Delay between received characters exceeded 30 seconds.
|The request (@xx) is not currently supported by the system.
|Unsupported Key Name/Table Number
|Currently only key 01, customer number, is supported. Or, the paging system table indicated by the table number received does not exist. (@GD and @MD only).
|Unsupported Data Field
|The indicated data field name is not currently supported.
|Bad Key Field Value/Record Number
|The key field value received was an invalid customer number or an incorrectly formatted customer number. Or, The record number received either does not exist in the paging system table or it cannot be viewed/edited. (@GD and @MD only).
|Bad Data Value
|Indicated data field value was invalid or incorrectly formatted.
|Duplicated Key Field Value
|The billing computer failed to specify just one key field value.
|Illegal/Wrong Request Formatg
|Request from billing computer did not have valid format. Or, The billing computer does not recognize the CNTL-B and CNTL-D delimiters for alphatext messages (for example, ^Balphatext^D).
|No Records Found
|Bad key field value entered, or customer does not exist.
|Record Already Reserved
|The billing computer asked to modify or create a subscriber record that was in use by another part of the paging system (rare), or was in use by a GL3000 operator (common).
|Unable to Allocate Resource
|The GL3000 does not have the memory resources available to create/modify the subscriber record(s) that require message services, group call, or extended group.
|Option Not Enabled
|Cannot modify character count for TWOTONE subscribers. Cannot modify A-tone or B-tone for non-TWOTONE subs.
|The request from the billing computer to send a page (using @PO) designated a blocked coverage region.
|Unexpected end of request; more characters were expected.
|Command Too Long
|The length of the request exceeded the Computer Data Buffer Length, or was too long to be sent over the network. The maximum allowable length for data_value_list for any GCP command is 500 characters.
|Node Select Error
|The billing computer requested a computer protocol connection over the network to a GL3000 terminal that does not exist. This error will be generated for any request except the null request until a valid select node request (@SN) is made.
|Node Timed Out
|Unable to respond to the billing computer's @SN request for a protocol connection over the network The billing computer is still conversing with the local GL3000, and should not reply (the local GL3000 has already tried several times). Try again later.
|Value out of Range
|The indicated data field value is out of range.
|Data List Too Long
|There were more than 44 items in the data list of the request.
|Task is Busy
|Busy servicing another remote connection (can service only one remote connection at a time). Therefore unable to establish a connection to the billing computer. Try again later.
|No Previous Output
|The first request received from the billing computer was @RP.
|Output Will Be Too Long
|The reply to the last request is too long to transmit.
|Access to Node Denied
|Attempt to sign on to another node through the protocol port was unsuccessful (other node not responding, time out etc.)
|Key List Too Long
|There were more than 44 key fields specified in the range command.
|Unable to recognize the given range command search operator.
|No More Records Found in Search Map
|Expected to find more range command records.
|Network Session Timeout
|Range command network session timeout.
|Search Number Parse Error
|Range command failed to parse the search result number correctly.
|Database too busy for range command search.
|Invalid Search Parameter
|Illegal key value used.
|Delay before receiving @GO exceeded one minute.
|Record is Read Only
|Read-Only records cannot be edited.
|Empty Data Page
|Empty data page is discarded and not sent.
|Cannot read command string.
|Graceful shutdown initiated
|The paging terminal operator has initiated a graceful shutdown.
|The paging customer being called is presently absent.
|No Retransmission Service
|The subscriber has no retransmission service.
|The subscriber has no mailbox.
|Message Not Found
|The messages being retrieved or retransmitted do not exist.
|Page Acknowledgment Error
|Failed to guarantee the page when the page guarantee notification option is on.
|Database Update Acknowledgment Error
|Failed to guarantee the update of the database on disk when the database update notification option is on.
|Failed to retransmit messages.
|Failed to retrieve message.
|Decremental Call Count
|Subscriber has no more prepaid pages.
|Restricted Character Set
|Invalid character found in page.
|A paging message was truncated because it exceeded the Max. Data Page Length.
|Follow-me Roaming Conflict
|The system could not allow Follow-me Roaming to be enabled because Page Forwarding is active.
|No Remote Programming
|The encoding format does not support Remote Programming.
|Unavailable Option for Service Type/Encoding format
|The subscriber's service type or encoding format do no support a transparent data page (@PD) or an OTAP (@SO) request (not implemented).
|OTAP Buffer in Use
|The OTAP (@SO) request is discarded because the specified buffer is being used by a previous OTAP request that is still in progress. Not implemented.
|Set Home Index Error
|A Set Home Index (@SH) request is not sent because the subscriber is waiting for the response from a previous @SH request.
|Paging System Table Error
|A Get Data (@GD) or Modify Data (@MD) request failed because the Paging System Table was locked by another paging system task.
|Network Card Error
|An OTAP command failed because no network card is installed/initialized on the GL3000. Not implemented.
|Node Address Error
|The specified node cannot be found.
|An OTAP command failed due to a database error. Not implemented.
|No NPCS Service
|NPCS service feature is disabled for this subscriber.
|No Roaming Service
|Roaming service feature is disabled for this subscriber.
|Invalid Area Code
|Area Code is invalid or out of range.
|Reject valid Area Code
|Area Code is valid but not accepted due to lack of resources.
|Invalid Login ID
|The login ID is invalid for the GCP Server.
|The password is invalid for the GCP Server.
|Invalid Login Procedure
|The first GCP command sent by the GCP over TCP client is not the Login Verification Request.
|The Send OTAP request was rejected because another OTAP is already pending for that subscriber.
|Overlong OTAP message
|The Send OTAP request was rejected because the OTAP message exceeded the Max. Data Page Length.
|The Send OTAP request was rejected because the subscriber had not registered.
|Incorrect Device Voice Compression
|The subscriber must have a valid device voice compression if the encoding format/service type implies that compressed voice may be sent
|Device Class does not Support Service
|If a device voice compression is selected and a device class is specified, the device voice compression must be supported by the device class.