ESME_RX_P_APPN in SMPP

What is ESME_RX_P_APPN?

ESME_RX_P_APPN (Error Code: 0x00000065) is an SMPP error indicating that the application encountered a processing error while handling a received PDU.

Possible Causes

  • The SMSC encountered an internal error while processing a received request.
  • The PDU format is invalid or contains unexpected data.
  • There is a misconfiguration or bug in the SMSC application handling the request.
  • The SMSC could not process the message due to resource constraints.

When Does It Happen?

This error occurs when the SMSC receives a request from the ESME but fails to process it due to an internal application issue.

Example SMPP PDU Transaction

Request PDU (submit_sm) Sent by ESME

0000003F (Length)
00000004 (Command ID for submit_sm)
00000000 (Command Status)
00000001 (Sequence Number)
00 (Service Type)
01 (Source Address TON - International)
01 (Source Address NPI - ISDN)
31323334 00 (Source Address: "1234")
01 (Destination Address TON - International)
01 (Destination Address NPI - ISDN)
39383736 00 (Destination Address: "9876")
00 (ESM Class)
00 (Protocol ID)
00 (Priority Flag)
00000000 (Schedule Delivery Time - Not Set)
00000000 (Validity Period - Not Set)
00 (Replace If Present Flag)
00 (Sm Default Msg ID)
0005 (Message Length)
48656C6C 6F (Message: "Hello")

Response PDU (submit_sm_resp) with ESME_RX_P_APPN

00000010 (Length)
80000004 (Command ID for submit_sm_resp)
00000065 (Command Status - ESME_RX_P_APPN)
00000001 (Sequence Number)

Issue: The SMSC encountered an application processing error while handling the submit_sm request.

How to Solve It?

  • Check SMSC logs for detailed error messages related to processing failures.
  • Ensure the request PDU is correctly formatted and adheres to SMPP specifications.
  • Verify that the SMSC is not experiencing high load or resource constraints.
  • Restart the SMSC application if persistent processing failures occur.
  • Contact the SMSC provider for further investigation if the issue persists.

Analyzing logs and debugging the SMSC's internal processing logic can help identify the root cause of this error.

More information