voicemail.xml 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
  4. <section id="voicemail" xmlns:xi="http://www.w3.org/2001/XInclude">
  5. <sectioninfo>
  6. <revhistory>
  7. <revision>
  8. <revnumber>$Revision$</revnumber>
  9. <date>$Date$</date>
  10. </revision>
  11. </revhistory>
  12. </sectioninfo>
  13. <section>
  14. <title>Introduction</title>
  15. <para>
  16. The voicemail system provides <application>ser</application> with
  17. voice announcement and recording capabilities. Voice messages may
  18. then be mailed to the called user. The system relies on
  19. <application>ser</application> for implementing the
  20. <acronym>SIP</acronym> stack and communicate with it through
  21. <acronym>FIFO</acronym>. It implements the dialog and media
  22. handling as described in RFC 3264 (An Offer/Answer Model with the
  23. Session Description Protocol) and RFC 1889 (Real time transport
  24. protocol) to realize its goal.
  25. </para>
  26. </section>
  27. <section>
  28. <title>Advantages</title>
  29. <para>
  30. <itemizedlist>
  31. <listitem>
  32. <para>
  33. Anyone deploying <application>ser</application> and
  34. <acronym>VoIP</acronym> should profit from this 'ready-to-run'
  35. application. It plugs into <application>ser</application> as
  36. easy as configuring the database location, announce file path
  37. and SMTP server address.
  38. </para>
  39. </listitem>
  40. <listitem>
  41. <para>
  42. Further, <application>voicemail</application>
  43. integrates the most popular free codecs (G.711ulaw,
  44. G.711alaw and GSM 06.10) and its own SMTP client, which
  45. means that you don't need to install anything else as
  46. <application>ser</application> and
  47. <application>voicemail</application>.
  48. </para>
  49. </listitem>
  50. <listitem>
  51. <para>
  52. If you want your voicemail system to support other
  53. codecs, a simple plugin system with SDK allows you to
  54. integrate them fast and simply (see the basis plugins
  55. for examples).
  56. </para>
  57. </listitem>
  58. </itemizedlist>
  59. </para>
  60. </section>
  61. <section>
  62. <title>Technical limitations</title>
  63. <para>
  64. <itemizedlist>
  65. <listitem>
  66. <para>
  67. The sound conversion engine doesn't support yet
  68. re-sampling. It means that input and output files have
  69. to be compatible with the sampling rate of the
  70. codec. All codecs included with the distribution work
  71. at 8kHz, which means that all the input and output
  72. files MUST be sampled at the rate of 8kHz.
  73. </para>
  74. </listitem>
  75. <listitem>
  76. <para>
  77. At the moment, voicemail only support the Microsoft Wav
  78. file format with PCM 16 bit, Mu-law and A-law 8 bit
  79. encoding.
  80. </para>
  81. </listitem>
  82. </itemizedlist>
  83. </para>
  84. </section>
  85. <section>
  86. <title>Compilation and installation</title>
  87. <para>
  88. <itemizedlist>
  89. <listitem>
  90. <para>
  91. First, you need to compile Ser with voicemail
  92. support. Therefore, you must edit Ser's Makefile.defs
  93. file and uncomment the line with '-DVOICE_MAIL' and
  94. '-D_TOTAG'.
  95. </para>
  96. </listitem>
  97. <listitem>
  98. <para>
  99. Then do 'make all' in Ser's root directory.
  100. </para>
  101. </listitem>
  102. <listitem>
  103. <para>
  104. Configure Ser to fit your needs. You can report to
  105. voicemail example config file to know what your
  106. configuration file should include. Note that voicemail
  107. only needs to know the user database location in order
  108. to work. Report to the README file in the vm module
  109. directory for description of the functions and variable
  110. that are used by voicemail and how they work.
  111. </para>
  112. </listitem>
  113. <listitem>
  114. <para>
  115. Finally, compile the voicemail application:
  116. <programlisting>
  117. [~/voicemail]$ cd ortp-0.5.0
  118. [~/voicemail/ortp-0.5.0]$ ./configure
  119. [~/voicemail/ortp-0.5.0]$ make all
  120. [~/voicemail/ortp-0.5.0]$ cd ..
  121. [~/voicemail]$ cd plug-in/gsm/gsm-????
  122. [~/voicemail/plug-in/gsm/gsm-????]$ make all
  123. [~/voicemail/plug-in/gsm/gsm-????]$ cd ../..
  124. [~/voicemail]$ make all
  125. </programlisting>
  126. You can then start voicemail with following
  127. command <command>ans_machine</command> and
  128. look if the default fit your needs. If not,
  129. type <command>ans_machine -h</command> to see
  130. how to change the default parameters.
  131. <!--<note>-->
  132. If <application>ans_machine</application> is
  133. not started or can't be joined while
  134. <application>ser</application> tries to
  135. communicate with it, the caller will become
  136. a '500 internal server error' with a comment
  137. saying what the trouble is.
  138. <!--</note>-->
  139. </para>
  140. </listitem>
  141. </itemizedlist>
  142. </para>
  143. </section>
  144. <section>
  145. <title>Availability, report bugs, contact the author</title>
  146. <para>
  147. Ser's Voicemail's home page is hosted at
  148. http://sems.berlios.de. A snapshot may be downloaded directly
  149. from the CVS tree. A pre-configured version of
  150. <application>ser</application> including
  151. <application>voicemail</application> will be soon available
  152. (from version 0.8.11). Bugs can be reported at the voicemail's
  153. home page. If you want to contact the author, use the contact
  154. email at the home page.
  155. </para>
  156. </section>
  157. </section>