Second call on encrypted connection

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/OpenBSC@lists.osmocom.org/.

Andreas Eversberg andreas at eversberg.eu
Thu Jul 11 07:00:53 UTC 2013


Holger Hans Peter Freyther wrote:
> b.) If it can not happen, use LOGL_ERROR so we potentially notice
> if it does happen and then we can re-consider.
>   
hi holger,

the new patch will give an error message, if location updating is
received after CM service request, but it finishes location updating in
case of this unexpected behavior.

regards,

andreas

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0001-Fix-Handle-CM-service-request-on-already-secured-cha.patch
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20130711/52922996/attachment.ksh>


More information about the OpenBSC mailing list