> > Woof! > > On Thu, 24 Sep 2009 15:21:45 -0400, Alfred Campbell <[email protected]> > wrote: > > > Other than G.729 not sure it makes sense to support more than the > media > > services can support. > > One of the major advantages of a pure SIP Proxy architecture is that > the > endpoints negotiate codecs directly with each other, and thus "sipXecs" > is > not in the way at all, unlike all(*) the other open source PBX systems > out > there. Limiting the codecs to what the media services supports is > defeating that advantage. The phones should negotiate with media > services > just like any other endpoint. Yes, we've seem some bugs on devices > with > regards to MOH, but I don't think that should be a reason to limit the > codecs. > > Let the phones speak any and all codecs they can handle. Let SIP do > it's > job and negotiate the best codec for the job. > > (*)As far as I know, there are no other pure SIP open source PBX's out > there! All are B2BUA's of some sort or another. >
I would imagine this could be done by naming things a certain way in the GUI to make it clear. It would be good for non-technical folks to know what codec's work with key services like voice mail :) > --Woof! _______________________________________________ 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/
