Universal Trace Analyzer
Error codes › MAP error

MAP error 39 noRoamingNumberAvailable

MAP error3GPP TS 29.002 §17.6.6

What it means

No roaming number was available to assign for this call (noRoamingNumberAvailable) -- a resource/capacity issue on the visited side, not a subscriber-reachability question.

Where you see it

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

What to check

Check with the visited network whether their roaming-number pool was exhausted at the time of the attempt.

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

Got a trace with MAP error 39 noRoamingNumberAvailable? 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 40 tracingBufferFullThe responding node's tracing buffer is full (tracingBufferFull) -- an…MAP error 36 unexpectedDataValueA field in the request had a value the responding node couldn't accept…MAP error 42 targetCellOutsideGroupCallAreaThe target cell for a group call is outside the group call area (targe…MAP error 35 dataMissingThe request was missing a mandatory field the responding node needed (…MAP error 43 numberOfPW-AttemptsViolationToo many incorrect password attempts were made (numberOfPW-AttemptsVio…MAP error 34 systemFailureAn internal failure on the responding node (systemFailure) -- not a po…