Equipment Protocol Error
Contents |
Inbound SMS API Inbound SMS SMPP Inbound SMS HTTP Number Lookup API Number Lookup using
Sm Delivery Failure Equipment Protocol Error
ENUM Number Lookup using HTTP Voice API Outbound Voice Inbound Voice equipment protocol error gsm USSD API USSD Flash via SMPP or HTTP SMS/USSD Fusion via SMPP or HTTP USSD Menus equipment protocol error map via SMPP or HTTP Error Specification Overview SMPP connection error codes Messages states Status reports error codes 1. Overview This specification covers error codes related to
Gsm Map Error Codes
the SMPP/HTTP communication. There are two different types of errors: (A) Errors generated on the SMPP/HTTP connection between customer and CLX Networks’ SMPP/HTTP server and (B) Errors received in the status reports (Delivery reports, DELIVER_SM). 2. SMPP connection error codes All errors on the SMPP connection received in SUBMIT_SM_RESP are described in
Smsc Error Code List
the SMPP Protocol Specification v3.4 Issue 1.2 chapter 5.1.3 command_status. 3. Messages states A message will always be in one of the following states: Message state Value Description ENROUTE 1 Message is in the process of being sent to the destination Delivered 2 Message has been delivered to destination EXPIRED 3 Message validity period has expired DELETED 4 Message has been deleted UNDELIVERABLE 5 Message is undeliverable UNKNOWN 7 Message is in invalid state The states are described in the SMPP Protocol Specification v3.4 Issue 1.2 chapter 5.2.28 message_state. The message state value is also attached in a SMPP Optional Parameter “message_state” value 0x0427 described in the SMPP Protocol Specification v3.4 Issue 1.2 chapter 5.3.2.35. 4. Status reports error codes The error codes are provided in status reports according to the SMPP Protocol Specification v3.4 Issue 1.2 Appendix B. The following are the error codes CLX Networks will be sending: Error Error Class Description Comment Treate
- SMSC V5 - Error … – Carrier https://www.clxnetworks.com/api-docs/documentation/outbound-sms-api/error-specification/ checked SMSC V5 logs on their network - identified Error 62 - equipment protocol error and blamed the handset. Carrier checked SMSC V5 logs http://comphelp.org/guide/smsc-equipment-protocol-error/ on their network - identified Error 62 - equipment protocol error and blamed the handset. Issue 36212 - android - SMSC V5 - Error … – Carrier checked SMSC V5 logs on their network - identified Error 62 - equipment protocol error and blamed the handset. Bookmark the permalink. Post navigation ← Ras Error 633 Sonicwall Ramsey Regression Specification Error Test For Omitted Variables → Search Striker WordPress Theme Powered By WordPress
36212: SMSC V5 - Error 62 equipment protocol error 1 person starred this issue and may be notified of changes. Back to list https://code.google.com/p/android/issues/detail?id=36212 Status: Obsolete Owner: ---- Closed: Dec 2014 Type-Defect Priority-Medium ReportedBy-User Sign in to add a comment Reported by stephen....@gmail.com, Aug 9, 2012 Intermittent issue with SMS not being received. DEVICE - Out of the box unlocked new Motorola XT910 updated to ICS 4.04 OTA from Motorola - this is stock international release (not Carrier branded) Issue also occurred on stock international equipment protocol release 2.3.6 before OTA upgrade + patch ISSUE - For some reason phone does not receive messages. I only become aware of this when a contact phones me to say "hey did you get my message - why didn't you respond" etc. Check the SMS app and nothing received. Power the device off and then power on and after a period of time equipment protocol error messages start being received again. Most recent example - no message received from midday Wednesday until late Thursday night. Actions taken - Isolation test performed at carriers retail store - however this really proved nothing as the issue is intermittent. Involved putting my SIM in another phone and sending and receiving messages. Carrier checked SMSC V5 logs on their network - identified Error 62 - equipment protocol error and blamed the handset. Suggested that I could try SIM replacement Micro SIM replaced - issue appeared to be fixed. Checked with carrier and not errors reporting in their logs since the changes of SIM. Issue happening again. worked for about 1.5 weeks until this Wednesday when it started again. Checked again with carrier - SMS logs again showing Error 62 equipment protocol error. Unable to reliably receive SMS which impacts ability to respond in a timely manner to autogenerated system support messages. This should just work without manual intervention to cold boot the phone. If you happen to have a development environment, please also run "adb bugreport" and archive the output as it could help diagnose the pro