VG350 with PLAR - keep getting call backs after hang up
This is a VG350 that is MGCP registered to a CUCM 11.0
I understand what is going on, but not how to fix it. Essentially we have these emergency call boxes. Someone hits the button and the call box goes off-hook and hits a blank translation pattern we have set up to PLAR the call to an emergency call system. The system picks up and the call proceeds correctly. However, if the system end hangs up, leaving the call box still off-hook, the call-box side doesn't seem to transition into the on-hook state. It's like it quickly goes on-hook and then back off-hook or something because it hits the PLAR translation pattern again and calls back. This happens in a never-ending loop until we find a way to make the call box hang up first.
Is there some kind of setting to make the VG350 endpoints go back on-hook and stay on-hook as soon as the other end hangs up?
Can you paste the gateway configuration as it relates to the ports.
Also look at the debug mgcp packet if all else fails see exactly what is happening. Document above should help.
Hookflash might not be involved at all, and the phone just goes right off hook again after it receives a disconnect. I guess with FXS if off hook you will be receiving power and dial tone as long as if you are off hook.
I guess a work around would be to manually shut the port if someone thinks the call and is over and walks away, until someone else can get there. (Not ideal I know)
But in my opinion the non technical problem may be why are the people answer the security phone hanging up on the caller. (Accident?) In which case maybe having the plar calling back right away is not a bad thing in the event of a accidental hang up.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.