My only concern would be if this configuration causes a call to drop when sipxbridge services are restarted and the system is utilizing an unmanaged SBC.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mossman, Paul (Paul) Sent: Wednesday, April 21, 2010 10:16 PM To: Scott Lawrence Cc: [email protected] Subject: Re: [sipX-dev] SIP Trunk using an Unmanaged SBC Route, why? Scott wrote: > On Wed, 2010-04-21 at 14:26 -0400, Mossman, Paul (Paul) wrote: > > > See above. We could add Outbound Address & Outbound Port > settings to > > "pure" SIP Trunks. > > > > To route a SIP Trunk's calls through an unmanaged SBC, then just > > configure the SBC's address/port right on the SIP Trunk. > > > > Same net effect as the association to an "Unmanaged" SBC > Route, except > > much simpler. > > > > (And yes, upgrades could preserve the pre-upgrade behaviour.) > > > > Make sense? > > I guess so... I may be handicapped by knowing too much about > how it really works. I understand completely. So any objections to removing Devices -> SBC Routes as part of XX-8137? -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
