| Technical Issues with Patches |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 21, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| sam New member Username: Samdsouza Post Number: 11 Registered: 08-2006 |
Hi Have noticed the following problems with the patches: 1. After installing patch2007.zip the User Account Statistics in the Web Admin doesnt display the User usage stats. The User usage stats are correctly displayed on NowSMS but not on the Web Admin. 2. Patches Released after 2006-09-18 have a bug with the Delivery Reports. Delivery Reports for binary content dont get routed to the user accounts. They do come in to the SMS-IN folder. Whereas Delivery Reports for plain text sms content works properly. 3. Account Balance validation doesnt work. If the client is sending via the web interface and his balance goes zero while sending or while he is connected then NowSMS doesnt stop the send. It shows negative balance in the user stats and the sms get processed even though the balance is negative. The admin interface shows "Current credits = 4294962861" and the main usage stats of the user shows the negative balance. This behavious is noticed while sending through the web interface. Sam | ||||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 144 Registered: 12-2006 |
Hi Sam, 1. We are aware of this problem, and it has been fixed. 2. We could use some more information regarding this issue. What is the type of external SMSC connection? We probably need a debug log in order to understand the issue. I just tried a quick test here, and didn't have a problem with delivery receipts getting routed back to the user account for either a text or binary message when routing externally via either SMPP or a GSM modem ... so there must be some other factor that I am issing. 3. I have seen where the web interface will display a very large number instead of a negative number if the account balance is negative. However, in my tests, this is only a cosmetic issue, as the user account can still not submit messages. And I have not seen any way to make the credit balance go negative other than entering negative numbers in the "credits to add" field. If you are aware of other means, then please advise. I suppose we could add some safety by preventing account balances from going below 0. But I am curious about any scenario through which a user with a negative account balance is allowed to submit messages. -- Malcolm Now Wireless Support | ||||
| sam New member Username: Samdsouza Post Number: 12 Registered: 08-2006 |
Hi Malcom Thanks for the reply. Following Responces 1. The Web Admin User usage stats issue is resolved. 2. Patches Released after 2006-09-18 have a bug with the Delivery Reports. Delivery Reports for binary content dont get routed to the user accounts. They do come in to the SMS-IN folder. Whereas Delivery Reports for plain text sms content works properly. I can confirm this doesnt work while sending binary like Ringtone. It works for text as well as unicode messaegs. When a binary like ringtone is sent..the delivery report comes in to the SMSIN folder but doesnt get routed to LocalUser in the SMSOUT file. For text as well as unicode messaegs the delivery report is logged getting routed to the LocalUser. I get the following content in the sms in Text,iHi1SFøΣ4pDI¥ìH9uDi£$èøΔdXYΓGLÅΔ ¿@ΘWNX6ih£!ΠøÑ2:¿Ö£#ùLΣ1hHΘ¥èY7nJ£!ΠøÑ2:¿Ö£#ùLΣ1hHΘ¥dÆ :ahi!TòS¤V¤_$RLÆ9:¿¡£¥èU2xhi1P@A £+èDf £$Ω$$@ ¡ΦæuΞ,123456 I have noticed a different nowsms message ID comming in. Previoulsy it used to be "454ACD54.req" and now its "00000005.req". Is this becuase of the change in message ID form AlphaNumeric to Numeric only? Patches Released before 2006-09-18 worked fine with the delivery reports for Ringtones. 3. Account Balance validation doesnt work. If the client is sending via the web interface and his balance goes zero while sending or while he is connected then NowSMS doesnt stop the send. It shows negative balance in the user stats and the sms get processed even though the balance is negative. The admin interface shows "Current credits = 4294962861" and the main usage stats of the user shows the negative balance. This behavious is noticed while sending through the web interface. I can confirm this is still an issue. I creted a useraccount. Put in 500 credits. I logged in to the web interface and submitted 1000 messages in a single session. all the 1000 messages got accepted and went to the Q folder. After that i clicked on the send text message link and it showed the Current credits = 4294962861. At this point of time when i again tried submitting messaegs it gave me the balance not available error. But when sending those 1000 sms it didnt give me an error after 500 sms credits were used and it actually accepted all the 1000 messaegs. Thanks Sam} | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6899 Registered: 10-2002 |
Hi Sam, I'm going to respond to the issues out of order, as #3 is the one that I am most concerned with. We've tried a variety of different versions of NowSMS, but we don't see this. We see the web interface reporting a very large number for the current credit balance (instead of a negative number), but we only see this occur if credits were subtracted from the account manually. As a test, I created a user account, and gave it 500 credits. I then went into "Send Text Message" and selected a distribution list with several thousand entries in it. NowSMS returned an error indicating that the credit limit was exceeded, and did not send any messages. (The account still had 500 credits, because no credits were deducted.) I'd like to know how to recreate this, because you must be doing something different. But in the meantime, we did make adjustments to the latest patch so that the credit balance could never "go negative". I expect that would resolve some problems you are having. The download is the same as before http://www.nowsms.com/download/patch2007.zip. But it still would not resolve a problem where a user has 500 credits, but is allowed to submit 1000 messages. Can you step me through the process to recreate this? You must be doing something different that I am not thinking of trying. 2. I don't see this behaviour. I've tried sending some ring tones with receipt requested, and there is nothing different about them. I think we need to see an SMSDEBUG.LOG in order to understand. (If you do not want to post it here, e-mail it to nowsms@now.co.uk with "Attention: Bryce" in the subject line. Include a reference to remind me why I asked to see the log file.) Regarding the change from "454ACD54.req" to "00000005.req", that is a somewhat temporary change. The 2007.01.30 version included a change to message id tracking. In some situations, this would cause the message id's to start at "00000001.req" after the first time this new version is started. (The 2007.01.31 version changed things so that it does not start at "00000001".) It is still an alphanumeric value. -bn | ||||
| sam New member Username: Samdsouza Post Number: 13 Registered: 08-2006 |
Hi Bryce Thanks for your reply. Following points: 3. "but we only see this occur if credits were subtracted from the account manually." I can confirm that I didnt substract the credits from the user account. The account went negative while submtting. I dont recollect doing anything special while getting that scenario. Tried submtting the messages couple of times using the web interface and it accepted and showed a negative balance. 2. The Delivery Reports for Ringtone are getting stuck in the smsin folder and they are not getting routed to the local user. The message ID after intalling the latest patch is still numeric. The message ID assinged for the outgoing sms is 0000001B while the incomming message id is 0000001C. Is this due to mismatch in the message ID? Following smsdebug log: 12:29:44:890 [0] main: Now SMS/MMS Gateway v2007.01.31 Web server started on port number 8800 12:29:46:890 [0] main: 24 Days remaining in trial version 12:29:46:890 [4] ThreadProcessModem: SDKLINK - VirtualSMSC 12:29:46:890 [5] ThreadProcessModem: SMPP - XX.XX.XX.XX:5003 12:29:46:890 [4] SenderAddressOverride: Yes 12:29:53:656 [9] ThreadSmppSubmitAsyncHelper: Start Thread 12:30:14:281 [10] ThreadProcessConnection: Processing connection from 67.15.56.13... 12:30:14:296 [10] ThreadProcessConnection: Processing request /?user=test&password=test&PhoneNumber=639207424555&&UDH=06050415811581&Data=6806 050415810000024A3A754D85A985B984814D85A985B98404006718A2F03303483303483302E83483 302E82F03303483303483302E83483302E82B02F03282F03282F02A83282F02A42F03303503282F0 2E43503503242F02A43483302E03483503242F02A40000&DCS=F5&Binary=1&Sender=123456 12:30:14:296 [10] Debug: 1 recipient entries 12:30:14:296 [10] ThreadProcessConnection: Before message loop 12:30:14:328 [10] ThreadProcessConnection: Before message loop 12:30:14:328 [10] ThreadProcessConnection: Begin message loop 12:30:14:343 [10] ThreadProcessConnection: End message loop 12:30:14:437 [10] ThreadProcessConnection: Request processing complete 12:30:14:703 [5] ThreadProcessModem: Processing 0000001B.req... 12:30:14:703 [5] SMPPSubmitAsyncQ: Depth 1 12:30:15:328 [9] CheckSmppSubmitAsyncQ: 0000001B 12:30:15:328 [9] SMPPSubmitAsyncQ: Depth 0 12:30:21:250 [5] SMPPReceiveMessageCallback: inbound message: sender=639207424555, recip=123456, pid=0, dcs=0, msgFlags=4, udh=, msg=iHi1cF Σ9¿dÇΓìH9uDi£$èøΔdXYΓGLÅΔ ¿@ΘWNX6ih£!ΠøÑ2:¿Ö£#ùLΞ1dD_¥èY7nJ£!ΠøÑ2:¿Ö£#ùLΞ1dD_¥dÆ:a hi!TòS¤V¤_$RLÆ9:¿¡£¥èU2xhi1P@A £+èDf £$Ω$$@ ¡ΦæuΞ 12:30:21:906 [7] ThreadProcessInboundSMS: Processing 0000001C.in... 3. Have noticed one more issue in the patches. It creates 2 folders for a same user in the Q folder when there are errors. "test" and "test###1". This I didnt notice previously. Regards Sam | ||||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 163 Registered: 12-2006 |
Sam, We're probably going to need to see an smppdebug.log (email it to nowsms@now.co.uk with "Attention: Malcolm" in the subject line, or post it here), because we need to see the raw submission and the raw receipt data that comes back. The multiple q folders is normal. It is a performance aid when submitting to more than 10000 recipients. -Malcolm | ||||
| sam New member Username: Samdsouza Post Number: 14 Registered: 08-2006 |
Hi Does the multiple Q folder come in even while sending to incorrect mobile numbers? I got the 2 folders when i was testing the web interface Following SMPP Debug logs: 15:03:24:031 (00000164) XX.XX.XX.XX --: SMPPBind: Got an SMPP response 15:03:24:031 (00000164) XX.XX.XX.XX <-: 21 byte packet 15:03:24:031 (00000164) XX.XX.XX.XX <-: 00 00 00 15 80 00 00 09 00 00 00 00 00 00 00 01 15:03:24:031 (00000164) XX.XX.XX.XX <-: 73 6D 73 6A 00 test 15:03:24:031 (00000164) XX.XX.XX.XX ->: 165 byte packet 15:03:24:031 (00000164) XX.XX.XX.XX ->: 00 00 00 A5 00 00 00 04 00 00 00 00 00 00 00 02 15:03:24:031 (00000164) XX.XX.XX.XX ->: 00 00 01 31 32 33 34 35 36 37 34 00 00 01 39 31 12345674 63 15:03:24:031 (00000164) XX.XX.XX.XX ->: 39 38 32 30 38 38 34 30 36 34 00 40 00 03 00 00 9207424555 @ 15:03:24:031 (00000164) XX.XX.XX.XX ->: 01 00 F5 00 70 06 05 04 15 81 15 81 68 06 05 04 p h 15:03:24:031 (00000164) XX.XX.XX.XX ->: 15 81 00 00 02 4A 3A 75 4D 85 A9 85 B9 84 81 4D J:uM M 15:03:24:031 (00000164) XX.XX.XX.XX ->: 85 A9 85 B9 84 04 00 67 18 A2 F0 33 03 48 33 03 g 3 H3 15:03:24:031 (00000164) XX.XX.XX.XX ->: 48 33 02 E8 34 83 30 2E 82 F0 33 03 48 33 03 48 H3 4 0. 3 H3 H 15:03:24:031 (00000164) XX.XX.XX.XX ->: 33 02 E8 34 83 30 2E 82 B0 2F 03 28 2F 03 28 2F 3 4 0. / (/ (/ 15:03:24:031 (00000164) XX.XX.XX.XX ->: 02 A8 32 82 F0 2A 42 F0 33 03 50 32 82 F0 2E 43 2 *B 3 P2 .C 15:03:24:031 (00000164) XX.XX.XX.XX ->: 50 35 03 24 2F 02 A4 34 83 30 2E 03 48 35 03 24 P5 $/ 4 0. H5 $ 15:03:24:031 (00000164) XX.XX.XX.XX ->: 2F 02 A4 00 00 / 15:03:24:718 CheckSmppSubmitAsyncQ: Mark submit as complete 15:03:24:718 CheckSmppSubmitAsyncQ: 45CC3FDF 15:03:24:718 (00000164) XX.XX.XX.XX --: WaitForResponseSMPP: SMPP Debug: received submit or data response 15:03:24:718 (00000164) XX.XX.XX.XX <-: 25 byte packet 15:03:24:718 (00000164) XX.XX.XX.XX <-: 00 00 00 19 80 00 00 04 00 00 00 00 00 00 00 02 15:03:24:718 (00000164) XX.XX.XX.XX <-: 32 30 42 35 31 33 32 44 00 20B5132D 15:03:31:500 (00000164) XX.XX.XX.XX --: WaitForResponseSMPP: SMPP Debug: received a deliver message 15:03:31:500 (00000164) XX.XX.XX.XX <-: 174 byte packet 15:03:31:500 (00000164) XX.XX.XX.XX <-: 00 00 00 AE 00 00 00 05 00 00 00 00 00 00 00 01 15:03:31:500 (00000164) XX.XX.XX.XX <-: 00 00 01 39 31 39 38 32 30 38 38 34 30 36 34 00 639207424555 15:03:31:500 (00000164) XX.XX.XX.XX <-: 00 01 31 32 33 34 35 36 37 34 00 04 00 00 00 00 12345674 15:03:31:500 (00000164) XX.XX.XX.XX <-: 00 00 00 00 79 69 64 3A 35 34 38 37 33 37 38 33 yid:54873783 15:03:31:500 (00000164) XX.XX.XX.XX <-: 37 20 73 75 62 3A 20 20 30 20 64 6C 76 72 64 3A 7 sub: 0 dlvrd: 15:03:31:500 (00000164) XX.XX.XX.XX <-: 20 20 30 20 73 75 62 6D 69 74 20 64 61 74 65 3A 0 submit date: 15:03:31:500 (00000164) XX.XX.XX.XX <-: 30 37 30 32 30 39 31 34 34 35 20 64 6F 6E 65 20 0702091445 done 15:03:31:500 (00000164) XX.XX.XX.XX <-: 64 61 74 65 3A 30 37 30 32 30 39 31 34 34 35 20 date:0702091445 15:03:31:500 (00000164) XX.XX.XX.XX <-: 73 74 61 74 3A 44 45 4C 49 56 52 44 20 65 72 72 stat:DELIVRD err 15:03:31:500 (00000164) XX.XX.XX.XX <-: 3A 30 30 30 20 54 65 78 74 3A 06 05 04 15 81 15 :000 Text: 15:03:31:500 (00000164) XX.XX.XX.XX <-: 81 68 06 05 04 15 81 00 00 02 4A 3A 75 4D h J:uM 15:03:31:500 (00000164) XX.XX.XX.XX ->: 17 byte packet 15:03:31:500 (00000164) XX.XX.XX.XX ->: 00 00 00 11 80 00 00 05 00 00 00 00 00 00 00 01 15:03:31:500 (00000164) XX.XX.XX.XX ->: 00 Regards Sam | ||||
| sam New member Username: Samdsouza Post Number: 15 Registered: 08-2006 |
Hi Plz find the smppdebug log attatched also. Thanks Sam
| ||||
| sam New member Username: Samdsouza Post Number: 18 Registered: 08-2006 |
Hi Bryce/Malcom Were you able to check this Delivery Report issue. Regards Sam | ||||
| sam New member Username: Samdsouza Post Number: 19 Registered: 08-2006 |
Hi Bryce/Malcom The issue with the Delivery Report for Binary still remains. My trial version of nowsms on my pc has got expired now but the following details might help in resolving the issue: Patches after 2006.09.18 For Ringtone/Logo or any binary message..the report which shows in the SMS in Folder comes as: Text,iHi1cfLΞ7dPASùH9uDi£$èøΔdXYΓGLÅΔ ¿@ΘWNX6ih£!ΠøÑ2:¿Ö£3ùøÆ1fD!¥èY7nJ£!ΠøÑ2:¿Ö£3ùøÆ1fD!¥dÆ :ahi!TòS¤V¤_$RLÆ9:¿¡£¥èU2xhi1P@A £+èDf £$Ω$$@ ¡ΦæuΞ,1234567 The above doesnt get routed to user account...nor does it show in the SMS out log as getting routed to local user. For patch 2006.09.18 For Ringtone/Logo or any binary message..the report which shows in the SMS in Folder comes as: Text,id:45F13597 sub: 0 dlvrd: 0 submit date:0703081309 done date:0703081309 stat:DELIVRD err:000 Text:ùéèΩΩhùéèΩ@@$J:uM,123456,SMSCReceiptMsgId=45F13597 The above gets routed to user account...and it does show in the SMS out log as getting routed to local user. Regards Sam | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6964 Registered: 10-2002 |
Hi Sam, Whatever is going on is definitely specific to your provider, as I can't recreate any such problem. It would be interesting to see an SMSDEBUG.LOG and SMPPDEBUG.LOG that covered the same period. But as I take a fresh look at it, I think I see what is going on. When your provider generates its return receipt, it is putting the user data header (UDH) from the original message into the text of the SMS. In particular, part of the UDH that is included in the text contains the character "81". This character is not valid in the GSM character set. Because some SMSCs actually send text that is 7-bit packed, this causes NowSMS to see this character as a trigger to try to unpack the text ... resulting in a garbled mess. While the UDH should not be included in the message in this way, NowSMS is definitely wrong to be scrambling the message. We're going to undo this auto-detection, and if someone is working with an SMSC that delivers SMS messages in 7-bit format (there are only a few of them), they will have to add a configuration parameter. I should be able to post an update in the next day or two. Meanwhile, to get your trial extended, please send an e-mail message to "nowsms@now.co.uk". Put "Attention: Bryce" on the subject line. In the text, please remind me of this instance, and include the "installation reference code" reported by the "Serial #" page of the NowSMS configuration. -bn | ||||
| sam New member Username: Samdsouza Post Number: 20 Registered: 08-2006 |
Hi Bryce Thanks for your reply. Following logs SMPPDEBUG.LOG (In this log the Delivery Report comes in properly) 17:25:05:125 (00000174) XX.XX.XX.XX <-: 32 37 45 32 44 32 39 33 00 27E2D293 17:25:11:796 (00000174) XX.XX.XX.XX --: WaitForResponseSMPP: SMPP Debug: received a deliver message 17:25:11:796 (00000174) XX.XX.XX.XX <-: 173 byte packet 17:25:11:796 (00000174) XX.XX.XX.XX <-: 00 00 00 AD 00 00 00 05 00 00 00 00 00 00 00 01 17:25:11:796 (00000174) XX.XX.XX.XX <-: 00 00 01 39 31 39 38 36 37 31 37 32 37 31 38 00 639207424555 17:25:11:796 (00000174) XX.XX.XX.XX <-: 00 01 31 32 33 34 35 36 37 00 04 00 00 00 00 00 1234567 17:25:11:796 (00000174) XX.XX.XX.XX <-: 00 00 00 79 69 64 3A 36 36 39 31 37 36 34 36 37 yid:669176467 17:25:11:796 (00000174) XX.XX.XX.XX <-: 20 73 75 62 3A 20 20 30 20 64 6C 76 72 64 3A 20 sub: 0 dlvrd: 17:25:11:796 (00000174) XX.XX.XX.XX <-: 20 30 20 73 75 62 6D 69 74 20 64 61 74 65 3A 30 0 submit date:0 17:25:11:796 (00000174) XX.XX.XX.XX <-: 37 30 33 30 39 31 37 30 37 20 64 6F 6E 65 20 64 703091707 done d 17:25:11:796 (00000174) XX.XX.XX.XX <-: 61 74 65 3A 30 37 30 33 30 39 31 37 30 37 20 73 ate:0703091707 s 17:25:11:796 (00000174) XX.XX.XX.XX <-: 74 61 74 3A 44 45 4C 49 56 52 44 20 65 72 72 3A tat:DELIVRD err: 17:25:11:796 (00000174) XX.XX.XX.XX <-: 30 30 30 20 54 65 78 74 3A 06 05 04 15 81 15 81 000 Text: 17:25:11:796 (00000174) XX.XX.XX.XX <-: 68 06 05 04 15 81 00 00 02 4A 3A 75 4D h J:uM 17:25:11:796 (00000174) XX.XX.XX.XX ->: 17 byte packet 17:25:11:796 (00000174) XX.XX.XX.XX ->: 00 00 00 11 80 00 00 05 00 00 00 00 00 00 00 01 17:25:11:796 (00000174) XX.XX.XX.XX ->: 00 SMSDEBUG.LOG (In this log the Delivery Report gets scrambled) 17:25:04:546 [5] ThreadProcessModem: Processing 0000006F.req... 17:25:04:546 [5] SMPPSubmitAsyncQ: Depth 1 17:25:05:140 [12] CheckSmppSubmitAsyncQ: 0000006F 17:25:05:140 [12] SMPPSubmitAsyncQ: Depth 0 17:25:11:796 [5] SMPPReceiveMessageCallback: inbound message: sender=639207424555, recip=1234567, pid=0, dcs=0, msgFlags=4, udh=, msg=iHi1c&NΣ7lP1sùH9uDi£$èøΔdXYΓGLÅΔ ¿@ΘWNX6ih£!ΠøÑ2:¿Ö£3ùLÆ1n¡9¥èY7nJ£!ΠøÑ2:¿Ö£3ùLÆ1n¡9¥dÆ :ahi!TòS¤V¤_$RLÆ9:¿¡£¥èU2xhi1P@A £+èDf £$Ω$$@ ¡ΦæuΞ Regarding my trial version getting expired I have installed nowsms on a different pc and tested it today. It would help if you have some kind of developer license for nowsms where you can provide the least possible speed per sms configuration for an extended duration. Also I installed the 20070306 and tried * SMS Gateway: See http://support.nowsms.com/discus/messages/1/20068.html (fix relating to user account specific HTML templates). I found that it was the same as before only. Can you let me know what excatly was fixed on the user account html templates? I mean after the fix how does it work? Thanks a lot Sam | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6977 Registered: 10-2002 |
Hi Sam, Send an e-mail to "nowsms@now.co.uk" with "Attention: Bryce" on the subject line ... and include the "installation reference code" reported by NowSMS in the "Serial #" tab. I will then send you an extended duration trial license. There is an update posted to http://www.nowsms.com/download/20070309.zip which fixes the problem that I described above. Regarding the user-specific HTML templates, I'll go over to that thread and post the info there. -bn | ||||
| sam New member Username: Samdsouza Post Number: 23 Registered: 08-2006 |
Hi Bryce Tested 20070309.zip update but the same results. The delivery report is still not in the proper format. Regards Sam | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6983 Registered: 10-2002 |
Hi Sam, My fault. I generated the install without all of the updated DLLs. The URL above has been updated with a fresh copy. The installer will identify as 2007.03.13. -bn | ||||
| sam New member Username: Samdsouza Post Number: 24 Registered: 08-2006 |
Hi Bryce Yes. This works now for the delivery reports. But I was testing sending 500 messages at a time via the web interface and i found that the processing was very slow as compared to previous patches. Has something else also changed? Regards Sam | ||||
| sam New member Username: Samdsouza Post Number: 25 Registered: 08-2006 |
Hi Bryce Regarding slow processing of sms messages it was my mistake. I was submitting an incorrect message paramter and the providers smpp connection was rejecting the messages. Regards Sam | ||||
| sam New member Username: Samdsouza Post Number: 26 Registered: 08-2006 |
Hi Bryce, I was testing ringtones for specific handsets and specific Operators but am getting majorly reject errors form the providers smpp connection. Can you suggest some site where i can find details regarding how to push binarys like ringtones specifically. Example How do I push ringtones for specific handsets and for specific Operators (MCC code usage) Also regarding the delivery reports..Should i set DefaultDelReceipt=Yes or DeliveryReceiptFlag=1 for requesting the delivery report back? Or ReceiptRequested=Yes is enough to set the dr flag=1 Regards Sam | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6996 Registered: 10-2002 |
Hi Sam, Ringtone formats are more an issue of being phone specific, rather than operator specific. The only time that MCC and MNC codes come into play are with the old style Nokia operator logo. (Nokia also has a new operator logo format, but this one just lets you configure a graphic for a small bar on the display, while the old fomat let you set a background for the phone's "idle" screen.) If the operator SMPP connection is rejecting the message, then this suggests that there is a problem with the basic message format. Usually this would be a UDH formatting error ... such as the length field not being set properly, or the length parameter for an individual element in the UDH not being set properly. (NowSMS should probably validate any UDH when accepting messages to help ... well, at least that would be a nice extra feature ... but it doesn't do that.) It is also possible that your operator/provider may have rules that do not allow certain formats. I can't say that I've seen too much of this, but I do remember once encountering a provider that would not accept WAP push messages. -bn | ||||
| sam New member Username: Samdsouza Post Number: 28 Registered: 08-2006 |
Hi Bryce Thanks for your inputs. Appreciate it. The validation of UDH would really help but that would be bit too much to ask for. Would like to make few suggestions on the web interface. It would be great to have a link on the web interface where useraccount can check the sms they have sent and the respective delivery reports. Or maybe some kind of HTTP call back where the user can input the message ID assinged and check the delivery report. Currently nowsms stores day wise text files of the sms sent and the delivery reports in the same file. It would be great if they can be displayed in the web interface. Regards Sam | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7007 Registered: 10-2002 |
Hi Sam, For the next major release, we are concentrating on improving some of the administrative/statistical capabilities. It won't have everything that everyone wants, but it will be a step in the right direction, and will gradually be improved in subsequent updates. Initially, users will have access to their logs via the web interface. But we're not doing anything with delivery reports initially ... there are longer term plans for this ... just not short term. We're open for more short term oriented suggestions. For example having a configuration option for a per-user callback URL to route delivery reports back to a user could be possible. Particularly if we could use a fixed template for the URL parameters, and users could specify a base URL on a per-user account basis (e.g., http://server/path/script.php would mean that we call that script with a fixed template of URL parameters). hmm.... -bn | ||||
| sam New member Username: Samdsouza Post Number: 29 Registered: 08-2006 |
Hi Bryce, Looks good enough. If the logs can be displayed via the user account then it would contain the delivery reports also. For the call back url I think it would be better if the user can check the delivery reports via the regular HTTP URL. Something on the following lines: http://server:8800/?user=test&password=test&MessageID=0000006F When the above url is called it can display a DLVRD or UNDLRVD status. This status can be picked/parsed form the log file which contains the delivery report with the corresponding message ID. This would not involve any kind of processing on nowsms behalf as compared to pushing deilvery reports to http://server/path/script.php Regards Sam | ||||
smppdebug
