Sending RCS
RCS(Rich Communication Suite) is a next-generation service that allows you to send a button and multiple message cards(Carousel) as one message. In order to send RCS service, a brand must be registered and message templates must be pre-registered at RCS Biz center in advance.
Sending RCS
The following is a code example that enables you to send messages based on various types of message formats through the RCS service.
NOTE
- For more details on specifications by message type, please refer to the Appendix. Layout Guide and Message Specs document.
- For data to enter in each table, please refer to the Table Specification document.
- To send RCS, you need to register and get your templates reviewed on the Kakao Biz Message site beforehand.
Sending RCSSMS
You can send short text messages through the RCSSMS service.
코드예제Sample Code of Sending RCSSMS
# Basic RCSSMS type + 1 BUTTON
INSERT INTO RCS_MESSAGE (
MSG_SEQNO,
RESERVE_DATE,
AGENCY_ID,
PHONE_NO,
CALLBACK,
MESSAGE_BASE_ID,
SERVICE_TYPE,
HEADER,
FOOTER,
COPY_ALLOWED,
BODY,
BUTTONS
) VALUES (
‘2022010100001’,
now(),
‘kakaoenterprise’,
‘01012345678’,
‘1544-0000’,
‘SS000000’, # Message template code
‘RCSSMS’, # [RCSSMS, RCSLMS, RCSMMS, RCSTMPL]
‘1’, # 0 : for Info, 1 : for ad
‘080-0000-0000’, # Required in case of ‘1(for ad)’
true,
‘{ "title": "","description":"This is a general RCSSMS test message.\\n" }’,
‘[
{
"suggestions":[{
"action":{
"urlAction": {
"openUrl": {
"url": "https://www.google.com"
}
},
"displayText": "Open Url",
"postback": {
"data": "set_by_open_url"
}
}
}]
}
]’
);
Sending RCSLMS
You can send a long message through RCSLMS.
코드예제Sample Code of Sending RCSLMS
# Basic RCSLMS type + 1 button
INSERT INTO RCS_MESSAGE (
MSG_SEQNO,
RESERVE_DATE,
AGENCY_ID,
PHONE_NO,
CALLBACK,
MESSAGE_BASE_ID,
SERVICE_TYPE,
HEADER,
FOOTER,
COPY_ALLOWED,
BODY,
BUTTONS
) VALUES (
‘2022010100001’,
now(),
‘kakaoenterprise’,
‘01012345678’,
‘1544-0000’,
‘SL000000’, # Message template code
‘RCSLMS’, # [RCSSMS, RCSLMS, RCSMMS, RCSTMPL]
‘1’, # 0 : for Info, 1 : for ad
‘080-0000-0000’, # Required in case of ‘1(for ad)’
true,
‘{"title": "RCSLMS title","description":" This is a general RCSLMS message."}’,
‘[
{
"suggestions":[{
"action":{
"urlAction": {
"openUrl": {
"url": "https://www.google.com"
}
},
"displayText": "Open Url",
"postback": {
"data": "set_by_open_url"
}
}
}]
}
]’
);
Sending RCSMMS(Vertical)
For RCSMMS, only pre-uploaded images can be sent. To send an image, it must be entered into the RCS_MESSAGE_CONTENTS table beforehand, and the image upload URL must be entered into the table after completion of the upload. When sending a message, the URL should be entered into the MMS_IMG_URL column.
코드예제Sample Code of Sending RCSMMS(Vertical)
# Basic RCSMMS type + 1 attachment + 1 button
INSERT INTO RCS_MESSAGE_CONTENTS(
REG_DATE,
IMG_FILE_PATH,
IMG_MIME_TYPE,
IMG_DESCRIPTION
) VALUES (
now(),
‘/files/test.jpg’,
‘image/jpg’,
‘Upload test image’
);
INSERT INTO RCS_MESSAGE (
MSG_SEQNO,
RESERVE_DATE,
PHONE_NO,
CALLBACK,
MESSAGE_BASE_ID,
SERVICE_TYPE,
HEADER,
FOOTER,
COPY_ALLOWED,
MMS_TITLE1,
MMS_MSG1,
MMG_IMG_URL1
BUTTONS
) VALUES (
‘2022010100001’,
now(),
‘01012345678’,
‘1544-0000’,
‘SM000000’, # Message template code
‘RCSMMS’, # [RCSSMS, RCSLMS, RCSMMS, RCSTMPL]
‘1’, # 0 : for Info, 1 : for ad
‘080-0000-0000’, # Required in case of ‘1(for ad)’
true,
‘20220608000001’,
‘1’,
‘MMS title’,
‘This is a general RCSMMS test message.’,
‘maapfile://testImgUrl’,
‘[
{
"suggestions":[{
"action":{
"urlAction": {
"openUrl": {
"url": "https://www.google.com"
}
},
"displayText": "Open Url",
"postback": {
"data": "set_by_open_url"
}
}
}]
}
]’
);
Sending RCSMMS(Carousel)
For RCSMMS (Carousel), you can only send images that have been uploaded in advance before sending. Carousel is a component that displays multiple horizontal slides of images or text.
코드예제Sample Code of Sending RCSMMS(Carousel)
# You can insert up to 5 carousels, with a maximum of 2 buttons per carousel.
INSERT INTO RCS_MESSAGE_CONTENTS(
REG_DATE,
IMG_FILE_PATH,
IMG_MIME_TYPE,
IMG_DESCRIPTION
) VALUES (
now(),
‘/files/caousel_001.jpg’,
‘image/jpg’,
‘Upload test image1’
);
INSERT INTO RCS_MESSAGE_CONTENTS(
REG_DATE,
IMG_FILE_PATH,
IMG_MIME_TYPE,
IMG_DESCRIPTION
) VALUES (
now(),
‘/files/caousel_002.jpg’,
‘image/jpg’,
‘Upload test image2’
);
INSERT INTO RCS_MESSAGE_CONTENTS(
REG_DATE,
IMG_FILE_PATH,
IMG_MIME_TYPE,
IMG_DESCRIPTION
) VALUES (
now(),
‘/files/caousel_003.jpg’,
‘image/jpg’,
‘Upload test image3’
);
INSERT INTO RCS_MESSAGE (
RESERVE_DATE,
PHONE_NO,
CALLBACK,
MESSAGE_BASE_ID,
SERVICE_TYPE,
HEADER,
FOOTER,
COPY_ALLOWED,
IMG_GROUP_CODE,
IMG_CNT,
MMS_TITLE1,
MMS_MSG1,
MMG_IMG_URL1,
MMS_TITLE2,
MMS_MSG2,
MMG_IMG_URL2,
MMS_TITLE3,
MMS_MSG3,
MMG_IMG_URL3,
BUTTONS
) VALUES (
now(),
‘01012345678’,
‘1544-0000’,
‘SMwMgM0300’, # Message template code
‘RCSMMS’ # [RCSSMS, RCSLMS, RCSMMS, RCSTMPL]
‘1’, # 0 : for Info, 1 : for ad
‘080-0000-0000’, # Required in case of ‘1(for ad)’
true,
‘20220608000001’,
‘1’,
‘MMS title1’,
‘1st Carousel message’’,
‘maapfile://testImgUrl_001’,
‘MMS title2’,
‘2nd Carousel meassage’’,
‘maapfile://testImgUrl_002’,
‘MMS title3’,
‘3rd Carousel message’’,
‘maapfile://testImgUrl_003’,
‘[
{
"suggestions":[{
"action":{
"urlAction": {
"openUrl": {
"url": "https://www.google.com"
}
},
"displayText": "Open Url",
"postback": {
"data": "set_by_open_url"
}
}
}]
}, # Button of 1st Carousel (1 button)
{}, # Button of 2nd Carousel (0 button)
{
"suggestions":[{
"action":{
"urlAction": {
"openUrl": {
"url": "https://www.google.com"
}
},
"displayText": "Open Url",
"postback": {
"data": "set_by_open_url"
}
}
}]
} # Button of 3rd Carousel (1 button)
]’
);
Sending RCSTMPL(Narrative)
RCSTMPL(Narrative) is a service that sends a message in the form of a pre-registered text template.
코드예제Sample Code of Sending RCSTMPL(Narrative)
# RCSTMPL
INSERT INTO RCS_MESSAGE (
RESERVE_DATE,
PHONE_NO,
CALLBACK,
MESSAGE_BASE_ID,
SERVICE_TYPE,
BODY
) VALUES (
now(),
‘01012345678’,
‘1544-0000’,
‘RCS_TMPL001’, # Message template code
‘RCSTMPL’, # [RCSSMS, RCSLMS, RCSMMS, RCSTMPL]
true,
‘{"description":"Hello. KRW 1,000 has been deposited from Gildong Hong."}’ # Modifiable section of the template
);
Sending RCSTMPL(Styled)
RCSTMPL(Styled) is a service that sends messages using pre-registered templates.
코드예제Sample Code of Sending RCSTMPL(Styled)
# RCSTMPL
INSERT INTO RCS_MESSAGE (
RESERVE_DATE,
PHONE_NO,
CALLBACK,
MESSAGE_BASE_ID,
SERVICE_TYPE,
BODY
) VALUES (
now(),
‘01012345678’,
‘1544-0000’,
‘RCS_TMPL001’, # Message template code
‘RCSTMPL’, # [RCSSMS, RCSLMS, RCSMMS, RCSTMPL]
true,
‘{
"Name of variable 1”:”Variable value”,
“Name of variable 2”:”Variable value”
}’
);
Sending Alternative Message of RCS
In case of failure to send RCS, it is possible to send alternative messages such as SMS or LMS.
코드예제Sample Code of Sending RCS + Alternative Message(SMS/LMS)
– RCSSMS + Alternative Message(SMS/LMS)
INSERT INTO RCS_MESSAGE (
RESERVE_DATE,
PHONE_NO,
CALLBACK,
MESSAGE_BASE_ID,
SERVICE_TYPE,
HEADER,
FOOTER,
COPY_ALLOWED,
BODY,
FALLBACK_YN,
FALLBACK_TYPE,
FALLBACK_CALLBACK,
FALLBACK_SUBJECT,
FALLBACK_MESSAGE
) VALUES (
now(),
‘01012345678’,
‘1544-0000’,
‘SS000000’,
‘RCSSMS’ # [RCSSMS, RCSLMS, RCSMMS, RCSTMPL]
‘1’, # 0 : for Info, 1 : for ad
‘080-0000-0000’, # Required in case of ‘1(for ad)’
true,
‘{ "title": "","description":"This is a general RCSSMS test message." }’,
true,
‘SM’, # [SM, LM]
‘1544-0000’,
‘’,
‘Alternative Message.’
);
RCS Mediator Error Cod
The mediator error codes related to RCS sending are as follows.
표Error Code legendCategory | Error Code scope of use |
---|---|
Samsung MaaP-Core | 40,000 |
Mobile carrier MaaP-FE | 50,000 |
Mobile carrier RcsBizCenter | 60,000 |
Mediator | 70,000 |
SAMSUNG MaaP-Core Error Code(40000~49999)
Samsung MaaP-Core error codes are as follows.
표SAMSUNG MaaP-Core Error Code (40000~49999)Error Code | Error Message | Description |
---|---|---|
40001 | Missing Authorization header | Valid access token in Authorization header is required for RESTful API calls. |
40002 | Missing token | Authorization header does not contain a token. Note that token type is required. |
40003 | Invalid token | Token has been tampered. |
40004 | Token has expired | Token has expired. |
40005 | Malformed token payload | Token payload has insufficient information. |
40006 | Invalid client id | Token is not issued to the client. |
40007 | Insufficient scope | Token is not authorized to use the scope. |
41000 | Internal Server Error | Internal Server Error |
41001 | RCS Request Timeout | RCS Request Timeout |
41002 | Revocation Failed | Revocation Failed |
41003 | Throttled by message rate | Throttled by message rate |
41004 | RCS Server Busy | RCS Server Busy |
41005 | RCS Server Temporarily unavailable | RCS Server Temporarily unavailable |
41006 | Session does not exist | Session does not exist |
41007 | Expired Before Session Establishment | Failed to send because it expired before RCS session connection |
41008 | Session already expired | Session already expired |
41009 | Device not support revocation | |
41010 | IMDN received even already revoked | IMDN received even already revoked |
41011 | Message was already revoked | |
41100 | Connecting RCS Allocator Failed | Message Status on Response of Sending Message API |
41101 | Connecting RCS Allocator Timeout | Message Status on Response of Sending Message API |
41102 | RCS Allocation Failed | Message Status on Response of Sending Message API |
41103 | RCS Allocation Timeout | Message Status on Response of Sending Message API |
41104 | Connecting RCS Failed | Message Status on Response of Sending Message API |
41105 | Connecting RCS Timeout | Message Status on Response of Sending Message API |
41106 | Sending Message to RCS Failed | Message Status on Response of Sending Message API |
41107 | Sending Message to RCS Timeout | Message Status on Response of Sending Message API |
41108 | RCS handle request Failed | Message Status Webhook |
41109 | RCS Internal Server Error | Message Status Webhook |
41110 | RCS User Not Found | Message Status Webhook |
41117 | Process Revocation Request Failed | Message Status Webhook |
41200 | User for Message receiving Not Found | |
41201 | Message Not Acceptable | Occurs when the SDP of the terminal does not have a feature tag required for message transmission during the message session formation process. |
41210 | User is not capable for TEXT | Occurs when there is no chat in the user's capability when the bot sends a text message. |
41211 | User is not capable for FT | Occurs when the bot does not have fthttp in the user's capability when sending a File message. |
41212 | User is not capable for RICHCARD | Occurs when bot or chatbot.sa does not exist in user capability when bot sends richcard message. |
41220 | User is not capable for XBOTMESSAGE 1.0 | clipboardAction, messageHeader, messageFooter, openrichcard, geolocationPushMessage, copyAllowed |
41221 | User is not capable for XBOTMESSAGE 1.1 | Occurs when clipboardAction, localBrowserAction, messageHeader, messageFooter, openrichcard, geolocationPushMessage, and copyAllowedBot send an extended message corresponding to v1.1, and bot, chatbot.sa, and xbotmessage 1.1 are not present in the user's capabilities. At this time, in xbotmessage, the parent version includes the child version. |
41222 | User is not capable for XBOTMESSAGE 1.2 | clipboardAction, localBrowserAction, messageHeader, messageFooter, openrichcard, geolocationPushMessage, copyAllowed, shareAction, streamingPlay |
41230 | User is not capable for OPENRICHARD 1.0 | Occurs when bot, chatbot.sa, xbotmessage 1.0 does not exist in user's capability when sending Openrichcard corresponding to v 1.0 |
41231 | User is not capable for OPENRICHARD 1.1 | Since the Openrichcard corresponding to v1.1 is currently not defined and used, this code does not actually occur. |
41232 | User is not capable for OPENRICHARD 1.2 | Since Openrichcard corresponding to v1.2 is currently not defined and used, this code does not actually occur. |
41240 | User is not capable for GEOLOCATION PUSH REQUEST | User is not capable for GEOLOCATION PUSH REQUEST |
41250 | Failed to get message content type | Failed to get message content type |
41300 | File download failed | |
42001 | Invalid state | Bot is in an invalid state to call the API. |
42002 | Invalid message | Message is missing required fields or has malformed format. |
42003 | Invalid date/time format | Date and time format does not comply with ISO 8601. |
42004 | Missing contact | Missing recipient information. |
42005 | Invalid contact | Incorrect contact format (e.g., phone number is not start with '+') |
42006 | Emulator access only | Bot is in a state which allows access via Emulator only. |
42007 | Contact not in whitelist | Bot is accessible only to authorized users via MaaP client. |
42008 | Missing message content | Token Has Expired |
42009 | Invalid message content | Message is not any of textMessage, fileMessage, audioMessage, geolocationPushMessage, richcardMessage, or isTyping. |
42010 | Ambiguous message | One and only one of textMessage, fileMessage, audioMessage, geolocationPushMessage, richcardMessage, or isTyping should be provided if sending a message to the user. |
42011 | Invalid message status | Invalid MessageStatus |
42012 | Invalid isTyping status | Invalid IsTyping Status |
42013 | Invalid traffic type | Invalid TrafficType |
42014 | Invalid suggested chiplist association | suggestedChipList can be used together with one and only one of textMessage, fileMessage, audioMessage, geolocationPushMessage, or richcardMessage. |
42015 | Empty text message | Empty TextMessage |
42031 | Missing richcard | richcardMessage should contain a message, which should contain either generalPurposeCard or generalPurposeCardCarousel. |
42032 | Ambiguous richcard | A message should contain either richcard or richcard carousel. |
42033 | Too many richcards | Richcard carousel exceeds the maximum allowed richcards. |
42034 | Missing richcard layout | generalPurposeCard or generalPurposeCardCarousel should contain layout. |
42035 | Missing richcard content | generalPurposeCard or generalPurposeCardCarousel should contain content. |
42036 | Invalid cardOrientation | cardOrientation should be either HORIZONTAL or VERTICAL. |
42037 | Missing image alignment | Richcard HORIZONAL orientation should contain image alignment. |
42038 | Invalid image alignment | imageAlignment should be either LEFT or RIGHT. |
42039 | Redundant image alignment | Richcard VERTICAL orientation should not contain image alignment. |
42040 | Invalid richcard carousel cardWidth | Richcard carousel cardWidth should be either SMALL_WIDTH or MEDIUM_WIDTH. |
42041 | Mismatched media height | Media height cannot be TALL_HEIGHT for SMALL_WIDTH carousel. |
42042 | Invalid richcard content | generalPurposeCard or generalPurposeCardCarousel content should have at least one of media, title, or description. |
42043 | Invalid suggestions | Suggestion list should contain at least one suggested reply or action. |
42044 | Too many suggestions in chiplist (max 11) | Suggestion list exceeds the maximum allowed items. |
42045 | Invalid suggestion | Suggestion should be either reply or action. |
42046 | Ambiguous suggestion | Suggestion should be one and only one reply or action. |
42047 | Ambiguous suggested action | Suggested action should be one and only one type of action. |
42048 | Too many suggestions in richcard (max 4) | Richcard suggestion list exceeds the maximun allowed items (4). |
42049 | Too many suggestion data (max 2048) | Suggestion data exceeds the maxmun data size (2048). |
42050 | Invalid Action | Either latitude and longitude or query are required in location. |
42051 | Invalid location | Either latitude and longitude or query are required in location. |
42052 | Ambiguous location | Location should contain either query or latitude and longitude. |
42053 | Invalid mapAction | One of showLocation or requestLocationPush is required in mapAction. |
42054 | Ambiguous mapAction | mapAction should contain either showLocation or requestLocationPush. |
42055 | Invalid dialerAction | One of dialPhoneNumber, dialEnrichedCall, or dialVideoCall is required in dialerAction. |
42056 | Ambiguous dialerAction | dialerAction should contain only one type of dialer action. |
42057 | Invalid composeAction | Either composeTextMessage or composeRecordingMessage is required in composeAction. |
42058 | Ambiguous composeAction | composeAction should contain only one type of compose action. |
42059 | Invalid settingsAction | Either enableDisplayedNotifications or disableAnonymization is required in settings action. |
42060 | Ambiguous settingsAction | settingsAction should contain only one type of settings action. |
42061 | Invalid ClipboardAction | ClipboardAciton should contain copy text. |
42062 | Missing localBrowserAction | LocalBrowserAction should contain url. |
42063 | Invalid ShareAction | ShareAction should contain url. |
42064 | Ambiguous ShareAction | Sharetext of ShareAction should contain text. |
42100 | Invalid thumbnail | thumbnailFileSize and thumbnailContentType should be provided together with thumbnailUrl. |
42101 | Missing fileUrl | Missing FileUrl |
42102 | Missing audio fileUrl | Missing AudioFile Url |
42103 | Missing pos | Missing Pos |
42104 | Missing Media information | Missing Media Information |
42105 | Missing Media Content Type | Missing Media Information |
42106 | Missing Media FileSize | Missing Media Information |
42107 | Missing Media Height | Missing Media Information |
42108 | Missing postback data information | Missing postback data information |
42201 | Invalid Location Label | geolocationPushMessage should not contain label length > 200 Characters. |
42202 | Invalid media content description | Content Description of media is not in limit < 1 Character or > 200 Character. |
42203 | Invalid media title | Media title is not in limit < 1 Character or > 200 Character. |
42204 | Invalid media description | Media card description is not in limit < 1 Character or > 2000 Character. |
42205 | Too many contents in richard carousel | Richcard carousel list exceeds the maximum allowed items (10). |
42206 | Invalid media file size | Minimum Value for file size is 0. |
42207 | Invalid expiry time format | Invalid expiry time |
42208 | Invalid expiry time | Invalid expiry time |
42301 | Ambiguous Openrichcard | OpenrichcardMessage should contain a message, which should contain either generalPurposeCard or generalPurposeCardCarousel. |
42302 | Missing Openrichcard | A OpenrichcardMessage should contain open_rich_card. |
42303 | Missing Openrichcard Layout Widget | Openrichcard should contain widget. |
42304 | Missing Openrichcard View Content | View layout of Openrichcard do not have mandatory parameters. |
42305 | Missing Openrichcard LinearLayout Content | Parameters in LinearLayout have invalid value. |
42306 | Missing Openrichcard Textview Content | TextView layout of Openrichcard do not have mandatory parameters. |
42307 | Invalid Contents In Openrichcard Textview | Parameters in TextView have invalid value. |
42308 | Invalid Text Length In Openrichcard Textview | text is not limit in [0 < text < 2000]. |
42309 | Missing Openrichcard Imageview Content | ImageView layout of Openrichcard do not have mandatory parameters. |
42310 | Too Small Media In Openrichcard Imageview | MediaFileSize is under 0. |
42311 | Invalid Openrichcard Imageview Scaletype | ScaleType value of ImageView should be center or centerCrop or centerInside or fitCenter or fitEnd or fitStart or fitXY or matrix. |
42312 | Missing Openrichcard width or height | width or height is not in Openrichcard. |
42313 | Invalid Openrichcard width or height | width or height in Openrichcard has invalid value. |
42314 | Invalid Openrichcard Common Contents | Common Contents in Openrichcard has invalid value. |
42315 | Too many child in open rich card | |
42401 | Invalid file type | Invalid file type |
42402 | Download failure | Download failure |
42501 | Missing contact | Missing contact |
42502 | Missing content | Missing content |
42503 | Missing title | Missing title |
42504 | Missing description | Missing description |
42505 | Missing image url | Missing image url |
42506 | Missing image type | Missing image type |
42507 | Missing button link | Missing button link |
42508 | Missing button text | Missing button text |
42509 | Invalid title | Invalid title |
42510 | Invalid description | Invalid description |
42511 | Invalid image url address | Invalid image url address |
42512 | Invalid button url address | Invalid button url address |
42513 | Invalid button text | Invalid button text |
42514 | Duplicated message ID | Duplicated message ID |
42601 | Too Many Request | Too Many Request |
Mobile carrier MaaP-FE Error Code(50000~59999)
Mobile carrier MaaP-FE error codes (50000~59999) are as follows.
표Mobile carrier MaaP-FE Error Code (50000~59999)Category | Error Code | Error Message | Description |
---|---|---|---|
N/A | 40000~49999 | MaaP-Core | Refer to SamSung MaaP-Core Error Code |
Authorization | 50001 | Missing Authorization header | |
50002 | Missing token | Missing Authorization header value | |
50003 | Invaild token | Tokens do not match. | |
50004 | Token has expired | Token has expired. | |
50005 | Authorization Error | Authentication Token Error | |
50006 | Invalid client id | The requested account information could not be found.(BP ID) | |
50007 | Invalid sender id | The requested broker transfer account could not be found.(RCS ID) | |
50008 | Invalid password | Invalid password | |
50009 | NonAllowedIp | IP is not allowed access. | |
50100 | Invalid state | Message transmission is not possible. (Request denied by server) | |
Limit | 50201 | Message TPS Exceeded | RCS message TPS exceeded. |
50202 | Message Quota Exceeded | RCS message quota exceeded. | |
- | 59001 | SystemError | System Error |
59002 | IOError | IO error occurred | |
General | 51001 | SystemError | System Error |
51002 | IOError | IO error occurred | |
51003 | DuplicationError | Duplicate Key Error | |
51004 | ParameterError | Request parameter format error | |
51005 | JsonParsingError | Request Body JSON Parsing Error | |
51006 | DataNotFound | Data not found. | |
51007 | Duplicated AutoReplyMsgId | Autoreply message ID already in use. | |
51008 | Duplicated PostbackId | Postback ID already in use. | |
Chatbot | 52001 | Invalid phone number format | The phone number format does not match. |
52002 | Invalid message status | The request cannot be processed. | |
52003 | Bot Aleady Exists | Chatbot ID already in use. | |
52004 | Bot Creation Failed | Cannot create chatbot. | |
52005 | Bot Update Failed | Chatbot information cannot be changed. | |
52006 | Brand Delete Failed | Brands with chatbots cannot be deleted. | |
52007 | InvalidChatbotServiceType | Chatbot Type should be set to a2p, chatbot | |
52008 | MismatchedChatbotId | Chatbot ID and Body Parameter mismatch in request URL parameter | |
52009 | Persistent Menu Permission Error | Persistent Menu registration is not allowed. | |
52010 | Invalid Persistent Menu Data | Persistent menu JSON data error | |
- | 52016 | Message Transmission Time Exceeding | Real-time messages are not delivered to Samsung within 10 seconds of incoming |
52023 | Messagebase Id Stopped Temporarily | Attempting to transmit by constructing a full message with a message base message whose message base status is 'pause’. | |
Webhook I/F | 52101 | Invalid Webhook Request Parameter | Invalid webhook broker request parameter. |
52102 | Webhook Host Connect Error | Webhook relay system connection error. | |
52103 | Webhook Host Server Request Failure | Mediator Webhook send request failed. | |
52104 | Webhook Response Receive Failure | Error receiving Mediator Webhook processing response. | |
52105 | Webhook Message Non Receive Failure | A webhook message not received error occurred. | |
52106 | Webhook Message Process Failure | A webhook message processing error has occurred. | |
Auto Reply Message | 52201 | Invalid Auto Reply Message ID | Autoresponder ID does not exist. |
52202 | Auto Reply Message Contents Error | There are required items missing from the content of the autoresponder message. | |
File | 53001 | Invalid file type | The file type the request could not be processed. |
53002 | File Attribute Error | File attribute error. | |
53003 | FileID format Error | File ID is missing or does not fit the ID format. | |
53004 | FileUploadError | File upload error | |
53005 | InvalidMultiPartRequest | Multipart data transfer error | |
53006 | Attached File Size Error | Upload file size exceeded | |
Webhook (Message) | 54001 | Invaild Contact number User | Not our customer. |
54002 | No Rcs Capability | This customer is your own customer, but is not a subscriber capable of receiving RCS messages. | |
54003 | Unable Sending to Recipient | Terminal equipment cannot transmit RCS messages. | |
54004 | MaaP Internal Error | Sending failed due to an issue in the MaaS system or RCS protocol (Samsung error 40001 ~ 41100, 42601) | |
Brand, Corp | 55001 | Corp Content Error | |
55002 | Invalid Property | Required parameter validation error | |
55101 | Agency Content Error | There are required fields missing agency information content. | |
55102 | Invalid AgencyId | AgencyID does not exist. | |
55103 | AgencyID permission error | AgencyID without agency authority to BrandID | |
55104 | Contract Content Error | The contract information is inaccurate or missing required items. | |
55201 | Brand Content Error | There are required fields that are missing brand information. | |
55202 | Brand name Error | Brand name is missing. | |
55203 | Brand profile image Error | Brand profile image is missing. | |
55204 | Brand CS number Error | Brand CS number is missing. | |
55205 | Brand menu Error | The maximum number of branded menus has been exceeded or is incorrect. | |
55206 | Brand category Error | Brand category settings are incorrect. | |
55207 | Brand homepage Error | Brand home page settings are incorrect. | |
55208 | Brand email Error | Brand email settings are incorrect. | |
55209 | Brand address Error | Brand address is incorrect. | |
55210 | Invalid BrandID | Brand ID does not exist. | |
55301 | Bot Content Error | There are inaccurate or missing required items in the chatbot information. | |
55302 | Invalid BotID | BotID (caller ID) does not match phone number format. | |
55303 | BotID permission error | BotID not present in BrandID | |
MessageBase | 55501 | Messagebase Content Error | The message base content is incorrect or has required fields missing. |
55502 | Invalid MessagebaseID | MessagebaseID does not exist. | |
55503 | MessagebaseID permission error | MessagebaseID that does not exist in BrandID. | |
55504 | Invalid formatstring | There is a required item missing from the messagebase's formatstring. | |
55505 | Invalid messagebase Policy Info | Policy Info in messagebase is incorrect or has required items missing. | |
55506 | Invalid messagebase param | Param in messagebase contains an incorrect or missing required item. | |
55507 | Invalid messagebase attribute | Attribute in messagebase contains incorrect or missing required fields. | |
55508 | Invalid messagebase type | There is an incorrect or missing required field of type in messagebase. | |
55509 | mismatching Product type | MessagebaseID does not match product type. | |
55601 | MessagebaseForm Content Error | The MessagebaseForm content is incorrect or has required fields missing. | |
55602 | Invalid messagebaseformID | Messagebaseform ID does not exist. | |
55603 | Invalid MessageBase ProductCode | Product code error in messaegBase | |
Send Message | 55701 | prohibited text content | "(Advertisement)" is not available. |
55702 | Action button Permission error | Action button was used in messagebaseID where action button is not allowed. | |
55703 | prohibited header value | Use of disallowed header values | |
55704 | prohibited footer field | Using a footer that does not match the header value (ex. header is 0, but there is a footer) | |
55705 | missing footer content | Missing footer value ((ex. header is 1, but footer is not) | |
55706 | footer content syntax Error | footer validation error (ex. number, hyphen only, 20 digits) | |
55707 | content pattern error | Mismatch with registered pattern. | |
55708 | Exceeded max character of title | Title exceeded the maximum number of characters. | |
55709 | Exceeded max character of description | Description exceeded the maximum number of characters. | |
55710 | Exceeded max number of buttons | Maximum number of buttons exceeded. | |
55711 | mismatching number of carousel card | Input does not match number of card in messagebaseID | |
55712 | Exceeded max size of media | Maximum media capacity exceeded. | |
55714 | Expired ReplyId | Reply ID has expired. | |
55715 | Not Found ReplyId | Reply ID does not exist. | |
55801 | GwVendor Content Error | Mediator information is incorrect or missing required fields. | |
55802 | Invalid message | The message format is incorrect or has required fields missing. | |
55803 | Message Syntax Error | The method of describing the message is incorrect. | |
55804 | Missing message content | Message content is missing or inaccurate. | |
55805 | Invalid message content | This is the type of message the request cannot be processed. | |
55806 | Duplicated MessageId | Message delivery is requested more than once with the same message ID. | |
55807 | Invalid Chatbot Permission | Chatbot permission error. | |
55808 | Invalid Chatbot Status | Chatbot status not available for outgoing. | |
55809 | Invalid Agency Permission | Agency permission error. | |
55810 | Invalid Expiry Field | Message expiration date input error. | |
55811 | Exceeded Max Character Of Param | The length of the messagebase parameter is greater than or equal to the limit. | |
55812 | Buttons Not Allowed | This is a message base that cannot receive button fields. | |
55813 | Exceed Button Text Length | Exceeds maximum number of button characters. | |
55814 | Invalid MessageBase Buttons | Button format error. | |
55815 | Message Body File Not Found | File does not exist or usageType error. | |
55816 | Mismatched Suggestions Count | Do not allow empty suggestions array. | |
55817 | Invalid Dest Phone Number | Received number format error. | |
55818 | Invalid MessageBase Id | Messagebase ID does not exist. | |
55819 | Invalid Chatbot Id | Chatbot ID does not exist. | |
55820 | Revoked Message | Webhook Revoked message | |
55821 | Etc TimeOut | Transmission success uncertain (revocation fail, etc.) | |
55822 | Canceled Message | Message canceled, not delivered | |
55822 | Invalid Chatbot Yn | Interactive service not available. | |
55823 | Mismatched suggestedChipList Count | Disallow Empty suggested ChipList array | |
55824 | Chiplist Not Allowed | Chiplist field is not available. | |
55825 | Buttons Reply Not Allowed | You cannot use Reply in a button field. | |
55880 | Mismatched CarouselButton Count | Different number of message card buttons. | |
55881 | Mismatched ChipList Count | Exceeded the number of chip lists. | |
55882 | ChipList Not Allowed | ChipList not available | |
55883 | Invalid ReplyId | Not a valid replyId | |
55884 | Missing ReplyId | Missing replyId value | |
55885 | Invalid User Contact For SessionMessage | Receive number not matching replyId | |
55886 | Invalid ChatbotId For Session Message | Not Chatbot ID matching replyId | |
55887 | Invalid MessageBase ProductCode For Session Message | Messagebase product code is not session message capable. | |
55888 | Not Allowed Chatbot For Session Message | Chatbot not capable of Session Messaging. | |
55900 | Non Retryable Error Caused By Invalid Message | Delivery failed due to incorrect message format and retry is not possible (Samsung error 42001 ~ 42514) | |
56002 | Revocation Failed | Message recall failure (Samsung error 41002) | |
56007 | Expired Before Session Establishment | Failed to send due to expiration before RCS session connection (Samsung error 41007) | |
59002 | Backend Error | Backend(Samsung MaaP G/W) server internal error | |
59003 | Backend Timeout | Backend(Samsung MaaP G/W) Server Timeout Occurred | |
59999 | Etc Error | Other undefined Error (Webhook Canceled message, etc.) | |
Temporary failure code | 51900 | Not Found Handler | Bad request. |
51901 | Samsung MaaP Connect IF Error | Samsung MaaS Gateway NB API Interworking Error | |
51902 | Samsung MaaP Service IF Error | Samsung MaaS Registry Chatbot API Integration Error | |
51903 | Capri IF Error | Capri Interworking error | |
51904 | Webhook Execute Imposible Status Failure | A webhook unprocessable status error occurred. | |
51905 | Webhook CDR Log Writing Failure | Failed to create Webhook message delivery billing history. | |
51906 | Invalid Webhook Url | Invalid Webhook Url. | |
51907 | Expired Webhook Message | This is an expired message. | |
51908 | Exceed Retry Count to Send Message | Message delivery failed due to excessive retries. | |
51909 | Non Existing Webhook Message | There is no webhook message. | |
51910 | Non Existing Webhook GW Vendor | Webhook shipper information does not exist. | |
51911 | No Subscription | There is no contractual relationship. | |
51912 | Failure in Preperation for sending Webhook | An error occurred while preparing a webhook message. | |
51913 | Failure in Updating Webhook Sending Result State | An error occurred while updating the status as a result of sending the Webhook. | |
51914 | Failure in Updating CDR Result State | An error occurred while updating the resulting CDR status. | |
51915 | Failure in Updating Completion Result State | An error occurred updating status as a result of completion processing. | |
51916 | Failure in Updating Expiration Result State | Expiration Handling Result An error occurred while updating the status. | |
51917 | Webhook Msg Log Creation Error | An error occurred during the create message history operation. | |
51918 | Webhook Msg Log Creation Failure | The create message history operation failed. | |
51919 | Invalid Webhook Receive Request Error | Invalid Webhook Request Error. | |
51920 | Non Existing Chatbot For Request | Information on request interactive chatbot does not exist. | |
51921 | Non Usable Chatbot State Error | Unavailable chatbot status error. | |
51922 | Non Existing Gw Vendor For Request | Interactive mediator information does not exist for the requesting interactive chatbot. | |
51923 | Non Definition Mo Message Url for Chatbot | Chatbot Mo sending URL information is undefined. | |
51924 | Webhook Gateway Execution Error | Webhook receive gateway execution error | |
51925 | Not Allowed Request Event Error | Unacceptable webhook event request error | |
51926 | Webhook Receive Execution Error | Error performing webhook receive processing | |
51927 | Webhook Receive Async Execution Error | Webhook receive processing asynchronous execution error | |
51928 | Non Definition Webhook Url for Gw Vendor Cid | Mediator CID Webhook transmission URL information is undefined. | |
51929 | Non Target GwVendor for CDR Log | This is a mediator that is not subject to billing. | |
51930 | Non Received Webhook Command Error Log | It is an execution command object non-delivery error. | |
51931 | Mo Message Registration Error | Mo message DB registration error occurred. | |
51932 | Mo Message Registration Failuer | Mo message DB registration operation failed. | |
51933 | Auto Reply Message Sending Error | An autoresponder sending action error has occurred. | |
51934 | Non Service Supported Error | This is an unprocessed service. | |
51935 | Samsung MaaP Core File Server Connection Error | Samsung MaaP Core file server connection error. | |
51936 | Message FileMessage Event File Download Error | File message download performance of file message event An error has occurred. | |
51937 | Message FileMessage Event File Download Error | File message download performance of file message event An error has occurred. | |
51938 | Message FileMessage Registration to DB Error | File information DB registration error for file message event occurred. | |
51939 | Message FileMessage Registration to DB Failure | The file information DB registration operation of the file message event failed. | |
51950 | Webhook Scheduler Async Execution Error | Webhook scheduler asynchronous execution error | |
51951 | Webhook Scheduler DB Execution Error | Webhook scheduler DB execution error | |
51952 | Webhook Scheduler DB Execution Failuer | Webhook Scheduler DB Execution Failed | |
51953 | Webhook Scheduler Process Execution Error | Webhook scheduler process execution error | |
51954 | Webhook Scheduler Process Execution Failuer | Webhook scheduler process failed | |
51955 | Webhook Scheduler Processor Execution Error | Webhook Scheduler Processor Execution Error | |
51956 | Webhook Scheduler Processor Execution Failuer | Webhook scheduler processor failed. | |
51957 | Non Existing Mo Message Error | Mo message does not exist. |
Mobile carrier RcsBizCenter Error code(60000~69999)
Mobile carrier RcsBizCenter error codes (60000~69999) are as follows.
표Mobile carrier RcsBizCenter Error code (60000~69999)Error Code (AS IS) |
Error Code (TO BE) |
Error Message | Description |
---|---|---|---|
60004 | 60004 | No Content | Request processed successfully, but no data. |
61001 | 61001 | Missing Authorization header | Missing Authorization header parameter |
61002 | 61002 | Missing Token | Missing Authorization header value (Token) |
61003 | 61003 | Invalid token | Invalid Token |
61004 | 61004 | Token has expired | Token has expired |
61005 | 61005 | Invalid client id | Invalid client id |
61006 | 61006 | Invalid secret key | Invalid secret key |
63001 | 63001 | No Brand Permission | No Brand Permission |
64001 | 64001 | Missing X-RCS-BrandKey header | Missing X-RCS-BrandKey header |
64002 | 64002 | Invalid Brand Key | Brand Key error in X-RCS-BrandKey |
64101 | 64101 | Invalid brandId on path parameter | Brand ID error in URL |
64102 | 64102 | Invalid agencyId on path parameter | Agency ID error in URL |
64103 | 64103 | Invalid corpRegNum on path parameter | Business registration number error in URL |
64104 | 64104 | Invalid personId on path parameter | Person ID error in URL |
64105 | 64105 | Invalid chatbotId on path parameter | Chatbot ID error in URL |
64106 | 64106 | Invalid messagebaseId on path parameter | Messagebase ID error in URL |
64107 | 64107 | Invalid messagebaseformId on path parameter | messagebaseform id error in url |
64201 | 64201 | Invalid query parameter ({name of paramter}) | Invalid Query parameter: (corresponding parameter) |
64202 | 64202 | Invalid query parameter value ({name of paramter}:{value}) | Query parameter value error: (error occurrence value) |
64203 | 64203 | query paramter required ({name of paramter}) | Missing Required Query Parameter: (Missing Parameter) |
64301 | 64301 | Missing Body data | Missing Body Data |
64302 | 64302 | Invalid JSON format | Body Data JSON Format Error |
64303 | 64303 | Invalid type of Attribute ({name of attribute}) | Attribute type error: (Error Occurring attribute) |
64304 | 64304 | Over specified size ({name of attribute}) | Exceeding the specified size: (attribute exceeding the size) |
64305 | 64305 | Missing Certification document | Missing communication service use certificate file when registering caller number |
64306 | 64306 | Exceed MDN registration quantity | Exceeds the number of registered caller IDs when registering the sender number |
64307 | 64307 | Missing MDN | Missing sender number when registering sender number |
64308 | 64308 | Invalid MDN format | Sender number format error when registering the sender number |
64309 | 64309 | Missing chatbot name | Missing chatbot name when registering caller number |
64310 | 64310 | Invalid display format | Display setting format error when registering caller number |
64311 | 64311 | Invalid smsmo format | Error in smsmo format when registering sender number |
64312 | 64312 | Missing messagebaseformId | Missing template form ID when registering template |
64313 | 64313 | Invalid messagebaseformId | Template form ID error when registering template |
64314 | 64314 | Missing Template name | Missing template name when registering template |
64315 | 64315 | Missing brandId | Brand ID missing when registering template |
64316 | 64316 | Invalid brandId | Brand ID error when registering template |
64317 | 64317 | Invalid agencyId | Agency ID error when registering template |
64318 | 64318 | Invalid formattedString format | FormattedString format error when registering template |
Mediator Error Code(70000~79999)
The Mediator Error code (70000~79999) is as follows.
표Mediator Error Code (70000~79999)Category | Error Code(RCS) | Error Code (TCP/CMA) |
Error Code (Xroshot) |
Error Message | Description |
---|---|---|---|---|---|
MaaP-Core | 40000~49999 | - | N/A | - | Refer to SamSung MaaS-Core Error Code |
MaaP-FE | 50000~59999 | N/A | - | Refer to MaaP-FE Error Code | |
RcsBizCenter | 60000~69999 | N/A | - | Refer to RcsBizCenter Error Code | |
Success | 00000 | 00000 | 0 | Success | Success |
Authorization | 70001 | Missing Authorization header | There is no authentication information in the HTTP request header. | ||
70002 | Missing token | There is no token in the credential. | |||
70003 | Invaild token | Tokens do not match. | |||
70004 | Token has expired | Token has expired. | |||
70005 | 70005 | 2 | Authorization Error | Authentication failed. | |
70006 | 70006 | Invalid client id | The requested account information could not be found (BP ID). | ||
70007 | 70007 | 5 | Invalid sender id | The requested relayer transfer account could not be found (RCS ID). | |
70008 | 70008 | 7, 8 | Invalid password | Invalid password | |
70009 | 17 | Non allowed ip | The IP is not allowed to access. | ||
General | 71001 | 71001 | 1, 500, 503, 504, 600, 603 |
System Error | System Error |
71002 | IOError | IOError | |||
71003 | 71003 | Duplication Error | Duplicate Key Error | ||
71004 | 71004 | Parameter Error | Request parameter format error | ||
71005 | 71005 | Json Parsing Error | Request Body JSON parsing error | ||
71006 | 71006 | Data Not Found | Data not found | ||
71007 | 71007 | 400 | Not Found Handler | This is an invalid request. | |
71008 | 71008 | Missing Mandatory Parameter | Required parameters are missing | ||
71009 | Invalid Data State | Invalid data state. | |||
71010 | MAAP-FE API Error | MAAP-FE API Error | |||
71011 | Kisa GW Error | Kisa GW Error | |||
Message | 72100 | 99, 403 |
Invalid State | Message transmission is not possible. (request denied by server) | |
72101 | 72101 | Common Info Error | Common message information is incorrect or missing required items. | ||
72102 | Legacy Info Error | Legacy message information is incorrect or has required items missing. | |||
72103 | 72103 | Rcs Info Error | The RCS message information is incorrect or has required items missing. | ||
72104 | 72104 | Message TPS Exceeded | RCS message TPS exceeded. | ||
72106 | 72106 | Message Media Not Found | Media files not found. | ||
72107 | 72107 | Invalid Media File Type | The file type the request could not be processed. | ||
72108 | 3 | Invalid Message Type | Message format error (if it does not conform to the message specification) | ||
72109 | 2101, 2152 |
Invalid Content Type | Not the right content | ||
72110 | 90 | Exceeded number of contents | Exceeded number of contents (Internal Agent) | ||
72111 | 91 | Data Type Error | Data Type Error (Internal Agent) | ||
72112 | 92 | Attached File Error | Attached File Error (Internal Agent) | ||
72113 | 93 | File Upload Error | File upload failed | ||
72114 | 94 | Convert Timeout | Convert Timeout | ||
72115 | 95 | Attached file size Error | Attached file size Error | ||
72116 | 96 | Webfile Download Error | Webfile Download Error | ||
72117 | 72117 | 208 | Exceeded message content size | Message overflowed and not received | |
72118 | 72118 | 214 | Sub Type Error | Sub Type Error (Failed to send) | |
72119 | 222 | Invalied Data Type | Invalied Data Type | ||
72120 | 2100 | Message Format Error | Message Format Error | ||
72121 | 2104 | Exceed Content Size | Content size too large to process | ||
72122 | 72122 | Invalid Chatbot Permission | There is no contractual relationship or the chatbot does not exist | ||
72123 | 72123 | Invalid Service Type | Not a valid message service type | ||
72124 | 72124 | Invalid Service Permission | Unable to send because there is no permission for the message service type | ||
72125 | 72125 | Invalid Expiry Option | Not a valid message Expiry Option | ||
72126 | 72126 | Invalid Header | Not a valid message header | ||
72127 | 72127 | Invalid Footer | Not a valid message footer | ||
72128 | 72128 | MessageSMSQuotaExceeded | Exceeded SMS sending quantity | ||
72129 | 72129 | MessageLMSQuotaExceeded | Exceeded LMS sending quantity | ||
72130 | 72130 | MessageMMSQuotaExceeded | Exceeded MMS sending quantity | ||
72131 | 72131 | MessageTMPLTQuotaExceeded | Exceeded TMPLT sending quantity | ||
72132 | Message CHAT Quota Exceeded | Exceeded CHAT sending quantity | |||
72133 | Chiplist Not Allowed | Chip list not available. | |||
72134 | Invalid Chatbot Chat Permission | There is no authority to two -way chatbots. | |||
72135 | Not Found Corp Chat | There is no two -way corporate data. | |||
72136 | Invalid Chat Message Permission | You are not entitled to interactive services. | |||
72137 | Not Found ReplyId | Reply ID does not exist. | |||
72138 | Expired ReplyId | Reply ID valid time has expired. | |||
Service | 73001 | 73001 | 27 | Unavailable Service | Send unregistered products |
73002 | UnsubscribedLegacyService | Legacyinfo is present, but there is no crossshot ID in the subscription information | |||
Spam | 74001 | 101 | Message Content Spam | Message Content Spam | |
74002 | 102 | Sender Number Spam | Sender Number Spam | ||
74003 | 103, 4404 | Receipient Number Spam | Receipient Number Spam | ||
74004 | 104 | Callback Number Spam | Callback Number Spam | ||
74005 | 108 | Same Message Limit | Same Message Limit | ||
74006 | 111 | Same Receipient Number Limit | Same Receipient Number Limit | ||
74007 | 114 | Number Theft Block | Number theft/alteration prevention blocking | ||
74008 | 115 | Callback Number Block | Block unregistered callback numbers | ||
74009 | 116 | Number Rule Violation Block | Block number rule violation | ||
NPDB | 75001 | 209 | NPDB user (send fail) | Number Portability DataBase user (send fail) | |
75002 | 212, 404, 202 |
There is no subscriber | There is no subscriber | ||
75003 | 213 | CAPRI & NPDB Error | Number Portability DataBase error | ||
75004 | 9, 10, 203 |
There is no end user | End-User (user) non-existence, termination, suspension | ||
75005 | 227, 228, 2107, 216 |
Receipient's number Error | Received number error (digit error, missing number) | ||
75006 | 2106 | Sender number Error | Sender number Error | ||
75007 | No Rcs Capability | This customer is a customer of the company, but is not a subscriber capable of receiving RCS messages. | |||
75008 | 75008 | Invalid User Contact | Incorrect standard call number | ||
Schedule Manager | 76001 | Capri interface Error | CAPRI integration failure | ||
76002 | Schedule Manager Internal Error | Schedule Manager Internal Error | |||
Xroshot Sender | 76003 | Not Found Rcs Subscriber | No RCS subscription information | ||
76004 | Xroshot Sender Internal Error | Xroshot Sender Internal Error | |||
Xroshot Manager | 76005 | Xroshot Manager Internal Error | Xroshot Manager Internal Error | ||
webhook | 77001 | 16, 112, 211, 487 |
Expired message received time | Legacy : Expired message received time (If you do not receive a 24-hour report after sending a message) RCS 3 days | |
77002 | 221 | Invalied Message Sequence | In case the message sequence number is incorrect | ||
77003 | Non Existing Webhook Message | Webhook dispatch message does not exist | |||
77004 | Invalid Webhook Message | This is an invalid webhook sending message. | |||
77005 | Non Existing Webhook Corporation | Webhook company information does not exist. | |||
77006 | Webhook Msg Log Writing Failure | Failed to write a webook message transfer history information. | |||
77007 | Disabled Send Webhook Msg | The webhook sending setting of the corresponding RCS ID is turned off. | |||
77008 | Webhook Failure Status | Receive webhook status code failure. | |||
77009 | Invalid Webhook Message | Webhook message is invalid. | |||
77010 | Invalid Webhook EventType | Webhook EventType is invalid. | |||
77011 | Invalid Webhook Message Status | Webhook Message Status type is invalid. | |||
77012 | Not Found Agency | Agency information does not exist. | |||
77013 | Non Existing MO Message | Mobile Originated message does not exist. | |||
78001 | 2103 | Unsupport Error | Unsupport Error | ||
78002 | 200 | Calling | Calling | ||
78003 | 201, 486 |
Device No response | No response (Device No response) | ||
78004 | 204 | Device Power Off | Device Power Off. | ||
78005 | 205 | Shaded Area | Shaded Area. | ||
78006 | 206 | Device Message Full | Device Message Full | ||
78007 | 210 | SMS Forward Exceed | SMS call forwarding count exceeded. | ||
78008 | 215 | Invalid Subscriber Name | For non-Korean/English subscribers | ||
78009 | 226 | No CallbackUrl User | Not a CallbackURL user | ||
78010 | 4305 | Invalid Device Error | Invalid Device Error | ||
Retry Manager | 79001 | Retry Count Exceeded | Retry count exceeded. | ||
Querymsgstatus API | 79002 | Concurrent Max Request Exceeded | Concurrent Max Request Exceeded | ||
79003 | RCS ID Mismatched | RCS ID mismatched. | |||
79004 | Invalid Query Request | Invalid Query Request. | |||
79005 | Exceed Query Limit Count | Exceed Query Limit Count. | |||
79006 | Request Query Execution Failure | Request Query Execution Failure. | |||
79007 | Duplicated Query Id | Duplicated Query ID. | |||
79008 | InvaildRequestError | Request to invalid server | |||
79009 | Reserved | Reserved | |||
79010 | Invalid Result Policy | Result message lookup policy is not valid. | |||
79011 | NonExistQueryId | Request ID does not exist error. | |||
MaaP-FE Fail | 79994 | KT MaaP-FE Fail | Failed due to KT carrier failure | ||
79995 | SKT MaaP-FE Fail | Failed due to SKT carrier failure | |||
79996 | LGU MaaP-FE Fail | Failed due to LGU carrier failure | |||
79997 | TimeOut | Transmission failure (expiryoption timeout, etc.) | |||
79998 | Etc TimeOut | Transmission success uncertain (expiryOption TimeOut, etc.) | |||
Unknown | 79999 | 207, 5300 |
Unknown Error | Unknown Error | |
Internal temporary failure code | 77701 | Non Existing Webhook Message | A message does not exist for the forwarded webhook message. | ||
77702 | Invalid Webhook Message | This is an invalid webhook sending message. | |||
77703 | Non Existing Webhook GW Vendor | There is no information on the WebHook Sending Company. | |||
77704 | Invalid Webhook GW Vendor | This is a misconduct of the wrong webhook. | |||
77705 | Webhook CDR Log Writing Failure | Failed to create Webhook message delivery billing history. | |||
77706 | Webhook Msg Log Writing Failure | Failed to write a webook message transfer history information. | |||
77707 | Failure in updating Webhook Message | Failed to change the status of the delivered webhook message. | |||
77708 | Invalid Webhook Request Parameter | Invalid Webhook broker request parameter. | |||
77709 | Webhook Host Connect Error | Sending relay system connection error | |||
77710 | Webhook Host Server Request Failure | Failed to send a webhook. | |||
77711 | Webhook Response Receive Failure | Dispatch Webhook Processing Response Receive An error occurred. | |||
77712 | Invalid Webhook Url | Invalid Webhook URL. | |||
77713 | Expired Webhook Message | This is an expired message. | |||
77714 | Exceed Retry Count to Send Message | Due to exceeding the number of times, the message was failed. | |||
77715 | Failure in Sending Message to MaaP Core FE | Failed to send message to MaaS Core. | |||
77716 | Failure in Linkage to BrandPortal Api Server | Failed to perform brand portal integration. | |||
77717 | Non Allowed Ip | This IP is not allowed to access. | |||
77718 | Corp/agency webhook Receive Failure | Corporate/agency webhook receive error. | |||
77719 | NonExistingResultMsgRcsMapping | Result message RCS mapping not present error. | |||
77720 | NonExistingResultMsg | Result query message non-existence error. | |||
77721 | ResultMsgRegisterFailuer | Results inquiry message registration failure | |||
77800 | Non CDR Target Message | The billing target message does not exist. | |||
77801 | Invalid Notification Param Error | Notification Request Parameter Error. | |||
77802 | Brand Portal Auth Token Error | A Brand Portal Authentication Token error has occurred. | |||
77803 | Brand Portal Host Connection Failure | Brand portal Host connection failure error occurred. | |||
77804 | Brand Portal Auth Token Request Failure | Error requesting Brand Portal authentication token. | |||
77805 | Brand Portal Auth Token Response Failure | Error occurred during the reception of the brand portal certification token response. | |||
77806 | Brand Portal Api Request Format Error | An error occurred in the format of the Brand Portal API integration request. | |||
77807 | Brand Portal UnAuthorized Token Error | Brand portal API linked token error occurred. | |||
77808 | Brand Portal Api Request Error | An error occurred when requesting the Brand Portal API linkage. | |||
77809 | Brand Portal Api Response Error | A brand portal API linkage response error has occurred. | |||
77810 | Brand Portal Api Processing Error | A brand portal API integration execution error occurred. | |||
77811 | Brand Portal Api No Data | Brand Portal API response result value is not found. | |||
77812 | Notification Internal Error | An error occurred while performing an internal notification operation. | |||
77813 | Failure Notification Hist Insert | An error occurred while registering Notification Hist. | |||
77814 | Invalid Notification Method | Invalid Notification Method. | |||
77815 | Invalid Notificiation Type | Invalid Notificiation Type. | |||
71816 | Whloesale Simulater Fail | Whole sale simulator interlocking error. |
Warning
When an error occurs in CMA, error description is transmitted in the form of CMA Hostname+Description.