Browse code

modules_k/*: moved k modules in directory modules/

Daniel-Constantin Mierla authored on 20/01/2013 11:57:52
Showing 1 changed files
1 1
deleted file mode 100644
... ...
@@ -1,80 +0,0 @@
1
-Presence_MWI Module
2
-
3
-Juha Heinanen
4
-
5
-   <jh@tutpro.com>
6
-
7
-Edited by
8
-
9
-Juha Heinanen
10
-
11
-   <jh@tutpro.com>
12
-
13
-   Copyright © 2007 Juha Heinanen
14
-     __________________________________________________________________
15
-
16
-   Table of Contents
17
-
18
-   1. Admin Guide
19
-
20
-        1. Overview
21
-        2. Dependencies
22
-
23
-              2.1. Kamailio Modules
24
-              2.2. External Libraries or Applications
25
-
26
-        3. Parameters
27
-        4. Functions
28
-
29
-Chapter 1. Admin Guide
30
-
31
-   Table of Contents
32
-
33
-   1. Overview
34
-   2. Dependencies
35
-
36
-        2.1. Kamailio Modules
37
-        2.2. External Libraries or Applications
38
-
39
-   3. Parameters
40
-   4. Functions
41
-
42
-1. Overview
43
-
44
-   The module does specific handling for notify-subscribe message-summary
45
-   (message waiting indication) events as specified in RFC 3842. It is
46
-   used with the general event handling module, presence. It constructs
47
-   and adds message-summary event to it.
48
-
49
-   The module does not currently implement any authorization rules. It
50
-   assumes that publish requests are only issued by a voicemail
51
-   application and subscribe requests only by the owner of voicemail box.
52
-   Authorization can thus be easily done by Kamailio configuration file
53
-   before calling handle_publish() and handle_subscribe() functions.
54
-
55
-   The module implements a simple check of content type
56
-   “application/simple-message-summary:” Content must start with
57
-   “Messages-Waiting” status line followed by zero or more lines that
58
-   consist of tabs and printable ASCII characters.
59
-
60
-2. Dependencies
61
-
62
-   2.1. Kamailio Modules
63
-   2.2. External Libraries or Applications
64
-
65
-2.1. Kamailio Modules
66
-
67
-   The following modules must be loaded before this module:
68
-     * presence.
69
-
70
-2.2. External Libraries or Applications
71
-
72
-   None.
73
-
74
-3. Parameters
75
-
76
-   None.
77
-
78
-4. Functions
79
-
80
-   None to be used in configuration file.
Browse code

modules*: regenerated readmes

Daniel-Constantin Mierla authored on 02/10/2011 08:53:35
Showing 1 changed files
... ...
@@ -23,8 +23,8 @@ Juha Heinanen
23 23
               2.1. Kamailio Modules
24 24
               2.2. External Libraries or Applications
25 25
 
26
-        3. Exported Parameters
27
-        4. Exported Functions
26
+        3. Parameters
27
+        4. Functions
28 28
 
29 29
 Chapter 1. Admin Guide
30 30
 
... ...
@@ -36,8 +36,8 @@ Chapter 1. Admin Guide
36 36
         2.1. Kamailio Modules
37 37
         2.2. External Libraries or Applications
38 38
 
39
-   3. Exported Parameters
40
-   4. Exported Functions
39
+   3. Parameters
40
+   4. Functions
41 41
 
42 42
 1. Overview
43 43
 
... ...
@@ -71,10 +71,10 @@ Chapter 1. Admin Guide
71 71
 
72 72
    None.
73 73
 
74
-3. Exported Parameters
74
+3. Parameters
75 75
 
76 76
    None.
77 77
 
78
-4. Exported Functions
78
+4. Functions
79 79
 
80 80
    None to be used in configuration file.
Browse code

docs: cleanup in xml files

- useless revision history removed
- docs depend on entities.xml
- updated global entities
- fixed the links to users and devel mailing lists
- fixed the link to tracker

Daniel-Constantin Mierla authored on 18/06/2011 21:21:41
Showing 1 changed files
... ...
@@ -10,10 +10,7 @@ Juha Heinanen
10 10
 
11 11
    <jh@tutpro.com>
12 12
 
13
-   Copyright � 2007 Juha Heinanen
14
-   Revision History
15
-   Revision $Revision: 1 $ $Date: 2007-04-30 14:05:57 +0200 (Mon, 30 Jan
16
-   2007) $
13
+   Copyright © 2007 Juha Heinanen
17 14
      __________________________________________________________________
18 15
 
19 16
    Table of Contents
... ...
@@ -56,8 +53,8 @@ Chapter 1. Admin Guide
56 53
    before calling handle_publish() and handle_subscribe() functions.
57 54
 
58 55
    The module implements a simple check of content type
59
-   "application/simple-message-summary:" Content must start with
60
-   "Messages-Waiting" status line followed by zero or more lines that
56
+   “application/simple-message-summary:” Content must start with
57
+   “Messages-Waiting” status line followed by zero or more lines that
61 58
    consist of tabs and printable ASCII characters.
62 59
 
63 60
 2. Dependencies
Browse code

Updates (doxygen documentation) to message waiting indication module

oej authored on 25/10/2009 20:03:57
Showing 1 changed files
... ...
@@ -12,60 +12,72 @@ Juha Heinanen
12 12
 
13 13
    Copyright � 2007 Juha Heinanen
14 14
    Revision History
15
-   Revision $Revision: 1 $ $Date: 2007-04-30 14:05:57 +0200 (Mon,
16
-                           30 Jan 2007) $
17
-     __________________________________________________________
15
+   Revision $Revision: 1 $ $Date: 2007-04-30 14:05:57 +0200 (Mon, 30 Jan
16
+   2007) $
17
+     __________________________________________________________________
18 18
 
19 19
    Table of Contents
20 20
 
21 21
    1. Admin Guide
22 22
 
23
-        1.1. Overview
24
-        1.2. Dependencies
23
+        1. Overview
24
+        2. Dependencies
25 25
 
26
-              1.2.1. Kamailio Modules
27
-              1.2.2. External Libraries or Applications
26
+              2.1. Kamailio Modules
27
+              2.2. External Libraries or Applications
28 28
 
29
-        1.3. Exported Parameters
30
-        1.4. Exported Functions
29
+        3. Exported Parameters
30
+        4. Exported Functions
31 31
 
32 32
 Chapter 1. Admin Guide
33 33
 
34
-1.1. Overview
34
+   Table of Contents
35
+
36
+   1. Overview
37
+   2. Dependencies
38
+
39
+        2.1. Kamailio Modules
40
+        2.2. External Libraries or Applications
35 41
 
36
-   The module does specific handling for notify-subscribe
37
-   message-summary (message waiting indication) events as
38
-   specified in RFC 3842. It is used with the general event
39
-   handling module, presence. It constructs and adds
40
-   message-summary event to it.
42
+   3. Exported Parameters
43
+   4. Exported Functions
41 44
 
42
-   The module does not currently implement any authorization
43
-   rules. It assumes that publish requests are only issued by a
44
-   voicemail application and subscribe requests only by the owner
45
-   of voicemail box. Authorization can thus be easily done by
46
-   Kamailio configuration file before calling handle_publish() and
47
-   handle_subscribe() functions.
45
+1. Overview
46
+
47
+   The module does specific handling for notify-subscribe message-summary
48
+   (message waiting indication) events as specified in RFC 3842. It is
49
+   used with the general event handling module, presence. It constructs
50
+   and adds message-summary event to it.
51
+
52
+   The module does not currently implement any authorization rules. It
53
+   assumes that publish requests are only issued by a voicemail
54
+   application and subscribe requests only by the owner of voicemail box.
55
+   Authorization can thus be easily done by Kamailio configuration file
56
+   before calling handle_publish() and handle_subscribe() functions.
48 57
 
49 58
    The module implements a simple check of content type
50
-   application/simple-message-summary: Content must start with
51
-   Messages-Waiting status line followed by zero or more lines
52
-   that consist of tabs and printable ASCII characters.
59
+   "application/simple-message-summary:" Content must start with
60
+   "Messages-Waiting" status line followed by zero or more lines that
61
+   consist of tabs and printable ASCII characters.
62
+
63
+2. Dependencies
53 64
 
54
-1.2. Dependencies
65
+   2.1. Kamailio Modules
66
+   2.2. External Libraries or Applications
55 67
 
56
-1.2.1. Kamailio Modules
68
+2.1. Kamailio Modules
57 69
 
58 70
    The following modules must be loaded before this module:
59 71
      * presence.
60 72
 
61
-1.2.2. External Libraries or Applications
73
+2.2. External Libraries or Applications
62 74
 
63 75
    None.
64 76
 
65
-1.3. Exported Parameters
77
+3. Exported Parameters
66 78
 
67 79
    None.
68 80
 
69
-1.4. Exported Functions
81
+4. Exported Functions
70 82
 
71 83
    None to be used in configuration file.
Browse code

* modules: presence_mwi, presence_xml, pua, pua_mi

Moved back to modules_k presence related modules, because they include
stuff from sl module that does not exist in modules yet.

Juha Heinanen authored on 18/04/2009 12:53:54
Showing 1 changed files
1 1
new file mode 100644
... ...
@@ -0,0 +1,71 @@
1
+Presence_MWI Module
2
+
3
+Juha Heinanen
4
+
5
+   <jh@tutpro.com>
6
+
7
+Edited by
8
+
9
+Juha Heinanen
10
+
11
+   <jh@tutpro.com>
12
+
13
+   Copyright � 2007 Juha Heinanen
14
+   Revision History
15
+   Revision $Revision: 1 $ $Date: 2007-04-30 14:05:57 +0200 (Mon,
16
+                           30 Jan 2007) $
17
+     __________________________________________________________
18
+
19
+   Table of Contents
20
+
21
+   1. Admin Guide
22
+
23
+        1.1. Overview
24
+        1.2. Dependencies
25
+
26
+              1.2.1. Kamailio Modules
27
+              1.2.2. External Libraries or Applications
28
+
29
+        1.3. Exported Parameters
30
+        1.4. Exported Functions
31
+
32
+Chapter 1. Admin Guide
33
+
34
+1.1. Overview
35
+
36
+   The module does specific handling for notify-subscribe
37
+   message-summary (message waiting indication) events as
38
+   specified in RFC 3842. It is used with the general event
39
+   handling module, presence. It constructs and adds
40
+   message-summary event to it.
41
+
42
+   The module does not currently implement any authorization
43
+   rules. It assumes that publish requests are only issued by a
44
+   voicemail application and subscribe requests only by the owner
45
+   of voicemail box. Authorization can thus be easily done by
46
+   Kamailio configuration file before calling handle_publish() and
47
+   handle_subscribe() functions.
48
+
49
+   The module implements a simple check of content type
50
+   application/simple-message-summary: Content must start with
51
+   Messages-Waiting status line followed by zero or more lines
52
+   that consist of tabs and printable ASCII characters.
53
+
54
+1.2. Dependencies
55
+
56
+1.2.1. Kamailio Modules
57
+
58
+   The following modules must be loaded before this module:
59
+     * presence.
60
+
61
+1.2.2. External Libraries or Applications
62
+
63
+   None.
64
+
65
+1.3. Exported Parameters
66
+
67
+   None.
68
+
69
+1.4. Exported Functions
70
+
71
+   None to be used in configuration file.
Browse code

* modules: peering, pua, pua_mi, presence, presence_xml, presence_mwi

Moved some k modules that don't exist in s from modules_k to modules.

Juha Heinanen authored on 18/04/2009 12:29:07
Showing 1 changed files
1 1
deleted file mode 100644
... ...
@@ -1,71 +0,0 @@
1
-Presence_MWI Module
2
-
3
-Juha Heinanen
4
-
5
-   <jh@tutpro.com>
6
-
7
-Edited by
8
-
9
-Juha Heinanen
10
-
11
-   <jh@tutpro.com>
12
-
13
-   Copyright � 2007 Juha Heinanen
14
-   Revision History
15
-   Revision $Revision: 1 $ $Date: 2007-04-30 14:05:57 +0200 (Mon,
16
-                           30 Jan 2007) $
17
-     __________________________________________________________
18
-
19
-   Table of Contents
20
-
21
-   1. Admin Guide
22
-
23
-        1.1. Overview
24
-        1.2. Dependencies
25
-
26
-              1.2.1. Kamailio Modules
27
-              1.2.2. External Libraries or Applications
28
-
29
-        1.3. Exported Parameters
30
-        1.4. Exported Functions
31
-
32
-Chapter 1. Admin Guide
33
-
34
-1.1. Overview
35
-
36
-   The module does specific handling for notify-subscribe
37
-   message-summary (message waiting indication) events as
38
-   specified in RFC 3842. It is used with the general event
39
-   handling module, presence. It constructs and adds
40
-   message-summary event to it.
41
-
42
-   The module does not currently implement any authorization
43
-   rules. It assumes that publish requests are only issued by a
44
-   voicemail application and subscribe requests only by the owner
45
-   of voicemail box. Authorization can thus be easily done by
46
-   Kamailio configuration file before calling handle_publish() and
47
-   handle_subscribe() functions.
48
-
49
-   The module implements a simple check of content type
50
-   application/simple-message-summary: Content must start with
51
-   Messages-Waiting status line followed by zero or more lines
52
-   that consist of tabs and printable ASCII characters.
53
-
54
-1.2. Dependencies
55
-
56
-1.2.1. Kamailio Modules
57
-
58
-   The following modules must be loaded before this module:
59
-     * presence.
60
-
61
-1.2.2. External Libraries or Applications
62
-
63
-   None.
64
-
65
-1.3. Exported Parameters
66
-
67
-   None.
68
-
69
-1.4. Exported Functions
70
-
71
-   None to be used in configuration file.
Browse code

- fix link entity names, patch from Carsten Gross - regenerate READMEs

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@4630 689a6050-402a-0410-94f2-e92a70836424

Henning Westerholt authored on 07/08/2008 09:15:08
Showing 1 changed files
... ...
@@ -1,4 +1,3 @@
1
-
2 1
 Presence_MWI Module
3 2
 
4 3
 Juha Heinanen
... ...
@@ -14,8 +13,8 @@ Juha Heinanen
14 13
    Copyright � 2007 Juha Heinanen
15 14
    Revision History
16 15
    Revision $Revision: 1 $ $Date: 2007-04-30 14:05:57 +0200 (Mon,
17
-   30 Jan 2007) $
18
-     _________________________________________________________
16
+                           30 Jan 2007) $
17
+     __________________________________________________________
19 18
 
20 19
    Table of Contents
21 20
 
... ...
@@ -44,8 +43,8 @@ Chapter 1. Admin Guide
44 43
    rules. It assumes that publish requests are only issued by a
45 44
    voicemail application and subscribe requests only by the owner
46 45
    of voicemail box. Authorization can thus be easily done by
47
-   Kamailio configuration file before calling handle_publish()
48
-   and handle_subscribe() functions.
46
+   Kamailio configuration file before calling handle_publish() and
47
+   handle_subscribe() functions.
49 48
 
50 49
    The module implements a simple check of content type
51 50
    application/simple-message-summary: Content must start with
Browse code

- regenerated all READMEs (make modules-readme exclude_modules="")

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@4596 689a6050-402a-0410-94f2-e92a70836424

Klaus Darilion authored on 06/08/2008 10:49:19
Showing 1 changed files
... ...
@@ -1,3 +1,4 @@
1
+
1 2
 Presence_MWI Module
2 3
 
3 4
 Juha Heinanen
... ...
@@ -13,8 +14,8 @@ Juha Heinanen
13 14
    Copyright � 2007 Juha Heinanen
14 15
    Revision History
15 16
    Revision $Revision: 1 $ $Date: 2007-04-30 14:05:57 +0200 (Mon,
16
-                           30 Jan 2007) $
17
-     __________________________________________________________
17
+   30 Jan 2007) $
18
+     _________________________________________________________
18 19
 
19 20
    Table of Contents
20 21
 
... ...
@@ -43,8 +44,8 @@ Chapter 1. Admin Guide
43 44
    rules. It assumes that publish requests are only issued by a
44 45
    voicemail application and subscribe requests only by the owner
45 46
    of voicemail box. Authorization can thus be easily done by
46
-   Kamailio configuration file before calling handle_publish() and
47
-   handle_subscribe() functions.
47
+   Kamailio configuration file before calling handle_publish()
48
+   and handle_subscribe() functions.
48 49
 
49 50
    The module implements a simple check of content type
50 51
    application/simple-message-summary: Content must start with
Browse code

- fix some FAQ entries, change missing entity, regenerate READMEs

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@4524 689a6050-402a-0410-94f2-e92a70836424

Henning Westerholt authored on 30/07/2008 09:20:54
Showing 1 changed files
... ...
@@ -23,7 +23,7 @@ Juha Heinanen
23 23
         1.1. Overview
24 24
         1.2. Dependencies
25 25
 
26
-              1.2.1. OpenSER Modules
26
+              1.2.1. Kamailio Modules
27 27
               1.2.2. External Libraries or Applications
28 28
 
29 29
         1.3. Exported Parameters
... ...
@@ -43,7 +43,7 @@ Chapter 1. Admin Guide
43 43
    rules. It assumes that publish requests are only issued by a
44 44
    voicemail application and subscribe requests only by the owner
45 45
    of voicemail box. Authorization can thus be easily done by
46
-   OpenSER configuration file before calling handle_publish() and
46
+   Kamailio configuration file before calling handle_publish() and
47 47
    handle_subscribe() functions.
48 48
 
49 49
    The module implements a simple check of content type
... ...
@@ -53,7 +53,7 @@ Chapter 1. Admin Guide
53 53
 
54 54
 1.2. Dependencies
55 55
 
56
-1.2.1. OpenSER Modules
56
+1.2.1. Kamailio Modules
57 57
 
58 58
    The following modules must be loaded before this module:
59 59
      * presence.
Browse code

- titles for admin, devel and faq chapters are defined via entities for coherence and easier management

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@3940 689a6050-402a-0410-94f2-e92a70836424

Daniel-Constantin Mierla authored on 19/03/2008 20:40:18
Showing 1 changed files
... ...
@@ -18,7 +18,7 @@ Juha Heinanen
18 18
 
19 19
    Table of Contents
20 20
 
21
-   1. User's Guide
21
+   1. Admin Guide
22 22
 
23 23
         1.1. Overview
24 24
         1.2. Dependencies
... ...
@@ -29,7 +29,7 @@ Juha Heinanen
29 29
         1.3. Exported Parameters
30 30
         1.4. Exported Functions
31 31
 
32
-Chapter 1. User's Guide
32
+Chapter 1. Admin Guide
33 33
 
34 34
 1.1. Overview
35 35
 
Browse code

- content of faq removed (mistakenly added by me after Henning did the cleanup for modules' docs; rev 3839)

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@3901 689a6050-402a-0410-94f2-e92a70836424

Daniel-Constantin Mierla authored on 10/03/2008 11:17:28
Showing 1 changed files
... ...
@@ -29,8 +29,6 @@ Juha Heinanen
29 29
         1.3. Exported Parameters
30 30
         1.4. Exported Functions
31 31
 
32
-   2. Frequently Asked Questions
33
-
34 32
 Chapter 1. User's Guide
35 33
 
36 34
 1.1. Overview
... ...
@@ -71,40 +69,3 @@ Chapter 1. User's Guide
71 69
 1.4. Exported Functions
72 70
 
73 71
    None to be used in configuration file.
74
-
75
-Chapter 2. Frequently Asked Questions
76
-
77
-   Revision History
78
-   Revision $Revision: 2 $ $Date: 2005-06-13 19:47:24 +0300 (Mon,
79
-                           13 Jun 2005) $
80
-
81
-   2.1.
82
-
83
-       Where can I find more about OpenSER?
84
-
85
-       Take a look at http://openser.org/.
86
-
87
-   2.2.
88
-
89
-       Where can I post a question about this module?
90
-
91
-       First at all check if your question was already answered on one
92
-       of our mailing lists:
93
-         * User Mailing List -
94
-           http://openser.org/cgi-bin/mailman/listinfo/users
95
-         * Developer Mailing List -
96
-           http://openser.org/cgi-bin/mailman/listinfo/devel
97
-
98
-       E-mails regarding any stable OpenSER release should be sent to
99
-       <users@openser.org> and e-mails regarding development versions
100
-       should be sent to <devel@openser.org>.
101
-
102
-       If you want to keep the mail private, send it to
103
-       <team@openser.org>.
104
-
105
-   2.3.
106
-
107
-       How can I report a bug?
108
-
109
-       Please follow the guidelines provided at:
110
-       http://sourceforge.net/tracker/?group_id=139143.
Browse code

- entity &user; replaced with &admin; to obey naming structure (entities to be replaced by xinclude); updated obsolete address tags - READMEs regenerated

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@3898 689a6050-402a-0410-94f2-e92a70836424

Daniel-Constantin Mierla authored on 07/03/2008 23:03:56
Showing 1 changed files
... ...
@@ -74,6 +74,10 @@ Chapter 1. User's Guide
74 74
 
75 75
 Chapter 2. Frequently Asked Questions
76 76
 
77
+   Revision History
78
+   Revision $Revision: 2 $ $Date: 2005-06-13 19:47:24 +0300 (Mon,
79
+                           13 Jun 2005) $
80
+
77 81
    2.1.
78 82
 
79 83
        Where can I find more about OpenSER?
Browse code

- modules documentation migrated from sgml to xml docbook format - many thanks to Edson <4lists (at) gmail (dot) com> for providing script to replace headers and rename files - contact updated - follows re-sync with todays changes and update of Makefile to generate README and html files from XML

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@3886 689a6050-402a-0410-94f2-e92a70836424

Daniel-Constantin Mierla authored on 07/03/2008 18:19:45
Showing 1 changed files
... ...
@@ -2,14 +2,22 @@ Presence_MWI Module
2 2
 
3 3
 Juha Heinanen
4 4
 
5
+   <jh@tutpro.com>
6
+
5 7
 Edited by
6 8
 
7 9
 Juha Heinanen
8 10
 
11
+   <jh@tutpro.com>
12
+
9 13
    Copyright � 2007 Juha Heinanen
14
+   Revision History
15
+   Revision $Revision: 1 $ $Date: 2007-04-30 14:05:57 +0200 (Mon,
16
+                           30 Jan 2007) $
10 17
      __________________________________________________________
11 18
 
12 19
    Table of Contents
20
+
13 21
    1. User's Guide
14 22
 
15 23
         1.1. Overview
... ...
@@ -20,7 +28,8 @@ Juha Heinanen
20 28
 
21 29
         1.3. Exported Parameters
22 30
         1.4. Exported Functions
23
-     __________________________________________________________
31
+
32
+   2. Frequently Asked Questions
24 33
 
25 34
 Chapter 1. User's Guide
26 35
 
... ...
@@ -43,27 +52,55 @@ Chapter 1. User's Guide
43 52
    application/simple-message-summary: Content must start with
44 53
    Messages-Waiting status line followed by zero or more lines
45 54
    that consist of tabs and printable ASCII characters.
46
-     __________________________________________________________
47 55
 
48 56
 1.2. Dependencies
49 57
 
50 58
 1.2.1. OpenSER Modules
51 59
 
52 60
    The following modules must be loaded before this module:
53
-
54 61
      * presence.
55
-     __________________________________________________________
56 62
 
57 63
 1.2.2. External Libraries or Applications
58 64
 
59 65
    None.
60
-     __________________________________________________________
61 66
 
62 67
 1.3. Exported Parameters
63 68
 
64 69
    None.
65
-     __________________________________________________________
66 70
 
67 71
 1.4. Exported Functions
68 72
 
69 73
    None to be used in configuration file.
74
+
75
+Chapter 2. Frequently Asked Questions
76
+
77
+   2.1.
78
+
79
+       Where can I find more about OpenSER?
80
+
81
+       Take a look at http://openser.org/.
82
+
83
+   2.2.
84
+
85
+       Where can I post a question about this module?
86
+
87
+       First at all check if your question was already answered on one
88
+       of our mailing lists:
89
+         * User Mailing List -
90
+           http://openser.org/cgi-bin/mailman/listinfo/users
91
+         * Developer Mailing List -
92
+           http://openser.org/cgi-bin/mailman/listinfo/devel
93
+
94
+       E-mails regarding any stable OpenSER release should be sent to
95
+       <users@openser.org> and e-mails regarding development versions
96
+       should be sent to <devel@openser.org>.
97
+
98
+       If you want to keep the mail private, send it to
99
+       <team@openser.org>.
100
+
101
+   2.3.
102
+
103
+       How can I report a bug?
104
+
105
+       Please follow the guidelines provided at:
106
+       http://sourceforge.net/tracker/?group_id=139143.
Browse code

- change module docs FAQ link to a common one in the doc dir - remove module specific FAQ content from the file in doc, this way no FAQ content will be created - credits for the patch/ the change scripts goes to Edson Gellert Schubert, 4lists at gmail dot com - update all READMEs, for most module docs the FAQ and devel information were now removed

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@3839 689a6050-402a-0410-94f2-e92a70836424

Henning Westerholt authored on 04/03/2008 13:15:47
Showing 1 changed files
... ...
@@ -20,9 +20,6 @@ Juha Heinanen
20 20
 
21 21
         1.3. Exported Parameters
22 22
         1.4. Exported Functions
23
-
24
-   2. Developer's Guide
25
-   3. Frequently Asked Questions
26 23
      __________________________________________________________
27 24
 
28 25
 Chapter 1. User's Guide
... ...
@@ -70,42 +67,3 @@ Chapter 1. User's Guide
70 67
 1.4. Exported Functions
71 68
 
72 69
    None to be used in configuration file.
73
-     __________________________________________________________
74
-
75
-Chapter 2. Developer's Guide
76
-
77
-   The module does not provide any API to use in other OpenSER
78
-   modules.
79
-     __________________________________________________________
80
-
81
-Chapter 3. Frequently Asked Questions
82
-
83
-   3.1. Where can I find more about OpenSER?
84
-   3.2. Where can I post a question about this module?
85
-   3.3. How can I report a bug?
86
-
87
-   3.1. Where can I find more about OpenSER?
88
-
89
-   Take a look at http://openser.org/.
90
-
91
-   3.2. Where can I post a question about this module?
92
-
93
-   First at all check if your question was already answered on one
94
-   of our mailing lists:
95
-
96
-     * User Mailing List -
97
-       http://openser.org/cgi-bin/mailman/listinfo/users
98
-     * Developer Mailing List -
99
-       http://openser.org/cgi-bin/mailman/listinfo/devel
100
-
101
-   E-mails regarding any stable OpenSER release should be sent to
102
-   <users@openser.org> and e-mails regarding development versions
103
-   should be sent to <devel@openser.org>.
104
-
105
-   If you want to keep the mail private, send it to
106
-   <team@openser.org>.
107
-
108
-   3.3. How can I report a bug?
109
-
110
-   Please follow the guidelines provided at:
111
-   http://sourceforge.net/tracker/?group_id=139143.
Browse code

- all README files regenerated from SGML

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@3351 689a6050-402a-0410-94f2-e92a70836424

Bogdan-Andrei Iancu authored on 13/12/2007 10:43:52
Showing 1 changed files
... ...
@@ -1,4 +1,3 @@
1
-
2 1
 Presence_MWI Module
3 2
 
4 3
 Juha Heinanen
... ...
@@ -8,7 +7,7 @@ Edited by
8 7
 Juha Heinanen
9 8
 
10 9
    Copyright � 2007 Juha Heinanen
11
-     _________________________________________________________
10
+     __________________________________________________________
12 11
 
13 12
    Table of Contents
14 13
    1. User's Guide
... ...
@@ -24,7 +23,7 @@ Juha Heinanen
24 23
 
25 24
    2. Developer's Guide
26 25
    3. Frequently Asked Questions
27
-     _________________________________________________________
26
+     __________________________________________________________
28 27
 
29 28
 Chapter 1. User's Guide
30 29
 
... ...
@@ -47,7 +46,7 @@ Chapter 1. User's Guide
47 46
    application/simple-message-summary: Content must start with
48 47
    Messages-Waiting status line followed by zero or more lines
49 48
    that consist of tabs and printable ASCII characters.
50
-     _________________________________________________________
49
+     __________________________________________________________
51 50
 
52 51
 1.2. Dependencies
53 52
 
... ...
@@ -56,28 +55,28 @@ Chapter 1. User's Guide
56 55
    The following modules must be loaded before this module:
57 56
 
58 57
      * presence.
59
-     _________________________________________________________
58
+     __________________________________________________________
60 59
 
61 60
 1.2.2. External Libraries or Applications
62 61
 
63 62
    None.
64
-     _________________________________________________________
63
+     __________________________________________________________
65 64
 
66 65
 1.3. Exported Parameters
67 66
 
68 67
    None.
69
-     _________________________________________________________
68
+     __________________________________________________________
70 69
 
71 70
 1.4. Exported Functions
72 71
 
73 72
    None to be used in configuration file.
74
-     _________________________________________________________
73
+     __________________________________________________________
75 74
 
76 75
 Chapter 2. Developer's Guide
77 76
 
78 77
    The module does not provide any API to use in other OpenSER
79 78
    modules.
80
-     _________________________________________________________
79
+     __________________________________________________________
81 80
 
82 81
 Chapter 3. Frequently Asked Questions
83 82
 
... ...
@@ -91,8 +90,8 @@ Chapter 3. Frequently Asked Questions
91 90
 
92 91
    3.2. Where can I post a question about this module?
93 92
 
94
-   First at all check if your question was already answered on
95
-   one of our mailing lists:
93
+   First at all check if your question was already answered on one
94
+   of our mailing lists:
96 95
 
97 96
      * User Mailing List -
98 97
        http://openser.org/cgi-bin/mailman/listinfo/users
Browse code

* Introduced presence_mwi module (see presence_mwi/README).

git-svn-id: https://openser.svn.sourceforge.net/svnroot/openser/trunk@2102 689a6050-402a-0410-94f2-e92a70836424

Juha Heinanen authored on 30/04/2007 13:43:26
Showing 1 changed files
1 1
new file mode 100644
... ...
@@ -0,0 +1,112 @@
1
+
2
+Presence_MWI Module
3
+
4
+Juha Heinanen
5
+
6
+Edited by
7
+
8
+Juha Heinanen
9
+
10
+   Copyright � 2007 Juha Heinanen
11
+     _________________________________________________________
12
+
13
+   Table of Contents
14
+   1. User's Guide
15
+
16
+        1.1. Overview
17
+        1.2. Dependencies
18
+
19
+              1.2.1. OpenSER Modules
20
+              1.2.2. External Libraries or Applications
21
+
22
+        1.3. Exported Parameters
23
+        1.4. Exported Functions
24
+
25
+   2. Developer's Guide
26
+   3. Frequently Asked Questions
27
+     _________________________________________________________
28
+
29
+Chapter 1. User's Guide
30
+
31
+1.1. Overview
32
+
33
+   The module does specific handling for notify-subscribe
34
+   message-summary (message waiting indication) events as
35
+   specified in RFC 3842. It is used with the general event
36
+   handling module, presence. It constructs and adds
37
+   message-summary event to it.
38
+
39
+   The module does not currently implement any authorization
40
+   rules. It assumes that publish requests are only issued by a
41
+   voicemail application and subscribe requests only by the owner
42
+   of voicemail box. Authorization can thus be easily done by
43
+   OpenSER configuration file before calling handle_publish() and
44
+   handle_subscribe() functions.
45
+
46
+   The module implements a simple check of content type
47
+   application/simple-message-summary: Content must start with
48
+   Messages-Waiting status line followed by zero or more lines
49
+   that consist of tabs and printable ASCII characters.
50
+     _________________________________________________________
51
+
52
+1.2. Dependencies
53
+
54
+1.2.1. OpenSER Modules
55
+
56
+   The following modules must be loaded before this module:
57
+
58
+     * presence.
59
+     _________________________________________________________
60
+
61
+1.2.2. External Libraries or Applications
62
+
63
+   None.
64
+     _________________________________________________________
65
+
66
+1.3. Exported Parameters
67
+
68
+   None.
69
+     _________________________________________________________
70
+
71
+1.4. Exported Functions
72
+
73
+   None to be used in configuration file.
74
+     _________________________________________________________
75
+
76
+Chapter 2. Developer's Guide
77
+
78
+   The module does not provide any API to use in other OpenSER
79
+   modules.
80
+     _________________________________________________________
81
+
82
+Chapter 3. Frequently Asked Questions
83
+
84
+   3.1. Where can I find more about OpenSER?
85
+   3.2. Where can I post a question about this module?
86
+   3.3. How can I report a bug?
87
+
88
+   3.1. Where can I find more about OpenSER?
89
+
90
+   Take a look at http://openser.org/.
91
+
92
+   3.2. Where can I post a question about this module?
93
+
94
+   First at all check if your question was already answered on
95
+   one of our mailing lists:
96
+
97
+     * User Mailing List -
98
+       http://openser.org/cgi-bin/mailman/listinfo/users
99
+     * Developer Mailing List -
100
+       http://openser.org/cgi-bin/mailman/listinfo/devel
101
+
102
+   E-mails regarding any stable OpenSER release should be sent to
103
+   <users@openser.org> and e-mails regarding development versions
104
+   should be sent to <devel@openser.org>.
105
+
106
+   If you want to keep the mail private, send it to
107
+   <team@openser.org>.
108
+
109
+   3.3. How can I report a bug?
110
+
111
+   Please follow the guidelines provided at:
112
+   http://sourceforge.net/tracker/?group_id=139143.