UID: root
PASSWD: mobicents



VM image is preconfigured to run with settings:
192.168.1.2 - SIP AS
192.168.1.3 - OpenIMS components, name server for open-ims.test domain.

Domain looks like:
192.168.1.2                     mobicents.open-ims.test
192.168.1.3                     pcscf.open-ims.test
192.168.1.3                     icscf.open-ims.test
192.168.1.3                     scscf.open-ims.test
192.168.1.3                     hss.open-ims.test
192.168.1.3                     open-ims.test

It can be configured with bind, but also requries changes in OpenIMS configuration files.


Important files are/can eb found

/etc/resolv.conf
/etc/named.*
/var/named/
/etc/hosts
/opt/OpenIMSCore


I.   Setting up domain
II.  Configure IMS core
III. Run
IV.  Possible problems






I. Setting up domain.

Bind configuration is more or less straightforward, however it does not provide much info on missconf.

File that should be modified are as follows:

* /etc/named.conf
   Usually only one line has to be changed to make it work (unless domain is changed)
   "listen-on port 53 { 127.0.0.1; 192.168.1.3;};"  - here last IP address should be changed to one that VM images binds to.
   

        
    However when domain changes, its good to follow files naming patter. Currently image reuses open-ims.test domain. 
    /etc/named.conf includes file: /etc/named.open-ims.test, if domain is to be changed it also should imply change of include statement and file name.
    For instance, if domain is to be changed to "mobicents.org", /etc/named.conf would should have import statement:
    
    include  "/etc/named.mobicents.org";

* /etc/named.* 
    Those files are included in named.conf. Definition they carry are: ZONE (domain name), zone file(file which defines hosts, etc. Note that this file can be found in /var/named/)
    File named.open-ims.test looks as follows:
    zone "open-ims.test" IN {
    type master;
    file "named.open-ims.test";
    allow-update { none };
    }

* /var/named/named.open-ims.test
    In /var/named there are various files, however to reconfigure IP/domain we are interested in one
    "named.open-ims.test" /etc/name.open-ims.test decalres that this file describes ZONE: open-ims.test
    (in case mobicents.org domain is used, file should have name following pattern)

    Few lines are of particular interest of user.
    Curently second line: "@ IN SOA hss.open-ims.test. root.mobicnets.open-ims.test. ("
    Names present should match one that can be found below:
    "IN NS hss.open-ims.test"
    
    To change IP/FQDN resolution one has to change ip numbers present in this file.
    For instance:
    mobicents         IN         A     192.168.100.2
    HSS               IN         A     192.168.100.20
    

    (Usually in example all IPs except mobicents(as) should match vm image bind address)
* /etc/resolv.conf
    This file controls how names are resolved. by default image makes use of dhcp, which overwrites this file.
    To make it work properly one one either has to make vmimage not use dhcp after altering file or edit it on each restart(if ip changes, steps above have to be redone)
    In /etc/named.conf one confires listen address of DNS server, this information has to be refelcted in resolv.conf
    Minimal edit is to put: "nameserver 192.168.1.3" (as in /etc/named.conf) - ip should reflect DNS listen address.

  
II. Configure OpenIMSCore

 To understand better steps undertaken here one should read:
 - http://www.mobicents.org/mss-diameter_sh.html
 - http://www.openimscore.org/installation_guide#step3


 * FHoSS /opt/OpenIMSCore/FHoSS/config
  Two file has to be modified:
 
  ** DiameterPeerHSS.xml (here ZONE is used as equivalent of DNS ZONE = open-ims.test, IP is used for vm bind address)
     
      FQDN="hss.${ZONE}"
      Realm="${ZONE}"  (realm does not have to be equal ZONE, its a diameter realm, which identifies common aps, etc.)

      <Peer FQDN="icscf.ZONE" Realm="${ZONE}" port="3869"/>
      <Peer FQDN="scscf.ZONE" Realm="${ZONE}" port="3870"/>

      <Acceptor port="3868" bind="${IP}"/>
  ** hss.properties - this fiels controlls where tomcat binds
     Two properties should be edited
     host=${IP}
     port=8080

  To make configuration changes take effect one has to recompile/redeploy
  In /opt/OpenIMSCore/FHoSS invoke:
  - ant compile
  - ant deploy


 * ser_ims configuration
  Folder /opt/OpenIMSCore/ser_ims/cfg contains most of files that will be used. 
  First thing is to edit "configurator.sh" file. Three lines are of interst:
  ** DDOMAIN="..."
  ** DSDOMAIN="..."
  ** DEFAULTIP="...."
 

  configurator.sh produces its output from files that reside in the same directory. To make it work correctly
  those three lines must match values in present files - (which is 192.168.1.3 and open-ims.test) once those are set in configurator.sh
  one can run it, and put proper values (domain and vm bind address)


  Now from /opt/OpenIMSCore one has to invoke following commands:

  - mysql -u root -p -h localhost < ser_ims/cfg/icscf.sql
  - mysql -u root -p -h localhost < FHoSS/scripts/hss_db.sql    
  - mysql -u root -p -h localhost < FHoSS/scripts/userdata.sql
 
  - cp ser_ims/cfg/*.cfg . 
  - cp ser_ims/cfg/*.xml . 
  - cp ser_ims/cfg/*.sh .


 * Configfure AS resolution
   One has to configure AS resoultion of DNS names. It either has to define hosts in its "hosts" file:

   192.168.1.2                     mobicents.open-ims.test
   192.168.1.3                     pcscf.open-ims.test
   192.168.1.3                     icscf.open-ims.test
   192.168.1.3                     scscf.open-ims.test
   192.168.1.3                     hss.open-ims.test
   192.168.1.3                     open-ims.test

   or follow DNS resolution and put nameserver entry in /etc/resolv.conf
III. Run

To run one has to follow step 6: http://www.openimscore.org/installation_guide#step6
To configure AS one has to follow: http://www.mobicents.org/mss-diameter_sh.html , but with consideration of IP/domain change.
    
      

IV.   Possible problems
There is known issue with vmware player(on some machines it does not work properly). There is a way to use virtualbox (since it is able to read vmdk file). 
This requires change in xorg.conf - graphic card type must be cahnged from "vmware" to "vesa" (or other emualted). Also virtualbox may require
some addons, instructions can be found here: http://blog.spind.net/2009/05/21/centos-5-64-on-sun-virtualbox-on-fedora-10-64/