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/12602 ) Change subject: Don't deliver alert notification to ESME not bound for RX ...................................................................... Patch Set 1: (1 comment) https://gerrit.osmocom.org/#/c/12602/1//COMMIT_MSG Commit Message: https://gerrit.osmocom.org/#/c/12602/1//COMMIT_MSG@7 PS1, Line 7: bound for RX 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/12602 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: openbsc Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I0e5d55d3fb6ac46d253902df2fe304e1b0fc8bbf Gerrit-Change-Number: 12602 Gerrit-PatchSet: 1 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:12 +0000 Gerrit-HasComments: Yes Gerrit-HasLabels: No -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20190117/1bd494fa/attachment.htm>