The following table lists error message that originate from the UP.Link server. You see these errors only if you are running the UP.Simulator in UP.Link mode.
Most of these problems can be resolved only by the UP.Link server administrator.
| String | Default Message | Cause/Solution |
|---|---|---|
|
0strings
|
System error
| |
|
1000strings
|
Invalid PDU type
| The dispatcher received an invalid request packet. This is a normal status message, so no solution is necessary. |
|
1001strings
|
Invalid scheme in
URL
| |
|
1003strings
|
Failed to encrypt
reply
| |
|
1004strings
|
Failed to decrypt
request
| |
|
1005strings
|
Unregistered device
| The subscriber is attempting to use a device (UP.Phone) that is not registered or provisioned on the UP.Link server. Make sure your UP.Phone or UP.Simulator is registered on the UP.Link server you are trying to connect to. The UP.Link server for the UP.Simulator is specified in the UP.Link Settings dialog box. For more information on registering your UP.Simulator, see UP.Link mode. |
|
1006strings
|
Invalid session ID
| |
|
1007strings
|
Client protocol
mismatch
| |
|
1008strings
|
Invalid cipher
parameters
| |
|
1009strings
|
Invalid server nonce
| An unregistered phone is impersonating a valid user. This may be caused by an attempted "man-in-the-middle" security attack. |
|
1016strings
|
Transaction was
cancelled
| |
|
1017strings
|
Request PDU is out
of sequence
| The Dispatcher got packets out of sequence. This is a normal status message, so no solution is necessary. |
|
1021strings
|
Internal server
error
| |
|
1028strings
|
Client protocol
error
| |
|
1029strings
|
Key exchange is
disabled
| The subscriber attempted to initiate a key exchange when key exchange was disabled. |
|
1030strings
|
Bad key was
generated, try again
| The crypto-ignition process (used to establish encrypted, authenticated communication between the UP.Link server and the UP.Phone) was unable to generate a strong key. |
|
1031strings
|
Unable to find your
certificate
| |
|
1032strings
|
You have been
redirected
| |
|
1033strings
|
Authentication error
| Authentication between the UP.Link server and the phone has failed. |
|
1034strings
|
Duplicate request
received
| |
|
1035strings
|
Internal UP.Link
error
| |
|
1036strings
|
Internal UP.Link
error
| |
|
1037strings
|
Internal UP.Link
error
| |
|
1038strings
|
This device is
disabled
| |
|
1039strings
|
You must perform key
exchange
| |
|
1040strings
|
You must verify your
key
| You must verify the key (by calling the UP.Link server operator). |
|
1041strings
|
Failed to decrypt
session request
| |
|
1042strings
|
Failed to encrypt
session reply
| |
|
1043strings
|
Protocol version
error
| The phone is requesting an obsolete version of HDTP. Your UP.Phone or UP.Simulator model might be obsolete. |
|
1044strings
|
HTTP response
exceeded limit
| The service has returned an HTTP response that exceeds the limit configured for the UP.Link server. |
|
4005strings
|
Internal fax manager
error
| The Fax Manager was not able to create a fax job spool file for this fax in the fax spool directory. The fax spool directory is either full or permissions are set incorrectly. |
|
4006strings
|
Internal fax manager
error
| The Fax Manager was not able to write the fax job to the spool directory. This normally occurs when the fax spool directory is full. |
|
4007strings
|
Internal fax manager
error
| The Fax Manager was not able to open the fax spool directory in order to purge the expired fax spool files. The directory either does not exist or the permissions are set incorrectly. |
|
4008strings
|
Fax interface is
disabled
|
The Fax Manager was not accessible when the |
|
4009strings
|
Internal fax manager
error
|
The Fax Manager was restarted and the |
|
5001.hdml
|
Invalid transmission
format
|
The phone is sending invalid data. This deck is in |
|
5002.hdml
|
Invalid transmission
frame type
|
The phone is sending invalid data. This deck is in |