Web Server

A web server, through the HTTP^4.9 and/or HTTPS protocols, is responsible for the answers to users requests, concerning the web pages lodged in it, and each server may lodge several sites. The IPBrick web server running in IPBrick 5.0 is Apache 2.2.3^4.10. The base virtual hosts registered in IPBrick are displayed after clicking on Web Server and may be seen in Figure 4.25.

**Figure 4.25:** Web Server - Hosted sites

IPBrick hosts the following sites by default:

ipbrick.domain.com: IPBrick web management interface;
myipbrick.domain.com: Site for LDAP users configuration reaching general and email definitions;
calendar.domain.com: Intranet LDAP agenda;
callmanager.domain.com: Flash application for VoIP;
contacts.domain.com: Intranet LDAP contacts management;
jwchat.domain.com: A web-based Jabber (XMPP) client for the IPBrick LDAP users;
mysqladmin.domain.com: MySQL database web management;
pgsqladmin.domain.com: PostgreSQL database web management;
ucoip.domain.com: UCoIP (Unified Communications over IP) site for LDAP users. All enterprise communications - Voice, Mail, Instant Messaging and Web - are managed in an integrated way, i.e. unified through a single individual or group address. To reach this goal, IPBrick uses only Internet communications services (SIP, SMTP/IMAP, XMPP and HTTP) integrating with DNS and LDAP support services.

The generic site is ucoip.domain.com but the idea is to have one site for each LDAP user. The following options are included:
- A IAX webphone for direct connection to the user SIP url;
- A SIP url link to call the user using a softphone previously installed at workstation;
- A web-based Jabber (XMPP) client to chat directly with the user;
- A SMTP link to mail the user using a email client at workstation;
Like we can see, for SIP/SMTP/XMPP the user will be reached using the single address user@domain.com. The UCoIP site design is simply but it can be improved. It's possible to use a specific FTP account for site management:
- username: ucoip;
- password: 123456.
Now we present all the necessary steps to configure a UCoIP site for a specific LDAP user with username jsmith, with IPBrick FQDN being ipbrick.domain.com:
- The user jsmith must go to https://myipbrick.domain.com and define a phone (depending of the IPBrick.GT routes can be a SIP/PSTN/GSM number) at field SIP Address. Examples: 101@domain.com, 00351221121112, 00351963322212;
- Activate the IM service at IPBrick.C - IM;
- Go to IPBrick.C - Web Server, click at ucoip.domain.com and define the alternative address jsmith.domain.com;
- At private/public DNS server add a record named jsmith, pointing to that IPBrick server;
webacula.domain.com: Bacula backup server web administration;
webmail.domain.com: Horde webmail client;

webphone.domain.com: It's a IAX webphone example. The idea is to view the page source code and include it in a real website. This webphone can be configured to call directly any number you want or to match some direct access for a VoIP funcionality (sequence, groups, IVR etc). To specify that, the variable called url must be changed.

The source code of this page is presented next:

    <script language="JavaScript">
    function webphone() {
    var day = new Date();
    var id = day.getTime();
    var url = 'index2.php';
    eval("page" + id + " = window.open('" + url +"' , '" + id + "',
    'toolbar=0,scrollbars=0,location=0,statusbar=0,menubar=0,
    resizable=0,width=285,height=430');");
   }
   </script>
   <h1>Example Link</h1>

   <a href="javascript:webphone()"><img alt="IPBrick.GT high
   versability working for the New Internet" src="webphone.jpg"></a>

Examples of url variable definition:

    var url = 'index2.php?user=jdomingues';
    var url = 'index2.php?user=200';
    var url = 'index2.php?user=IVR2';

NOTE: From now, this webphone can be used only with Internet Explorer.

Footnotes

... HTTP ^4.9: HyperText Transfer Protocol
... 2.2.3 ^4.10: For more information please visit http://www.apache.org

Subsections

iPortalMais