>> >> >> >> 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. >
It sounds to me your looking to do what SipX did before 4.0 and sipxbridge. That is to say, when you do NOT enable SipxBridge, Sipx does not handle the media. You are then required to have some SBC device to handle the NAT/anchoring of media. Ingate devices are very popular. Of course, you need to ask your self if deploying an SBC at each branch is any better than setting up a local SipX install (which also gets you local survivability). For branches we use an all flash device to keep it "hands-off". M _______________________________________________ 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/
