Browse code

Improved the view of some sections

Nils Ohlmeier authored on 21/07/2003 18:01:45
Showing 1 changed files
... ...
@@ -14,6 +14,13 @@
14 14
 			<firstname>Dan</firstname>
15 15
 			<surname>Austin</surname>
16 16
 		</author>
17
+		<editor>
18
+			<firstname>Nils</firstname>
19
+			<surname>Ohlmeier</surname>
20
+			<address>
21
+				<email>nils@iptel.org</email>
22
+			</address>
23
+		</editor>
17 24
 	</authorgroup>
18 25
 	<copyright>
19 26
 		<year>2002-2003</year>
... ...
@@ -78,8 +85,36 @@ The newest release may be found in the folder /latest
78 85
 	<section>
79 86
 		<title>Installation Notes</title>
80 87
 		<para>
81
-Supported architectures: Linux/i386, Linux/armv4l, FreeBSD/i386, OpenBSD/i386
82
-Solaris/sparc64
88
+Supported architectures:
89
+		</para>
90
+		<itemizedlist>
91
+			<listitem>
92
+			<para>
93
+			Linux/i386
94
+			</para>
95
+			</listitem>
96
+			<listitem>
97
+			<para>
98
+			Linux/armv4l
99
+			</para>
100
+			</listitem>
101
+			<listitem>
102
+			<para>
103
+			FreeBSD/i386
104
+			</para>
105
+			</listitem>
106
+			<listitem>
107
+			<para>
108
+			OpenBSD/i386
109
+			</para>
110
+			</listitem>
111
+			<listitem>
112
+			<para>
113
+			Solaris/sparc64
114
+			</para>
115
+			</listitem>
116
+		</itemizedlist>
117
+		<para>
83 118
 (For other architectures the Makefiles might need to be edited)
84 119
 There are various configuration options defined in the Make file.
85 120
 		</para>
... ...
@@ -105,8 +140,7 @@ flex
105 140
 		</listitem>
106 141
 		<listitem>
107 142
 		<para>
108
-GNU make (on Linux this is the standard "make", on FreeBSD and Solaris is
109
- called "gmake")
143
+GNU make (on Linux this is the standard <quote>make</quote>, on FreeBSD and Solaris is called <quote>gmake</quote>)
110 144
 		</para>
111 145
 		</listitem>
112 146
 		<listitem>
... ...
@@ -116,28 +150,27 @@ sed and tr (used in the make files)
116 150
 		</listitem>
117 151
 		<listitem>
118 152
 		<para>
119
-GNU tar ("gtar" on Solaris) and gzip if you want "make tar" to work
153
+GNU tar (<quote>gtar</quote> on Solaris) and gzip if you want <quote>make tar</quote> to work
120 154
 		</para>
121 155
 		</listitem>
122 156
 		<listitem>
123 157
 		<para>
124
-GNU install or BSD install (on Solaris "ginstall") if you want "make
125
-  install", "make bin", "make sunpkg" to work
158
+GNU install or BSD install (on Solaris <quote>ginstall</quote>) if you want <quote>make install</quote>, <quote>make bin</quote>, <quote>make sunpkg</quote> to work
126 159
 		</para>
127 160
 		</listitem>
128 161
 		<listitem>
129 162
 		<para>
130
-?mysql? if you need MySQL support
163
+<quote>mysql</quote> if you need MySQL support
131 164
 		</para>
132 165
 		</listitem>
133 166
 		<listitem>
134 167
 		<para>
135
-?Apache (httpd)? if you want serweb support
168
+<quote>Apache (httpd)</quote> if you want serweb support
136 169
 		</para>
137 170
 		</listitem>
138 171
 		<listitem>
139 172
 		<para>
140
-?PHP, MySQL-PHP? for serweb support
173
+<quote>PHP, MySQL-PHP</quote> for serweb support
141 174
 		</para>
142 175
 		</listitem>
143 176
 		<listitem>
... ...
@@ -158,41 +191,65 @@ Installing SER on a RedHat Linux distribution for example, is a simple matter of
158 191
 	<section>
159 192
 		<title>Install the package</title>
160 193
 		<para>
161
-Example /root>rpm -i ser-08.10-2.i386.rpm
194
+Example:
162 195
 		</para>
196
+		<screen>
197
+		/root>rpm -i ser-08.10-2.i386.rpm
198
+		</screen>
163 199
 		<para>
164 200
 Packages for other popular distributions are available, and can be installed using the appropriate package manager for that distribution.
165 201
 		</para>
166 202
 		<para>
167
-On many platforms you can start the service with /etc/init.d/ser start.  RedHat systems will use /etc/rc.d/init.d/ser start.
203
+On many platforms you can start the service with:
168 204
 		</para>
205
+		<screen>
206
+	/etc/init.d/ser start
207
+		</screen>
208
+		<para>
209
+		RedHat systems will use:
210
+		</para>
211
+		<screen>
212
+	/etc/rc.d/init.d/ser start
213
+		</screen>
169 214
 		<para>
170 215
 You now have a functioning SIP server, but what can you do with it?  At this point not very much.  With an SIP client, such as Microsoft MSN Messenger 4.6, you can register with the server, send Instant Messages to other logged on clients of the same server, and even have voice conversations with them.
171 216
 		</para>
172 217
 		<para>
173
-That sounds pretty good, but maybe you?d like to add a little more security, or make you server accessible to others.
218
+That sounds pretty good, but maybe you'd like to add a little more security, or make you server accessible to others.
174 219
 		</para>
175 220
 	</section>
176 221
 	<section>
177 222
 		<title>Serctl Utility</title>
178 223
 		<para>
179
-To do so, first set the environment variable SIP_DOMAIN to your domain name, e.g., in Bourne shell, call export SIP_DOMAIN=<quote>foo.bar</quote>
224
+To do so, first set the environment variable SIP_DOMAIN to your domain name, e.g., in Bourne shell (bash), call:
180 225
 		</para>
226
+		<screen>
227
+		export SIP_DOMAIN=<quote>foo.bar</quote>
228
+		</screen>
181 229
 		<para>
182 230
 If you wont the system to created this variable automatically, you need to add the line
183 231
 		</para>
232
+		<screen>
233
+		export SIP_DOMAIN=<quote>foo.bar</quote>
234
+		</screen>
184 235
 		<para>
185
-export SIP_DOMAIN=<quote>foo.bar</quote> in the end of file /etc/profile.
236
+		in the end of file /etc/profile.
186 237
 		</para>
187 238
 		<para>
188 239
 If you are using other than 'localhost' mysql server for maintaining subscriber database, change the variable 'SQL_HOST' to the proper host name in the serctl script.
189 240
 		</para>
190 241
 		<para>
191
-Run the serctl utility  /usr/sbin/serctl monitor.
242
+Run the serctl utility
192 243
 		</para>
244
+		<screen>
245
+		/usr/sbin/serctl monitor
246
+		</screen>
193 247
 		<para>
194
-       /usr/local/sbin/serctl monitor  (if you installed from a tar.gz or Solaris package).
248
+If you installed from a tar.gz or Solaris package:
195 249
 		</para>
250
+		<screen>
251
+		/usr/local/sbin/serctl monitor
252
+		</screen>
196 253
 	</section>
197 254
 	<section>
198 255
 		<title>DNS SVR Resource Records</title>
... ...
@@ -205,20 +262,20 @@ These requirements can be meet by using DNS SVR Resource Records, available in B
205 262
 		<para>
206 263
 The format for a SVR RR is this:
207 264
 		</para>
208
-		<programlisting>
209
-_service._protocol        SVR Priority Weight     Port hostname
210
-		</programlisting>
265
+		<screen>
266
+		_service._protocol        SVR Priority Weight     Port hostname
267
+		</screen>
211 268
 		<para>
212 269
 In this case we want to establish an entry for our primary SIP server, gateway.mydomain.com, that will listen on UDP port 5060.  The entry will look like this:
213 270
 		</para>
214
-		<programlisting>
215
-_sip._udp         SRV     0  0   5060  gateway.mydomain.com
216
-		</programlisting>
271
+		<screen>
272
+		_sip._udp         SRV     0  0   5060  gateway.mydomain.com
273
+		</screen>
217 274
 		<para>
218 275
 Placement of the new resource record is important.  Here is a sample zone file:
219 276
 		</para>
220 277
 		<para>
221
-		<programlisting>
278
+		<screen>
222 279
 ; zone 'mydomain.com'   last serial 1998071308
223 280
 $ORIGIN com.
224 281
 mydomain  86400           IN      SOA     gateway.mydomain.com. postmaster.mydomain.com. (
... ...
@@ -237,19 +294,19 @@ $ORIGIN fitawi.com.
237 294
 _sip._udp               SRV  0 0  5060  gateway.mydomain.com.
238 295
 gateway         IN      A               192.168.0.1
239 296
 www             IN      CNAME           gateway.mydomain.com.
240
-		</programlisting>
297
+		</screen>
241 298
 		</para>
242 299
 		<para>
243 300
 After reloading your zone file you can verify that the entry is working by using dig.
244 301
 		</para>
245
-		<para>
302
+		<screen>
246 303
         dig -t SRV _sip._udp.mydomain.com
247
-		</para>
304
+		</screen>
248 305
 		<para>
249 306
 The results should look something like this:
250 307
 		</para>
251 308
 		<para>
252
-		<programlisting>
309
+		<screen>
253 310
 ; &lt;&lt;>> DiG 9.1.0 &lt;&lt;>> -t SRV _sip._udp.mydomain.com
254 311
 ;; global options:  printcmd
255 312
 ;; Got answer:
... ...
@@ -273,7 +330,7 @@ gateway. mydomain.com.     86400   IN      A       192.168.0.150
273 330
 ;; SERVER: 192.168.0.150#53(192.168.0.150)
274 331
 ;; WHEN: Tue Dec  3 08:34:17 2002
275 332
 ;; MSG SIZE  rcvd: 132
276
-		</programlisting>
333
+		</screen>
277 334
 		</para>
278 335
 	</section>
279 336
 	<section>
... ...
@@ -291,26 +348,29 @@ To install support for a MySQL database you will need to download the package se
291 348
 If you do not already have a copy of MySQL installed, download it from your <ulink url="http://www.mysql.com"></ulink>
292 349
 		</para>
293 350
 		<para>
294
-Once you have MySQL installed and started, execute /usr/sbin/ser_mysql.sh.
351
+Once you have MySQL installed and started, execute
295 352
 		</para>
353
+		<screen>
354
+		/usr/sbin/ser_mysql.sh
355
+		</screen>
296 356
 		<para>
297 357
 You can verify that the database has been created, and correct permissions assigned by using the mysql management tool and these steps:
298 358
 		</para>
299 359
 		<para>
300
-		<programlisting>
360
+		<screen>
301 361
 Mysql> select * from user;
302 362
 | Host               | User  | Password         | Select_priv | Insert_priv | Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv | Index_priv | Alter_priv |
303 363
 | %                  | ser   | 4e633cf914a735a0 | N           | N           | N           | N           | N           | N         | N           | N             | N            | N         | N          | N               | N          | N          |
304 364
 | localhost          | ser   | 4e633cf914a735a0 | Y           | Y           | Y           | Y           | Y           | Y         | Y           | Y             | Y            | Y         | N          | Y               | Y          | Y          |
305 365
 | %                  | serro | 7cb73a267cb7bd5f | N           | N           | N           | N           | N           | N         | N           | N             | N            | N         | N          | N               | N          | N          |
306 366
 | localhost          | serro | 7cb73a267cb7bd5f | Y           | N           | N           | N           | N           | N         | N           | N             | N            | N         | N          | N               | N          | N          |
307
-		</programlisting>
367
+		</screen>
308 368
 		</para>
309 369
 		<para>
310 370
 The above results show that the two user, ser and serro, have been created and granted the permissions needed to access the database.  Note that in the above example the permissions have been modified to deny access to these accounts from any system(%) other than local host.
311 371
 		</para>
312 372
 		<para>
313
-		<programlisting>
373
+		<screen>
314 374
 mysql> connect ser;
315 375
 Connection id:    294
316 376
 Current database: ser
... ...
@@ -339,7 +399,7 @@ mysql> show tables;
339 399
 mysql> select * from subscriber;
340 400
 | phplib_id                        | USER_ID | PASSWORD | FIRST_NAME | LAST_NAME | PHONE        | EMAIL_ADDRESS              | DATETIME_CREATED    | DATETIME_MODIFIED   | confirmation                     | flag | SendNotification | Greeting | HA1                              | REALM      | ha1b                             | perms | allow_find | timezone            |
341 401
 | 4cefa7a4d3c8c2dbf6328520bd873a19 | admin     | heslo | first        | admin    | 557-8469     | admin@iptel.org      | 2002-12-02 19:20:41 | 2002-12-02 20:29:46 | 80e0f273b2067d40277b49ff842bb9e3 | o    |                  |          | c79a8f8f08596baa84bb02c88884426d | iptel.org | f322c94b8b2fbe557d43ab3ac9e05b3a | admin | 1          | America/Los_Angeles |
342
-		</programlisting>
402
+		</screen>
343 403
 		</para>
344 404
 		<para>
345 405
 This last query shows that you have one user account defined and it has administrator privileges.
... ...
@@ -359,21 +419,21 @@ Now that we have a working MySQL database, we need to modify the configuration f
359 419
 		<para>
360 420
 To enable support for the new MySQL database we need to load the appropriate module.  That is accomplished by uncomment this line:
361 421
 		</para>
362
-		<para>
363
-loadmodule "//usr/lib/ser/modules/mysql.so
364
-		</para>
422
+		<screen>
423
+		loadmodule "//usr/lib/ser/modules/mysql.so
424
+		</screen>
365 425
 		<para>
366 426
 Next we need to set SER to use the database and write changes instead of just caching them in memory.  This is done by means of commenting this line:
367 427
 		</para>
368
-		<para>
369
-  modparam ("usrloc", "db_mode",  0)
370
-		</para>
428
+		<screen>
429
+		modparam ("usrloc", "db_mode",  0)
430
+		</screen>
371 431
 		<para>
372 432
 And uncomment this line:
373 433
 		</para>
374
-		<para>
375
-  modparam ("usrloc", "db_mode", 2)
376
-		</para>
434
+		<screen>
435
+		modparam ("usrloc", "db_mode", 2)
436
+		</screen>
377 437
 		<para>
378 438
 Note on db_modes:
379 439
 		</para>
... ...
@@ -408,12 +468,10 @@ Periodically writes contact information to the database based in the in memory c
408 468
 		<para>
409 469
 We have the option of storing passwords in our database in plain text.  This allows for password recovery and makes the initial setup and testing easier.  To enable this feature uncomment these lines:
410 470
 		</para>
411
-		<para>
412
-  modparam (<quote>auth</quote>, <quote>calculate_ha1</quote>, yes)
413
-		</para>
414
-		<para>
415
-  modparam (<quote>auth</quote>, <quote>password_column</quote>, <quote>password</quote>)
416
-		</para>
471
+		<screen>
472
+		modparam (<quote>auth</quote>, <quote>calculate_ha1</quote>, yes)
473
+	modparam (<quote>auth</quote>, <quote>password_column</quote>, <quote>password</quote>)
474
+		</screen>
417 475
 		<para>
418 476
 These lines work together.  The first tells SER to generate a hash based on username, password and realm.  The second tells SER where to look for the plain-text password in the database.
419 477
 		</para>
... ...
@@ -427,16 +485,19 @@ Change (uri==?myself?) to (uri=~?mydomain.com?)
427 485
 Uncomment these lines and change all instances of iptel.org to mydomain.com
428 486
 		</para>
429 487
 		<para>
430
-		<programlisting>
488
+		<screen>
431 489
 if (!www_authorize("mydomain.com", "subscriber")) {
432 490
         www_challenge("mydomain.com", "0");
433 491
         break;
434 492
 };
435
-		</programlisting>
493
+		</screen>
436 494
 		</para>
437 495
 		<para>
438
-We're now ready to restart ser.  On RedHat use /etc/rc.d/init.d/ser restart
496
+We're now ready to restart ser.  On RedHat use
439 497
 		</para>
498
+		<screen>
499
+		/etc/rc.d/init.d/ser restart
500
+		</screen>
440 501
 	</section>
441 502
 	<section>
442 503
 		<title>Adding an admin for your realm</title>
... ...
@@ -449,9 +510,9 @@ Basic account manipulation can be performed with the serctl script, located in /
449 510
 		<para>
450 511
 To add a user use these commands
451 512
 		</para>
452
-		<para>
453
-serctl add JoeUser qwerty joe@mydomain.com
454
-		</para>
513
+		<screen>
514
+		serctl add JoeUser qwerty joe@mydomain.com
515
+		</screen>
455 516
 		<para>
456 517
 The system notify for <quote>Type MySQL Password</quote>, the default password is <quote>heslo</quote>
457 518
 		</para>
... ...
@@ -459,7 +520,7 @@ The system notify for <quote>Type MySQL Password</quote>, the default password i
459 520
 To make JoeUser an administrator, we need to logon to MySQL and modify the database.
460 521
 		</para>
461 522
 		<para>
462
-		<programlisting>
523
+		<screen>
463 524
 mysql> connect ser;
464 525
 
465 526
 mysql> update subscriber set perms=?admin? where USER_ID=?JoeUser?;
... ...
@@ -468,7 +529,7 @@ Rows matched: 1  Changed: 1  Warnings: 0
468 529
 
469 530
 mysql> select * from subscriber;
470 531
 | 4cefa7a4d3c8c2dbf6328520bd873a19 | JoeUser     | qwerty |  |   |   | joe@mydomain.com   | 2002-12-02 19:20:41 | 2002-12-02 20:29:46 | 80e0f273b2067d40277b49ff842bb9e3 | o    |                  |          | c79a8f8f08596baa84bb02c88884426d | mydomain.com | f322c94b8b2fbe557d43ab3ac9e05b3a | admin | 1          | America/Los_Angeles |
471
-		</programlisting>
532
+		</screen>
472 533
 		</para>
473 534
 		<para>
474 535
 The third from last field shows that Joe has been assigned admin privileges.
... ...
@@ -483,7 +544,7 @@ At this point Joe can logon to our server, but since he is the only user, there
483 544
 The script serctl can be used to manage users, access control lists, in memory contacts, and to monitor server health.  Executing serctl with no arguments will produce this output:
484 545
 		</para>
485 546
 		<para>
486
-		<programlisting>
547
+		<screen>
487 548
 usage:
488 549
            * subscribers *
489 550
  serctl add &lt;username> &lt;password> &lt;email> .. add a new subscriber (*)
... ...
@@ -514,7 +575,7 @@ usage:
514 575
    If the variable PW is set, the password will not be prompted.
515 576
 
516 577
      ACL privileges are: local ld int voicemail free-pstn
517
-		</programlisting>
578
+		</screen>
518 579
 		</para>
519 580
 	</section>
520 581
 	<section>
... ...
@@ -522,26 +583,22 @@ usage:
522 583
 		<para>
523 584
 User account management is performed with these commands:
524 585
 		</para>
525
-		<para>
526
-serctl add
527
-		</para>
528
-		<para>
529
-serctl password
530
-		</para>
531
-		<para>
532
-serctl rm
533
-		</para>
586
+		<screen>
587
+		serctl add
588
+	serctl password
589
+	serctl rm
590
+		</screen>
534 591
 		<para>
535 592
 The contents of the in memory cache can be managed with the ul argument.  Care must be taken to with these commands.  For example:
536 593
 		</para>
537
-		<para>
538
-serctl ul rm joe
539
-		</para>
594
+		<screen>
595
+		serctl ul rm joe
596
+		</screen>
540 597
 		<para>
541 598
 Will remove the current contact information about Joe from memory
542 599
 		</para>
543 600
 		<para>
544
-Whereas serctl rm joe will delete joe?s account.
601
+Whereas <quote>serctl rm joe</quote> will delete joe's account.
545 602
 		</para>
546 603
 	</section>
547 604
 	<section>
... ...
@@ -550,7 +607,7 @@ Whereas serctl rm joe will delete joe?s account.
550 607
 The command <quote>serctl ul show</quote> will list any currently registered clients.  The output will look like this:
551 608
 		</para>
552 609
 		<para>
553
-		<programlisting>
610
+		<screen>
554 611
 ===Domain list===
555 612
 ---Domain---
556 613
 name : 'location'
... ...
@@ -598,7 +655,7 @@ prev   : (nil)
598 655
 
599 656
 ---/Domain---
600 657
 ===/Domain list===
601
-		</programlisting>
658
+		</screen>
602 659
 		</para>
603 660
 	</section>
604 661
 	<section>
... ...
@@ -607,7 +664,7 @@ prev   : (nil)
607 664
 Two commands can be used to check the health of the server.  The first command serctl ps returns a list of all SER related processes, the ip address and the port they are listening on.  For example:
608 665
 		</para>
609 666
 		<para>
610
-		<programlisting>
667
+		<screen>
611 668
 [root@gateway /root]# serctl ps
612 669
 0       31029   attendant
613 670
 1       31033   receiver child=0 sock=0 @ 127.0.0.1::5060
... ...
@@ -620,13 +677,13 @@ Two commands can be used to check the health of the server.  The first command s
620 677
 8       31040   receiver child=3 sock=1 @ 192.168.0.1::5060
621 678
 9       31049   fifo server
622 679
 10      31072   timer
623
-		</programlisting>
680
+		</screen>
624 681
 		</para>
625 682
 		<para>
626 683
 The second command, serctl monitor, shows the server version, uptime, pending and completed transactions, and the number of major category responses the server has sent.  Another example:
627 684
 		</para>
628 685
 		<para>
629
-		<programlisting>
686
+		<screen>
630 687
 [cycle #: 1; if constant make sure server lives and fifo is on]
631 688
 Server: Sip EXpress router (0.8.10 (i386/linux)
632 689
 Now: Wed Dec  4 10:13:02 2002
... ...
@@ -650,14 +707,14 @@ failures: 0
650 707
 UsrLoc Stats
651 708
 Domain Registered Expired
652 709
 'location' 2 2
653
-		</programlisting>
710
+		</screen>
654 711
 		</para>
655 712
 	</section>
656 713
 	</chapter>
657 714
 	<chapter>
658 715
 	<title>Installing SERweb</title>
659 716
 	<para>
660
-The SERweb package can be downloaded from ftp://ftp.berlios.de/ser/latest/serweb
717
+The SERweb package can be downloaded from <ulink url="ftp://ftp.berlios.de/ser/latest/serweb"></ulink>
661 718
 	</para>
662 719
 	<para>
663 720
 The pages associated with SERweb provide a starting point to customize your SIP user account management tools.
... ...
@@ -683,13 +740,13 @@ In case your server performs multiple functions, and you want to just add the SE
683 740
 Unzip the files into a temporary directory, such as /root/serweb.  The directory will contain these files:
684 741
 		</para>
685 742
 		<para>
686
-		<programlisting>
743
+		<screen>
687 744
 -rw-rw-r--    1 827      2020        18561 Sep 25 16:31 COPYING
688 745
 drwxr-xr-x    2 827      2020         1024 Nov 27 16:43 CVS
689 746
 -rw-rw-r--    1 827      2020          529 Sep 25 16:29 README
690 747
 drwxr-xr-x    7 827      2020         1024 Nov 27 22:24 html
691 748
 drwxr-xr-x    3 827      2020         2048 Sep 26 10:26 phplib
692
-		</programlisting>
749
+		</screen>
693 750
 		</para>
694 751
 		<para>
695 752
 On the Linux RedHat Version 8 root directory on web server is /var/www/html/
... ...
@@ -697,36 +754,32 @@ On the Linux RedHat Version 8 root directory on web server is /var/www/html/
697 754
 		<para>
698 755
 Move the html directory to the root of your web server:
699 756
 		</para>
700
-		<para>
701
-mv html /var/www/html/htdocs/serweb
702
-		</para>
757
+		<screen>
758
+		mv html /var/www/html/htdocs/serweb
759
+		</screen>
703 760
 		<para>
704 761
 Move the phplib directory to your web server application directory:
705 762
 		</para>
763
+		<screen>
764
+		mv phplib /var/www/html/phplib
765
+		</screen>
706 766
 		<para>
707
-mv phplib /var/www/html/phplib
708
-		</para>
709
-		<para>
710
-Following files must be updated with this ?new? path to the libraries:
711
-		</para>
712
-		<para>
713
-./admin/prepend.php
714
-		</para>
715
-		<para>
716
-./user_interface/prepend.php
717
-		</para>
718
-		<para>
719
-./user_interface/reg/prepend.php
767
+Following files must be updated with this <quote>new</quote> path to the libraries:
720 768
 		</para>
769
+		<screen>
770
+		./admin/prepend.php
771
+	./user_interface/prepend.php
772
+	./user_interface/reg/prepend.php
773
+		</screen>
721 774
 		<para>
722 775
 For these files the variable: $_PHPLIB[<quote>libdir</quote>]  = <quote>../../phplib/</quote>; becomes $_PHPLIB[<quote>libdir</quote>]  = <quote>../../../phplib/</quote>;
723 776
 		</para>
724 777
 		<para>
725 778
 In the ./admin directory edit the files acl.php, index.php, and users.php will need their path to the forms library updated.  For this example, add ../ to the existing line
726 779
 		</para>
727
-		<para>
728
-:require <quote>../../../phplib/oohforms.inc</quote>;
729
-		</para>
780
+		<screen>
781
+		:require <quote>../../../phplib/oohforms.inc</quote>;
782
+		</screen>
730 783
 		<para>
731 784
 In the ./user_interface directory the following files need the same change:
732 785
 		</para>
... ...
@@ -742,15 +795,11 @@ Finish.php, get_pass.php, index.php
742 795
 		<para>
743 796
 The last changes occur in the config.php file to provide the location for graphic files, style sheets and time zone information.  Update the following variables:
744 797
 		</para>
745
-		<para>
746
-$this->root_path=<quote>/serweb/</quote>;
747
-		</para>
748
-		<para>
749
-$this->fifo_server = <quote>/tmp/ser_fifo</quote>;
750
-		</para>
751
-		<para>
752
-$this->zonetab_file =   <quote>/usr/share/zoneinfo/zone.tab</quote>;
753
-		</para>
798
+		<screen>
799
+		$this->root_path=<quote>/serweb/</quote>;
800
+	$this->fifo_server = <quote>/tmp/ser_fifo</quote>;
801
+	$this->zonetab_file =   <quote>/usr/share/zoneinfo/zone.tab</quote>;
802
+		</screen>
754 803
 		<para>
755 804
 //TZ zone descriptions file, usually: /usr/share/zoneinfo/zone.tab
756 805
 		</para>
... ...
@@ -772,23 +821,19 @@ This will insure sending a registration feedback mail to SIP server using its IP
772 821
 		<para>
773 822
 We need to update /usr/local/apache/htdocs/serweb/config.php to represent our realm.  The following variables need to be changed to our domain:
774 823
 		</para>
775
-		<para>
776
-$this->realm=<quote>mydomain.com</quote>;
777
-		</para>
778
-		<para>
779
-$this->domainname=<quote> mydomain.com</quote>;
780
-		</para>
781
-		<para>
782
-$this->web_contact=<quote>sip:JoeUser@ mydomain.com</quote>;
783
-		</para>
824
+		<screen>
825
+		$this->realm=<quote>mydomain.com</quote>;
826
+	$this->domainname=<quote> mydomain.com</quote>;
827
+	$this->web_contact=<quote>sip:JoeUser@ mydomain.com</quote>;
828
+		</screen>
784 829
 		<para>
785 830
 //address of pseudo sender
786 831
 		</para>
832
+		<screen>
833
+		$this->default_domain=<quote> mydomain.com</quote>;
834
+	$this->mail_header_from=<quote>Registration@ mydomain.com</quote>;
835
+		</screen>
787 836
 		<para>
788
-$this->default_domain=<quote> mydomain.com</quote>;
789
-		</para>
790
-		<para>
791
-$this->mail_header_from=<quote>Registration@ mydomain.com</quote>;
792 837
 		</para>
793 838
 		<para>
794 839
 Additionally we will want to modify the section for Terms and Conditions, either replacing it with appropriate language for our services, or at least replacing iptel.org with our domain information.
... ...
@@ -829,9 +874,9 @@ Detailed information about the communications between clients and the SIP server
829 874
 		<para>
830 875
 Ngrep is a capable of listening in on network traffic and filtering it in much the same way as grep can locate patterns in files.  To monitor the communications between a client, joe, and the server the following command would be run on the server:
831 876
 		</para>
832
-		<para>
833
-ngrep  -n 5060 -d eth0 joe
834
-		</para>
877
+		<screen>
878
+		ngrep  -n 5060 -d eth0 joe
879
+		</screen>
835 880
 		<para>
836 881
 Since SIP communications are ASCII based, all events such as REGISTER, INVITE, SUBSCRIBE, etc. are captured.  The output of ngrep can identify problems with SIP addresses, or client identity.
837 882
 		</para>
... ...
@@ -972,14 +1017,14 @@ sip-server ipv4:192.168.0.1      **  IP address of our SIP server
972 1017
 The following is an extremely simple sample of how to relay a call from a SIP client to the PSTN
973 1018
 		</para>
974 1019
 		<para>
975
-		<programlisting>
1020
+		<screen>
976 1021
 # attempt handoff to PSTN
977 1022
                  if (uri=~<quote>^sip:9[0-9]*@mydomain.com</quote>) {  ##  This assumes that the caller is
978 1023
                         log(<quote>Forwarding to PSTN\n</quote>);      ##  registered in our realm
979 1024
                         t_relay_to( <quote>192.168.0.2</quote>, <quote>5060</quote>);  ##  Our Cisco router
980 1025
                         break;
981 1026
                  };
982
-		</programlisting>
1027
+		</screen>
983 1028
 		</para>
984 1029
 	</section>
985 1030
 	</chapter>