| 2 way problems with HTTPS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Lance Taschner Unregistered guest |
I am having a problem getting 2 way working with SSL. Whenever I use HTTPS as a received SMS command I get an SSL connection error. We are using an Apache web server. Any ideas? Here is a copy of the debug log (Note: server = our server, phone numbers are changed but real phone numbers were used). 13:57:24:446 [2] ModemReceiveMessages: Decoding received message index 1 from message storage ME 13:57:24:446 [2] ModemReceiveMessages: 07914140279560F0240AA1010101006500005070523165228A16466953C7A42A9AD3A38E5E6697CD A018CE86BB01 13:57:24:446 [2] ModemReceiveMessages: SMSC address len = 7 13:57:24:446 [2] ModemReceiveMessages: SMSC Address = +14047259060 13:57:24:446 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 13:57:24:446 [2] ModemReceiveMessages: Sender address len = 10 13:57:24:446 [2] ModemReceiveMessages: Sender Address = 1010100056 13:57:24:446 [2] ModemReceiveMessages: PID = 00 13:57:24:446 [2] ModemReceiveMessages: DCS = 00 13:57:24:446 [2] ModemReceiveMessages: Anticipated user data length = 22 13:57:24:446 [2] ModemReceiveMessages: Message = FRM:LT MSG:test 13:57:24:446 [2] ModemReceiveMessages: AT+CMGD=1 13:57:24:556 [3] ThreadProcessInboundSMS: Processing 42E55234.in... 13:57:24:556 [3] GetProgramToExecute: https://server/staging/sms/page.php?mobileno=1234567890&message=test&recipient=1 234567890 13:57:24:556 [3] ThreadProcessInboundSMS: Executing https://server/staging/sms/page.php??mobileno=1234567890&message=test&recipient= 1234567890 13:57:24:556 [3] RetrieveURL: Retrieving https://server/staging/sms/page.php?mobileno=1234567890&message=test&recipient=1 234567890 13:57:24:556 [3] RetrieveURL: Looking up server 13:57:24:586 [3] RetrieveURL: SSL_connect: Error 140770FC making SSL connection | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4694 Registered: 10-2002 |
Hi Lance, Do you have any problems connecting to that 2-way command with a web browser? The error code is indicating an unknown protocol error when negotiating an SSL/TLS connection with the server. We're using OpenSSL, which is pretty standard, and it should be configured to handle SSL2/SSL3/TLS1 with all of the standard ciphers. Can you issue the same URL request from a web browser without any problem? -bn | |||
