Sorry the error is ambiguous as it covers multiple internal scenarios.
MBA error is a generic server response received toward the SMSC when the originating texter SMS profile did not receive transaction approval to proceed from the charging/billing platform that tracks the transactions. Since most plans are unlimited messaging, this internal sequence is seamless to most users. The charging nodes track permissions for plans like Family Allowance (time of day, day of week restrictions), originator/recipient blocks, prepaid and postpaid permissions, etc.
There are several reasons this occurs. Either the internal charging connection was unreachable at the time of the transaction, the senders prepaid profile is mismatched (setup as prepaid when the charging profile is postpaid), or there was a routing profile mistake on the SMSC. I am aware of a global SMSC routing profile for the cluster that impacted multiple users but was removed.
I hope this answered your concerns and that your SMS is working properly.
This thread was the product of our fantastic collaborators during DIGITS Beta! As many terms have changed and bugs have been exterminated since the Beta launched, the information here may no longer be accurate. If you still have a question, please search our active threads or ask a new question in the DIGITS space!