SMSDEBUG.LOG format | Search |
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through June 02, 2011 ⬆ |
◄ ► |
Author | Message | |||
Jorge Arévalo New member Username: Jorgearevalo Post Number: 1 Registered: 12-2009 |
Hello, How should I interpret the output messages that appear in SMSDEBUG.LOG? For example, if I send a dummy message ("a" letter) to a mobile phone number (using "Normal" message type and Class 1), in the SMSDEBUG.LOG file I get: 18:05:30:197 [6] ThreadProcessModem: OUT: AT+CMGS=13 18:05:30:290 [6] ThreadProcessModem: IN: > 18:05:30:290 [6] ThreadProcessModem: OUT: 000107098156917197F900110161 What does this last hex string mean? I'm trying to interpret it following this pattern: http://www.dreamfabric.com/sms/, but it doesn't match... Many thanks in advance! | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1536 Registered: 08-2008 |
Hi Jorge, The SMSDEBUG.LOG exists primarily to help us troubleshoot problems, so we don't have any documentation on it's format. In this case you are seeing the AT commands sent to the modem using ETSI GSM 07.05 format. (www.etsi.org ) -- Des | |||
Jorge Arévalo New member Username: Jorgearevalo Post Number: 2 Registered: 12-2009 |
Ok, I've downloaded this standard: Digital cellular telecommunications system (Phase 2+); Use of Data Terminal Equipment - Data Circuit terminating; Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) (GSM 07.05 version 7.0.1 Release 1998) I supose is the right one... ¡Many thanks! | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1539 Registered: 08-2008 |
Yes. You will also want 03.40 which defines the PDU format. And I believe it is 03.38 that defines the text encoding format. (Follow the references from 07.05.) -- Des |