10.12.2012 Views

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

GSM 09.02 - Version 5.3.0 - Digital cellular telecommunications - ETSI

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Page 448<br />

<strong>GSM</strong> <strong>09.02</strong> <strong>Version</strong> <strong>5.3.0</strong>: August 1996<br />

- User Determined User Busy (UDUB)<br />

This condition occurs when a call is offered to an MS and the MS responds "User Busy" because<br />

the subscribers resources (terminal or person using them) are busy (reference TS <strong>GSM</strong> 02.01).<br />

This busy condition is treated in exactly the same way as Network Determined User Busy, see<br />

above.<br />

If the Busy Subscriber error cause does not indicate one of the above states then the VLR will treat this<br />

error as More Calls Allowed.<br />

CUG Failure<br />

Failure will be due either to the VLR being unable to convert the Interlock code into an Index, or the CUG<br />

Call Authorization check for call forwarding interaction may not be successful. This will result in VLR<br />

terminating the procedure for this call by setting MAP_SEND_INFO_FOR_INCOMING_CALL service user<br />

error to "CUG Reject" in the case of CUG authorization failure, and "System Failure" for failure to convert<br />

the CUG Interlock Code to an Index. This is then sent to the MSC, the procedure in the VLR is then<br />

terminated.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!