09-28-2012 10:00 AM - edited 03-16-2019 01:26 PM
Hello,
I know the Valcome V-9970 seems to be a topic of conversation here and I've skimmed the other posts but can't quite put all the pieces together for a true solution. Short story I have a Valcom V-9970 hanging off an FXS port on a VG224 and randomly the port will get stuck in off-hook. So you either have to bounce the Valcom or the VG and then life goes back to normal. Is this because we have the Valcom set for silence detection vs the absolute cut off? Or is it a port level issue on the VG?
Currently the Valcom is set as such:
Silence Time enable
Disconnect on Dial Tone enable
4 seconds time out for silence
Loop detect enable
The VG port is configured as such:
voice-port 2/23
output attenuation -6
timeouts initial 60
timeouts interdigit 60
timeouts ringing infinity
Thank you in advance.
09-28-2012 01:01 PM
Hi,
Can you try adding this line of cli
!
voice-port 2/23
supervisory disconnect lcfo
!
Regards,
Alex.
Please rate useful posts.
09-28-2012 01:03 PM
Should be able to test this out first thing Monday. And that is what I was wondering about as well if the supervisory disconnect was the answer.
Thanks.
09-25-2015 09:49 AM
Hi tpfrankli
I am facing the same issue. Is that issue resoved?
I have connected the vogan paging V9970 with vg224 using RJ11 cable. It is reaching the Paging but not hear any thing in the paging speaker.
Below are the configurations
voice-port 2/8
timeouts initial 120
timeouts interdigit 60
timeouts call-disconnect infinity
timeouts ringing infinity
timeouts wait-release infinity
timeouts power-denial 2500
caller-id enable
Kindly send me the configuration that you did.
Thanks.
10-03-2012 11:13 AM
Well I gave it ago. Interestingly enough I'm wondering if supervisory disconnect lcfo is a default setting as it does not show in the IOS port configuration. And it appears to not have resolved the issue either as less than an hour later the site called complaining of the same issue. Upon investigating you could see the FXS port was stuck off-hook idle. A shut / no shut of the port restored functionality.
This VG224 is MGCP controlled and running IOS vg224-i6k9s-mz.124-24.T3.bin. I'm wondering if moving to 12.4(24)T8 might resolve some of the problems.
Thoughts?
Thanks.
10-04-2012 05:05 AM
Hi,
The only other suggestion I can make is that you set your port/dial peer to
produce dial tone on the remote on hook condition.
You have to configure this on the dial peer
http://www.cisco.com/en/US/docs/ios/voice/fxs/configuration/guide/fxsbasic.html#wp1019753
Lets say that port 23 is using dial peer 23
!
dial-peer voice 23 pots
tone dialtone remote-onhook
!
It worth a try.
Regards,
Alex.
Please rate useful posts.
10-04-2012 05:24 AM
acampbell wrote:
Hi,
The only other suggestion I can make is that you set your port/dial peer to
produce dial tone on the remote on hook condition.You have to configure this on the dial peer
http://www.cisco.com/en/US/docs/ios/voice/fxs/configuration/guide/fxsbasic.html#wp1019753Lets say that port 23 is using dial peer 23
!
dial-peer voice 23 pots
tone dialtone remote-onhook
!It worth a try.
I believe it could hep with an H.323 setting, unfortunatly OP is using MGCP.
10-10-2012 09:08 PM
That is the sucky part about FXS, supervisory disconnect blows. Use an FXO. I usually use a bogen tamb2 with the power adapter.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide