2 way doesn't send output to HTTP url

2 way doesn't send output to HTTP url SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through April 16, 2015 » 2 way doesn't send output to HTTP url « Previous || Next »
Author Message
George Sharvadze
New member
Username: Gsharvadze

Post Number: 1
Registered: 09-2014
Posted on Thursday, September 11, 2014 - 12:26 pm:   

Hi

I'm using NowSMS v2014.02.28 build. It doesn't send the output to the HTTP URL added under "Process Received SMS messages".

The URL is accessible and is working from the browser. Even this example doesn't work:

Can you please help me with this issue?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5037
Registered: 08-2008
Posted on Thursday, September 11, 2014 - 06:56 pm:   

Hi,

I'm not sure exactly what you mean by "send the output" ... do you mean the 2-way command is not being run? Or do you mean the output from the 2-way command is not being sent in reply?

I am assuming the 2-way command is not being run.

In that case, I would suggest the following:

1.) Does NowSMS show that it is receiving any messages? In other words, does the SMS received counter increase?

2.) Do the messages appear if you click view button on the 2-way page, or is the list empty?

3.) Is the "SMS Command Prefix" (or "Keyword" in newer versions) set to *? Note ... the documentation shows "*", but that does not mean include "" characters. Only *

4.) Is the receive phone number setting blank? Please try it blank.

5.) Enable the SMSDEBUG.LOG. Send in another message and view that log to look for any details about the received message. Sometimes this will show an unexpected typo or other unexpected information.

--
Des
NowSMS Support
George Sharvadze
New member
Username: Gsharvadze

Post Number: 2
Registered: 09-2014
Posted on Friday, September 12, 2014 - 11:30 am:   

Than you for your response. I've figured out the "2 way" configuration...

One more question: I receive the following response from the provider: "0000 - 393560156"

Is it possible to somehow parse the Message ID after this string "0000 - "?


Thank you in advance
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5038
Registered: 08-2008
Posted on Friday, September 12, 2014 - 07:20 pm:   

Hi George,

Is this an HTTP SMSC connection? and you are using the MessageIDResponsePrefix setting?

If so, what does the raw response look like? Is it XML based?

I know our parsing stops at white space, even if it is inside an XML element, but perhaps it should not. Is the 0000 - significant, or is that part fixed?

--
Des
NowSMS Support
George Sharvadze
New member
Username: Gsharvadze

Post Number: 3
Registered: 09-2014
Posted on Monday, September 15, 2014 - 07:34 am:   

Hi

1. Is this an HTTP SMSC connection? - Yes, it is
2. Are using the MessageIDResponsePrefix setting? - Yes
3. What does the raw response look like? Is it XML based? - No, it's just a following string: 0000 - 393560156. We're currently using the setting MessageIDResponsePrefix=00, this logs the second part of the error code, for example for the response code 0009, 09 will be logged in the file

What I'd like to do is to transfer the above response to some third party HTTP URL, instead of just logging it. Any idea is greatly appreciated

Thank you
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5040
Registered: 08-2008
Posted on Monday, September 15, 2014 - 09:57 am:   

Hi George,

We are open to suggestions on how to better handle the response parsing. Unless I am misinterpreting, it sounds like you need an option to allow spaces in the message ID. Do you agree?

For a log alternative, try the accounting callbacks. In the SMSOUT callback, the upstream ID will be reported.

--
Des
NowSMS Support

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