>You don't need to configure the phones, just check to see if it is enabled by >default. >There is a codec preference, so it matches the first agreed to codec with FS, >but if >it is "device-to-device" then you certainly need to place something in between >to >"force" g.729, which would be a SBC with transcoding capability, at which >point >you do not need FS licensing.
Yes, device to device (remote to remote). As the phones we are using don't have transcoding capabilities, setting them to prefer g.729, calling another remote with g.729 still doesn't compress the data. Too bad OpenSBC doesn't support codecs, I could get to testing some things while waiting on 4.4. > 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. That's easy enough to live with then. >> 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. Yup, sipx devs are fantastic at refining things for ease of use in time. > 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. Are you saying that only calls to AA, VM, etc, would use the codec and not inter office calls? Maybe I'm misunderstanding inter-office. In my case, I mean remote users calling each other over the Internet. Anyone know what a reasonable release time frame might be for 4.4? _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
