Loop Current Disconnect

[voxabox]

Hi, Justin....

I dug out this ancient post as I believe the problem has returned.
Now with the PAP2 instead of the 502, what should the correct setting be and where is it in the PAP2?

My memory fades quickly, but for a long while with the PAP2, I don't recall hearing the fast busy recording on my answer machine. I don't use the system VM. It seems to have returned the last few days, but I can't swear to it..

Thanks...

burris

burris,
IIRC, on the linksys/sipura ATAs the params are 'CPC Delay' and 'CPC Duration'

[burris]

Thanks...

I'll take a look and try some different numbers..

[fisamo]

The relevant number for you should be CPC duration. As previously, I recommend 500 - 750 ms. With settings in that range, you'll probably get the disconnect then reorder tone (or "if you'd like to make a call, please hang up and dial again" type recording, but more likely reorder).

If you set for 1000 ms or longer, it should work as well, but instead of reorder or recording, you might actually get a fresh dialtone.

[burris]

The PAP2 CPC duration comes provisioned from support with a value of "0" and a CPC delay of "2"

Maybe this is the reason?

[burris]

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!

I dug up this old thread as it is still happening when I use the PAP2...I don't recall it doing this when I use the SPA2102 and the 502 is history..

I'm provisioned at the moment and these are the settings....
CPC Delay:2
Interdigit Long Timer:10

If you have the fix, please hard code it for me. If not and you want me to try some other timings, I will be happy to do so.

Thanks....

burris

[mdlawler]

I believe setting CPC duration to 1 will solve this.

[burris]

I believe setting CPC duration to 1 will solve this.

I just reset it to 1 and it seems to have solved the problem.
If I decide to turn on provisioning again, I'll have to remember to put in a ticket to have support hard code it for me..

Thanks for your help..