/mcpcall was cleared because of a supplementary service constraint. The diagnostic field can contain additional information about the supplementary service and the reason for rejection. Number Changed The typical scenario is a subscriber has changed their number. 22 Returned to a calling party when the called number indicated by the calling party is no longer assigned. The new called party number can be optionally included in this diagnostic field. Redirection to a new destination The typical scenario is the call is forwarded. 23 Used by a general ISUP protocol mechanism that decides that the call must be sent to a different called number. Exchange routing error The typical scenario is the network is overloaded. 25 Indicates that the destination indicated by the calling party cannot be reached because an intermediate exchange has released the call because it reached a limit in the execution of the hop counter procedure. Nonselected user clearing The typical scenario is a called number failure. 26 Indicates that the called number has not been awarded the incoming call. Socket failure Typical scenarios include: Transmission Control Protocol (TCP) socket connection failure. • Problem sending an H.323 SETUP. • Problem sending a SIP INVITE. • Send or receive error occurs on the connected socket. • 27 CC_CAUSE_DESTINATION_OUT_OF_ORDER Indicates that the destination indicated by the originator cannot be reached because the interface of the destination does not function correctly. The signaling message cannot be delivered to the remote party. The typical scenario is the caller is calling with the use of a Invalid number format 28 Indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete.