| SMPP users |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 16, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Omar |
I have 3 SMPP connections(3 ports) with same operator.On my clients needs to connect with my through SMPP.(He has 2 shortcodes in every port) I have 2 questions: 1-Should I have him 3 SMPPs or 1 SMPP connection? 2-When he want to send SMS,how the SMS go through my connections? I mean suppose I have port 211x ,474x & 789x? and the client has 2111,2112 from firts port,4779 fro second and 7892 from the third. If he want to send sms from 7892,how it will send from port 789? I hope that I was clear. | |||
| Des - NowSMS Support New member Username: Desosms Post Number: 4 Registered: 08-2008 |
Hi, I probably need more details (more complete description of each connection and short codes associated with it) in order to give you a clear answer. However, unless there is something unusual ... your client probably only needs 1 SMPP connection to your system. When they submit a message to your system, the sending short code will decide which connection the message gets routed to. The following link describes the logic for this type of sender-based routing: http://blog.nowsms.com/2008/07/routing-sms-messages-to-specifc-smsc.html -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 2 Registered: 01-2008 |
Hi, the connections with same operator and I can send only in UAE(that is all the nos will start with 97150) .first SMPP has port 211,and the second 474 and the third is 789) and each port has 10 shortcodes:from 0-9 like 2110,2111,2112,...2119. and the client has the shortcodes 2112,2115,4741,4744,7890. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 113 Registered: 08-2008 |
Hi, Are you using the "Default Sender Address" setting for each SMPP connection, something like this: "2110,2111,2112,2113,2114,2115,2116,2117,2118,2119"? That would tell NowSMS that messages addressed from any of those sender addresses go out that specific SMPP connection. Then, for this client, you would define a "Forced Sender Address" of "2112,2115,4741,4744,7890", so that they can only send out using one of those short codes. They can submit any of those short codes to you via a single connection. -- Des NowSMS Support | |||
| Omar |
hi, thanks Des, I got what you mean. I was thinking in the same idea.But this can be applied only if the sender is known(fixed),but suppose I have dynamic sender Id and have many SMPPS,how can I force the client to use SMPP1 or SMPP2 or SMPP3? I have also another question in how nowsms queues the SMS. Nowsms uses the queing method(first comes first goes). suppose I send 200 SMS,250 SMS and 300 SMS respectively throygh the same SMPP Nowsms what will do first take the 200 and then put the 250 down and the other 300 at last,then It will send from first to last. but if I send the same patches throught 3 SMPPs, Did nowsms will do the same?or it will try to connect through the three SMPPS at same time? | |||
| Des - NowSMS Support New member Username: Desosms Post Number: 8 Registered: 08-2008 |
Hi Omar, This is possible, but it is trickier. If you have particular SMPP user accounts that you want to route via specific outbound SMSC connections, then are configuration settings that can be applied in SMSGW.INI. These settings are applied under the section header definition for the SMSC (e.g., [SMPP - server:port]). AllowedUserOnly= AllowedUser1= AllowedUser2= AllowedUser...= These configuration settings are defined to limit particular outbound "SMSC" connections to use by selected "SMS Users" accounts. AllowedUserOnly=Yes -- This setting specifies that the SMSC connection can only be used by users that are specifically authorised to use this SMSC. When routing messages from users that are not specifically authorised for this connection, NowSMS will not use this SMSC and route messages as if this SMSC definition did not exist. AllowedUser1=username -- This setting can be repeated with sequentially assigned numbers (e.g., AllowedUser2=xxx; AllowedUser3=yyyy). This entry is used to specify specific "SMS Users" accounts that are allowed to use the SMSC connection when AllowedUserOnly=Yes. Note: It is NOT necessary to restart NowSMS when making updates to the AllowedUserOnly or AllowedUser1 settings in SMSGW.INI. These changes will be detected dynamically by NowSMS. Regarding your other question ... I am not sure I understand the question, but the following answers might help. If you have multiple outbound SMSC connections, NowSMS will process them all simultaneously. If you have multiple inbound SMPP connections ("SMS Users") sharing outbound connections, there are two settings on the "SMS Users" page that can be useful. Enable "Separate outbound message queues for each user", and define a "User Queue Size Threshold" value. The "User Queue Size Threshold" is the most messages submitted by any one user that NowSMS will process before going back to check other user queues. Let's say you set this value to 50. If one user submits 1000 messages, NowSMS will only process 50 in a row from that user before going back to check other user queues. -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 2 Registered: 01-2008 |
thanks Des, sorry not this what I mean,My question is sending an SMS campaign through mutiple SMPPS will be faster than sending it in 1 SMPP? Second question I see that when I give a user SMPP that I can't process these SMS from 2 way? Is there a way to process these SMS.like saving in DB,or sending a reply? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 145 Registered: 08-2008 |
In most cases, yes. If this is an outbound SMPP connection from NowSMS, go into "Advanced Settings" and enable SMPP Async mode with a window size of at least 5.
That is correct. Are you trying to process delivery receipts, or are you trying to process all messages? -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 3 Registered: 01-2008 |
No I want to save these SMS in my Database,but in future may be I want to reply to these SMS. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 146 Registered: 08-2008 |
I'm confused. What messages do you want to save? Do you mean the messages that are submitted by the SMPP client ("SMS Users" account)? They will be logged in the SMSOUT-yyyymmdd.LOG file when they are sent out. You can also implement an accounting callback, so that when the user submits the message, you receive an HTTP callback with the message details. The accounting callbacks are described here: http://www.nowsms.com/support/bulletins/tb-nowsms-001.htm That link is a little old, and it doesn't mention that all of the message details are passed in the accounting callback. SMS accounting callbacks (including PreAuth) include additional information about the message, beyond what is described at that page. Additional parameters are: “&SubmitIP=” (IP address of submitting client) “&Sender=” (sender address of SMS message) “&Binary=” (set to 1 if message is binary) “&PID=” (Protocol ID), “&DCS=” (data coding scheme value) “&UDH=” (user data header) “&Data=” (hex string with message data for binary messages) “&Text=” (UTF-8 text of message). The “PreAuth” can also now return a specific SMPP error code to be returned to a submitting SMPP client (previously, if PreAuth=Deny” was returned in the response, the SMPP error code ESME_RTHROTTLED was always returned). To return an error, the HTTP response to the PreAuth accounting callback should include the text, SMPPErrorCode=#### or SMPPErrorCode=0x####, where #### is the SMPP error code to be returned. (If the “0x” prefix is present, the error code is assumed to be in hex format, otherwise it is assumed to be in decimal.) -- Des NowSMS Support | |||
| Omar New member Username: Kfsmart Post Number: 4 Registered: 01-2008 |
Hi Des, I mean I want to save The SMS In that is directed to the SMPP client. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 147 Registered: 08-2008 |
It gets written to the log files, but there is no HTTP callback. It will be written to the SMSOUT-yyyymmdd.LOG with the field that normally contains the outgoing status and SMSC listed as "OK -- LocalUser:accountname". And it will be written to SMS-yyyymmdd.LOG in the USERS\accountname directory. | |||
| Omar New member Username: Kfsmart Post Number: 5 Registered: 01-2008 |
Hi Des, May be I was not clear, look first when any SMS comes to nowsms,I process it as 2 way,saving in DB and then send a reply SMS(I'm not checking command returns response text),I'm processing as my wish and having reporting to all SMS coming. I have some clients taking some shortcodes, from the reports I can see how many SMS came to each shortcode. Now I have a new client that wants SMPP connectivity as I told you previous.I want to do the same,saving the SMS In in my DB that I can monitor the SMS IN from my own reports. Can I do this from nowsms?because I see that I can't do this in 2way? Second Issue when the client sends SMS can I also have records to these other than the log files(I mean saving it in my own application? Hope you can reply soon? thanks in advance | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 148 Registered: 08-2008 |
Hi Omar, When the client receives an SMS message, the only way that you can know this is via the log files. It will be written to the SMSOUT-yyyymmdd.LOG with the field that normally contains the outgoing status and SMSC listed as "OK -- LocalUser:accountname". (Yes, it is in the OUT log, not the IN log. The IN log also will have a record of the message, but the IN log does not log that the message is getting routed to the user, while the OUT log does.) And it will be written to SMS-yyyymmdd.LOG in the USERS\accountname directory. When the client sends an SMS message, the HTTP accounting callback that I mentioned above is triggered, and this gives you details of the message. (The messages will also be recorded in SMSOUT and USERS\accountname logs.) -- Des NowSMS Support | |||
