//Editor-Info: -*- text -*- // //Subject: TOVE project / uni/bisup // //File: uni_bisup.txt // //Version: $Revision: 1.1 $ // //State: $State: Exp $ // //Date: $Date: 1998/07/15 11:14:04 $ // //Organisation: // Helsinki University of Technology // Laboratory of Telecommunications Software and Multimedia // //Author: // Timo Kokkonen // //Description: // Comparison of UNI3.1 and B-ISUP primitives and parameters. // //Copyright: // // //Licence: // // //History: // ///////////////////////////////////////////// ///////////////////////////////////////////// //// bisup messages -> uni3.1 messages //// ///////////////////////////////////////////// ///////////////////////////////////////////// ---------------------------------------------------------------------------------- | Messages header | ---------------------------------------------------------------------------------- - Routing label For ATM virtual connection the same routing label must be used for each message that is transmitted for that connection. - Message type code - Message length Number of octets included in the B-ISDN user part message content and the message compatibility information fields. - Message compatibility information The message compatibility information defines the behaviour of a switch if the message is not understood. FIELDS: - Broadband/Narrow-band interworking indicator - Pass not possible indicator - Discard message indicator - Send notification indicator - Release call indicator - Transit at intermediate exchange indicator (these fields are defined in Information element header) ---------------------------------------------------------------------------------- | Information element header | ---------------------------------------------------------------------------------- - Parameter name - Length indicator Number of octets included in the Parameter compatibility information and parameter content. - Parameter compatibility information The parameter compatibility information defines the behaviour of a switch if the parameter is not understood. FIELDS: - Pass not possible indicator Information sent to inform another node on what action to take if "pass on" was requested due to compatibility reason but "pass on" was not possible due to interworking with pre-ISUP 1992 signaling. - Discard parameter indicator Information sent to inform another node to discard the related parameter, due to compatibility reason. - Discard message indicator Information sent to inform another node to discard the related message, due to compatibility reason. - Send notification indicator Information sent to inform another node to sent notification, due to compatibility reason, if the related message or parameter is unrecognized. - Release call indicator Information sent to inform another node to release call or not, by compatibility reason, if the related message or parameter is unrecognized. - Transit at intermediate exchange indicator Information sent to inform a transit node (type B), whether it shall react on the rest of the instruction indicators or not, if the related message or parameter is unrecognized. - Broadband/Narrow-band interworking indicator Information sent indicating reaction to be taken if unrecognized information is received at a broadband/Narrow-band interworking point. ///////////////////////////////////////////// Call Control primitives between AP and SACF ///////////////////////////////////////////// ---------------------------------------------------------------------------------- | Bisup primitive: Set_Up(Req/Ind) -> | | Message: Initial Address(IAM) (0000 0001) | ---------------------------------------------------------------------------------- A message sent in the forward direction to initiate seizure of an outgoing virtual channel and to transmit number and other information relating to the routing and handling of a call. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - ATM cell rate Information classified by the cell rate identifier indicating the number of cells per second that are required for the call. The cell rate value is unchanged as it traverses the B-ISDN network. FIELDS: - Cell rate identifier: Information sent to identify the applicability of the cell rate. The use of the peak cell rate (and for future releases the use of the average cell rate) in traffic control is specified in Rec. I.371 Used 7 bit length identifier for the Cell rate. - Cell rate: A code expressing in pure 3 octet integer representation the number of cells per second. >>>>> in Uni3.1 ATM traffic Descriptor found same information !! Note that in bisup there is 4 possoble variations and uni 12 (e.g. in setup-message this is mandatory IE). - Broadband bearer capability Information sent in the forward direction to indicate a required broadband connection oriented bearer service (Rec. F.811) to be provided by the network. FIELDS: - Coding standard: Information sent in association with a parameter identifying the standard in witch the parameter format is describle. >>>>> in Uni3.1 this field is included in IE's header. - Bearer class - Traffic type - Timming requirements - Susceptibility to clipping - User-plane connection configuration >>>>> in Uni3.1 Broadband Bearer Capability found same information (e.g. in setup message this is mandatory IE). - Called party number Information to identify called party. FIELDS: - Odd/even Information sent in association with an address, indicating whether the number of address signal contained in the address is even or odd. - nature of address indicator Information sent in association with an addrerss indicating the nature of that address, e.g. ISDN international number, ISDN national significant number, or ISDN subscrible number. - internal network number indicator Information sent to the destination exchange for specific numbers, e.g. roaming numbers, indicating whether or not the number contained in the parameter is generated by network. - Numbering plan indicator Information sent in association with a number indicating the numbering plan used for that number (e.g. ISDN number, Telex number. - Address signal An element of information in a network number. The address signal may indicate digit values 0 to 9, code 11 or code 12. One address signal value (ST) is reserved to indicate the end of the called party number. Digits are coded in 4 bit fields. >>>>> in Uni3.1 Called party number found same information (e.g. in setup message this is mandatory IE). - Calling party's category Information sent in the forward direction indicating the category of the calling party and, in the case of semi-automatic calls, the service language to be spoken by the incoming, delay and assistance operators. >>>>> Not found in Uni3.1 - Origination ISC point code (Note 2) Information sent in the initial address message of an international call, indicating the point code of the originating ISC. - The signaling point The signaling point code is a pure binary representation of the code allocatrd to a node in the signaling network. >>>>> Not found in Uni3.1 - Propagation delay counter Information sent in forward direction to indicate the propagation delay of a connection. This information is accumulated whilst the parameter is transferred trougth the network. The propagation delay is presented by a counter counting in integer multiples of 1 ms. >>>>> Not found in Uni3.1 - Exchange type (Note 1) Note 1: (Q.2764 page 23) The exchange type of parameter takes the appropriate value from the list in 1.1. It is passed the AE so that the protocol can bevaried depending on the role the that the exchange is performing for this call/connection. Unlike the other parameters, it does not relate to a prot§ocol information element. This parameter is only present in the request primitive. Note 2: This parameter is Mandatory when the Set_Up Request is issued at an outgoing international exchange. ---------------------------------------------------------------------------------- | Bisup primitive: Address_Complete(Req/Ind) -> | | Message: Address Complete(ACM) (0000 0110) | ---------------------------------------------------------------------------------- A message sent in the backward direction indicating all the address signals required for routing the call to the called party have been received. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Called party's indicators Information sent in the backward direction consisting of the called party's status indicator and the called party's category indicator. >>>>> Not found in Uni3.1 ---------------------------------------------------------------------------------- | Bisup primitive: Incoming_Resources_Accepted(Req/Ind) -> | | Message: IAM Acknowledge(IAA) (0000 1010) | ---------------------------------------------------------------------------------- A message sent in the backward direction in the response to an IAM message. The IAA indicates that the IAM has been accepted and the requested bandwidth on the incoming leg (both directions) is available. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Incoming_Resources_Rejected(Req/Ind) -> | | Message: IAM Reject(IAR) (0000 1011) | ---------------------------------------------------------------------------------- A message sent in the backward direction in the response to an IAM message indicating call refusal due to resource unavailability. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Cause indicators Information sent in either direction indicating where and why the call failed or was cleared. - Coding standard: >>>>> in Uni3.1 this field is included in IE's header. >>>>> in Uni3.1 Cause found same information (e.g. in release message this is mandatory IE). ---------------------------------------------------------------------------------- | Bisup primitive: Subsequent_Address(Req/Ind) -> | | Message: Subsequent Address(SAM) (0000 0010) | ---------------------------------------------------------------------------------- A message sent that may be sent in forward direction following an initial address message, to convey additional called party number information. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Subsequent number Information sent in the forward direction in case of call set-up with overlap address signaling, coverying one or more address signals of the called party number. FIELDS: - Odd/even - Address signal Coded as Called party number->address signal >>>>> Not found in Uni3.1 ---------------------------------------------------------------------------------- | Bisup primitive: Release(Req/Ind) -> | | Message: Release(REL) (0000 1100) | ---------------------------------------------------------------------------------- A message sent in either direction to indicate that call/connection is being released due to the reason (cause) supplied and that the resources are ready to be made available for new traffic on receipt of the release complete message. --------------- Mandatory IEs: --------------- - Cause indicators Defined earlier (see IAR). ---------------------------------------------------------------------------------- | Bisup primitive: Release(Res/Con) -> | | Message: Release Complete(RLC) (0001 0000) | ---------------------------------------------------------------------------------- A message sent in either direction in response to the receipt of a released message, when the resources of the call/connection concerned have been made available for new traffic. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Answer(Req/Ind) -> | | Message: Answer(ANM) (0000 1001) | ---------------------------------------------------------------------------------- A message sent in the backward direction indicating all the address signals required for routing the call to the called party have been received and the call has been answered. In semi-automatic working this message has a supervisory function. In automatic working this message is used in conjugation with charging information in order to: - start metering the charge to the calling subscriber (see Rec. Q.28) - start measurement of call duration for international accounting purposes (see Rec. E.260). --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Progress(Req/Ind) -> | | Message: Call progress(CPG) (0010 1100) | ---------------------------------------------------------------------------------- A message, sent in either direction during the set-up or active phase of the call indicating that an event, which is of significance to the originating or terminating access, has accurred. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Suspend(Req/Ind) -> | | Message: Suspend(SUS) (0000 1101) | ---------------------------------------------------------------------------------- A message sent in either direction indicating that the calling or called party has been temporarily disconnected. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Suspend/resume indicators Information sent in the suspend and resume messages to indicate whether suspend/resume was initiated by an ISDN subscriber or by the network. >>>>> Not found in Uni3.1 ---------------------------------------------------------------------------------- | Bisup primitive: Resume(Req/Ind) -> | | Message: Resume(RES) (0000 1000) | ---------------------------------------------------------------------------------- A message sent in either direction indicating that the calling or called party, after having been suspended, is reconnected. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Suspend/resume indicators Defined earlier (see SUS). ---------------------------------------------------------------------------------- | Bisup primitive: Forward_Transfer(Req/Ind) -> | | Message: Forward Transfer(FOT) (0000 1000) | ---------------------------------------------------------------------------------- A message sent in the forward direction on semi-automatic calls when the outgoing international exchange operator wants the help of an operator at the incoming international exchange. The message will normally serve to bring an assistance operator (see Rec. Q101) in the circuit if the call is automatically set up at the exchange. When the call is complete via an operator (incoming or delay operator) at the incoming international exchange, the message should preferably cause this operator to be recalled. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Network_Resource_Management(Req/Ind) -> | | Message: Network Resource Management (0011 0010) | ---------------------------------------------------------------------------------- A message sent in order to modify network resources associated with a certain call. The message is sent along an estabilished path in any direction in any phase of call. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Segmentation(Req/Ind) -> | | Message: Segmentation(SGM) (0011 1000) (national use) | ---------------------------------------------------------------------------------- Message sent in either direction to convey an additional serment of an overlength message. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ///////////////////////////////////////////////// Maintance Control primitives between AP and SACF ///////////////////////////////////////////////// ---------------------------------------------------------------------------------- | Bisup primitive: Block_Resource(Req/Ind) -> | | Message: Blocking(BLO) (0001 0011) | ---------------------------------------------------------------------------------- A message sent only for maintance purposes to the exchange at the other end of virtual path connection, to cause an engaged condition of that resource for subsequent calls outgoing from that exchange. An exchange receiving the blocking message must be capable of accepting incoming calls on the concerned resource unless it has also sent a blocking message for that resource. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Resource identifier Information sent identify the resources to be reset or (un)blocked. >>>>> Not found in Uni3.1 ---------------------------------------------------------------------------------- | Bisup primitive: Block_Resource(Res/Con) -> | | Message: Blocking Ack(BLA) (0001 0101) | ---------------------------------------------------------------------------------- A message sent in response to a blocking message indicating that the resource has been blocked. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Unblock_Resource(Req/Ind) -> | | Message: Unblocking(UBL) (0001 0100) | ---------------------------------------------------------------------------------- A message sent to the exchange at the other end of a virtual path connection to cancel, in that exchange, the engaged condition of the resource caused by a previously sent blocking message. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Resource identifier Defined earlier (see BLO). ---------------------------------------------------------------------------------- | Bisup primitive: Unblock_Resource(Res/Con) -> | | Message: Unblocking Ack(UBA) (0001 0110) | ---------------------------------------------------------------------------------- A message sent in response an unblocking message indivating that the resource has been unblocked. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Reset_Resource(Req/Ind) -> | | Message: Reset(RSM) (0001 0010) | ---------------------------------------------------------------------------------- A message sent to release a resource (e.g. a virtual connection or a signaling identifier) when, due to memory mutilation or other causes it is unknown whether for example, a release or a complete message is appropriate. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Resource identifier Defined earlier (see BLO). ---------------------------------------------------------------------------------- | Bisup primitive: Reset_Resource(Res/Con) -> | | Message: Reset Ack(RAM) (0000 1111) | ---------------------------------------------------------------------------------- A message sent in response to a reset message indicating that the resources have been released. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: User_Part_Available(Req/Ind) -> | | Message: User Part Test(UPT) (0011 0100) | ---------------------------------------------------------------------------------- A message sent in either direction to test the status of a user part marked as unavailable for a signaling point. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: User_Part_Available(Res/Con) -> | | Message: User Part Available(UPA) (0011 0101) | ---------------------------------------------------------------------------------- A message sent in either direction as a response to a user part test message, to indicate that the user part is available. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Check_Resource_Begin(Req/Ind) -> | | Message: Consistency Check Req(CSR) (0000 0101) | ---------------------------------------------------------------------------------- A message sent for maintance purposes to the exchange at the other end of a virtual path connection to verify the consistent and correct allocation of a virtual path connection identifier to a virtual path. The test will cause the remote (receiving) exchange to active an ATM cell monitoring device fot the indicated recource --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Resource identifier Defined earlier (see BLO). ---------------------------------------------------------------------------------- | Bisup primitive: Check_Resource_Begin(Res/Con) -> | | Message: Consistency Check Req Ack(CSRA) (0001 0001) | ---------------------------------------------------------------------------------- A message sent in response to a consistency check message indicating that the ATM cell monitoring device has been activated for the indicated resource. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Check_Resource_End(Req/Ind) -> | | Message: Consistency Check End(CCE) (0001 0111) | ---------------------------------------------------------------------------------- A message sent to the exchange at the other end of a virtual path connection indicating the end of the consistency check sequence and to deactive the consistency check ATM cell monitoring devices. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) ---------------------------------------------------------------------------------- | Bisup primitive: Check_Resource_End(Res/Con) -> | | Message: Consistency Check End Ack(CCEA) (0001 1000) | ---------------------------------------------------------------------------------- A message sent in response to a continuity check end message indicating the result of the consistency check and that the consistency check monitoring device has been activated. --------------- Mandatory IEs: --------------- - Message compatibility information (this is not an IE) - Consistency chack result information Information sent indicating the result of the consistency check. >>>>> Not found in Uni3.1 ///////////////////////////////////////////// Compatibility primitives between AP and SACF ///////////////////////////////////////////// ---------------------------------------------------------------------------------- | Bisup primitive: Unrecognized_Message_Type(Req/Ind) -> | | Message: Any Unrecognized message () | ---------------------------------------------------------------------------------- --------------- Mandatory IEs: --------------- - ---------------------------------------------------------------------------------- | Bisup primitive: Confusion(Req/Ind) -> | | Message: Confusion(CFN) (0010 1111) | ---------------------------------------------------------------------------------- A message sent in responser to any (othet than a confusion message) if the exchange does not regognize the message or detects a part of the message as being unrecognized and the instruction indicator requested notification. --------------- Mandatory IEs: --------------- - /////////////// Other messages /////////////// ---------------------------------------------------------------------------------- | Bisup primitive: () -> | | Message: User-to-user information(USR) (0010 1101) | ---------------------------------------------------------------------------------- A message to be used for the transport of user-to-user signaling independent of call control message. --------------- Mandatory IEs: --------------- /////////////////////////////////////////// /////////////////////////////////////////// //// uni3.1 messages -> bisup messages //// /////////////////////////////////////////// /////////////////////////////////////////// ---------------------------------------------------------------------------------- | Messages header | ---------------------------------------------------------------------------------- Sec. 5 page 183 - Protocol discriminator - Call reference - Message type - Message length ---------------------------------------------------------------------------------- | Information element header | ---------------------------------------------------------------------------------- Sec. 5 page 193 - Coding standard - IE instruction field The IE instruction field is only interpreted in case of unrecognized information element identifier or unrecognized information element contents. ///////////////////////////// Call estabilishment messages ///////////////////////////// ---------------------------------------------------------------------------------- | Uni3.1 message: Call proceeding (0000 0010) | ---------------------------------------------------------------------------------- This message is sent by the called user to the network or by the network to calling user to indicate that the requested call estabilishment has been initiated and no more call estabilishment information will be accepted. --------------- Mandatory IEs: --------------- - Message header - Connection identifier (Note 1) The Connection identifier information element identifiers the local ATM connection recources on the interface. >>>>> in bisup Connection identifier found same information (e.g. in message Setup this is optional IE). - Endpoint reference (Note 2) The purpose of the Endpoint reference information element is to identify the individual endpoints of a point-to-multipoint. The Endpoint Reference Identifier Value 0 is always used to identify the first party of a point-to- multipoint call. A non-zero value is always used to identify subsequent parties of a point-to-multipoint call. >>>>> Not found in bisup Note 1 - Mandatory in the network-to-user direction if this message is the first message in response to a SETUP message. It's mandatory in the user-to-network direction if this message is the first response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message. Note 2 - Mandatory if an Endpoint reference was included in the SETUP message. ---------------------------------------------------------------------------------- | Uni3.1 message: Connect (0000 0111) | ---------------------------------------------------------------------------------- The message is sent by the called user to the network and by the network to the calling user to indicate call acceptance by the called user. --------------- Mandatory IEs: --------------- - Message header - Connection identifier (Note 1) Defined earlier (see Call proceeding). - Endpoint reference (Note 2) Defined earlier (see Call proceeding). Note 1 - Mandatory in the network-to-user direction if this message is the first message in response to a SETUP message. It's mandatory in the user-to-network direction if this message is the first response to a SETUP message, unless the user accepts the connection identifier indicated in the SETUP message. Note 2 - Mandatory if an Endpoint reference was included in the SETUP message. ---------------------------------------------------------------------------------- | Uni3.1 message: Connect acknowledge (0000 1111) | ---------------------------------------------------------------------------------- This message is sent by the network to the called user to indicate the user has been awarded the call. It is also sent by the calling user to the network to allow symmetrical call control procedures. --------------- Mandatory IEs: --------------- - Message header ---------------------------------------------------------------------------------- | Uni3.1 message: Setup (0000 0101) | ---------------------------------------------------------------------------------- This message is sent by the calling user to the network and by the network to the called user to initiate call estabilishment. --------------- Mandatory IEs: --------------- - Message header - ATM traffic descriptor The purpose of the ATM traffic descriptor information is to specify the set of traffic parameters which, together, specifya traffic control capability. FIELDS - Cell rate identifier: Used 8 bit length identifier for the Cell rate. - Cell rate: A code expressing in pure 3 octet integer representation the number >>>>> in bisup ATM cell rate found same information !! Note that in Uni there is 12 possoble variations and bisup only 4 (e.g. in message initial address this is mandatory IE). - Broadband bearer capability The purpose of the Broadband bearer capability information element is to indicate a requested broadband connection oriented bearer service (see ITU_T Rec F.811) to be provided by the network. FIELDS: - Bearer class - Traffic type - Timming requirements - Susceptibility to clipping - User-plane connection configuration >>>>> in bisup Broadband bearer capability found same information (e.g. in message initial address this is mandatory IE). - Called party number The purpose of the Called party number information element is to identify the called party of a call. FIELDS: - Type of number - Addressing/numbering plan identification - Address/Number DIgits If use of the E.164 numbering plan is indicated in the addressing/ numbering plan identification, the numbering digits appear in multiple octet 6's in the same order in witch they would be entered on a numeric keypad; i.e., the number digit witch would be entered first is located in first octet 6. Digits are coded in IA5 characters. Birs 8 is set 0. - ATM Endsystem Address Octets If the use of ATM Endsystem Address is indicated in the addressing/ numbering plan identification, the address is coded as describled in ISO 8348/AD 2, using the preferred binary encoding of the ISO NSAP format. >>>>> in bisup called party number found same information (e.g. in message initial address this is mandatory IE). - Connection identifier Defined earlier (see Call proceeding). - QoS parameter The purpose of the Quality of Service parameter information element is to request and indicate the Quality of service Class for a connection. If information about the requested Quality of Service Class is not available for the network at the terminating interface (e.g. because an intermediate network did not transfer the Quality of Service parameter information element), the network will generate the default value ("Unspecifified QoS class") for the Quality of Service parameter information element for the transfer to the called user. FIELDS: - QoS Class Forward - QoS Class Backward >>>>> Not found in bisup /////////////////////// Call clearing messages /////////////////////// ---------------------------------------------------------------------------------- | Uni3.1 message: Release (0101 1101) | ---------------------------------------------------------------------------------- This message is sent by the user to request the network to clear the end-to-end connection (if any) or is sent by the network to indicate that the end-to-end connection is cleared and that the receiving equipment should release the virtual channel and prepare to release the call reference after sending a RELEASE COMPLETE. --------------- Mandatory IEs: --------------- - Message header - Cause the Cause information element describles the reason for generating certain messages, provides diagnostic information in the event of procedural errors, and indicates the location of the cause originator. The Cause information element and diagnostic may be repeated in a message. FIELDS: - Location - Cause value - Dianostic >>>>> in bisup Cause found same information (e.g. in IAM Reject message this is mandatory IE). ---------------------------------------------------------------------------------- | Uni3.1 message: Release complete (0101 1010) | ---------------------------------------------------------------------------------- This message is sent by the user or the network to indicate that the equipment sending the message has released the virtual channel (if any) and call reference, the virtual channel is available for reuse, and the receiving equipment shall release the call reference. --------------- Mandatory IEs: --------------- - Message header - Cause (Note 1) Defined earlier (see Release). Note 1 - Mandatory in the first call clearing message; including when the RELEASE COMPLETE message is sent as a result of an error condition. ---------------------------------------------------------------------------------- | Uni3.1 message: Restart (0101 0110) | ---------------------------------------------------------------------------------- This message is sent by the user or network to request the recipient to restart (i.e., release all resources associated with) the indicated virtual channel or all virtual channels controlled by the Signaling Virtual Channel. --------------- Mandatory IEs: --------------- - Message header - Restart indicator The purpose of the Restart indicator information element is to identify the class of the facility to be restarted. FIELSD: - Class >>>>> Not found in bisup ---------------------------------------------------------------------------------- | Uni3.1 message: Restart acknowledge (0101 1110) | ---------------------------------------------------------------------------------- This message is sent to acknowledge the receipt of a RESTART message and to indicate that the requested restart is complete. --------------- Mandatory IEs: --------------- - Message header - Restart indicator Defined earlier (see Restart). /////////////////////// Miscellaneous messages /////////////////////// ---------------------------------------------------------------------------------- | Uni3.1 message: Status (0111 1101) | ---------------------------------------------------------------------------------- This message is sent by the user or the network in response to a STATUS ENQUIRY message or at any time to report certain error conditions listed uni3.1 specs 5.5. --------------- Mandatory IEs: --------------- - Message header - Call state The purpose of the Call state information element is to describle the current status of a call or a global interface state. >>>>> Not found in bisup - Cause Defined earlier (see Release). ---------------------------------------------------------------------------------- | Uni3.1 message: Status enquiry (0111 0101) | ---------------------------------------------------------------------------------- This message is sent by the user or the network at any time to solicit a STATUS message from the peer layer 3 entity. Sending a STATUS message in response to a STATUS ENQUIRY message is mandatory. --------------- Mandatory IEs: --------------- - Message header ///////////////////////////// Point-to-multipoint messages ///////////////////////////// ---------------------------------------------------------------------------------- | Uni3.1 message: Add party (1000 0000) | ---------------------------------------------------------------------------------- This message is sent to add a party to an existing connection(see uni3.1 specs 5.6). --------------- Mandatory IEs: --------------- - Message header - Called party number Defined earlier (see Setup). - Endpoint reference Defined earlier (see Call proceeding). ---------------------------------------------------------------------------------- | Uni3.1 message: Add party acknowledge (1000 0001) | ---------------------------------------------------------------------------------- This message is sent to acknowledge that the ADD PARTY request was successful. --------------- Mandatory IEs: --------------- - Message header - Endpoint reference Defined earlier (see Call proceeding). ---------------------------------------------------------------------------------- | Uni3.1 message: Add party reject (1000 0010) | ---------------------------------------------------------------------------------- this message is sent to acknowledge that the ADD PARTY request was not successful. --------------- Mandatory IEs: --------------- - Message header - Cause Defined earlier (see Release). - Endpoint reference Defined earlier (see Call proceeding). ---------------------------------------------------------------------------------- | Uni3.1 message: Drop party (1000 0011) | ---------------------------------------------------------------------------------- This message is sent to drop (clear) a party from an existing point-to-multipoint connection. --------------- Mandatory IEs: --------------- - Message header - Cause Defined earlier (see Release). - Endpoint reference Defined earlier (see Call proceeding). ---------------------------------------------------------------------------------- | Uni3.1 message: Drop party acknowledge (1000 0100) | ---------------------------------------------------------------------------------- This message is sent in response to a DROP PARTY message to indicate that the party was dropped from the connection. --------------- Mandatory IEs: --------------- - Message header - Cause Defined earlier (see Release). - Endpoint reference Defined earlier (see Call proceeding).