| Multi sender addresses rangs in one single SMPP account |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 16, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| mSalim Frequent Contributor Username: Salim Post Number: 129 Registered: 04-2005 |
Hi everyone, I have two different SMPP accounts: every SMPP has a rang of Sender addresses (Short codes) to the same Mobile Operator. instead of prefered SMSC defined on the mobile receipient level, I want to know if on the default sender address, we can specify a rang of default sender adresses, separated by comma.. I didn't try it, but if there is somebody who experienced the issue, it's helpful because if I miss a short code - sender address to wrong SMPP account, the reciepient will not get charged.. BR Salim | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 100 Registered: 08-2008 |
Hi Salim, Yes, you can put a comma delimited list of sender addresses into the "Default Sender Address" field. (Do not include any spaces around the commas.) There is some version restriction on this. This particular feature was added starting with the 2007.03.06 release. -- Des NowSMS Support | |||
| mSalim Frequent Contributor Username: Salim Post Number: 130 Registered: 04-2005 |
Hi Des, thank you for the response, I did it directly form the GUI as well as on the INI file, but it doesn't work with Version 5.51k.. as testing. am using live my Lisence 2008, are you sure it will support such features? because I didn't want to play with live servces gateway.. I mean it taking the 1st SMPP account by overiting the default sender list 123,234,345 Please advice BR Salim | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 105 Registered: 08-2008 |
Hi Salim, Yes. Let me explain more about how it works. Let's say you have a "Default Sender Address" defined as "123,234,345". NowSMS (2007 or 2008) will route messages to that account if the message has a sender address of "123", "234" or "345". (If you want to quickly confirm this after making the change, submit some test messages uring URL submission ... e.g., http://127.0.0.1:8800/?PhoneNumber=xxxxx&Sender=123&Text=This+is+a+test) You probably don't have the following configuration, but I mention it just for completeness ... If you have the SMSC route defined as "Support any outbound message traffic", so that the connection is used for general routing (i.e., not just for messages that match on the sender address), then if you send a message without a sender over that connection, NowSMS will automatically apply the first address (123) as the sender address. If 234 or 345 is specified as a sender, they will be allowed. Any other sender address will be converted to 123 when sending. -- Des NowSMS Support | |||
| mSalim Frequent Contributor Username: Salim Post Number: 131 Registered: 04-2005 |
Hi Des, Thanks as always.. same as you above describe I did on the sender address section, what I meant is your confirmation, and now I will proceed.. is there any way to enable it on the 5.51b/k this could be another improvement, because I was sure that v2006/2007/2008 should support such features... please advice.. BR Salim | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 119 Registered: 08-2008 |
[The following post was lost in our web server crash last week. I found it in an archive, and am reposting it here.] Hi Salim, I've checked my notes, and I'm not aware of anything. NowSMS 2006 didn't have this support either. This configuration option didn't happen until 2007 ... which does seem hard to believe, because this seems a common issue. I did look back through some old notes, and some people found that they were able to get around this in older versions by manually editing SMSGW.INI. The trick was to add additional section headers to the file like this: [SMPP - server:port] SenderAddress=123 [SMPP - server:port] SenderAddress=456 [SMPP - server:port] SenderAddress=789 NowSMS would read the extra sender addresses from SMSGW.INI, and use these settings for sender based routing. (Make sure that "Allow Sender Address Override" is checked for the account for this to work.) The danger of this approach is that if you change any settings via the NowSMS configuration program, the settings might not get updated correctly. So use this with caution. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 120 Registered: 08-2008 |
[Salim's follow-up reply was also lost in our web server crash. I am reposting it here.] Hi Des, Lot of thanks because I wasn't yet guess that older are able too.. you means if I have in each SMPP account more than one Short number I have to repeat under them like below: [SMPP - server:port] SenderAddress=123 SenderAddress=345 SenderAddress=456 [SMPP - server:port] SenderAddress=456 SenderAddress=373 SenderAddress=676 [SMPP - server:port] SenderAddress=344 SenderAddress=688 if so, this will be great, I will proceed on it right away Thank you in advance. BR Salim | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 121 Registered: 08-2008 |
Hi Salim, Sorry for the lost messages when our web server crashed last week. Let me clarify my earlier response. The trick requires actually repeating the section header. So let's me use a better example to explain. Let's say that you have 2 SMPP connections. smpp1:2700 can use sender address 111, 112 and 113. smpp2:4900 can use sender address 211, 212 and 213. The trick works like this ... at the end of the SMSGW.INI file, add additional repeated section headers for each SMSC. So you'd add: [SMPP - smpp1:2700] SenderAddress=111 [SMPP - smpp1:2700] SenderAddress=112 [SMPP - smpp1:2700] SenderAddress=113 [SMPP - smpp2:4900] SenderAddress=211 [SMPP - smpp2:4900] SenderAddress=212 [SMPP - smpp2:4900] SenderAddress=213 Having repeated section headers is not valid formatting for an INI file. And it may cause some confusion when updating. (When updating, the repeated section headers could get deleted, although I did not see that happen in my tests.) However, while it may valid formatting ... NowSMS reads these extra section headers for building its sender-based routing table. -- Des NowSMS Support | |||
| mSalim Frequent Contributor Username: Salim Post Number: 133 Registered: 04-2005 |
Hi Des, Many thanks for the details.. I could said I planned it today but I was afraid may be you was busy. Fortunately you recover the web server back Am sure that as logical experience it should work with care as you mainly mentioned on the INI.. I will update you the testing result.. BR Salim | |||
