--- a/doc/app_acct.conf.sample	Wed Sep 01 16:49:02 2010 +0900
+++ b/doc/app_acct.conf.sample	Fri Sep 03 16:46:16 2010 +0900
@@ -44,7 +44,7 @@
 #  "AVP-dictionary-name";
 #
 # Note that at the moment, GROUPED AVP are not supported. Also, only the top-level AVPs are
-# search. This behavior can be changed quite easily if needed.
+# searched. This behavior can be changed quite easily if needed.
 
 # The following list is informative only.
 # You may also consult RFC4005 sections 10.2.1 and 10.2.2 for other examples
@@ -107,8 +107,9 @@
 # "Route-Record" = { multi=5; }; # Record the last 5 hops of the message
 
 # This is the database table corresponding to this list:
-# CREATE TABLE app_acct (
+# CREATE TABLE incoming (
 #     "recorded_on" timestamp with time zone NOT NULL,
+#     "recorded_serv" bytea NOT NULL,
 #     "Origin-Host" bytea NOT NULL,
 #     "Origin-Realm" bytea NOT NULL,
 #     "Destination-Realm" bytea,
@@ -194,9 +195,14 @@
 # Timestamp_field:
 # Optionaly, you can specify a name of a field that will receive the value 'now' when a new record is inserted.
 # Default: no timestamp is inserted.
-# Example: Timestamp_field = "inc_ts";
+# Example: Timestamp_field = "recorded_on";
+
+# Server_name_field:
+# Optionaly, you can specify a field which will receive the Diameter Identity of the local server for each record saved.
+# This is useful especially if you have several Accounting servers and want to check Load-Balancing behavior or so,
+# after aggregating all the data.
+# Default: no server name inserted.
+# Example: Server_name_field = "recorded_serv";
 
 
 
-
-