Try this...
http://www.bogen.com/products/pdfs/telephonepagepdfs/tamb2m.pdf
-Original Message-
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Loren
Hillukka
Sent: Monday, September 25, 2017 3:31 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Call
It may be that the person performing the page and placing the paging port
on hold is in the front office and isn't within earshot of the plant floor.
I could definitely see that.
In addition to checking the options on the paging system itself, have you
considered the option of configuring the Hold
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
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
mailto:lchillu
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
I've been having this issue a bit this morning, and I don't recall having this
issue in the past, but for some reason it seems like when I do an export all
phones from CUCM (v9.1 here) it seems like for some reason if a phone is
missing any XML data, it throws off the entire CSV past the XML pie
