Telos Zephyr Xstream - Manual (Page 317)

USER’S MANUAL
Appendix 3 – ISDN Cause Phrases/Values 305
This cause indicates that the user has requested a bearer capability which is implemented by the
equipment which generated this cause but the user is not authorized to use it. This is a common
problem caused by wrong Telco provisioning of the line at the time of installation.
Cause No. 58 – Bearer capability not presently available
This caused indicates the user has requested a bearer capability which has been implemented
by the equipment, but is not available at this time.
CLASS 1.4 (Service or option not implemented)
Cause No. 63 – Service or option not available, unspecified
This cause is used to report a service or option not available, only when no other cause in this
class applies.
Cause No. 65 ‐ Bearer Capability not implemented (Incompatible bear cap)
This cause indicates that the equipment sending this cause does not support the bearer
capability requested.
Cause No. 66 – Channel type not implemented
This cause is returned when the called party has reached a channel type not supported.
Cause No. 69 – Requested facility not implemented
This cause indicates that the network (or node) does not support the requested bearer
capability and therefore cannot be accessed at this time.
Cause No. 79 – Service or option not implemented, unspecified
This cause is used to report a service or option not implemented event only when no other
cause in this class applies.
CLASS 1.5 (Invalid message; e.g. parameter out of range)
Cause No. 88 ‐ Incompatible destination
This cause indicates that the equipment sending this cause has received a request to establish a
call which has low layer compatibility, high layer compatibility or other compatibility attributes
(e.g. data rate, DN sub‐address) which cannot be accommodated. This cause can also be
returned by a switch to a CPE when trying to route a call to an incompatible facility, or one
without data capability.
Cause No. 90 – Destination Address Incomplete/Non‐existent CUG