Comment # 9
on bug 8165
from Geoff Hart
Hi,
I believe the fields are identical, so for this specific instance treating them
the same would be safe. If we code a general patch to ignore case, this does
not guarantee that any other cases would also be safe though.
In the S1AP protocol, all messages except a Release Request from MME->eNB use
one or both of MME-UE-S1AP-ID and ENB-UE-S1AP-ID individually. In a Release
Request from MME->eNB specifically, it uses this data structure instead of the
two individual values. I'm not really sure why this exception exists, but the
values are the same. I can't think of any reason someone would filter on this
in & out of a data structure because in this specific instance, it's conveying
the same information.
In 'Sample capture showing issue', apply filter 's1ap.ENB_UE_S1AP_ID ==
1718662' and 's1ap.eNB_UE_S1AP_ID == 1718662' to see what's going on.
Geoff
You are receiving this mail because:
- You are watching all bug changes.