Friends,
Sharing an observation regarding MTNL triband :
During installation, the username (phone number)
and password (CA number per phone bill) are
supplied into the router and "saved" therein.
Whenever switched on thereafter, the router
must be automatically supplying the "saved"
username and password to authenticate into
the MTNL exchange/infra.
The user is thus absolved of the need to submit
username and password each time it is powered on.
I use MTNL triband at home and at office.
The MTNL exchanges are 2557xxxx
and 2548xxxx respectively.
A few weeks ago, my office connection stopped working.
>From the symptoms and some investigations, I suspected
the MTNL/Dlink502/ADSL router in the office is misbehaving.
To confirm my doubts,
I took the router from home to office;
disconnected the suspect office router;
reconnected the home router in the office;
connection was working fine !
I logged my complaint on their helpdesk
(dial 1504 from an MTNL line).
followed up with the local MTNL office,
and obtained a replacment for the defective
MTNL ADSL router.
Food for thought:
----------------
>From my test of swapping my home and office
routers with NIL change to username/password
(i.e. used my home router as-is in the office),
it appears to me that :
the MTNL exchange/infra is not verifying username
submitted by router against the telecom network's
caller-id mechanism.
Vulnerablity to misuse apart,
I guess the upside is that we now probably
have a "roaming" (tri)band(width)
Any guesses on "by design" or "by accident" ?
---
vkb