Response to Inbound - HTTP Post not working

Response to Inbound - HTTP Post not working SearchSearch
Author Message
Ganesan
New member
Username: Ganesan

Post Number: 1
Registered: 09-2006
Posted on Saturday, September 09, 2006 - 12:42 pm:   

Hello Bryce,

We receive SMS from an SMPP Connection.

The message gets logged in SMSin.log

But the HTTP post in the Command to execute doesnt seem to have executed.

Please suggest how, we can trouble shoot on this.

Thanks & Regards
Ganesh
Ganesan
New member
Username: Ganesan

Post Number: 2
Registered: 09-2006
Posted on Monday, September 11, 2006 - 05:51 pm:   

we have short code(5 digit) enabled for the SMPP profile.We bind with our operator, with the following settings.
Source TON = 5,
Source NPI = 0,
Dest TON = 1,
Dest NPI = 1.

we are binding as both transceiver & receiver in same channel.

Please let us know, if we are missing any configuration, to make the HTTP Post work.

Please treat this as urgent.

Thanks
Ganesh
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6492
Registered: 10-2002
Posted on Tuesday, September 12, 2006 - 12:49 pm:   

Hi Ganesh,

Does the message go into the SMS-IN directory?

I'd suggest enabling the SMSDEBUG.LOG (easiest to do this on the "Serial #" page of the config), and then let's take a closer look at what the debug log shows when it is receiving the message.

It would also help to see your SMSGW.INI file, that way I can see the 2way commands that you have defined, as well as if there are any overrides for received messages to get routed to a local "SMS Users" account.

-bn
Ganesan
New member
Username: Ganesan

Post Number: 3
Registered: 09-2006
Posted on Tuesday, September 12, 2006 - 01:43 pm:   

Thank you Bryce.

No Bryce, the message DOES NOT go into the SMS-IN directory. I think it would not, since I have configured a "command to execute" in 2-way sms.}

For more information, below is a portion of my smsin.log

2006-09-12 04:38:40,1121611611,Text,32052 Error Invalid Number. Please re-send using a valid 10 digit mobile number. gistme emb,18182571710
2006-09-12 04:41:28,08028732122,Text,gistme emb,+32052
2006-09-12 04:41:36,1121611611,Text,32052 Error Invalid Number. Please re-send using a valid 10 digit mobile number. gistme emb,18182571710
2006-09-12 04:56:13,08028732122,Text,gistme emb,+32052
2006-09-12 04:56:20,1121611611,Text,32052 Error Invalid Number. Please re-send using a valid 10 digit mobile number. gistme emb,18182571710
2006-09-12 05:01:35,08028732122,Text,gistme emb,+32052
2006-09-12 05:07:39,08028732122,Text,gistme emb,+32052

The HTTP Post works for

“2006-09-12 04:56:20,1121611611,Text,32052 Error Invalid Number. Please re-send using a valid 10 digit mobile number. gistme emb,18182571710


Does this have something to do with the Source TON?

If so, how can I configure a same SMPP profile to use both “alpha characters” & “Numbers starting with ‘+’ sign” for source address.

The Source TON values, for the two above cases are given as 5 and 3 respectively, in the NowSMS manual. Is my understanding correct?

Please help me out.
Ganesan
New member
Username: Ganesan

Post Number: 4
Registered: 09-2006
Posted on Tuesday, September 12, 2006 - 02:12 pm:   

For More Information

when I removed the command to execute, the sms did not go into the SMS-IN directory.

But I see it in the smsin.log.

Thanks
Ganesan
New member
Username: Ganesan

Post Number: 5
Registered: 09-2006
Posted on Tuesday, September 12, 2006 - 03:22 pm:   

SMSdebug.log & smppdebug.log attached...
application/octet-streamSMSDebug.log
smsdebug.log (3.5 k)
application/octet-streamSMPPDebug.log
smppdebug.log (74.5 k)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6513
Registered: 10-2002
Posted on Friday, September 15, 2006 - 07:39 pm:   

Based upon your log files, the received message appears to be getting routed to a connected SMPP client.

I don't know enough about your configuration to know why this is the case ... but I assume there is some routing of received messages configured for this "SMS Users" account. Any such routing will route the message directly to the SMPP client and bypass any 2-way command processing.