Woof! Mark wrote:
> Create a reg event subscription with registrar against each user in > the paging zone. This allows paging server to track all phone > registrations for all users in the paging zone. Yep, could do that--or suck in the registration list from the registrar with an XML query--or read the IMDB registrar table--or just send the INVITE directly to the registrar and parse the results of the 302 response. All of these approaches were considered (and rejected) in the sipXpage design. > Upon incoming paging > call create separate INVITE dialogs towards each registered phone. > This way no paralell forking is done and calls to multiple phones are > made at the same time. That would only work if you bypass the proxy, sending the INVITE's directly to the registered address. If you don't, then the calls all fork anyway. Do you really want page's to bypass the proxy, and the associated permissions, CDR, and other issues that would cause? I didn't want to do that, and then have sipXpage have to take on the responsibilites of both the proxy AND the registrar. The idea of associating a "primary line" or "page flag" with a given registration was floated, but it didn't work as there was no way to associate a given registration with any particular device. All the phones just don't do that consistently. So, the simple approaches have been rejected, and there are the work arounds as Scott mentioned. Anyone have a way of doing this that doesn't violate the rules of physics, or end up replicating large swaths of existing code just to support a minor feature? --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
