Lonnie Abelbeck wrote:
> On Sep 16, 2008, at 8:26 AM, David Kerr wrote:
>
> David,
> I guess 1 and 2 are for me...
>
>   
>> Now that I have the 0.6 branch running in my sandbox I started to  
>> configure it and have found a couple of things.
>>
>> 1) The webgui uses a directory "rc.conf.d" into which network  
>> settings are placed, and the documentation recommends that we put a  
>> "user.conf" file in here for our own settings.  I found that this  
>> file was not created by default, and therefore did not appear in the  
>> list of files that can be edited by the GUI.  I had to upload one  
>> myself, after which it appeared in the list in the GUI.  It would be  
>> nice if a user.conf file was created by default (blank, with just a  
>> few comment lines with instructions maybe?)
>>     
>
> Easy enough to do, I actually thought about it, you make a good point.
>
>   
>> 2) I asked for, and Lonnie implemented, a way to launch the asterisk- 
>> gui from the web interface. Lonnie created a field into which I  
>> could enter any URL and a link appears in the top right.  What is  
>> the right naming convention for this URL if I want to have the gui  
>> substitute the URL base name rather than hardcode a IP address or  
>> name (like "pbx")... in otherwords, the "link" URL needs to be  
>> different depending on whether I access the Astlinux box through the  
>> EXTIF or the INTIF.
>>     
>
> The only solution I can think of is to configure your DNS servers to  
> map the same the same name to get forwarded to the same box.
>
> My first thought (with only one cup of coffee) was to use localhost,  
> but that won't work since the name is resolved in your browser.
>
> The connection is your browser  => altweb versus your browser =>  
> asterisk-gui, and they use different web servers.
>
> I don't see any other way.
>   

You can just serve back whatever prefix came in the original GET 
request, right?

If the user said:

http://host.mydomain.com/foo

then return something starting with http://host.mydomain.com/ and if he 
said:

http://192.168.1.1/foo

then return something starting with http://192.168.1.1/ -- this will 
also make it more compatible with reverse-proxy servers operating 
through a NATting gateway.

-Philip


>   
>> Also.. Astlinux now has the asterisk-gui version 2,  nice... But  
>> FYI, I have found problems with a change that they implemented in  
>> how asterisk Contexts are named in extensions.conf and users.conf...  
>> which is incompatible with the old way of doing things (and in my  
>> opinion wrong).  I have started a discussion on this over in the  
>> asterisk-gui list at http://lists.digium.com if you are interested.
>>
>> Thanks,
>> David
>>     
>
> Lonnie
>   


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to [EMAIL 
PROTECTED]

Reply via email to