| Problem sendin SMS through SMPP SMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Dinesh Bharathy Arumugam New member Username: Gistdinesh Post Number: 5 Registered: 07-2006 |
Hello Bryce I have configured an SMPP SMSC, for sending & receiving SMS. Though the connection test is successful,I am unable to send SMS. I get the following error in the smppdebug.log. "01:58:45:343 (00000164) 196.10.101.28 --: SMPPSubmitMessage: Got an SMPP response 01:58:45:343 (00000164) 196.10.101.28 <-: 16 byte packet 01:58:45:343 (00000164) 196.10.101.28 <-: 00 00 00 10 80 00 00 04 00 00 00 08 00 00 00 1B 01:58:45:343 (00000164) 196.10.101.28 --: SMPPEnquireLink: Sending enquire_link 01:58:45:671 (00000164) 196.10.101.28 --: SMPPEnquireLink: Response received for enquire_link 01:59:24:265 (00000164) 196.10.101.28 --: SMPPEnquireLink: Sending enquire_link 01:59:24:578 (00000164) 196.10.101.28 --: SMPPEnquireLink: Response received for enquire_link 01:59:26:968 (000001D8) 196.10.101.28 --: SMPPEnquireLink: Sending enquire_link 01:59:27:062 (000001D8) 196.10.101.28 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging 01:59:27:546 (000001D8) 196.10.101.28 --: SMPPEnquireLink: Response received for enquire_link 01:59:45:906 (00000164) 196.10.101.28 ->: 53 byte packet 01:59:45:906 (00000164) 196.10.101.28 ->: 00 00 00 35 00 00 00 04 00 00 00 00 00 00 00 1F 5 01:59:45:906 (00000164) 196.10.101.28 ->: 00 00 00 00 01 01 39 31 39 38 39 34 38 31 39 38 9198948198 01:59:45:906 (00000164) 196.10.101.28 ->: 33 34 00 00 00 00 00 00 00 00 00 00 08 48 65 6C 34 Hel 01:59:45:906 (00000164) 196.10.101.28 ->: 6C 6F 20 68 69 lo hi 01:59:47:921 (00000164) 196.10.101.28 --: SMPPSubmitMessage: Got an SMPP response 01:59:47:921 (00000164) 196.10.101.28 <-: 16 byte packet 01:59:47:921 (00000164) 196.10.101.28 <-: 00 00 00 10 80 00 00 04 00 00 00 08 00 00 00 1F 01:59:47:921 (00000164) 196.10.101.28 --: SMPPEnquireLink: Sending enquire_link 01:59:48:265 (00000164) 196.10.101.28 --: SMPPEnquireLink: Response received for " also the following in the SMSDEbug.log " 01:58:12:203 [8] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=%2B919894819834&Text=Hello+hi&InfoCharCou nter=&PID=&DCS=&Submit=Submit 01:58:12:203 [8] Debug: 1 recipient entries 01:58:12:218 [8] Debug: +919894819834 01:58:12:234 [8] ThreadProcessConnection: Request processing complete 01:58:12:406 [6] ThreadProcessModem: Processing 44D1BAA4.req... 01:58:13:812 [6] ThreadProcessModem: Error: ERROR: System Error 01:58:15:140 [6] ThreadProcessModem: Processing 44D1BAA4.req... 01:58:15:453 [6] ThreadProcessModem: Error: ERROR: System Error 01:58:45:015 [6] ThreadProcessModem: Processing 44D1BAA4.req... 01:58:45:343 [6] ThreadProcessModem: Error: ERROR: System Error 01:59:45:906 [6] ThreadProcessModem: Processing 44D1BAA4.req... 01:59:47:921 [6] ThreadProcessModem: Error: ERROR: System Error 02:00:00:031 [0] main: 26 Days remaining in trial version 02:01:17:953 [6] ThreadProcessModem: Processing 44D1BAA4.req... 02:01:18:265 [6] ThreadProcessModem: Error: ERROR: System Error 02:03:18:062 [6] ThreadProcess}Modem: Processing 44D1BAA4.req... 02:03:18:375 [6] ThreadProcessModem: Error: ERROR: System Error" Please Help me out. Thank you. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6307 Registered: 10-2002 |
Hi, Unfortunately I think you will have to ask your SMS service provider. When we submit the message, your service provider is returning an error code that is defined in the SMPP spec simply as 'System Error'. So your provider should be able to provide some insight as to why. They might require certain parameters to be set. But looking at your log, I do have one idea. Edit the properties for the SMPP connection, and set a sender address...your provider might not like the blank sender address. Tney might have other restrictions on what values are valid for the sender address. -bn | |||
| Dinesh Bharathy Arumugam New member Username: Gistdinesh Post Number: 6 Registered: 07-2006 |
Thank You very much. I am working out with my SMS Provider. Let me get back to you, once I get hold of the problem. Thanks Again | |||
| Dinesh Bharathy Arumugam New member Username: Gistdinesh Post Number: 7 Registered: 07-2006 |
Hello Bryce You were right about certain parameters to be set. Now, the gateway is sending the SMS(as I see from the SMSOut.log). But the SMS is not received on the phone. I wasn't able to find a tab that says "Registered Delivery:" - That is used to track, if the message was delivered or not. Please let me know, if we have an equivalent tab in NowSMSgateway. Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6350 Registered: 10-2002 |
It depends on how you are interfacing with NowSMS. If you would like a delivery receipt, include the HTTP parameter "&ReceiptRequested=Yes" when submitting messages to NowSMS. It is also possible to default to this parameter for all messages submitted to NowSMS via HTTP by editing SMSGW.INI, and setting ReceiptRequested=Yes under the [SMSGW] header. In SMPP environments, the delivery receipt that comes back usually starts with "id:", so if you want to process these via HTTP, you would configure a 2-way command with a command prefix of "id:*". When a receipt is routed via a 2-way command, there is an additional @@ variable supported: @@RECEIPTMESSAGEID@@ contains the NowSMS message id for which this is a receipt. When you submit a message to NowSMS via HTTP, the HTTP response from NowSMS will include "MessageID=xxxxxxxx" ... and this "xxxxxxx" is what should come back in the @@RECEIPTMESSAGEID@@ variable if delivery receipts are properly implemented by your SMS service provider. If you're not using HTTP to talk to NowSMS ... but are using SMPP ... then what I've said doesn't apply, and NowSMS just uses standard SMPP formats for routing receipts back to the appropriate submitting client. -bn | |||
