| Linking Accounts to Specific Gateways |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| John Roth New member Username: Ispeakgeek Post Number: 1 Registered: 08-2006 |
Hello! I'm wondering if there is a way to link a specific SMS User account with a gateway. We have an SMPP simulator that we use to allow our customers to test our system without actually submitting a message to a live SMSC. What we'd like to be able to do is to offer them a log in to the testing pages for NowSMS that will only send messages through to that simulated gateway. I know from the archived post here (http://support.nowsms.com/discus/messages/1/5972.ht ml) that I can limit the accounts that can use a gateway by adding AllowedUserXX entries to the SMSGW.ini file, but my understanding is that, while that would create the link between the account and the gateway, it would also mean that no other accounts would be able to use that gateway. The problem there is that we also want to be able to allow our regular accounts to be able to specify a ROUTE=TEST when they want to send messages through the SMPP simulator while using their own SMS accounts. Is there a way to do this through another configuration setting? Perhaps something in the files that define the SMS users? I'd hate to have to create two definitions for the SMPP simulator gateway - one dedicated to the test account and the other for defining the TEST route. Thanks for any help! John | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6330 Registered: 10-2002 |
Hi John, Hmm ... It would be interesting to have an option to map the SMPP "service_type" value to a particular route, or some such logic. That's not something that we can do today ... and I'm not necessarily saying that we will do that in the future ... I'm just thinking out loud about what might make for a good way to support what I think you're trying to accomplish. It sounds like you want to have the ability for customers to sometimes route messages via the simulator route ... but at other times, have them route normally. If my understanding is correct, then an idea would be simply to associate a "Default Sender Address" with the simulator route. Whenever a user submits a message with that address as the sender, it will get routed via the simulator. -bn | |||
| John Roth New member Username: Ispeakgeek Post Number: 3 Registered: 08-2006 |
Hi Bryce! Could do, but the drawback to that approach would be that they wouldn't be able to test both Text and Numeric values for originators (unless we set up multiple simulator gateway connections). I think that I'm looking more for something like being able to specify either a Default Route or an Allowed Routes property for individual user accounts. This would have the additional benefit of allowing us to dedicate gateway connections to a specific customer (or group of customers) or to specify a lower volume gateway for entry-level customers. Think that'd make the feature list for the next version?  Cheers, John | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6389 Registered: 10-2002 |
Hi John, Yeah, that makes sense. Actually, just having an allowed routes attribute for each user account would make sense. As opposed to the current approach of having an allowed users attribute for each route. My brain is hurting a little bit thinking about it right now. Logically, I think you could apply the same rules using either approach. But either way, I don't know how this would address your concern about the test route, unless I am not understanding your intent. If a client has access to both a production and a test route, how does the client indicate that the message should go through the test route? Unless the intent is that the client starts out on the test route ... and then moves to the production route after they are approved? In which case, I'm wondering if the current "allowed user" logic that we have could still be workable ... but with a configuration interface that looked at it from the user perspective instead of the connection perspective. Sorry if I'm not making much sense ... it is Friday ... it's late ... and I'm just trying to think through whether our current logic could be kept on the server end, with just a user interface on the configuration end that applied the restrictions on a per-user account basis. -bn | |||
| John Roth New member Username: Ispeakgeek Post Number: 5 Registered: 08-2006 |
Sorry, I probably should have stated what I was planning a little more clearly in my original post. Our current system allows them to pass in a Test=true parameter to our front-end, which should then ensure that their message doesn't go through a live SMPP connection. I suppose, now that I think about it, that I could just do that by translating the Test=true parameter into a submission to NowSMS that includes (or overrides) Route=SMPPSimulator. My original thought had been to have one or more accounts specifically dedicated to testing, so we'd give our users (or prospective users) access to a user account, say one called 'Simulator'. That user account would then ideally be routed only through the SMPP simulator gateway. From what you've said, it sounds like if we specify that the SMPP Simulator has an allowed user list that includes those test accounts that'd also cover that too. Can I set the allowed users through the UI or do I have to go into the INI? If so, what's the name of the attribute to set? In either case, we'd still really like to be able to specify the gateways that a user account can make use of. We can always implement something like that for our own least cost routing by maintaining a list of routes for each user and then specifying the route in our post to NowSMS - it would be great to be able to do that from within NowSMS though! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6405 Registered: 10-2002 |
Hi John, Right now you can only set those "allowed user" settings via direct edits of the SMSGW.INI file. The following settings can be added to an SMSC specific section of SMSGW.INI (e.g., [SMPP - a.b.c.d:xyz] section): 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. Logically, it would make more sense (at least to me, and probably to most others) if the attributes were associated with a user account, rather than associating them with an SMSC definition. But in the end, the result should be the same. Ideally, when we finally setup a UI for configuring this attribute, the UI should have the ability to view the attributes from both perspectives. (e.g., edit a user account and have a pop-up to show which SMSC routes they can access, or go into an SMSC definition and have a pop-up to show which users are allowed to access the route) -bn | |||
