search

karthikindia / redfire

Automatically exported from code.google.com/p/redfire
0 stars 0 forks source link

Wrong server name. #28

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set the xmpp.domain in openfire to domain.com
2. Have an SRV record in domain.com point to the host (jabber.domain.com)
3. Connect and try to run video.

What is the expected output? What do you see instead?
Expect to see video but instead unable to connect. The client tried to run the 
video through domain.com which doesnt contain a server. Upon login Spark does 
an SRV lookup to find the server for domain.com (jabber.domain.com) but in this 
case you must edit red5.properties which is impossible on hundreds of systems 
running spark. Entering jabber.domain.com in the server upon login does not 
fix. Redfire should so an SRV lookup to find the correct servername or if Spark 
makes the servername available it needs to use this.

What version of the product are you using? On what operating system?
Latest Openfire, Redfire, Spark and Flash.

Please provide any additional information below.
Changing the xmpp.domain on the server to jabber.domain.com fixes this problem 
and makes the video work, but then breaks federation with other systems as when 
userx@domain.com is entered externally the ID is invalid because it is really 
userx@jabber.domain.com but domain.com still resolves the SRV to point to the 
server when the xmpp.domain is incorrect.

Original issue reported on code.google.com by whitehaw...@gmail.com on 20 Feb 2012 at 11:31

GoogleCodeExporter commented 9 years ago 
I found this while investigating privacy plugin issues related to the same 
where you connect via a host/name that is not the true server hostname. (like I 
use domain.com with srv records instead of connecting directly to 
jabber.domain.com, jabber.domain.com is the host but the domain set in the 
config is domain.com and the dns used to connect is domain.com) They fixed the 
privacy plugin with this message, maybe this will help with fixing this issue?

automatically discover true xmpp location using 
DNSUtil.resolveXmppDomain(serviceName); use it instead of connection.getHost

Original comment by whitehaw...@gmail.com on 6 Mar 2012 at 3:58