On Mon, 2010-02-01 at 16:09 -0500, Tony Graziano wrote: > > > On Mon, Feb 1, 2010 at 3:49 PM, Scott Lawrence > <scottlawr...@avaya.com> wrote: > On Mon, 2010-02-01 at 14:25 -0600, mkitchin.pub...@gmail.com > wrote: > > Does anyone know if this is even a common feature among SIP > servers? > > Verizon is indicating they have never worked with a client > setup that > > didn't support this. Maybe something is getting lost in > translation > > here. > > > I'm not clear on what you're going to have in the branch. > What is the > complete sequence of devices and network segments between the > phone in a > branch and your central sipXecs, and where are the connections > to > Verizon? > > > > He wants sipx in the HQ with the remote branch phones registering to > it, using sipXbridge as the gateway for the trunks, but with the media > anchored at the handsets in the branches to the Verizon Gateway (not > to sipXbridge).
Right... the feature you're looking for is: http://track.sipfoundry.org/browse/XX-5034 it's not expressed the same way, but that's what you would need. If implemented, it would allow sipXbridge to get out of the media path. That issue is not yet scheduled for any specific release. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/