[cisco-voip] Call length on paging ports

[Ben Amick]

Call me crazy, but wouldn’t someone in the plant hear that they put the paging system on hold and fix it by picking the call back up? Ryan’s suggest would belay it, but user training would also be a good mention.

A secondary measure is to look at what you’re hooked up to. In the past almost all of the FXO based paging systems run through a paging adapter of sorts, like a Valcom. Those typically have a setting on them that you can set max timeout as well as on-hook detection.

Ben Amick
Unified Communications Analyst

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Huff
Sent: Monday, September 25, 2017 3:37 PM
To: Loren Hillukka <lchillukka at hotmail.com>
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Call length on paging ports

You might find that editing the softkey template and relocating the hold softkey away from the end call softkey for the connected state might be a solution (that way you don’t have to alter the behavior of the pots line).

Thanks,

Ryan

On Sep 25, 2017, at 3:31 PM, Loren Hillukka <lchillukka at hotmail.com<mailto:lchillukka at hotmail.com>> wrote:
I have a plant building with a 4351 connected to a paging system via an FXO port.  Site has phones connected to CUCM, gw is not MGCP.  Users at the plant are notorious for paging, then pressing "hold" instead of "end call" on the Cisco phones they page from. The plant floor then gets MOH playing and nobody else can page until I shut/no shut the port or they unplug the cable from the fxo port.

Any idea if a max length of call timer can be applied only to that one fxo port, to disconnect any call to it after 15 seconds or so?

Thanks
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<http://cp.mcafee.com/d/2DRPowrhvKUOUYDsQsCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCQkdvd7dzhO_R-sssd7bOb_nKnh7e8YztdOZXIZh55qWqJQmul3PWApmU6CQjq9K_nhjjpd7dQXCzATsSjDdqymoIToHMd9_7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddEFEIICMnWhEwdbtFkJkKpH9oQKCy0iQYYQg7_0zcCq8aMd42SApg8Cy1qIpQdIc6Vet2kjPD>


Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170925/f2ac8e23/attachment.html>