Trouble Configuring SMPP SMSC as SMPP Server | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
Author | Message | |||||||
Ganesan New member Username: Ganesan Post Number: 6 Registered: 09-2006 |
Hello Bryce We have configured an SMPP SMSC for OutBound SMS. We now want to set up an SMPP Server, with the same SMPP Profile. We have a mobile Operator, providing us the Short Code & the operator is binding with us, through the same SMPP Profile. Now, can we send and receive SMS through a single SMPP SMSC & use it as the SMPP Server also, for the Short code provider to bind with. or, can we use the same SMPP profile for two different SMPP SMSC - one for outbound & other for binding with the Operator? Please help me out. Thanks | |||||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6503 Registered: 10-2002 |
Hi Ganesan, I'm sorry, but I am having some trouble understanding what you are asking. You can add additional outbound SMSC connections. And you can also add inbound connections (define inbound accounts under "SMS Users"). Can you explain what you need more information about? Then I will try to help. | |||||||
Ganesan New member Username: Ganesan Post Number: 7 Registered: 09-2006 |
Bryce, I have two SMSCs configured in my NowSMS gateway. One is a GSM Modem and the other is an SMPP SMSC. The SMPP profile is provided by MTN. we have defined Users for each SMSC and have also defined routenames to send sms, specifically using a particular SMSC. we are able to send and receive sms. Now, we wanted to bind with one of the monile operators, for shortcode service. So, we enabled SMPP server, and defined ports for the same, in our nowSMS gateway, under the "web" tab. We have enabled SMPP & web login for SMPPUser and web login for GSM User. We are binding with the short code provider with the same smpp profile and the username & password is that of the SMPP User. With this binding, the sms sent by the operator, logs in the smsin.log. simultaneously, a log is entered in the smsout.log also. And, the HTTP post we set up in command to execute, does not fire, as the sms sent by the short code operator is received. Please refer the log files, debug logs & the screenshots attached, for more clearity. Thanks Ganesan | |||||||
Ganesan New member Username: Ganesan Post Number: 8 Registered: 09-2006 |
the log files are here...
| |||||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6522 Registered: 10-2002 |
You have configured both of your SMSC connections (SMPP and modem) to route all received messages to an "SMS Users" account (in one case "GSMUser", in the other case "SMPPUser"). Received SMS messages are being routed to the user account that you requested them to be routed to. When you configure messages to be routed in this way, they are not routed to a 2-way command. | |||||||
Ganesan New member Username: Ganesan Post Number: 9 Registered: 09-2006 |
Hello Bryce, I have unchecked the "route to local user" in both my SMSCs. Still, the command to execute doesnot fire. Also, is it normal, that the sms received from a short code, is sent to the short code, automaically through the smsc? For example: I have the following log from smsin.log 2006-09-13 02:39:52,08028732122,Text,gistme emb,+32052 and the following from smsout.log 2006-09-13 02:39:55,4506C11A.req,70.88.83.34,+32052,OK -- COM1:,SubmitUser=smppuser;Sender=08028732122;Text="gistme emb" Please help. Thanks | |||||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6530 Registered: 10-2002 |
No, this is not normal, unless you have configured it to be so. See the definition of the user account that you have defined under "SMS Users" named "SMPPUser". There is a setting there "Route received messages to user via SMPP" ... and you have defined "+32052" here. This means that any messages received by NowSMS that are addressed to this number will be routed to this "SMS Users" account ... and not process by 2-way SMS. -bn | |||||||
Ganesan New member Username: Ganesan Post Number: 10 Registered: 09-2006 |
Hello Bryce I have unchecked the "Route received messages to user via SMPP" in SMS Users, for SMPP User. But still, the command to execute does not fire. Also I still see the following log in smsout.log 2006-09-19 07:26:53,450E6F18.req,70.88.83.34,+32052,OK -- SMPP - smpp.mtnairborn.com:5016,SubmitUser=smppuser;Sender=GistMe;SMSCMsgId=235521111;T ext="gistme emb#news" please help Thanks Ganesh | |||||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6542 Registered: 10-2002 |
Hi Ganesh, According to that log entry, the message is being submitted by an "SMS Users" account named "smppuser". 2-way commands are triggered for messages received via a connection defined in the "SMSC" list. -bn | |||||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6543 Registered: 10-2002 |
P.S. - If I'm not understanding, please enable the "SMSDEBUG.LOG" on the "Serial #" page of the configuration dialog. I can better understand what is going on if I see the SMSDEBUG.LOG. | |||||||
Ganesan New member Username: Ganesan Post Number: 11 Registered: 09-2006 |
Please find the attached smsdebug.log
| |||||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6556 Registered: 10-2002 |
I look at the log, and I see 2-way commands being executed. I'm sorry if I seem like I am being difficult, but I don't understand what I'm supposed to be helping you resolve. Can you give me an example of an inbound message that was not routed to a 2-way command so that I can find a reference to it in this (or an updated) SMSDEBUG.LOG? | |||||||
Ganesan New member Username: Ganesan Post Number: 12 Registered: 09-2006 |
Hello Bryce I have attached the screen shot of my current SMPP smsc & sms user settings. (Please note that, I have unchecked routing in both smsc configuration & sms user configuration - But Still, the sms gets logged within the sms users folder) Here are my logsPlease check the Time of log) SMSDebug.log ------------- 03:32:29:578 [3] ThreadProcessModem: Modem initialization complete: COM1: 03:32:29:687 [8] ThreadProcessSMPPConnection: Processing SMPP connection from 70.88.83.34... 03:32:32:937 [9] ThreadProcessSMPPConnection: Processing SMPP connection from 70.88.83.34... 03:33:34:437 [9] SMPPServerReceiveMessageCallback: inbound message: sender=2348033831157, recip=+32052, pid=0, dcs=0, msgFlags=0, udh=, msg=gistme emb#news 03:33:34:734 [4] ThreadProcessModem: Processing 4513BBBB.req... 03:33:34:734 [4] SMPPSubmitAsyncQ: Depth 1 03:33:36:062 [4] CheckSmppSubmitAsyncQ: 4513BBBB 03:33:36:062 [4] SMPPSubmitAsyncQ: Depth 0 04:00:00:500 [0] main: 30 Days remaining in trial version 04:10:31:171 [8] ThreadProcessSMPPConnection: Releasing SMPP connection from 70.88.83.34 04:10:31:171 [9] ThreadProcessSMPPConnection: Releasing SMPP connection from 70.88.83.34 SMSIn.log ---------------- 03:32:29:578 [3] ThreadProcessModem: Modem initialization complete: COM1: 03:32:29:687 [8] ThreadProcessSMPPConnection: Processing SMPP connection from 70.88.83.34... 03:32:32:937 [9] ThreadProcessSMPPConnection: Processing SMPP connection from 70.88.83.34... 03:33:34:437 [9] SMPPServerReceiveMessageCallback: inbound message: sender=2348033831157, recip=+32052, pid=0, dcs=0, msgFlags=0, udh=, msg=gistme emb#news 03:33:34:734 [4] ThreadProcessModem: Processing 4513BBBB.req... 03:33:34:734 [4] SMPPSubmitAsyncQ: Depth 1 03:33:36:062 [4] CheckSmppSubmitAsyncQ: 4513BBBB 03:33:36:062 [4] SMPPSubmitAsyncQ: Depth 0 04:00:00:500 [0] main: 30 Days remaining in trial version 04:10:31:171 [8] ThreadProcessSMPPConnection: Releasing SMPP connection from 70.88.83.34 04:10:31:171 [9] ThreadProcessSMPPConnection: Releasing SMPP connection from 70.88.83.34 Users/SMPPUser/smsin.log -------------------------- 2006-09-22 03:33:34,smppuser,SMSSubmit,+32052,70.88.83.34,4513BBBB.req,Text,Sender=23480338 31157;Text=gistme emb#news smsout.log ---------------- 2006-09-22 03:33:36,4513BBBB.req,70.88.83.34,+32052,OK -- SMPP - smpp.mtnairborn.com:5016,SubmitUser=smppuser;Sender=GistMe;SMSCMsgId=236422678;T ext="gistme emb#news" Please suggest us a solution, to get the 2 way command working. When I removed the 2 way command, the message did not fall into the SMSIN Directory also. Thanks | |||||||
Ganesan New member Username: Ganesan Post Number: 13 Registered: 09-2006 |
| |||||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6571 Registered: 10-2002 |
Hi Ganesan, The message is not getting routed to a user account, it is getting routed to an SMSC account. This line in SMSOUT:
... indicates that the message was submitting by user ("SMS Users") account "smppuser", and that it was routed out to the SMPP SMSC connection "smpp.mtnairborn.com:5016". 2-way commands are not executed when a message is received from a local user account ("SMS Users"). 2-way commands are executed when a message is recevied from an SMSC connection. | |||||||
Ganesan New member Username: Ganesan Post Number: 14 Registered: 09-2006 |
Thanks Bryce That clearifies many confusions, but one thing. How do we prevent a message from getting routed to an SMSC account? Is it something, that we can control from our gateway configuration settings? Please help us out. I think we are very close to wind up this issue. Thanks Ganesh | |||||||
Ganesan New member Username: Ganesan Post Number: 15 Registered: 09-2006 |
Hello Bryce.... ? How do we prevent a message from getting routed to an SMSC account? Please help... | |||||||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6595 Registered: 10-2002 |
Hi Ganesh, The expectation of NowSMS is that if you connect an SMPP client to NowSMS (with NowSMS as the server), then any message submitted by that client are intended to be routed out to an SMSC account. The only exception is that you can define "Recipient address(es) to route to this recipient" under an "SMS Users" account, and the message will be routed to that user account (for pickup by an SMPP client) instead of routing outbound to an "SMSC" connection. There is no facility to have messages submitted by an SMPP client (with NowSMS as the SMPP server) to be routed to the 2-way command facility. Is this what you are trying to accomplish? -bn |