Meaning
A network reject code specified in cellular protocols signals that roaming is not allowed in a particular tracking area. Terminal equipment receives cause 13 during a tracking area update or attach procedure when the subscription lacks roaming rights in that geographical region. This restriction prevents the device from attempting subsequent automatic attachments within the restricted tracking area, limiting registration attempts to other available areas.
Handover protocols rely on this mechanism to ensure that devices do not waste radio resources repeatedly polling blocked stations.
Protocol Action
Network gateways evaluate the subscriber profile during registration to enforce regional service boundaries. When the mobile station requests access from an unauthorized tracking area, the core network terminates the session and returns cause 13 in the reject message. This action instructs the device to update its internal forbidden tracking area list immediately.
Device Response
Handsets receiving this specific rejection modify their internal state to avoid futile signalling. The modem enters a restricted state where it skips the offending tracking area in subsequent automatic scans, saving battery power and network resources. It only clears this forbidden status when the user manually initiates a network selection or the subscriber identity module is cycled.
Network Recovery
Integration engineers configure tracking area boundaries to align with commercial roaming agreements. When subscription profiles change, the network utilizes over-the-air updates or resets the connection to force the modem to scan again. Proper configuration ensures that terminal devices do not remain permanently blocked after a subscription update.
