| Response code 500 when sending 10 MMS request |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 13, 2018 ⬆ |
◄ ► |
| Author | Message | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5733 Registered: 08-2008 |
Hi Pankaj, I need to understand the context of this 500 error. Where does it occur? HTTP response from NowSMS to your application? Or in the MMSC logs when NowSMS submits to mobile operator? If the latter, then your mobile operator may have a limit on the number of recipients per MMS. By default, for an MM1/modem connection, NowSMS imposes a limit of 50 recipients per MMS. If a message is sent to more than 50 recipients, NowSMS will split the message into groups of no more than 50 recipients. For example, if you send to 51 recipients, NowSMS will make 1 submission for the first 50 recipients, then another submission for the 1 remaining recipient. Some mobile operator may have lower recipient limits. This limit can be set in the "MMSC Routing" definition under the "Max Recipients per Message" setting. You might want to try setting this to 1 to have NowSMS submit one at a time. -- Des NowSMS Support | ||||
| Pankaj Mathur New member Username: Pankajmathur Post Number: 14 Registered: 08-2015 |
Hi Des, We are getting HTTP connection time out from nowSMS to our application. Also previously "Max Recipients per Message" was set to Default which i have changed it to 50. So does this mean now we can send 50 MMS message to nowSMS in single batch? What is default in "Max Recipients per Message"? Thanks Pankaj | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5739 Registered: 08-2008 |
Hi Pankaj, That setting will have no impact on the problem that you are seeing. It affects communication between NowSMS and the mobile operator. 50 is currently the default setting for an MM1 connection. This is all irrelevant if you are experiencing a timeout between your application and NowSMS. Are you using accounting callbacks? If so, then they are processing too slowly. There will be one callback per recipient, and the HTTP response is not returned until all callbacks are complete. An MMSCDEBUG.LOG would give me a better idea of what is happening, but based upon the information so far, this is my best guess. -- Des NowSMS Support | ||||
| Pankaj Mathur New member Username: Pankajmathur Post Number: 15 Registered: 08-2015 |
Hi Des, How to change the call back settings. Please explain more. Also attaching the MMSCdebug log with you please check.
| ||||
| Pankaj Mathur New member Username: Pankajmathur Post Number: 16 Registered: 08-2015 |
Hi Des, Request you to please update on the status? Thanks | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5741 Registered: 08-2008 |
Sorry...I had looked at the log and did not see any indication of problems. So I was hoping you would come back with more information. But thinking about it, I now realize that you are using URL submission and even though it is MMS, the details would be recorded in the SMSDEBUG.LOG, so I actually need to see that. Sorry it has taken me so long to get this understanding. -- Des NowSMS Support | ||||
| Pankaj Mathur New member Username: Pankajmathur Post Number: 17 Registered: 08-2015 |
Hi Des, Please find attached the SMSCdebug log. Request your quick reply.
Thanks Pankaj Mathur | ||||
| Pankaj Mathur New member Username: Pankajmathur Post Number: 18 Registered: 08-2015 |
Hi Des Please ignore the previous attachment. attached the SMSCdebug Log. Thanks Pankaj Mathur
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5744 Registered: 08-2008 |
Hi Pankaj, OK, I don't see any processing delays that would explain why you are seeing timeouts. Accounting callbacks are not being used, so that advice does not apply. But I do have a theory that your app is getting confused by keep-alive sockets, as I do see odd timings for when the app releases the connection. Edit SMSGW.INI and add this setting under the [SMSGW] header: EnableKeepAlive=No -- Des NowSMS Support | ||||
