Few days ago I asked the question below:
I appreciate the quick respond from Dave but I have received no further follow up so I conducted my own test over the past week end and figured out that the Disconnect Tone detection of SPA3102 firmware 5.1.10(GW) is completely broken.
I have changing the parameters below around and tested every possible combinations and the result is still failed:
PSTN Disconnect Detection
Detect CPC: yes & no
Detect Polarity Reversal: yes & no
Min CPC Duration: 0.09, 0.1, 0.2, 0.3, 0.4, 0.5
Detect Disconnect Tone: yes
Disconnect Tone: 480@-10 to -30,620@-10 to -30;2(.5/.5/1+2)
then I use the softphone to record the disconnect tone into a .wav file and use Audacity to analyze the spectrum and confirmed the 2 frequencies peak of the PSTN Disconnect Tone from my PSTN side are in fact 468Hz and 615Hz, they're only 2.5% and 0.8%, respectively, off the defined frequencies in the ToneScript and should be well within tolerance of detection. I really don't know why the SPA3102 cannot detect it correctly.
I was about to give up but Google again and found someone mentioned the Disconnect Tone detection to a PBX box can only be fixed by downgrade the SPA3102 firmware. I have 3.3.6(GW) and 5.1.7(GW) on hand and I am not connected to a PBX but anyway I give it a try...
Bingo! I hit the Jackpot!
Now I use:
Disconnect Tone: 480@-19,620@-19;2(.5/.5/1+2)
and restored all the above parameters to their default values. SPA3102 can detect the disconnection instantly without any delay after the firmware downgrade. Tried both version all works.
Cisco people, may I have your attention to report this to your engineering team and look into this problem of the current firmware?