The 8 series fiasco for Indian Telecom Operators

Well its was well known that mobile numbers with 8 are going to start soon. But it so happened that my dear friend Daaku took a new Tata Docomo connection. Now the amazing thing was that it starts with 805xx-xxxxx. So now if I try to call this friend of mine, my Vodafone network tells me that its an invalid number. I was confused and so I asked my friend daaku to call me. I got his number in caller ID but calling it was again not possible. Obviously its not mistake in dialing the number, rather its a stupid things that Vodafone and possibly other networks too have done.

So here is my guess what has happened. Vodafone, takes the number +91805xx-xxxxx as 91 for country(that India), 80(Code for Bangalore) and 5 would be Tata Indicom as they provide landline with that series. Interestingly Vodafone seems to have not configured its network to this change which happened for mobile numbers starting with 8.

I tried contacting Vodafone customer care, they seemed to be unaware of the issue and they said they would get back to me soon(24hours it seems).

But the point here is, whats TRAI and DoT doing. Have they not informed the operators of this change or are the operators at lax. Who ever it might be, the fault must be found and it must be ensured that in future such stupid things do not happen.

Comments

Post a Comment

Popular posts from this blog

[24th November 2024] Interesting Things I Learnt This Week

Image
1. AI Makes Tech Debt More Expensive - The core argument is that generative AI significantly widens the gap between codebases with low and high tech debt. Companies with clean code can leverage generative AI to write code much faster, while companies with messy legacy codebases struggle to adopt these new tools. This widens the gap between the two codebases, making tech debt even more expensive for companies with outdated systems. My Take : Legacy systems inevitably accumulate technical debt. A common analogy for this is the state of urinals over time: missed targets lead to increasing mess, keeps pushing people away from urinals and leading to more mess in turn. AI-powered coding tools could potentially accelerate the accumulation of tech debt. However, skilled engineers can leverage AI to reduce and even eliminate it. Ultimately, AI is just a tool, and human judgment remains crucial for making informed decisions. I hope AI will be used responsibly to drive positive outcomes. 2. Make...
Read more

[17th November 2024] Interesting Things I Learnt This Week

Image
 1. Booleans are a trap : Booleans, while seemingly simple, can introduce complexity and limitations into domain modeling. When used to represent complex states, booleans can lead to unclear code and potential errors. To avoid these pitfalls, consider using enums or enum sets. These approaches provide a more expressive and maintainable way to model complex states in your applications. My Take : I wish I had learned this earlier in life. When working with Google Docs, I realized the limitations of booleans. Expanding boolean-based behaviors often led to adding more fields, making the system complex. Enums would have provided a simpler solution. The problem wasn't just the booleans themselves, but also the need to pass them through multiple layers of the stack, often requiring additional parameters. Another important aspect of enums is the inclusion of an " enum not specified " state. This state explicitly indicates that an enum value hasn't been set, which can be usef...
Read more

[1st December 2024] Interesting Things I Learnt This Week

Image
1. C++ Pitfalls - this article, explains some of the pitfalls you can fall into when programming in C++ and shares their experience with them. This includes Operator precedence, Arithmetic conversion rules, Right bit-shift, Implicit conversions and Order of evaluation.  My Take : We've all read about JavaScript's quirks, leading to unexpected outputs. But let's remember that such behaviors aren't unique to JavaScript. Even languages like C and C++ have their share of ambiguities and compiler-specific behaviors. While it's tempting to dive deep into these intricacies, I've found that focusing on clear, consistent, and unambiguous code is often more practical. However, understanding these nuances is essential for any experienced programmer. It helps us avoid pitfalls and write robust, reliable code. Remember, mastering a language isn't just about writing "Hello World." It involves delving into its intricacies, including its counterintuitive and ambi...
Read more