| Author |
Message |
Alan Wright
New member
Username: Alanw
Post Number: 1
Registered: 10-2007
| | Posted on Wednesday, October 24, 2007 - 09:44 am: | |
Hi Folks,
Can more than one MMSC be active?
If yes, then how do i share the database between the machines, to ensure that if a failure occurs, the other active server can take over a transaction?
Also, do I need to ensure that an MMSC must process all transactions for the MMS message flow from start to end?
Thanks |
Malcolm - Now Support
Moderator
Username: Malcolm
Post Number: 258
Registered: 12-2006
| | Posted on Wednesday, October 24, 2007 - 01:55 pm: | |
Hi Alan,
For full redundancy, you can use a server mirroring product like Marathon.
There are other alternatives for load balancing, but there are some limitations and issues.
One common configuration is a load-balanced solution. Each MMSC has both a unique local host name/address ... and a shared name/address through a load balancer.
When an MMS client sends a message, it could get directed by the load balancer to any of the MMSCs. The MMSC that processes the message sends an MMS notification out that resolves to that MMSC's unique host name/address instead of the shared identity.
In this configuration, the MMSCs operate independently. They do not know about each other ... they do not have any shared message store or database.
The limitation of this configuration is the MMSC user database is different on each MMSC. This causes a problem if the "MMSC Users" list is auto-provisioned and being used for MMS message routing. (A user that is in the "MMSC Users" list will always receive MMS messages via direct delivery.)
We are currently working on a solution that will allow multiple MMSCs to automatically synchronise their user databases in a load balanced configuration. It is supposed to be ready by the end of this year.
If you are interested more in redundancy, it is possible to use coniguration parameters to point the servers to common data stores. See http://www.nowsms.com/discus/messages/485/17220.html. Specifically the DataDir setting specifies where the MMSC message files reside, the VASPQDir setting specifies where the outbound MMSC routing queue resides, and the QDir setting specifies where the outbound SMS message queue resides. With these settings pointing to shared volumes, more than one MMSC can be working with the same message store.
However, there is still the problem with the "MMSC Users" database not being possible to share between multiple MMSCs. This is currently a high priority development item that we hope to have news about very soon.
-malcolm |
Alan Wright
New member
Username: Alanw
Post Number: 2
Registered: 10-2007
| | Posted on Friday, October 26, 2007 - 05:30 am: | |
Hi Malcolm,
You mention this
The limitation of this configuration is the MMSC user database is different on each MMSC. This causes a problem if the "MMSC Users" list is auto-provisioned and being used for MMS message routing. (A user that is in the "MMSC Users" list will always receive MMS messages via direct delivery.)
Could you please elaborate what you mean exactly? Give a MMS flow for example where user1 goes to MMSC1 and user 2 goes to MMSC2. |
|
Search
Last
