This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Harald Welte gerrit-no-reply at lists.osmocom.orgHarald Welte has posted comments on this change. ( https://gerrit.osmocom.org/12599 ) Change subject: Don't send Alert Notifications to ESME not bound for RX ...................................................................... Patch Set 2: Why is that? I would argue there are many applications where you may want to transmit a SMS from ESME to the MS in response to an activity report. In that case, IIRC, the ESME would only be bound for TX but still want notifications? Basically, I think to avoid constraining use cases we should send notifications to any ESME that is bound to any of RX/TX/TRX. -- To view, visit https://gerrit.osmocom.org/12599 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-msc Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Iec92d4c145ca050c2e212139572eeaae581b99df Gerrit-Change-Number: 12599 Gerrit-PatchSet: 2 Gerrit-Owner: Keith Whyte <keith at rhizomatica.org> Gerrit-Reviewer: Jenkins Builder (1000002) Gerrit-CC: Harald Welte <laforge at gnumonks.org> Gerrit-Comment-Date: Thu, 17 Jan 2019 12:23:24 +0000 Gerrit-HasComments: No Gerrit-HasLabels: No -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20190117/68b7fc9c/attachment.htm>