Wednesday, July 25, 2007 3:13 PM
Just wondering what the process is whereby anonymous meeting participants join a Live Meeting web conference being held within my organization. All they receive is an email containing a link to "meetip:[SIP URI]:conference key etc..."
How does their Live Meeting client (with no prior configuration) find my Web Conferencing edge server? I know there are DNS records and queries that are issued to find the Access edge server for SIP signalling, but how does this then point them to the Web Conferencing edge server? Having trouble finding technical details about this in the documentation so we know what we need to set up in terms of DNS records etc.
Wednesday, July 25, 2007 8:47 PM
You need to add an SRV record (_sip._tls.yourcompany.com) on the DNS that resolves your external domain, that points to an A record (aes.yourcompany.com:443) that contains the address of your Access Edge Server (x.x.x.x).
When an external user receives an invitation with your sip uri (email@example.com) it will send a DNS query to see where is the access edge server that service yourcompany.com
Hope it helps,
Thursday, August 02, 2007 5:25 AM
Can you let us know the status of your issue? Were you able to follow msabena's instructions?
Friday, August 03, 2007 2:25 PM
Unfortunately our non-Microsoft DNS server does not support SRV records, so I am not able to follow the solution verbatim, but the description answers my question. After failing the SRV record queries, the RTM release of the Live Meeting 2007 Console will issue an explicit A record query for sip.mydomain when a meeting is issued from my organisation (e.g. ben@mydomain) so all we have to do is set up the right A records. Reading further through the documentation, it seems the actual Web Conferencing server is one of these in-band provisioning attributes, since I need to configure my external web conferencing server name, and external meeting content URLs within the server.