Scott Lawrence wrote: > The short answer is "No", but of course there are ways to get > the effect that is desired. > > The first thing to understand is that we don't make calls to > Users, or to Phones: we make calls to Addresses, specifically > to a SIP URI. > Normally a given URI is the address of some user, but it can > be anything.
Scott, 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. > 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. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
