HTTPSMC gives HTTP/1.0 500 Internal Server Error

HTTPSMC gives HTTP/1.0 500 Internal Server Error SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 20, 2013 » HTTPSMC gives HTTP/1.0 500 Internal Server Error « Previous || Next »
Author Message
New member
Username: Mdfaisalpapa

Post Number: 1
Registered: 03-2013
Posted on Sunday, March 03, 2013 - 03:26 pm:   

I have taken Bulk SMS Service from

the url for sending the sms is d=SENDID&to=1234567890&msg=NAME:VENKATASUBRAMANIAN%20C.Bal(07/02/2013)42839(C)%20Last%203%20Transactions%2001/02/13%20SR%201173%2001/02/13 %20VR%209000%2018/01/13%20FW%2010000%20For%20Help%20SMS%20SAPF%20HELP&route=T

The uname and pwd are self explanatory. Senderid and route are legal requirement in INDIA.

I have added a HTTPSMC in NowSMS with the following entries

Server Type=BT Ignite ( I set it to custom but it get changed to BT Ignite on saving the settings)

Server URL=
Templete URL Text=/sendsms?uname=username&pwd=password&senderid=SENDID&to=@@PhoneNumber@@&msg =@@Text@@&route=T

Templete URL Binary=/sendsms?uname=username&pwd=password&senderid=SENDID&to=@@PhoneNumber@@&m sg=@@Text@@&route=T&udh=@@UDH@@

udh is not required but NowSMS requires this to save the settings.

When I try to send SMS sending Fails with HTTP/1.0 500 Internal Server Error. But iam able to send SMS through entering URL in my browser's address bar. The SMSDEBUG.log conatins the following entry

18:40:29:201 [16] ThreadProcessModem: Processing 5113E9C6.req...
18:40:29:201 [16] ThreadProcessModem: GET d=senderid&to=1234567890&msg=NAME:VENKATASUBRAMANIAN%20C.Bal(07/02/2013)42839(C)%20Last%203%20Transactions%2001/02/13%20SR%201173%2001/02/13 %20VR%209000%2018/01/13%20FW%2010000%20For%20Help%20SMS%20SAPF%20HELP&route=T HTTP/1.1
User-Agent: Now SMS/MMS Gateway v2012.06.28
Accept: */*
Connection: close

18:40:29:906 [16] HttpResponseWait: Ok
18:40:29:906 [16] ThreadProcessModem: HTTP/1.0 500 Internal Server Error
Date: Sun, 03 Mar 2013 13:09:24 GMT
Server: Apache
Content-Length: 0
Content-Type: text/html; charset=UTF-8
Connection: Close

18:40:29:906 [16] WaitForSocketClose: WinSock reported ioctlsocket complete
18:40:29:906 [16] ThreadProcessModem: Error: HTTPSMSC: Connection failed, HTTP status code = 500.
18:40:29:906 [16] ThreadProcessModem: SMS message could not be sent to 1234567890(HTTP -, HTTPSMSC: Connection failed, HTTP status code = 500.
21:09:06:470 [0] UseRouteCache: Yes
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4303
Registered: 08-2008
Posted on Monday, March 04, 2013 - 06:00 pm:   


Does the exact same URL, if you cut and paste from MMSCDEBUG.LOG, work from the browser?

The service is returning an error in that URL, so the only solution is to determine what part of the URL is causing a problem.

NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics