after thinking on it some more, clarification might help: because none of this is behind NAT your remote users are not "remote", so anchoring the media is not an option because i'm not sure it is necessary.
Enables NAT traversal capabilities in support of remote workers and remote servers behind NAT sipXbridge IS anchoring the media for all of your calls now. The only question is why you would create a phone system for branch offices without actually placing the system in the branch office, which does not give you any type of usability in the event of an Internet failure, etc. On Mon, Feb 1, 2010 at 1:37 PM, Tony Graziano <[email protected]>wrote: > sipXbridge is a media anchor. > > You would connect remote sipx systems and connect them to verizon as you > have your central system. You would then create a dialplan to allow them to > route calls directly between each other (sipx to sipx). > > > On Mon, Feb 1, 2010 at 1:27 PM, [email protected] < > [email protected]> wrote: > >> Excuse my ignorance here if I'm butchering some terminology. After a >> pretty successful roll out at our corporate office, we are looking >> possible implementations at some of our remote facilities that have old >> dying key systems. All our facilities are connected to our corporate >> office by Verizon T1 MPLS links. From a network perspective, they do >> have the ability to hit the Verizon cloud directly without coming back >> to our corporate office first. Verizon is our VOIP provider. Our desire >> is to send the RTP traffic from a remote facility directly to Verizon >> without coming to corporate first. We do not want to put any equipment >> at the facility, except the handsets. We want to utilize our central >> Sipx server(s) at our corporate office. Verizon says they can let the >> sip traffic go through through corporate, but then route the RTP traffic >> directly out the local port. This is the description from Verizon on how >> this works: >> >> "The term we use for allowing the RTP media to flow directly from our >> VoIP node (SBC) directly to your remote office is called “Media >> Release”. The opposite of that is “Media Anchor” (aka hair pining) which >> requires the media to “anchor” to the IP PBX and uses 2x the bandwidth >> into and back out to the remote." >> >> Is this something Sipx supports? I tried Googling Sipx and "media >> release" but I don't get any hits. Maybe there is a different term I >> should be using. We have Cisco routers at each location if that is >> relevant. >> >> Sipx 4.0.4, sixbridge, Verizon VOIP, No firewall (not needed, private >> connection), Polycom 450s and 550s - bootrom 4.2.1, firmware 3.1.3C split. >> >> Thanks as always, >> Matthew >> _______________________________________________ >> sipx-users mailing list [email protected] >> 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/ >> > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > Why do mathematicians always confuse Halloween and Christmas? > Because 31 Oct = 25 Dec. > > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list [email protected] 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/
