Ah, see, there is a better way.  Thanks for pointing that out, Jacob.  I take 
it 
you change http.host, rtmp.host, and rtmps.host to the FQDN?

Dimitri
 

On Friday 28 September 2012 3:16:09 pm Jacob Gaiski wrote:
> Did you set the bindings to your external IP address in red5.properties?
>
>
>
>
> From: David Takle
> Sent: Friday, September 28, 2012 3:13 PM
> To: [email protected]
> Subject: Re: Sending IP Address in Emails
>
> Dimitri,
> Your comment raises a lot of questions for me.
> First, are you using a laptop/desktop for your server? If so, how did you
> get a domain name for it? Second, using 'ipconfig' on my XP, I got a
> 192.168.x.x address that worked fine from my 2nd computer. Was that only
> because it is on the same side of the modem? Would that address not work
> for the rest of the world to use? Thanks!
> ~David
>
>
> On Fri, Sep 28, 2012 at 3:04 PM, Dimitri Yioulos <[email protected]>
> wrote:
>
>   I've found that you need to log into OM with the FQDN of your OM server
> (e.g. http://openmeetings.mydomain.tld:5080/openmeetings).  At first, I was
> using the internal address of the OM server, so my invitees were instructed
> to go to the meeting at http://192.168.x.x<meeting_id>.  Clearly, that
> didn't work.  Others may know of another way to accomplish what you're
> after.
>
>   Dimitri
>
>   On Friday 28 September 2012 2:56:08 pm David Takle wrote:
>   > The Derby DB went nutso on me, so I started over with MySQL.
>   > Things are working nicely now.
>   > However, when I send out an email invite, it says "localhost" which
>   > means nothing to the recipient.
>   > How do I send my IP address in the email?
>   >
>   > Further, how do I get the IP address of my PC when it goes through a
>   > wireless router? If I go to a website that provides my IP address, it
>   > gives the address of my router, not the PC. If I substitute that IP
>   > address in the email invitation, it does not connect to OpenMeetings
>   > because the router does not recognize the request.
>   >
>   > ~David
>
>   --
>   This message has been scanned for viruses and
>   dangerous content by MailScanner, and is
>   believed to be clean.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Reply via email to