Stats with more then one SMSC connection

Stats with more then one SMSC connection SearchSearch
Author Message
Anonymous
 
Posted on Monday, January 17, 2005 - 08:47 am:   

Is it posible to see in the stats, to get stats for how many messages each user is sending via each SMSC connection.

E.g. you have a connection for some different coutries, you set it up to sort on the countrycode, because there is different prices on them. I need to see how many each user sends to each country.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3899
Registered: 10-2002
Posted on Monday, January 17, 2005 - 09:06 pm:   

Unfortunately, there are no easy to access stats to tell you this.

There is an SMS-yyyymmdd.LOG file in USERS\accountname.

For each message that a user account submits, there is an SMSSubmit log entry. Here you will see the phone number that they are sending the message to, and there will be a message id that looks like this:

xxxxxxxx.req

or

sar-xxxxxxxxxxx-xx-xx-xx.req

It is possible to correlate that ID with an idea from the SMSOUT-yyyymmdd.LOG files, which will tell you which SMSC a message was ultimately routed via.

So it's possible, but hard to do after the fact.

What most people do is make use of the "accounting callbacks", described at http://www.nowsms.com/support/bulletins/tb-nowsms-001.htm.

What they do is that they keep track of their own accounting statistics based upon these callbacks instead of relying on the stats that NowSMS produces directly.

-bn
rtoustrup
Unregistered guest
Posted on Tuesday, January 18, 2005 - 12:09 pm:   

Can those acconting callback be feeded into a system, so that you can get some stats easyer to get a komplet picture of the sends ?.

rtoustrup
Unregistered guest
Posted on Tuesday, January 18, 2005 - 03:38 pm:   

I have found how the SMSout log is build, which information is where and so, but how is the SMSSubmit logs build.

Correlate the ID, and taking User from SMSSubmit and
SMSC name from SMSOut. Should be posible to make an app to do this.

Regarding the Callback, can you give me a example of such a sting, they need to contain the 2 infos SMSC and User name.

Thanks...
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3949
Registered: 10-2002
Posted on Thursday, January 20, 2005 - 10:31 pm:   

As I think about it more, the callbacks do not directly address your concern, so they might not be of benefit to you.

The callback tells you when a message is submitted and when it is accepted for delivery. But currently, it does not tell you when a message is actually routed externally ... so it does not tell you which SMSC receives the message.

What you can do with the callback is perform your own analysis of the recipient address, and where you know it will be routed. But unfortunately, the callback doesn't tell you this.

The URL for the callback is configurable, but basically you'd end up getting callbacks like this:

pre-auth:

http://x.x.x.x/path?PreAuth=Yes&Type=SMSSend&From=test&MsgCount=1

On acceptance by NowSMS:

http://x.x.x.x/?Type=SMSSend&From=test&To=xxxxxxxxx&MessageID=xxxxxxxx.req