Of particular interest at the moment is how we should discover your STUN & TURN servers. Does the client have the servers hardcoded, or does it get them sent to it during the web authentication? Would you consider adding SRV records in the SIP style of _stun._udp.gmail.com etc for making at least your STUN servers available to 3rd party clients?
We agree we need to support and document a public way of stun and relay discovery, and relay server resource allocation. This needs to be addressed in the jingle jeps as well. The discovery mechanism in use by the Talk client at the moment isn't something we can support for general use. We'll look into this. Regards, Scott
