| How to view LOGs of messages |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 03, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Rahul Hukku New member Username: Rahulhukku Post Number: 3 Registered: 08-2004 |
Dear bryce, I have written a java program to use the NOWSMS API to push WAP OTA settings . How can i veiw a log information of the messages sent by NOWMS to the SMSC. regds, | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3302 Registered: 10-2002 |
Hi Rahul, The SMSOUT-yyyymmdd.LOG file will contain details of messages dispatched to the SMSC. -bn | |||
| Rahul Hukku New member Username: Rahulhukku Post Number: 4 Registered: 08-2004 |
hi, i checked out the SMSOUTxxxxx.log file details. A sample string extract from that file is "2004-08-12 11:10:01,SAR-9822003851-a0-3-1.req,10.0.0.72,9822003851,OK -- CIMD - 1". Can u tell me- 1)what does the SAR in the above string mean ? 2) The "OK" in the above string -- does it mean that the SMSC has sent a success acknowledgement to NOWSMS for the PDU sent. thnx, rahul. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3328 Registered: 10-2002 |
Hi Rahul, The following thread has additional information that you will find helpful: http://support.nowsms.com/discus/messages/1/5804.html To answer your questions: 1.) "SAR-" is just part of the internal request id. When a message is in multiple parts, NowSMS currently uses this syntax in the request id to help it manage the multiple parts. 2.) Yes. | |||
| Rahul Hukku New member Username: Rahulhukku Post Number: 7 Registered: 08-2004 |
bryce, thnx for all the info. Another question is ; how is the retry table implemented in NOWSMS. 2. where are the messages(to be retried) stored in NOWSMS ? rahul. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3341 Registered: 10-2002 |
Rahul, If the SMSC is down (cannot connect or login), then messages are held, and no retries are counted. Retry logic kicks in if there is an error occurs when submitting the message to an SMSC (SMSC returns an error response, or the connection fails during submission). Some of the retry behaviour is specific to particular SMSC types (for example, there is some special behaviour for some SMPP response codes), but there is currently no special handling for any CIMD specific response codes. The following settings can be specified under the [SMSGW] section header of SMSGW.INI: RetryDelay=#### specifies a number of seconds to wait to retry sending after an error condition, the default value is 30. RetryDelayMultiplier=### specifies a multiplier to be applied for successive send failures, the default value is 1. For each failed attempt, the retry delay will be the product of RetryDelay*RetryDelayMultiplier*#FailedAttempts. To use a fixed retry delay of RetryDelay, specify RetryDelayMultiplier=0. RetryDelayAfterAttempts=### specifies that the retry delay should only be applied after ### failed attempts, the default value is 2. NowSMS will immediately retry a failed message send until it has made RetryDelayAfterAttempts, after which it will apply a retry delay. RetryMaxAttempts=### specifies the maximum number of retries that NowSMS will attempt before a message is rejected, the default value is 20. | |||
