MMS PreAuth Transaction ID

MMS PreAuth Transaction ID SearchSearch
Author Message
Kumara
New member
Username: Dial12345

Post Number: 3
Registered: 07-2009
Posted on Monday, July 13, 2009 - 09:27 am:   

Hi,

1. I have some issues regarding MMS accounting callbacks.
according to the description in given documents, there is no transaction id is sent with PreAuth request.
So if multiple PreAuth requests sent by MMSC , when replies received , how the replies are differenciated ?

2. What is the maximum number of users can be provisined in NOW SMS MMS GW ?


thanks,
Kumara.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1037
Registered: 08-2008
Posted on Monday, July 13, 2009 - 10:43 pm:   

Hi Kumara,

1. That is correct, there is no way to correlate a PreAuth request with the actual MMSSend accounting callback.

The PreAuth is not a reservation.

99.9% of the time, the MMSSend accounting callback will be followed by an MMSSend callback.

An MMS client on a mobile phone does not open simultaneous connections, so for a phone client, if you see another PreAuth, then the previous send was not accepted for some reason.

It's best to think of the PreAuth as a credit check (or recipient validity check in some environments). But not as a reservation.

2. We don't impose a limit. The local user accounts go into an SQLite database which is quite efficient. Early versions of the MMSC used to run into performance problems adding new users when you got above a few hundred thousand users, but since changing to the new format a few years ago, we haven't seen any performance issues with large numbers of provisioned users.

--
Des
NowSMS Support
Kumara
New member
Username: Dial12345

Post Number: 4
Registered: 07-2009
Posted on Tuesday, July 14, 2009 - 01:44 pm:   

hello Des,

I still have some queries regarding Accounting callbacks. Please consider the following scenario.
1. A sends a message to B & the same time X sends a message to Y but X does not have enough credit in his account.
2. PreAuth callbacks are sent for both messages 3. In reply , "OK" received for A & "PreAuth=Deny" received for X . but how MMSC distinguish to which message received OK & to which received Deny ?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1039
Registered: 08-2008
Posted on Tuesday, July 14, 2009 - 03:01 pm:   

Hi Kumara,

I understand your concern better now.

Each accounting callback is a synchronous HTTP transaction. (HTTP is synchronous by design.)

NowSMS sends the HTTP GET request and waits for a response.

If multiple requests are received at exactly the same time, additional HTTP connections are created.

Keep-alive sockets are used to minimise the number of connections created (once a response is received on a connection that connection is available for another request to re-use).

The important thing to realise is that there may be more than one instance of your accounting callback active at the same time. (And on busy systems, this is extremely likely.)

--
Des
NowSMS Support
Kumara
New member
Username: Dial12345

Post Number: 5
Registered: 07-2009
Posted on Wednesday, July 15, 2009 - 02:58 pm:   

hello Des,

Why MMS GW does not send a unique ID for each transaction ?
If the application sends a unique ID & expects the response with same ID it would be easier to do the charging & logging each event.

thanks,
Kumara.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1048
Registered: 08-2008
Posted on Wednesday, July 15, 2009 - 06:16 pm:   

Hi Kumara,

It's just the way that we implemented it. These accounting callbacks were based upon the ones that we first designed on the SMS side of the product.

On the SMS side, if a message is addressed to multiple recipients, we do one "PreAuth" callback ... but as the message is processed, a separate message ID will be generated for each recipient.

MMS works differently, in that the same Message ID can be shared by each recipient instance.

But, we implemented the callback the same way.

The "PreAuth" callback is generated before any processing is performed against the message, and a message ID has not been assigned yet (and will never be assigned if the "PreAuth" callback rejects the message).

--
Des
NowSMS Support