= Mexlca - Expansion = 

    Expand existing infrastructue to have more than 1 interpretation channel

= Development Approaches =

    Leave everything as is, and just work on the mexcla.tac (twisted service)

    Build a form that creates the channel, and determines how many interpretation channels exist, using the mexcla.tac infrastructure.

    Revamp the whole fucking thing and use freeswitch webrtc Sip.js, this option may or may not require also using the mexcla.tac.

== Everything in tact ==
=== Pros ===

    Easiest to accomplish

    Faster

    Keeps the same not perfectly beautiful interface.

    Not too much work

=== Cons ===

    Not resolving current problems with mexcla (which might be a problem with the protocol)

    Does not improve sound quality.

    Does not improve development of webrtc.

    Does not fully integrate into our webrtc infrastructure.

    Limits user interaction.

== Build webform for handling channel creation ==
=== Pros ===

    Allows better interaction for people hosting a call.

    Permits language designation for the specific interpretation channel, i.e. more info for callers.

    Helps expand functionality, specific to each call.

    Relatively easy to implement.

    Would allow for adding features (pads, irc, calc, presentation, chat) to the channel.

=== Cons ===

    Would require work, more development and testing.

    Would create more bugs.

== Revamp ==
=== Pros ===

    integrate live (video) and mexcla (audio) 

    get to learn cool new things

    Tighter integration to freeswitch (probably)

    Perhaps better audio quality

    Would be using websockets.

    We'd be cutting edge!!!!

    perhaps better integration with live.m.o

=== Cons ===

    Don't know what we're doing

    Possibly lots more bugs

    perhaps we end up revamping live.m.o too