Loop Current Disconnect

[voxabox]

We've pushed out a small change in the HT502 default provisioning, enabling the 'Loop Current Disconnect' feature with a current disconnect duration of 200 milliseconds.

Essentially, all this does is cut the 'fast busy' signal you'd get when still on the phone after someone disconnects. This is probably most noticeable when you have an answering machine in usage instead of your voice mail, the caller hangs up, and your answering machine is left recording a long and annoying fast busy!

FWIW,
I;ve been experimenting with the settings...
while setting the current disconnect duration to the min. value (100ms) does not completely solve my problem with the answering machine recording the fast busy tone (ticket #BLE-267247), it helps keep it short(er)

I wish GS

1. let us specify a shorter value for the setting
2. provided a setting that allows delaying emitting of fast busy (upon loop disconnection)

Cheers,
-v

[VOIPoJustin]

What happens exactly? Your answering machine picks up even before that 100ms duration is over?

[voxabox]

What happens exactly? Your answering machine picks up even before that 100ms duration is over?

VOIPoJustin, take a look at the ticket(BLE-267247)
even with "Loop Current Disconnect" enabled and "Current disconnect duration" of 200,
the answering machine is still able to record the fast busy tone (just a little bit shorter) after the caller hangs up
perhaps I can try a longer duration for "Current disconnect duration" - I;ve not tried anything longer than 200 ms

[fisamo]

I'd recommend going longer. The answering machine 'hangs up' when it detects the loop disconnect, and a longer disconnect would be easier to detect. FWIW, choosing something like 1 second is closer to a 'hook flash'; when I've played with the feature on my PAP, I found 500 - 750ms to work well.