[cisco-voip] shared line as primary line

[Ryan Ratliff]

Yup, the component that controls the line has to tell every phone that the
line exists on to start ringing.  The signal goes out to the component that
controls the phone in some random order and depending on how many phones the
line is shared across this can be quick enough to be simultaneous or it can
appear spread out.  If the phones are registered to different subscribers
the rings can be that much more spread out.


-Ryan 
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Robert Kulagowski
Sent: Friday, July 27, 2007 10:52 AM
To: Cisco VoIPoE List
Subject: Re: [cisco-voip] shared line as primary line

Bill Simon wrote:
> I do it with my test phones, all have the same single DN assigned, and 
> it doesn't seem to be a problem at all.  Why does Cisco say not to do 
> this?

Maybe because it exposes the fact that not all the lines would start ringing
at the same time?  I'm running into this situation at a remote site
(Beijing, with call processing cluster in the U.S.) - no receptionist, so
the main number is on every phone.  When the main number gets a call various
phones start ringing, but the ring cadence is such that they're "out of
phase" with each other.

Without doing traces, I'm guessing it's because CM has to unicast to each
phone to get them to start ringing. (And because of TCP delay it just makes
it apparent)

CM 4.1.3sr2, phones are running 8.2.1
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip