long sms problem
Added by zahidmahmood over 7 years ago
please check the screen shorts and log file SMS#9 recieve two times but when i check my mobile sent items its show SMS#9 send one time please check i download your latest version of toolkit but still facing same problem
1.bmp (2.25 MB) 1.bmp | |||
2.bmp (2.25 MB) 2.bmp | |||
messagingtoolkit_201005.log (393 KB) messagingtoolkit_201005.log |
Replies (1)
RE: long sms problem - Added by admin over 7 years ago
Hi,
Please see below 2 PDU received. Take note of the SMSC timestamp. They are different.
There could be various reasons for this, either
- your mobile tries to send to SMSC multiple times (1st time the mobile perceives and not successful but is actually received by SMSC). In this case your mobile still should 1 time
- the SMSC sends to the receiving modem/mobile multiple times.
07912903000040F2400C91290360868592000001504201104502A0050003010301A6CDE928074A82DA6172191406C1E56F75794C07D1D1613A485E0E93E7A076793E0F9FCB739059FE6E83C22072981E1687E76550D84D06CDCB6EF21C444797DB2C50D84D6E28D2EE79594E9F83E8E832485E1E97D3F63219D42ECFE7E173790E4ABB4161F79B8E2ECB41F4B0985D7681A8E8B2BC0CBA87E7A0307BFE06CDEB70F85B4E0799DF PDU LENGTH IS 167 BYTES ADDRESS OF DELIVERING SMSC NUMBER IS : +92300000042 TYPE OF NR. : International NPI : ISDN/Telephone (E.164/163) MESSAGE HEADER FLAGS MESSAGE TYPE : SMS DELIVER MSGS WAITING IN SC : YES SEND STATUS REPORT : NO USER DATA HEADER : PRESENT REPLY PATH : NO ORIGINATING ADDRESS NUMBER IS : +923006685829 TYPE OF NR. : International NPI : ISDN/Telephone (E.164/163) PROTOCOL IDENTIFIER (0x00) MESSAGE ENTITIES : SME-to-SME PROTOCOL USED : Implicit / SC-specific DATA CODING SCHEME (0x00) AUTO-DELETION : OFF COMPRESSION : OFF MESSAGE CLASS : NONE ALPHABET USED : 7bit default SMSC TIMESTAMP : 5/24/10 10:01 AM GMT+5.00 USER DATA PART OF SM USER DATA LENGTH : 160 septets UDH LENGTH : 5 octets UDH : 00 03 01 03 01 UDH ELEMENTS : 00 - SM concatenation 8bit ref. 3 (0x03) Bytes Information Element 001 : SM reference number 003 : number of messages 001 : this SM sequence number USER DATA (TEXT) : SMS#9 I made a project that reads messages from a database and sends them, and inserts the received messages in another table. There was also support fo 07912903000040F2440C91290360868592000001504201301002A0050003010301A6CDE928074A82DA6172191406C1E56F75794C07D1D1613A485E0E93E7A076793E0F9FCB739059FE6E83C22072981E1687E76550D84D06CDCB6EF21C444797DB2C50D84D6E28D2EE79594E9F83E8E832485E1E97D3F63219D42ECFE7E173790E4ABB4161F79B8E2ECB41F4B0985D7681A8E8B2BC0CBA87E7A0307BFE06CDEB70F85B4E0799DF PDU LENGTH IS 167 BYTES ADDRESS OF DELIVERING SMSC NUMBER IS : +92300000042 TYPE OF NR. : International NPI : ISDN/Telephone (E.164/163) MESSAGE HEADER FLAGS MESSAGE TYPE : SMS DELIVER MSGS WAITING IN SC : NO SEND STATUS REPORT : NO USER DATA HEADER : PRESENT REPLY PATH : NO ORIGINATING ADDRESS NUMBER IS : +923006685829 TYPE OF NR. : International NPI : ISDN/Telephone (E.164/163) PROTOCOL IDENTIFIER (0x00) MESSAGE ENTITIES : SME-to-SME PROTOCOL USED : Implicit / SC-specific DATA CODING SCHEME (0x00) AUTO-DELETION : OFF COMPRESSION : OFF MESSAGE CLASS : NONE ALPHABET USED : 7bit default SMSC TIMESTAMP : 5/24/10 10:03 AM GMT+5.00 USER DATA PART OF SM USER DATA LENGTH : 160 septets UDH LENGTH : 5 octets UDH : 00 03 01 03 01 UDH ELEMENTS : 00 - SM concatenation 8bit ref. 3 (0x03) Bytes Information Element 001 : SM reference number 003 : number of messages 001 : this SM sequence number USER DATA (TEXT) : SMS#9 I made a project that reads messages from a database and sends them, and inserts the received messages in another table. There was also support fo 3 (0x03) Bytes Information Element 001 : SM reference number 003 : number of messages 001 : this SM sequence number USER DATA (TEXT) : SMS#9 I made a project that reads messages from a database and sends them, and inserts the received messages in another table. There was also support fo