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 412<br />

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

Routing Failure<br />

Failure to provide routing information is reported by the HLR to the Gateway MSC in the<br />

MAP_SEND_ROUTING_INFORMATION service confirm. The MAP User Error parameter will indicate one<br />

of the following conditions:<br />

MAP User Error<br />

Unknown Subscriber ISUP Error = 1<br />

Absent Subscriber " " = 18<br />

Call Barred " " = 21<br />

Forwarding Violation " " = 21<br />

Number Changed = 22<br />

CUG Reject " " = 55<br />

Teleservice/Bearer Service not provisioned = 57<br />

Facility Not Supported " " = 69<br />

Data Missing " " =111<br />

Unexpected Data Value " " =111<br />

System Failure " " =111<br />

NOTE: A suggested mapping is shown above between the MAP User Error value and the ISUP<br />

Error Cause, this is only provided to aid understanding. CCITT Q.6xx-series of<br />

recommendations provide further guidance for the mapping of Error Cause values<br />

(specifically ISUP and TUP errors).<br />

Table 18.2/1: Suggested mapping between ISUP and MAP Errors<br />

Regardless of the reason for routing failure the Gateway MSC will construct a Release message (I_REL),<br />

selecting the appropriate Error Cause value, and return this to the network. The procedure in the Gateway<br />

MSC will then be terminated.

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

Saved successfully!

Ooh no, something went wrong!