This section documents the Parlay X fault messages.
- A policy error occurred. Error code is %1.
- Explanation:
-
A policy error occurred. Error code is %1. This means that the client application has exceeding
some usage restrictions.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Privacy verification failed for address %1, request is refused.
- Explanation:
-
Privacy verification failed for address %1. Request is refused. This means that
the client application is trying to access a user device that it is not authorized for.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Too many addresses specified in message part %1.
- Explanation:
-
Too many addresses specified in message part %1. The client application has passed in
too many addresses for the operation.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Unlimited notification request not supported.
- Explanation:
-
Unlimited notification request not supported. The client application
should limit the notification requests.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Too many notifications requested.
- Explanation:
-
Too many notifications requested. The client application should not request as
many notifications.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Group specified in message part %1 not allowed.
- Explanation:
-
Group specified in message part %1 not allowed. Groups are limited
to certain operations.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Nested group specified in message part %1 not allowed.
- Explanation:
-
Nested group specified in message part %1 not allowed.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Charging is not supported.
- Explanation:
-
Charging is not supported. Charging is supported on only some operations.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Invalid frequency requested.
- Explanation:
-
Invalid frequency requested.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Busy criteria is not supported.
- Explanation:
-
Busy criteria is not supported.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Attempt to exceed maximum number of members in a group. Maximum number allowed is %1.
- Explanation:
-
Attempt to exceed maximum number of members in a group. Maximum number allowed is %1.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Attempted to add a group to an existing group. Subgroups are not supported.
- Explanation:
-
Attempted to add a group to an existing group. Subgroups are not supported. The
service has some limitations on group management.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Group name is too long. Maximum length allowed is %1.
- Explanation:
-
Group name is too long. Maximum length allowed is %1. The
group database has a defined maximum length.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Group URI %1 already exists. Group not created.
- Explanation:
-
Group URI %1 already exists. Group not created.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Vouchers not accepted.
- Explanation:
-
Vouchers not accepted.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Requested accuracy is not supported.
- Explanation:
-
Requested accuracy is not supported.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Geographic notification is not available
- Explanation:
-
Geographic notification is not available.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Periodic notification is not available
- Explanation:
-
Periodic notification is not available.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Too many participants
- Explanation:
-
Too many participants. A limited number is supported by this operation.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Unavailable media.
- Explanation:
-
Unavailable media. The referenced media is not available.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Maximum duration exceeded. Maximum allowed is %1 seconds.
- Explanation:
-
Maximum duration exceeded. Maximum allowed is %1 seconds.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- A service error occurred. Error code is %1.
- Explanation:
-
A service error occurred. Error code is %1.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Invalid input value for message part %1.
- Explanation:
-
Invalid input value for message part %1.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Invalid input value for message part %1, valid values are %2.
- Explanation:
-
Invalid input value for message part %1, valid values are %2.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- No valid addresses provided in message part %1
- Explanation:
-
No valid addresses provided in message part %1.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Correlator %1 specified in message part %2 is a duplicate.
- Explanation:
-
Correlator %1 specified in message part %2 is a duplicate.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Group %1 in message part %2 is not a valid group.
- Explanation:
-
Group %1 in message part %2 is not a valid group.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Invalid charging information.
- Explanation:
-
Invalid charging information.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Overlapped Criteria %1.
- Explanation:
-
Overlapped Criteria %1. Multiple notification requests have
been made for the same device, and only one is supported.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Accuracy of location is not within acceptable limit.
- Explanation:
-
Accuracy of location is not within acceptable limit.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- No subscription request from watcher %1 for attribute %2
- Explanation:
-
No subscription request from watcher %1 for attribute %2.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- %1 is not a watcher
- Explanation:
-
%1 is not a watcher.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- End user authentication failed.
- Explanation:
-
End user authentication failed.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Voucher %1 is not valid.
- Explanation:
-
Voucher %1 is not valid.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Call has already been connected, it cannot be cancelled.
- Explanation:
-
Call has already been connected; it cannot be cancelled.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Call has already been terminated.
- Explanation:
-
Call has already been terminated.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Charging operation failed, the charge was not applied.
- Explanation:
-
Charging operation failed; the charge was not applied.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Message too long. Maximum length is %1 characters.
- Explanation:
-
Message too long. Maximum length is %1 characters.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Data format not recognized for message part %1.
- Explanation:
-
Data format not recognized for message part %1. The
client application should use a supported format.
- User Response:
-
- Refer to the Parlay X specification for specific details.
- Delivery Receipt Notification not supported.
- Explanation:
-
Delivery Receipt Notification not supported. The client application
will not know if the message is successfully received by
the target device, only that it is successfully sent.
- User Response:
-
- Refer to the Parlay X specification for specific details.