MSs which do not explicitly support CCBS are not precluded from attempting to activate CCBS or from accepting a CCBS Recall. The mechanisms employed to offer the CCBS service to these MSs shall be a matter for individual networks.
The network shall send DISCONNECT to MS A (cause #17 or #34) with diagnostic field indicating CCBS is Possible, and a progress indicator indicating inband information is available. This inband information shall be used to indicate CCBS possible. The absence of a progress indicator in the DISCONNECT, prevents subscriber A from successfully activating CCBS. If subscriber A requests CCBS, MS A will send a REGISTER message, containing a ProcessUnstructuredSS-Request invoke component. The receiving network entity shall pass the data received in the request to the application handling USSD operations and shall wait for the response of the application. When the application accepts the request and terminates the dialogue, the network shall clear the transaction by sending a RELEASE COMPLETE message containing a return result component.
If the network is unable to process the request received from the MS, it shall clear the call independent transaction by sending a RELEASE COMPLETE message containing a return error component.
When the call independent transaction has been cleared, either the MS or the network shall release the call related transaction by sending a RELEASE COMPLETE message.
The CCBS recall shall be treated as a mobile terminated call set-up. The network shall send a SETUP message to MS A, which causes the MS to ring indicating that destination B is now idle. If subscriber A accepts the CCBS recall, MS A shall establish a new call with the CONNECT message.