On Wed, 2008-09-10 at 18:40 -0400, Gertsvolf, Mark (CAR:9D30) wrote: > > Just to reiterate the comments I put into the JIRA ticket: > http://track.sipfoundry.org/browse/XECS-1652 > I feel that from the user's point of view paging in its current form > behaves inconsistently in the case of multiple registrations per user. > Page is delivered to one of the registered phones in a random fashion. > That was my rational for raising the issue.
and I agree, but in the absence of device-unique addresses, it's not that easy to fix this. > > The only way to get around this forking behavior is to ensure > > that it doesn't happen - that every address in a paging group > > has exactly one appearance on any device. We _could_ do that > > by configuring the targets in a paging group as a separate > > line on the phone. So if you want to make my office phone be > > part of a paging group, then that phone gets an additional > > "paging" line added to it, and the address of that paging > > line is added to the group. In theory, sipXconfig could just > > generate these "paging" line addresses, and then configure > > them onto phones as needed. > > I agree with your observation that this workaround has the limitation of > consuming a key on the set. It also requires a dedicated user/extension > just for the purpose of paging. well, there's no shortage of addresses in SIP :-) If we could put an "invisible" address on a phone, we could generate addresses that won't collide with any that users create. The more serious problem is that of the paging address being visible. This same problem comes up in other places, including the Hotelling proposal and sending configuration update notifications. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
