Assigned
Status Update
Comments
an...@google.com <an...@google.com>
yu...@google.com <yu...@google.com>
an...@google.com <an...@google.com>
be...@google.com <be...@google.com>
sh...@google.com <sh...@google.com> #2
Thanks for your suggestion! We are currently evaluating this request, but do not have any plans to implement it at the moment. Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.
as...@gmail.com <as...@gmail.com> #3
I've transitioned from this team. Thanks!
as...@gmail.com <as...@gmail.com> #4
Please let me know if you need any other information.
sh...@google.com <sh...@google.com> #5
Thanks for your post.
The engineering team will look into the issue and explore if there are feasible ways to resolve it as soon as possible.
We will let you know as soon as additional updates are made available.
The engineering team will look into the issue and explore if there are feasible ways to resolve it as soon as possible.
We will let you know as soon as additional updates are made available.
as...@gmail.com <as...@gmail.com> #6
Hi,
Its been almost 6 months ago... do you have any update?
Its been almost 6 months ago... do you have any update?
as...@gmail.com <as...@gmail.com> #7
Hi,
Any updates? almost a year???
Any updates? almost a year???
ma...@gmail.com <ma...@gmail.com>
th...@gmail.com <th...@gmail.com> #8
We need this feature too. Sometimes we get only 16bit CID without RNC-ID because in the core network no information about RNC-ID
Description
In Combain DB it exists ("w4f" fallback).