There is no specific tutorial but the addition of a new application server can be done in few steps using the FHoSS web interface:
1. Create the application server entry, assign the routable SIP address for that application server. The choice for “Default handling” indicates to the S-CSCF what should be done with the SIP session in case that the SIP AS address is not reachable.
2. Define a trigger point that matches the criteria to trigger one of the applications on the app server
3. link the application server to the trigger point by creating a new intial Filter Criteria (iFC)
4. add the iFC to the service profile of the applicable users (e.g. the "default_sp")
5. make sure that the service profile is assigned to the users public identity in the user profile section and prioritize their handling in the S-CSCF (0 has the highest priority)
Depanding on the incoming message descriptions given in the trigger point defintion you have many options to trigger specific AS addresses via certain iFC definitions for almost any scenario. Per default, we just provide one service profile with a simple iFC for an imagined presence server.
The usual problem that occurs when the additional resources are generated, through ant gen, without a current Intenet connection is:
Error reading import file 'http://www.w3.org/2001/xml.xsd': java.net.NoRouteToHostException: No route to host.
This occurs because the source generator tries to import the specified file from the remote address. The solution is:
<xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="file:///opt/OpenIMSCore/FHoSS/xsd/xml.xsd"/>
ant gen