-A query was raised by the respected customer when and EARFCN 42330 was observed in our test &

we anticipated it as
other operators EARFCN which was due to the fact that this EARFCN was not available in the provided data base. In the
next email it was confirmed the EARFCN for MTNi and used in R7 for LTE-TDD so, we started following and asked you
when another new EARFCN was observed in an other test in the next slide.
We generated a proper email before furnishing the report to confirm that his EARFCN 41690 belongs to MTN or not to
avoid any confusion, which means that we are following the customer step by step.
A query was raised for the PS-Throughput snapshot, but before the convention was different as we are quite conscious to
never add any thing from our side but to follow the customer step by step, also this was a previous report for which we
were not asked to do so. Once the DT guys leaves the location sending him again become impossible for us because of a
tight plan.
After it was asked to include the analysis we did it for each and every report onwards with proper
recommendations and this was also not asked before to do the analysis.
It was again an issue of the data base where we could not find any PCI-123 to locate it and show it on the plot.
Also if we are using two EARFCN we will definitely get two of them some times as we are not suppose to lock any
of them.