Universal Trace Analyzer
Error codes › MAP error

MAP error 31 subscriberBusyForMT-SMS

MAP error3GPP TS 29.002 §17.6.6

What it means

The subscriber was busy specifically for mobile-terminated SMS delivery (subscriberBusyForMT-SMS).

Where you see it

In a returnError component of a MAP dialogue over TCAP/SCCP (roaming, SMS, call routing).

What to check

Check which network element sent the returnError (calling GT) and the operation it answered.

Got a trace with MAP error 31 subscriberBusyForMT-SMS? Drop it in the analyzer: it finds the step that really failed first, which node sent the code and what to ask the other side. Captures, test-system PDFs and vendor exports. 5 free analyses a month, no sign-up.

Analyze a trace free

Related codes

MAP error 30 longTermDenialA long-term restriction is denying this request (longTermDenial) -- wo…MAP error 32 sm-DeliveryFailureThe short message couldn't be delivered (sm-DeliveryFailure).…MAP error 29 shortTermDenialA short-term restriction is currently denying this request (shortTermD…MAP error 33 messageWaitingListFullThe subscriber's message waiting list is full (messageWaitingListFull)…MAP error 28 incompatibleTerminalThe subscriber's terminal is incompatible with what this procedure req…MAP error 34 systemFailureAn internal failure on the responding node (systemFailure) -- not a po…