- 06 5月, 2012 14 次提交
-
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
- 05 5月, 2012 17 次提交
-
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
We now break out each module and component of FreeSWITCH into a separate individually-installable package. For each package with executables or modules, we also build a package that includes the stripped debugging symbols so that users can be helpful when they discover bugs in FreeSWITCH. As of this commit, we successfully build 263 distinct binary packages starting from a clean minimal image on both Debian Sid and Debian Squeeze. To keep this manageable, we include a program that generates the various Debian packaging files from a consolidated description of the modules and their metadata. The program can even generate this configuration file by walking the FreeSWITCH source tree. To provide a smooth user experience, we provide meta-packages that install sensible sets of modules and other components. All files are installed into the traditional and customary Linux directories that you would expect in accordance with the Filesystem Hierarchy Standard (FHS). This commit also adds support for running FreeSWITCH as a forked systemd service in Debian. For more information about the technical details of the source packaging, how to build the binary packages from source, and how you can contribute, please read debian/README.source. To learn about how this packaging affects you as a user and how to use the finished Debian packages, read debian/README.Debian. Signed-off-by:
Travis Cross <tc@traviscross.com>
-
由 Travis Cross 提交于
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-
- 04 5月, 2012 9 次提交
-
-
由 Anthony Minessale 提交于
add pickup endpoint and app to dptools add pickup/keyname to forked dial, then route a call to call app pickup(keyname) to have your channel return from originate. sub to pickup+keyname or presence map the pickup proto to use on blf
-
由 Anthony Minessale 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
-
由 Travis Cross 提交于
...it's always the seemingly trivial changes.
-
由 Travis Cross 提交于
...and replace with a TODO explaining why the function stub is there.
-
由 William King 提交于
If the notify event contains call-info headers, then process the call-info linked list into comma separated values and add them to a header on the event.
-
由 Anthony Minessale 提交于
-
由 Anthony Minessale 提交于
-