[cisco-voip] question regarding 'prime line'

[Karl Whitson]

Tim,

 

You may be over engineering the solution.  I use a wireless headset (GN
9120) with a handset lifter and do remote answer all day long on all
three lines.  The key is to connect the wireless headset up to the
handset port (inline with the handset) and not use the headset port on
the phone.  Then when any of the lines are ringing, when you press the
remote answer button it will lift the receiver and they can begin to
talk, no matter which line is ringing.  They will even get a beep in the
ear with the GN 9120 and 9350 (not sure of other models).  Then you will
not have to adjust this setting and risk having a negative effect on
other users.  I find that having the personal line as line one is a good
rule of thumb and a good design. 

 

Karl Whitson

CMB Technologies

40 Cape Rd.

Milford, MA  01757

DID:  (508) 422-8413

Cell:  (603) 930-4189

Fax:  (508) 634-8678

Karl.Whitson at cmbtec.com

www.cmbtec.com

TO OPEN A SUPPORT CASE EMAIL SUPPORT at CMBTEC.COM
<mailto:SUPPORT at CMBTEC.COM>  OR CALL (508) 422-8429

  

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tim Reimers
Sent: Wednesday, September 27, 2006 4:54 PM
To: cisco-voip at puck.nether.net
Cc: Alan Surrette
Subject: [cisco-voip] question regarding 'prime line'

 

 

Question on answering lines with wireless headsets: 

Here's my configuration: 

We have a number of secretaries with their own personal line as #1 
They also have the main school number as their second/third button. 
They want to use wireless headsets and be able to be away from their
desk and answer the main school line. 
My understanding is that they can only answer line#1 with most
headsets-- since the headset does not have a way to select a line
remotely to answer.

Therefore-- 
We've considered reprogramming their phones to  have the main # as the
first button, and have their personal line as second or third.

That way, the wireless headset will answer the main line correctly: 

Upon inquiring of our vendor what the ramifications would be of making
the main# the first button, the answer was: 
"When they hit Messages, they'll get the Vmbox for the system, not their
own mailbox" 
because we've set the option below to "true" 

"Always Use Prime Line for Voice Message : This parameter specifies
valid value as True or False. If the flag is set to True, when the
message button is pressed, primary line gets chosen and becomes the
active line. If the flag is set to False, phone automatically select a
line with voice mail as the active line based on the line status.
This is a required field.
Default: false."  (Ours is "true") 

If I change that,  and someone has two lines on their phone with two
different Vmboxes (ie, the school main# with a CallHandler set up for
RNA on that line, their own personal line, and then shared lines for the
principal, the AP, etc etc)

How will the Messages button function? 
What will happen when there are -no- active lines? Would that button
take you to the CH for the main school line on button #1 ??

Would it take you to the next available 'on hook' line and the related
mailbox? 
or would it be random -- such that they might find that the Messages
button one time gets their VM, another time gets them the Principals vm
on line #3, or AP on #4, etc?

Mainly, I guess I'm looking to find out if the approach of 'main line as
button#1' to fix the headset issue is the right way to go, and if that
IS the right direction, 

what does "based on the line status" mean with respect to the option
above? 

Does this make sense to folks? I can re-explain if it's not clear... 

thanks, Tim 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060927/54b7308b/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2318 bytes
Desc: image001.jpg
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20060927/54b7308b/attachment-0001.jpe