[cisco-voip] sharedline behaviour with 4.x
Ryan Ratliff
rratliff at cisco.com
Fri Mar 17 15:15:30 EST 2006
It was the change allowing a greater number of max calls per line
that allows the other phones to make new calls in the first place as
far as I know.
-Ryan
On Mar 17, 2006, at 2:07 PM, Ed Leatherman wrote:
I've never seen anyway to make it work differently
On 3/17/06, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
With shared lines and 3.x while I was on the line, any new incoming
calls were handled exclusively by the person who was handling the
call, effectively blocking any other instances of that shared line
from receiving or placing new calls.
With 4.x things work quite a bit differently such that any new
incoming calls ring on other sets and other sets can place new calls
from that shared line.
I think this new feature is great, but I'm sure there are people who
will want to use the old way of things. I understand that I can set
the busy trigger and max calls to prevent other phones from doing
this, but this also affects the phone who is in control of the active
call.
Has anyone found a way around this? Is there a service parameter that
I'm missing?
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Sanity First : Number of days with fewer than
50 messages in my inbox at the end of the day: 14
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
More information about the cisco-voip
mailing list