IPAWS Publishing Status Values
Code |
Publishing Status Message |
Everbridge Status Description |
000 |
Training mode enabled - message not sent to CMAS/WEA |
Training Mode has been enabled and the message will not be sent to CMAS/WEA. (Commercial Mobile Alert System/Wireless Emergency Alert) |
010 |
Message Submitted to Mobile Phone Providers |
Message as accepted by CMAS and transmitted to mobile phone providers. |
100 Series - CMAS Dissemination Status
100 |
Invalid federal alert gateway id |
Mobile phone provider gateway rejected message. |
101 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway rejected message. |
102 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway rejected message. |
103 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway rejected message. |
104 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway rejected message. |
105 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway rejected message. |
106 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway rejected message. |
107 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway rejected message. |
108 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway rejected message. |
198 |
gateway-endpoint-invalid-response |
Mobile phone provider response contains invalid response. |
199 |
CMAS/WEA Error - Contact Everbridge |
Mobile phone provider gateway unavailable. |
200 Series - CAP Exchange Status Messages
200 |
Message has been CAP validated |
The XML document passes the first set of conformance tests. |
201 |
Duplicate Notification ID - Contact Everbridge |
IPAWS received an alert message containing an Everbridge Notification ID matching the Notification ID of a previous message. |
202 |
Message signature accepted by CAP Exchange |
CAP Exchange validation to indicate that digital signature is valid. |
207 |
Update or Cancel message is missing the initial Notification ID - Contact Everbridge |
CAP Alert (Update, Cancel, Ack, Error) message missing <reference> element. |
208 |
Digital Signature invalid. Check your credentials and try again. |
CAP Exchange validation to indicate that digital signature is not valid. |
209 |
Update or Cancel Message references an expired alert |
Referenced CAP Alert (Ack/Error) message is expired. |
210 |
Not authorized for this broadcast. Check the Addresses field and try again. |
COG is not authorized to post to Broadcast COG and the posted CAP Alert <addresses> element includes the Broadcast COG. |
211 |
Message marked as Restricted. Check the "Restriction" field and try again. |
The <restriction> element is not present with content when <scope> element is equal to "Restricted". |
212 |
Message marked as Private. Check the "Addresses" filed and try again. |
The <addresses> element is not present with content when <scope> element is equal to "private". |
213 |
Circle included with message is not valid - Contact Everbridge |
Additional validation to verify that Circle format is the paired values of a point and radius. |
214 |
Circle or polygon is outside of authorized geographic area |
The <area> block <circle> and/or <polygon> element does not fall within the geographic area of authorized FIPS or Marine Zones. |
215 |
Not authorized for event code CAPEXCH |
Alert Originator COG is not authorized for <eventCode> in COG Profile to disseminate CAP Alert Message. |
216 |
Polygon included with message is not valid - Contact Everbridge |
Additional validations to look for polygon that may cause issues in downstream systems (e.g., polygons with a collocated line segment with zero area, polygon with boundary crossover, and zero area polygons). |
217 |
Error with date format in message - Contact Everbridge |
One or more of the date fields in the XML do not contain the date in the required format. |
218 |
Referenced update or cancel alert not found - Contact Everbridge |
Referenced CAP Alert (ACK/ERROR) message cannot be found in IPAWS-OPEN. |
219 |
CAP Message not authorized for selected geographic area |
Alert Originator COG not authorized for <geocode> in COG Profile to disseminate CAP Alert Message. |
221 |
IPAWS Error - Contact Everbridge |
Message format and content does not meet requirements for exchanging messages with other COGs. |
222 |
Invalid characters included in Identifier and Sender fields - Contact Everbridge |
We are setting the <identifier> element and the <sender> element to the Notification ID. |
223 |
SAME Code contains invalid characters. Check the SAME code and try again. |
Invalid SAME code value. |
224 |
References field is not in expected format - Contact Everbridge |
Structure for <references> element not in the "sender, indentifier, sent" format. |
300 Series - Core IPAWS Profile Status Messages
301 |
Message Status was TEST and message not sent to CMAS/WEA |
The user selected "Test" from the Message Status field before sending the message. This may have been done to test our feature or train user. |
303 |
Message Error - Contact Everbridge |
Everbridge took more than 5 minutes to send the message to the IPAWS-OPEN aggregator application after the user clicks on SEND. (assuming no errors on the UI) |
305 |
Invalid FIPS - Message not accepted by CMAS/WEA |
The Federal Information Processing Standard (FIPS) code used in conjunction with the message is either invalid or is not within the client's geographical jurisdiction. |
311 |
IPAWS rejected message; Invalid Event Code used in alert |
The event code used for IPAWS dissemination is invalid; please select a valid event code. |
312 |
IPAWS rejected message; Invalid Event Code used in alert | This error code is returned if the value for the SAME Organization Code in the Alert Originator's COG Profile. |
313 |
IPAWS rejected message; Invalid scope value |
Invalid value in <scope> element for IPAWS Dissemination. |
318 |
Referenced alert not found |
Referenced CAP Alert (Cancel) message cannot be found in IPAWS-OPEN. |
400 Series - NWEM Status Messages
400 |
Message has been validated for NWEM |
Valid Format for NWEM message. |
401 |
Message not sent to NWEM |
The message was not sent due to an NWEM channel error such as channel blocking. |
402 |
Message missing required "EAS-ORG" value |
Advisory Code – to indicate that Alert validated for NWEM dissemination does not contain “EAS-ORG” parameter. |
404 |
Required reference number missing for update/cancel message |
Element <references> - empty/missing for Update and Cancel messages. |
405 |
Required language value missing - Contact Everbridge |
Element <language> - empty/missing. |
409 |
Required effective value missing - Contact Everbridge |
Element <effective> missing. |
410 |
Required Sender Agency Name value missing |
Element <senderName> - empty/missing. |
411 |
Required element missing headline |
Element <headline> - empty/missing. |
412 |
NWEM system error |
Message/BPEL dissemination system error. |
413 |
NWEM message not authorized for selected geographic area |
Element <area><geocode><value> not authorized for COG in HazCollect. |
414 |
Required Time Zone value missing |
Element <parameter> <valueName> equal to "timezone" and <value> is empty. |
415 |
Not authorized for selected Event Name |
Alert Originator not authorized for <eventCode> in COG Profile to disseminate NWEM Message. |
417 |
Required Affected region value missing |
Element <area> without a SAME <geocode> element. |
418 |
Referenced NWEM alert for update not found |
Referenced CAP Alert (Update) message cannot be found in IPAWS-OPEN |
419 |
NWEM Not authorized for entered SAME code |
Alert Originator not authorized for <geocode> in COG Profile to disseminate NWEM Message. |
420 |
Invalid parameter value - Contact Everbridge |
Element <parameter> <valueName> equal to “EAS-ORG” and <value> is “WXR”. |
423 |
Invalid CAP format - Contact Everbridge |
Multiple info block in Alert message |
424 |
Invalid Language Value - Contact Everbridge |
Element <language > - not two allowed values: "en-US" or "es-US". |
425 |
Invalid Event value - Contact Everbridge |
Element <event> - not: ‘Administrative Message/Follow up Statement’, ‘Avalanche Watch’, ‘Avalanche Warning’, ‘Child Abduction Emergency’, ‘Civil Danger Warning’, ‘Civil Emergency Message’, ‘Practice/Demo Warning’, ‘Earthquake Warning’, ‘Evacuation Immediate’, ‘Fire Warning’, ‘Hazardous Materials Warning’, ‘Law Enforcement Warning’, ‘Local Area Emergency’, ‘National Information Center’, ‘Network Message Notification’, ‘National Periodic Test’, ‘Nuclear Power Plant Warning’, ‘Radiological Hazard Warning’, ‘Routine Weekly Test’, ‘Shelter in Place Warning’, ‘911 Telephone Outage Emergency’, ‘Volcano Warning’. |
426 |
Invalid Response Type value - Contact Everbridge |
Element <responseType> is equal to any value except: Shelter, Evacuate, Prepare, Execute, Monitor, Assess, None. |
427 |
Invalid Event Type - Contact Everbridge |
More than one Element for <eventCode>. |
428 |
Selected Event Type not valid for geographic area |
eventCode valueName is not 'SAME'. |
429 |
Selected Event Type not valid - Contact Everbridge |
Value in event does not map to the eventCode value, i.e. Event="Civil Emergency Message" and eventcode value not “CEM”. |
430 |
Selected Event Type not valid - Contact Everbridge |
All eventCode values except: "AVW", "CDW", "CEM", "EQW", "EVI", "FRW", "HMW", "LEW", "NUW", "RHW", "SPW", "VOW", "AVA", "CAE", "LAE", "TOE", "ADR", "NIC", "DMO", "NPT", "RMT", "RWT", "NMN". |
431 |
Invalid expiration value - Contact Everbridge |
1) sent < expire 2) expire must not exceed sent by more than 360 minutes 3) expire must differ from sent in exactly 15 minute intervals up to 120 minutes 4) expire must differ from sent in exactly 30 minute intervals between 120 and 360 minutes. |
432 |
Invalid effective value - Contact Everbridge |
sent and effective are NOT equal. |
433 |
Invalid Onset value - Contact Everbridge |
onset contains a time. |
434 |
Invalid Sender Agency Name value |
Element <senderName> is missing or has does not have 3 comma separated values. |
435 |
Invalid value in Message to Public - special characters are not accepted |
|
436 |
Invalid Timezone value - Contact Everbridge |
Element <parameter> for timezone is missing. |
437 |
Invalid Headline value |
Element <headline> length >= 160 characters. |
438 |
Invalid Affected Area value |
Element <area><geocode> contains invalid values. |
439 |
Missing Description value |
description = empty/missing. |
440 |
Not authorized for NWEM alerts |
COGID not authorized to for HazCollect. |
441 |
Unable to reach NWEM service |
Unable to connect to Hazcollect server. |
442 |
Missing Source value |
Element <source> - empty/missing. |
443 |
Only one SAME code is accepted per NWEM alert |
Only one geocode is assigned to a <area> block for NWEM. |
500 Series - EAS Specific Status Messages
500 |
Message successfully sent to EAS |
Valid EAS Message is Disseminated. |
501 |
Message not sent to EAS - Contact Everbridge |
Message not disseminated due to channel blocking or other associated error. |
502 |
Missing Parameter value - Contact Everbridge |
A parameter value is missing. |
503 |
Invalid Parameter value - Contact Everbridge |
Advisory Code – to indicate that Alert validated for EAS dissemination does not contain “EAS-ORG” parameter. |
505 |
Invalid mimeType value - Contact Everbridge |
Element <resource> <mimeType> for broadcast content for delivery to the public does not “contain” one of the following values:
|
506 |
Expires time is greater than allowed - Contact Everbridge |
Element <expires> time more than 99.5 hrs after sent time. |
507 |
Required message description text missing - Contact Everbridge |
Element <description> is empty/missing. |
512 |
EAS system error |
Message/BPEL dissemination system error. |
515 |
Not EAS authorized for selected Event Type. Check the Type and try again. |
Alert Originator not authorized for <eventCode> in COG Profile to disseminate EAS Message. |
518 |
Update or Cancel message is missing reference ID - Contact Everbridge. |
Referenced CAP Alert (Update) message cannot be found in IPAWS-OPEN. |
519 |
Not EAS authorized for selected jurisdiction. Check the SAME code and try again. |
Alert Originator not authorized for <geocode> in COG Profile to disseminate EAS Message. |
521 |
Exceeded EAS SAME code; max limit of 31. Check selected SAME codes and try again. |
EAS CAP Alert contains more than the geocode max limit for EAS, which currently is 31 geocodes. |
600 Series - CMAS Specific Status Messages
600 |
Message successfully sent to WEA |
Everbridge receives this message if the XML document passes all validation tests and is accepted by the mobile carrier gateways. |
601 |
Message not sent to WEA - Contact Everbridge |
Everbridge receives this error message if the COG ID is blocked from using CMAS or IPAWS is unable to deliver messages to CMAS. |
602 |
Message Error - Contact Everbridge |
Everbridge should not receive this message since we are not populating this element in the XML. |
603 |
Max text length exceeded - Contact Everbridge |
The message was rejected by WEA. Possible causes:
|
604 |
Language field error - Contact Everbridge |
Everbridge should not receive this message since we hard-code the XML <language> element to en-US" or "es-US". |
605 |
Update message contains invalid Urgency, Severity, or Certainty values. Check selection and try again. |
If Alert Update message contains invalid CMAS values for <urgency>, <severity>, or <certainty> elements, then CMAC Cancel Message is disseminated. |
606 |
Invalid Event Name value. Check selection and try again. |
Invalid Event Code for CMAS dissemination. |
607 |
Polygon exceeds 100 points. Check polygon and try again. |
Element <area><polygon> contain more than 100 polygon elements. |
608 |
Marine Zone Affected Region selected. Remove and try again. |
The COG ID attempting to send the message is not approved to send CMAS/WEA messages. |
610 |
Message Error - Contact Everbridge |
Interim Status Code – to indicate a Marine Zone geocode was not disseminated to CMAS. Once all Wireless Carriers are able to handle Marine Zone codes this response will no longer be used. |
611 |
Client not authorized for WEA messages - Contact FEMA IPAWS |
Everbridge receives this message if the COG ID assigned to the client is not approved for CMAS messages |
612 |
WEA System Error - Contact Everbridge |
The cause of this error is unknown. |
613 |
Expiration time greater than 24 hours - Contact Everbridge |
Everbridge receives this message if the value in <expires> is more than 24 hours than the value in <sent> . Users are prevented from being able to set the expiration for the message to more than 24 hours. |
615 |
Not WEA authorized for selected Event Type. Check the Event Type and try again. |
Alert Originator not authorized for <eventCode> in COG Profile to disseminate CMAS Message. |
616 |
Invalid Parameter format - Contact Everbridge |
CMAMtext parameter name has the incorrect case: (e.g., not exactly "CMAMtext"). |
617 |
Message in Spanish submitted to WEA |
Advisory Code – to indicate if an Alert contains both and English and Spanish <info> blocks and <CMAMtext> <parameter> was provided in the Spanish <info> block. |
618 |
Message in Spanish not submitted to WEA |
Advisory Code – to indicate if an Alert contains both and English and Spanish <info> blocks and <CMAMtext> <parameter> was not provided in the Spanish <info> block. Spanish <CMAMtext> <parameter> needs to be provided for retrieval by Wireless Carriers. |
619 |
Not WEA authorized for selected jurisdiction. Check the SAME code and try again. |
Alert Originator not authorized for <geocode> in COG Profile to disseminate CMAS Message. |
620 |
Update or Cancel message not sent to WEA because referenced message was not sent. |
This advisory response code indicates that an Update or Cancel message was not disseminated as a WEA message to Wireless Carriers, because the referenced alter was never disseminated as a WEA message. |
621 |
Invalid characters in URL. Check the text and try again. |
One of the following not-allowed characters was included in the CMAMtext parameter:
|
800 Series - Public Non-EAS Specific Status Messages
800 |
Message successfully sent to Public Feed |
Valid Non-EAS Public Message is disseminated. |
801 |
Message not sent to Public Feed |
Message not disseminated due to channel blocking, is an EAS message, or other associated error. |
802 |
Message sent to Public channel |
This advisory response code is returned to indicate that BLOCKCHANNEL-PUBLIC is being bypassed, if the CAP Alert contains BLOCKCHANNEL-PUBLIC parameter and configuration is set to bypass BLOCKCHANNEL-PUBLIC. |
812 |
Public Feed system error - Contact Everbridge |
Message/BPEL dissemination system error. |
815 |
Not Public Feed authorized for selected Event Name. Check selection and try again. |
Alert Originator not authorized for <eventCode> in COG Profile to disseminate PUBLIC Message. |
818 |
Update message referenced not found - Contact Everbridge |
Referenced CAP Alert (Update) message cannot be found in IPAWS-OPEN. |
819 |
Not Public Feed authorized for selected jurisdiction. Check the SAME code and try again. |
Alert Originator not authorized for <geocode> in COG Profile to disseminate PUBLIC Message. |
900 Series - Everbridge Status Codes
000 |
Training mode enabled - message not sent to WEA |
Message to the user when the Training Mode flag is selected in the notification form. |
996 |
Message not sent - Contact Everbridge |
Message to the user when unable to successfully send message. |
997 |
Message not sent - Expired certificate - Contact Org Administrator. |
Message to the user when the message was successfully signed but the COG certificate has expired or there is a connection issue with IPAWS. NOTE: Everbridge will make three additional retries before posting the final 997 error. |
998 |
Message sent - Pending IPAWS Response - Refresh Page |
Message to the user when the outbound message is "stuck" in the application and the reason is not obvious or known. |
999 |
IPAWS Service Unavailable - Contact Everbridge |
Message to the user when Everbridge is unable to connect to the IPAWS-OPEN aggregator gateway. The gateway is unavailable. |
Article Feedback
While we can’t respond to you directly, we’d love to know how we can improve the article.
Please sign in to leave a comment.