NowSMS Admin API !!

NowSMS Admin API !! SearchSearch
Author Message
Andrew
New member
Username: Xserver1

Post Number: 1
Registered: 06-2010
Posted on Thursday, June 24, 2010 - 05:09 pm:   

I am currently testing the trial version of NowSMS and it is working as per the expectations.

But i would like to know that does NowSMS offers any Web Administration SDK by which i can write down an application to talk to NowSMS configs directly ?

It will make my life real easy as i never want to give access of the NowSMS Server to my support team.

Regards
Andrew
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2273
Registered: 08-2008
Posted on Thursday, June 24, 2010 - 11:04 pm:   

Hi Andrew,

There are a couple of web APIs, but they don't give you full access to the server configuration. (For example, adding/deleting/modifying SMSC connections ... for that you need to use VNC or Remote Desktop.)

User account provisioning is described here:

http://www.nowsms.com/support/bulletins/tb-nowsms-013.htm

And a status/statistics for monitoring is described here:

http://blog.nowsms.com/search/label/statistics

There is also a limited web interface for user account provisioning, statistics and accessing log files. It is enabled with with a setting on the "Web" page of the NowSMS configuration dialog, and it is accessed by adding "/admin" to the NowSMS URL.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2275
Registered: 08-2008
Posted on Thursday, June 24, 2010 - 11:48 pm:   

Hi Andrew,

There are a couple of web APIs, but they don't give you full access to the server configuration. (For example, adding/deleting/modifying SMSC connections ... for that you need to use VNC or Remote Desktop.)

User account provisioning is described here:

http://www.nowsms.com/support/bulletins/tb-nowsms-013.htm

And a status/statistics for monitoring is described here:

http://blog.nowsms.com/search/label/statistics

There is also a limited web interface for user account provisioning, statistics and accessing log files. It is enabled with with a setting on the "Web" page of the NowSMS configuration dialog, and it is accessed by adding "/admin" to the NowSMS URL.

--
Des
NowSMS Support
Andrew
New member
Username: Xserver1

Post Number: 2
Registered: 06-2010
Posted on Friday, June 25, 2010 - 06:45 am:   

Any provision to add / edit SMSC connection , stop / start NowSMS Service and do more advances stuff over Web ?
Andrew
New member
Username: Xserver1

Post Number: 3
Registered: 06-2010
Posted on Friday, June 25, 2010 - 07:34 am:   

i will add all my queries to this respective post.

1. How can we route a SMPP Client to a specific upstream SMPP gateway. I already have the idea to route numbers to specific gateway but what if i want to route all traffic of a #SMPPCLIENT1 to #1.SMPPGW and #SMPPCLIENT2 through #2.SMPPGW
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2279
Registered: 08-2008
Posted on Friday, June 25, 2010 - 07:57 pm:   


quote:

Any provision to add / edit SMSC connection , stop / start NowSMS Service and do more advances stuff over Web ?




No.

There are some customers who do their own direct modification of the SMSGW.INI file.

If the service needs to restart, it can update ConfigurationUpdateTriggerRestart= under the [SMSGW] header of SMSGW.INI. Normally, you just set this value to local time YYYYMMDDHHMMSS. If NowSMS sees that this value has changed to a larger value it triggers the service to restart.

(Adding/deleting SMSC connections requires a service restart at this time.)


quote:

1. How can we route a SMPP Client to a specific upstream SMPP gateway. I already have the idea to route numbers to specific gateway but what if i want to route all traffic of a #SMPPCLIENT1 to #1.SMPPGW and #SMPPCLIENT2 through #2.SMPPGW




It depends on your requirements. For simple requirements, you can force a sender address to be applied to all messages from a user account, and use sender based routing.

For more advanced requirements, there are the AllowedUser settings. There's a simple example that explains them here: http://support.nowsms.com/discus/messages/1/24836.html(search on AllowedUserOnly for more).

For even more advanced configurations, it is possible to implement an HTTP based routing callback. Basically, when a message is submitted, we ask you how to route it.

If you are implementing accounting callbacks for user charging, you may want to consider this, because it happens in one of the accounting callbacks, so it doesn't add any additional overhead. The process is described here: http://blog.nowsms.com/2009/01/dynamic-sms-message-routing-with-http.html


--
Des
NowSMS Support
Andrew
New member
Username: Xserver1

Post Number: 4
Registered: 06-2010
Posted on Friday, June 25, 2010 - 09:00 pm:   

I am working on Dynamic Sender ID's. A Single SMPP User Account will pass multiple sender id. which is out of my control.

So what will be useful is to route the entire SMPP user to a specific upstream gateway. ( maybe i can add route string in SMSGW.INI ? )

As of now i am not using NowSMS for accounting callbacks.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2280
Registered: 08-2008
Posted on Friday, June 25, 2010 - 09:41 pm:   

The limitation of the AllowedUser settings is that you mark an SMSC connection as "AllowedUserOnly=Yes".

This means that a user can only have messages routed to that connection if they are explicitly allowed.

It works well for a system with a few outbound SMSC links, and a manageable number of user accounts.

However, the logic is that the SMSC connection is restricted until one or more users are allowed to use it.

This works for a lot of scenarios. But it seems to be the inverse of what you are asking for.

You're looking at each user, and applying route restrictions to each user.

By contrast, we're looking at each connection and applying user restrictions to the route.

You can accomplish most of the same restrictions either way. The links from that other discussion thread have a better description.

--
Des
NowSMS Support
Andrew
New member
Username: Xserver1

Post Number: 5
Registered: 06-2010
Posted on Tuesday, June 29, 2010 - 10:06 am:   

I tried restriction the user to a particular SMSC . But it seems that the user is sending msg through the uplink SMPP which have "support any outbound traffic"

[SMSGW]
WebAuth=Yes
WebMenu=Yes
WebPort=8800
IPAddress=99.99.99.99
SMPPPort=9999
Modem1=SMPP - 111.111.111.111:111
Debug=Yes
AdminUser=admin
AdminPassword=admin
ReceiveSMS=No
ReceiveMMS=No
Modem2=SMPP - 123.123.123:123

[SMPP - 111.111.111.111:111]
SMPPVersion=v3.4
UserName=smpp1
Password=pwd1
SenderAddressOverride=Yes
Receive=Yes
ReceiveMMS=No
UseSSL=No
LongSMSAlt=Yes
WindowSize=20
RetryDelay=30
RetryDelayMultiplier=0
RetryDelayAfterAttempts=1
RetryMaxAttempts=1

[SMPP - 123.123.123.123:123]
SMPPVersion=v3.4
UserName=smpp2
Password=pwd2
SenderAddressOverride=Yes
Receive=Yes
ReceiveMMS=No
UseSSL=No
LongSMSAlt=Yes
WindowSize=20
RetryDelay=30
RetryDelayMultiplier=0
RetryDelayAfterAttempts=1
RetryMaxAttempts=1
AllowedUserOnly=Yes
AllowedUser1=user1;



user1 is in NowSMS user list but the messages are sent via SMPP - 111.111.111.111


Any Idea ?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2288
Registered: 08-2008
Posted on Tuesday, June 29, 2010 - 04:27 pm:   

Remove the ";" after user1.

If multiple users need to be specified, they are specified like this:

AllowedUser1=usera
AllowedUser2=userb
Andrew
New member
Username: Xserver1

Post Number: 6
Registered: 06-2010
Posted on Tuesday, June 29, 2010 - 09:06 pm:   

I tried without ";" but result is still the same.

Do i need to restrict all the SMPP connection and explicitly allow users to use the SMPP ?

What i mean to say is NowSMS logic looks for "Support Any Outbound Message Traffic" and then checks for the "AlloweduserOnly" or vice versa ?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2299
Registered: 08-2008
Posted on Tuesday, June 29, 2010 - 09:23 pm:   

Sorry Andrew,

I forgot how this setting works.

You're right the "AllowedUser" is evaluated secondary, after other routing logic is evaluated.

If other routes are do not have AllowedUserOnly=Yes, then an "AllowedUser" on one connection could also be routed via any unrestricted routes.

This is different from how the "preferred" recipient address masks work ... and different from the "sender" matching.

I was definitely wrong in suggesting these settings.

Unless you can apply AllowedUserOnly=Yes to the other connections, and list allowed users for those other connections, this will not work.

I need to go back and discuss this with some other members of our team. Maybe there is some other alternative that I am forgetting.

Or maybe we need to figure out how to add a new configuration setting to simply force a user to a particular route, without requiring all routes to have user restrictions.

--
Des
NowSMS Support