Load balancing / HA?

[Antony Stone]

Hi.

I'm currently using kannel as my SMSC gateway, on two servers, with a shared
MySQL database, so that if one kannel instance sends out an MT SMS, and the
delivery notification report comes in to the other kannel instance, the message
ID can be matched up and we can pass the notification on to the correct
originating user.

I'm not very impressed with the maintenance or support for kannel, so I'm
looking around for a better SMSC gateway.

My question is: can Jasmin also do this, to match inbound / outbound messages
between two instances running on different servers?


Thanks,


Antony.

--
Numerous psychological studies over the years have demonstrated that the
majority of people genuinely believe they are not like the majority of people.

Please reply to the list;
please *don't* CC me.

[Bruno C]

I'm not sure if i understood your requirement, but you can multiple instances on same redis/rabbit server, this way you'll have shared ids, not tested eventually ...

[Luca Maghini]

Interesting question,

I suppose that both server connects in transceiver mode to the same upstream provider (with the same credential), isn't it?

In the opposite case all messages sent from server A wil be "DLRed" to A and B cannot receive any "unmappable" DLR... and vice versa.

Jasmin use Redis for that purpose so I suppose that different installations may share the redis DB just configuring the same redis server and db number on every node.

But I never tried it, let's wait answer from project mantainer or someone that tried this configuration.

[Antony Stone]

On Friday 23 October 2020 at 21:39:14, Luca Maghini wrote:

> Interesting question,
> I suppose that both server connects in transceiver mode to the same
> upstream provider (with the same credential), isn't it?

Right.

> In the opposite case all messages sent from server A wil be "DLRed" to A
> and B cannot receive any "unmappable" DLR... and vice versa.

Exactly.

> Jasmin use Redis for that purpose so I *suppose* that different

> installations may share the redis DB just configuring the same redis server
> and db number on every node.

Unfortunately, what I'm deliberately setting up is a High Availability system
(which just happens also to be load-balanced), and therefore any Single Point
of Failure is not an option.

To the best of my knowledge, redis cannot be clustered across multiple
machines (someone please correct me if I'm wrong), so each Jasmin server
pointing at a single redis server does not meet requirements.

> But I never tried it, let's wait answer from project mantainer or someone
> that tried this configuration.

Yes, I thought it would not be an unusual requirement, but so far this is only
the second response I've had in 6 weeks, neither of which were examples of
known-working solutions :(

I must admit I'm surprised and disappointed by the very low level of postings
on this list - am I missing out on some other Jasmin support forum where most
of the users and developers discuss things, or is it simply that not many
people use and talk about Jasmin?


Antony.

--
Archaeologists have found a previously-unknown dinosaur which seems to have
had a very large vocabulary. They've named it The Saurus.

[Luca Maghini]

Redis can be clustered for HA and/or performance purpose.

https://redis.io/topics/cluster-spec

This group was blocked from google until some weeks ago so people get used to crete a github issue (improperly) to ask anything.

Anyway there isn't so much people talking about jasmin for what I observed in the lasty year also there.

All people wait that the project mantainers do the magic and few people try to contribute, even using the group or suggesting solutions.

[Rasto Rickardt]

Hello,

not maintainer, just a user.

On redundancy - we are using 2 separate instances of Jasmin (redis,
rabbit, jasmin daemons) in front of 2 SMS centers.

Both SMPP & HTTP frontends are behind HAProxy loadbalancer, this is
frontend for users.

Master redis can have multiple replicas, but it might not solve your
failure mode.

On the other side, everything is RabbitMQ based, so you can setup your
own custom consumer and feed selected queue to database. That way you
can have application-level driven DB replicas.

Hope that helps,

Kind Regards

r.

On 23/10/2020 21:39, Luca Maghini wrote:
> Interesting question,
> I suppose that both server connects in transceiver mode to the same
> upstream provider (with the same credential), isn't it?
> In the opposite case all messages sent from server A wil be "DLRed" to A
> and B cannot receive any "unmappable" DLR... and vice versa.
>

> Jasmin use Redis for that purpose so I _suppose_ that different

> --
> Jasmin SMS Gateway -- http://jasminsms.com
> Commercial support:
> https://jasminsms.atlassian.net/servicedesk/customer/portal/1
> ---
> You received this message because you are subscribed to the Google
> Groups "Jasmin SMS Gateway" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jasmin-sms-gate...@googlegroups.com
> <mailto:jasmin-sms-gate...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/jasmin-sms-gateway/40a001c1-586c-4913-9661-89747cdb272an%40googlegroups.com
> <https://groups.google.com/d/msgid/jasmin-sms-gateway/40a001c1-586c-4913-9661-89747cdb272an%40googlegroups.com?utm_medium=email&utm_source=footer>.