I've never tried. In the way paging is designed, its entirely possible that latency is causing the audio to be too late and not used.
" broadcast tone" then "go offhook" and now "deliver this audio to all members". try a paging group of one remote phone. my guess is it will work. the local phones all ack back and begin audio and the remote phone is too late and is excluded. On Jun 24, 2011 5:02 AM, "andrewpitman" <andrewpit...@comcast.net> wrote: > > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <61038> > Message-ID: <ee6e.4e037...@forum.sipfoundry.org> > > > > Quote: >> Paging remote workers... Please pick up the courtesy >> phone. ;) > > > I'm trying to get paging groups to work with my 4.4.0 setup, > which includes both near and far end NAT traversal. While > you can hear the notification tone through the phone sending > the page, and the phones in the paging group ring and > auto-answer, there's no audio once connected. I'm wondering > if this feature, while it appears to handle NAT traversal > for the SIP messaging, is actually set up to properly handle > relaying of the media in this configuration like it would > have to. > > Has anyone been able to get paging to work with "remote > workers" or is this a "local phone"-only feature? > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
