|NowSMS MMSC in A2P mode||Search|
|SMS & MMS Technical Forum » MMS & SMS Technical Discussions (unsupported) » NowSMS MMSC in A2P mode||« Previous || Next »|
Post Number: 1
Is there any deployment of NowSMS MMSC in A2P mode? Does it support A2P mode? Can you please give me a rough idea of the throughput achieved by NowSMS MMSC in A2P mode. What type of hardware is required to achieve this throughput?
|Des - NowSMS Support
Post Number: 1767
Throughput varies extensively depending on your outbound MMS connection.
Is NowSMS configured as a direct delivery MMSC? Or is it routing messages to an operator MMSC using MM1, EAIF, MM7?
Earlier versions of NowSMS were not as robust with external EAIF or MM7 connections, but in recent years that code has all been optimised to make use of keep-alive sockets and multiple concurrent connections.
I'm sorry that I'm not giving you a very clear answer, but there are wide discrepancies in performance expectations depending on what your external MMS delivery path is.
If NowSMS is functioning as a direct delivery MMSC, then the limiting factor is usually the outbound SMS transmission speed. (In most configurations, each MMS recipient for a message results in 2 SMS messages that need to be sent out.)
In MM1 configurations, the modem speed is a limiting factor. You can, of course, use multiple modems ... but to estimate throughput, you also have to know the average size of messages being sent.
In MM7 configurations, it can depend on whether or not your provider supports multiple concurrent connections (and how many), as well as what speed limits they have imposed on your account.
If you can provide some more detail on your outbound MMS delivery path, as well as the types of content sending scenarios you are expecting, then we can probably come up with more meaningful rough estimates.
|Naresh chandra das
Post Number: 1