You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Delivery receipt codes from providers are mapped to error codes (for LaML) and readable causes for everything else.
ex: 30005 -> invalid_destination_handset
Changes
One of our MMS codes was mapping to invalid_destination_handset, but that was not correct. In order to be more accurate, we created a new code/cause for this error.
SW REST Changes
We added the code/cause mms_expired_rejected_failed_or_unsupported - it maps to the same message "MMS Sent: Expired, Rejected, Failed, or Not Supported" https://signalwire.com/docs/apis/error-codes
Important
30008/unknown_destination_handset is not going away or changing in any way - this particular provider error just will map to something else now. The existing documentation on this can remain unchanged.
Notes
Barring any issues, this will be live with the production deployment on 5/14.
A few parts are intentionally vague to conceal internal provider details - however, please feel free to reach out with any questions!
references https://github.com/signalwire/cloud-product/issues/15730
Background
Delivery receipt codes from providers are mapped to error codes (for LaML) and readable causes for everything else.
ex: 30005 -> invalid_destination_handset
Changes
One of our MMS codes was mapping to
invalid_destination_handset, but that was not correct. In order to be more accurate, we created a new code/cause for this error.LaML Changes
We added a new code,
30011, that maps to the message "MMS Sent: Expired, Rejected, Failed, or Not Supported".https://signalwire.com/docs/compatibility-api/rest/error-codes
SW REST Changes
We added the code/cause
mms_expired_rejected_failed_or_unsupported- it maps to the same message "MMS Sent: Expired, Rejected, Failed, or Not Supported"https://signalwire.com/docs/apis/error-codes
Important
30008/unknown_destination_handsetis not going away or changing in any way - this particular provider error just will map to something else now. The existing documentation on this can remain unchanged.Notes
Barring any issues, this will be live with the production deployment on 5/14.
A few parts are intentionally vague to conceal internal provider details - however, please feel free to reach out with any questions!