Hey guys,Recently I have shifted to freedom one second planAs a matter of testI made test calls of 10 Seconds each (10 X 10 Calls) to airtel numberEverytime the deduction was more than 10 Paisa for Eg. some times it was 11 or 11. something.Even I checked my call log it said 10 Seconds callIs there is anything problem with my set or should i raise a query with airtel.
-
Amazon Deals - ToS - Like us?
Problem with Airtel One Second plan
- Thread starter mastbhai
- Start date
- Replies 13
- Views 4,205
mehrotra.akash
Regular
TRAI allows an error of 1 sec for call duration measurements
I made test calls of 10 Seconds each (10 X 10 Calls) to airtel number
Everytime the deduction was more than 10 Paisa for Eg. some times it was 11 or 11. something.
Even I checked my call log it said 10 Seconds call
if u dial a number.. the person picks and disconnect the call.. does it show as 0 second call or 1 second call?? If i am not wrong Nokia shows 1 second after the second is over i.e if it's a 10.1 seconds call (technically 11th second running) then also it would be shown as a 10 second call in the log.
maybe u should try a 20 and a 30 second call if still 21 and 31 paise get deducted then i think this logic works.
Everytime the deduction was more than 10 Paisa for Eg. some times it was 11 or 11. something.
Even I checked my call log it said 10 Seconds call
if u dial a number.. the person picks and disconnect the call.. does it show as 0 second call or 1 second call?? If i am not wrong Nokia shows 1 second after the second is over i.e if it's a 10.1 seconds call (technically 11th second running) then also it would be shown as a 10 second call in the log.
maybe u should try a 20 and a 30 second call if still 21 and 31 paise get deducted then i think this logic works.
mehrotra.akash
Regular
if u dial a number.. the person picks and disconnect the call.. does it show as 0 second call or 1 second call?? If i am not wrong Nokia shows 1 second after the second is over i.e if it's a 10.1 seconds call (technically 11th second running) then also it would be shown as a 10 second call in the log.
maybe u should try a 20 and a 30 second call if still 21 and 31 paise get deducted then i think this logic works.
u r correct on that..
what happens is that if the cell says that duration is 20sec, actually 20sec have been completed and 21 sec is going on
like, if u say tht ur age is 18yrs, u may actually be 18yrs and 1 day old or 18 yr and 300 days old, but its still said as 18 yrs(as the least count would be taken as years, if it was taken as months or days , a similar example would apply)
similarly, the 1 second least count was OK for a 1 min pulse and even for 10 min pulse, as an error would occur at every 60 or 600 seconds and an error of upto 1 sec in 60 or more seconds is acceptable
the same is not valid with a 1 sec pulse, and what is needed is a least count in ms so that there is accuracy in the counting of seconds.
however, as the losses of the per second error are small, and the cost of implementing the ms accuracy will be high, it is better that it not be implemented as that would cause rate increases.
maybe u should try a 20 and a 30 second call if still 21 and 31 paise get deducted then i think this logic works.
u r correct on that..
what happens is that if the cell says that duration is 20sec, actually 20sec have been completed and 21 sec is going on
like, if u say tht ur age is 18yrs, u may actually be 18yrs and 1 day old or 18 yr and 300 days old, but its still said as 18 yrs(as the least count would be taken as years, if it was taken as months or days , a similar example would apply)
similarly, the 1 second least count was OK for a 1 min pulse and even for 10 min pulse, as an error would occur at every 60 or 600 seconds and an error of upto 1 sec in 60 or more seconds is acceptable
the same is not valid with a 1 sec pulse, and what is needed is a least count in ms so that there is accuracy in the counting of seconds.
however, as the losses of the per second error are small, and the cost of implementing the ms accuracy will be high, it is better that it not be implemented as that would cause rate increases.
rohitrohan
Regular
Agree with all of you...
Pay per Second is a New Scheme but remember if u had Disconnected any call earlier at 59 Seconds u were charged for the another minute..
It takes time to Disconnect fully from the Network too, say 1 or Fraction of a Second
The Call usually jumps a Second and using A CDMA phone is more Irritating..
It starts counting the minute it starts ringing :impissed:
Pay per Second is a New Scheme but remember if u had Disconnected any call earlier at 59 Seconds u were charged for the another minute..
It takes time to Disconnect fully from the Network too, say 1 or Fraction of a Second
The Call usually jumps a Second and using A CDMA phone is more Irritating..
It starts counting the minute it starts ringing :impissed:
mehrotra.akash
Regular
so if we dont answer the call but caller is ringing
the caller will be charged?
NO, the phone counter does start, but not the charge counter on the operator side, i.e. ur call log will contain inaccurate data, but charges will still be OK
the caller will be charged?
NO, the phone counter does start, but not the charge counter on the operator side, i.e. ur call log will contain inaccurate data, but charges will still be OK
mehrotra.akash
Regular
i thought gsm phones logged call durations properly?
they do but may have an error of 1sec, as the least count is 1sec
they do but may have an error of 1sec, as the least count is 1sec