On Mon, Jan 17, 2011 at 12:22 PM, [email protected] <[email protected]>wrote:
> On Mon, 17 Jan 2011 11:46:35 -0500, Tony Graziano wrote: > > I think you would be so much better off waiting for 4.4, and adding some > > licenses to FS for g.729 then. > > That's exciting. > > I've not kept track of what's coming so wasn't aware of this. Went and > looked and read this. > http://wiki.sipfoundry.org/display/sipXecs/G729 > > That gives us a couple of ways of doing things. Is this system wide or will > it be possible to do it by groups? I don't see any mention of this. > System wide. > > Sounds like sipx will be able to do it's own transcoding in the near future > then, which means being able to give remote users codec choices perhaps. The > licensing installation sounds a bit involved considering that managing > licenses, actually, mainly adding more channels will probably be an ongoing > thing. > > Its a work in progress. > Each license is actually one encoder and one decoder so one license per > call right? I'm mainly concerned with in-network calls, I believe they are > called 'inter office' calls, between two people. > That is not involved. It's only calls TO the media server (AA.voicemail, etc.). Its a matter of whether the provider supports g729 in this instance. You can then force (in 4.4) the FS server to prefer g729. > > I'd love to offload sipx in another way, by letting it act as a > switchboard, connecting calls together and getting out of the picture so > it's not using my bandwidth. The two remotes would then talk to each other > and only accounting information would come to sipx. Don't think I've seen > such a product/project yet. > Sure, its called an SBC, but its another device.. > > Dreaming :). > > Dream on, not really possible with sip and nat traversal, at least not reliably. On a LAN it does this, in NAT it does not and won't unless they rewrite SIP to something else... > > > > > You will have issues with renegotiating and > > such that you will want to make transcoding possible with the media > server. > > This approach using FS does not work in 4.21 because FS does not support > > that licensing in 4.21. > > > > On Mon, Jan 17, 2011 at 11:41 AM, [email protected] <[email protected]> > > wrote: > >> On Mon, 17 Jan 2011 10:55:39 -0500, Matt White wrote: > >>> Each phone or phone group can have the codecs configured. Simply put > >>> G.729 > >>> as the highest perferred codec and the phone will use that codec > first. > >>> > >>> you can also restrict which codecs SipxBridge allows and restrict that > >>> to > >>> G.729 as well. But that would not affect intraoffice calls. > >>> > >> > >> Thing is, the remotes would have various soft-phones and sip phones. So > >> basically, I could in fact do this but would have to limit what remotes > >> are using? > >> > >> As to intra office, you mean in-network, sip-to-sip calls? Because, > those > >> are the ones I'm trying to control most. > >> > >> > >> _______________________________________________ > >> sipx-users mailing list > >> [email protected] > >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net <http://support.myitdepartment.net>Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
