[cisco-voip] question regarding 'prime line'

[Tim Reimers]

Thanks!
 
I think I'll probably follow the idea mentioned before, if the type of headset that's been ordered will do it-
but this does give a good understanding of what 'status' might be..
Didn't think of "with a waiting VM"...
 
T

________________________________

From: Keith Klevenski [mailto:keith.klevenski at rig.net]
Sent: Wed 9/27/2006 5:27 PM
To: Tim Reimers; cisco-voip at puck.nether.net
Cc: Alan Surrette
Subject: RE: [cisco-voip] question regarding 'prime line'



Tim,

 

My impression of setting Always Use Prime Line for Voice Message to true means that whenever the messages button is pressed it will check the vm for line 1 no matter if there are other lines on the phone with other vm boxes configured.  It will simply always check the vm for line 1 when pressed no matter what.  To check vm for other lines you'd have to go off hook on the other line and then press the messages or dial the vm pilot number of course.  I am pretty confident about this as we have this in place now in one of our clusters.

 

We had this issue recently where the person wanted to press the messages button and have it go to line 1's vm as this was on a 7960 with a 7914 expansion module.  Every time they pressed the messages button it would go to what they thought was a seemingly random line which was actually a line that had a new vm waiting.

 

If this setting is left at the default of False then if the line that has new vm waiting is in use then I would assume it would go to the next line that is not in use that has a new vm.  I would also assume if there were no lines with new vm then line 1 would be used.  This would be what is meant by 'based on line status' is whether the line is in use or not.  If in use it will just go to the next line with new vm that is not in use.

 

Again, these are assumptions that seem to make sense as I haven't sat down and tested all of this.  Hope this helps.

 

Keith 

 

 

 

________________________________

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 3: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/86744a81/attachment.html