Scott Lawrence wrote:
On Fri, 2009-08-07 at 09:37 +0100, Keith Gearty wrote:
Paul Mossman wrote:
The admin should see simply a list of codecs that can be selected and
de-selected.
As I understand it, SipXecs cannot and should not work quite like that.
As far as SipXecs cares, the codec names are nothing more than text
strings. RTP packets can carry streaming media of any type (not just
VoIP) and SipXbridge is designed to pass these packets without
interpreting them. It would be nice to be able to apply a codec exclude
list to a particular SIP trunk or gateway, and since all the messaging
passes through SipXproxy I should think that would be possible. But the
admin should be able to build the exclude list by entering text strings
and adding them to the list. For convenience, you could have a combo
box of "common" codecs to choose from, but the admin shouldn't be
limited to just those.
I feel pretty strongly that sipXecs should not manipulate codecs in any
way in transit unless there is no alternative.
The goal is to make session media an end-to-end negotiation - this
allows endpoints to innovate, and one of the advantages that sipXecs has
over systems that are B2B at the media layer is that new and improved
media endpoints just work in sipXecs.
But that would be true if you followed my suggestion as well. No codec
manipulation is required, just filtering of the codec names (treated as
text strings) in the SIP messaging, according to an exclude list. That
to me seems like the cleanest way to prevent high-bandwidth codec being
used across a particular SIP trunk or site-to-site (gateway) interface.
If you can suggest a better way of achieving this, then please do.
_______________________________________________
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/
