8ca3a4978d
* 3d positions were being rendered without an enclosing `<gml:pos>` element resulting in invalid XML. * There was no way to set the `id` attribute on the enclosing `tuple`, `device` and `person` elements. * There was no way to set the value of the `deviceID` element. * Parsing of degree and radian UOMs was broken resulting in them appearing outside an XML element. * The UOM schemas for degrees and radians were reversed. * The Ellipsoid shape was missing and the Ellipse shape was defined multiple times. * The `crs` location_info parameter, although documented, didn't work. * The `pos3d` location_info parameter appears in some documentation but wasn't being parsed correctly. * The retransmission-allowed and retention-expiry sub-elements of usage-rules were using the `gp` namespace instead of the `gbp` namespace. In addition to fixing the above, several other code refactorings were performed and the unit test enhanced to include a round trip XML -> eprofile -> XML validation. Resolves: #1667 UserNote: Geolocation: Two new optional profile parameters have been added. * `pidf_element_id` which sets the value of the `id` attribute on the top-level PIDF-LO `device`, `person` or `tuple` elements. * `device_id` which sets the content of the `<deviceID>` element. Both parameters can include channel variables. UpgradeNote: Geolocation: In order to correct bugs in both code and documentation, the following changes to the parameters for GML geolocation locations are now in effect: * The documented but unimplemented `crs` (coordinate reference system) element has been added to the location_info parameter that indicates whether the `2d` or `3d` reference system is to be used. If the crs isn't valid for the shape specified, an error will be generated. The default depends on the shape specified. * The Circle, Ellipse and ArcBand shapes MUST use a `2d` crs. If crs isn't specified, it will default to `2d` for these shapes. The Sphere, Ellipsoid and Prism shapes MUST use a `3d` crs. If crs isn't specified, it will default to `3d` for these shapes. The Point and Polygon shapes may use either crs. The default crs is `2d` however so if `3d` positions are used, the crs must be explicitly set to `3d`. * The `geoloc show gml_shape_defs` CLI command has been updated to show which coordinate reference systems are valid for each shape. * The `pos3d` element has been removed in favor of allowing the `pos` element to include altitude if the crs is `3d`. The number of values in the `pos` element MUST be 2 if the crs is `2d` and 3 if the crs is `3d`. An error will be generated for any other combination. * The angle unit-of-measure for shapes that use angles should now be included in the respective parameter. The default is `degrees`. There were some inconsistent references to `orientation_uom` in some documentation but that parameter never worked and is now removed. See examples below. Examples... ``` location_info = shape="Sphere", pos="39.0 -105.0 1620", radius="20" location_info = shape="Point", crs="3d", pos="39.0 -105.0 1620" location_info = shape="Point", pos="39.0 -105.0" location_info = shape=Ellipsoid, pos="39.0 -105.0 1620", semiMajorAxis="20" semiMinorAxis="10", verticalAxis="0", orientation="25 degrees" pidf_element_id = ${CHANNEL(name)}-${EXTEN} device_id = mac:001122334455 Set(GEOLOC_PROFILE(pidf_element_id)=${CHANNEL(name)}/${EXTEN}) ```
The Asterisk(R) Open Source PBX
By Mark Spencer <markster@digium.com> and the Asterisk.org developer community.
Copyright (C) 2001-2025 Sangoma Technologies Corporation and other copyright holders.
SECURITY
It is imperative that you read and fully understand the contents of the security information document before you attempt to configure and run an Asterisk server.
See Important Security Considerations for more information.
WHAT IS ASTERISK ?
Asterisk is an Open Source PBX and telephony toolkit. It is, in a sense, middleware between Internet and telephony channels on the bottom, and Internet and telephony applications at the top. However, Asterisk supports more telephony interfaces than just Internet telephony. Asterisk also has a vast amount of support for traditional PSTN telephony, as well.
For more information on the project itself, please visit the Asterisk Home Page and the official Asterisk Documentation.
SUPPORTED OPERATING SYSTEMS
Linux
The Asterisk Open Source PBX is developed and tested primarily on the GNU/Linux operating system, and is supported on every major GNU/Linux distribution.
Others
Asterisk has also been 'ported' and reportedly runs properly on other operating systems as well, Apple's Mac OS X, and the BSD variants.
GETTING STARTED
Most users are using VoIP/SIP exclusively these days but if you need to interface to TDM or analog services or devices, be sure you've got supported hardware.
Supported telephony hardware includes:
- All Analog and Digital Interface cards from Sangoma
- Any full duplex sound card supported by PortAudio
- The Xorcom Astribank channel bank
UPGRADING FROM AN EARLIER VERSION
If you are updating from a previous version of Asterisk, make sure you read the Change Logs.
NEW INSTALLATIONS
Ensure that your system contains a compatible compiler and development libraries. Asterisk requires either the GNU Compiler Collection (GCC) version 4.1 or higher, or a compiler that supports the C99 specification and some of the gcc language extensions. In addition, your system needs to have the C library headers available, and the headers and libraries for ncurses.
There are many modules that have additional dependencies. To see what
libraries are being looked for, see ./configure --help, or run
make menuselect to view the dependencies for specific modules.
On many distributions, these dependencies are installed by packages with names
like 'glibc-devel', 'ncurses-devel', 'openssl-devel' and 'zlib-devel'
or similar. The contrib/scripts/install_prereq script can be used to install
the dependencies for most Debian and Redhat based Linux distributions.
The script also handles SUSE, Arch, Gentoo, FreeBSD, NetBSD and OpenBSD but
those distributions mightnoit have complete support or they might be out of date.
So, let's proceed:
-
Read the documentation.
The Asterisk Documentation website has full information for building, installing, configuring and running Asterisk. -
Run
./configure
Execute the configure script to guess values for system-dependent variables used during compilation. If the script indicates that some required components are missing, you can run./contrib/scripts/install_prereq installto install the necessary components. Note that this will install all dependencies for every functionality of Asterisk. After running the script, you will need to rerun./configure. -
Run
make menuselect
This is needed if you want to select the modules that will be compiled and to check dependencies for various optional modules. -
Run
make
Assuming the build completes successfully: -
Run
make install
If this is your first time working with Asterisk, you may wish to install the sample PBX, with demonstration extensions, etc. If so, run: -
Run
make samples
Doing so will overwrite any existing configuration files you have installed. -
Finally, you can launch Asterisk in the foreground mode (not a daemon) with
asterisk -vvvc
You'll see a bunch of verbose messages fly by your screen as Asterisk initializes (that's the "very very verbose" mode). When it's ready, if you specified the "c" then you'll get a command line console, that looks like this:
*CLI>
You can typecore show helpat any time to get help with the system. For help with a specific command, typecore show help <command>.
man asterisk at the Unix/Linux command prompt will give you detailed
information on how to start and stop Asterisk, as well as all the command
line options for starting Asterisk.
ABOUT CONFIGURATION FILES
All Asterisk configuration files share a common format. Comments are
delimited by ; (since # of course, being a DTMF digit, may occur in
many places). A configuration file is divided into sections whose names
appear in []'s. Each section typically contains statements in the form
variable = value although you may see variable => value in older samples.
SPECIAL NOTE ON TIME
Those using SIP phones should be aware that Asterisk is sensitive to large jumps in time. Manually changing the system time using date(1) (or other similar commands) may cause SIP registrations and other internal processes to fail. For this reason, you should always use a time synchronization package to keep your system time accurate. All OS/distributions make one or more of the following packages available:
- ntpd/ntpsec
- chronyd
- systemd-timesyncd
Be sure to install and configure one (and only one) of them.
FILE DESCRIPTORS
Depending on the size of your system and your configuration, Asterisk can consume a large number of file descriptors. In UNIX, file descriptors are used for more than just files on disk. File descriptors are also used for handling network communication (e.g. SIP, IAX2, or H.323 calls) and hardware access (e.g. analog and digital trunk hardware). Asterisk accesses many on-disk files for everything from configuration information to voicemail storage.
Most systems limit the number of file descriptors that Asterisk can have open at one time. This can limit the number of simultaneous calls that your system can handle. For example, if the limit is set at 1024 (a common default value) Asterisk can handle approximately 150 SIP calls simultaneously. To change the number of file descriptors follow the instructions for your system below:
PAM-BASED LINUX SYSTEM
If your system uses PAM (Pluggable Authentication Modules) edit
/etc/security/limits.conf. Add these lines to the bottom of the file:
root soft nofile 4096
root hard nofile 8196
asterisk soft nofile 4096
asterisk hard nofile 8196
(adjust the numbers to taste). You may need to reboot the system for these changes to take effect.
GENERIC UNIX SYSTEM
If there are no instructions specifically adapted to your system
above you can try adding the command ulimit -n 8192 to the script
that starts Asterisk.
MORE INFORMATION
Visit the Asterisk Documentation website for more documentation on various features and please read all the configuration samples that include documentation on the configuration options.
Finally, you may wish to join the Asterisk Community Forums
Welcome to the growing worldwide community of Asterisk users!
Mark Spencer, and the Asterisk.org development community
Asterisk is a trademark of Sangoma Technologies Corporation
[Sangoma] [Home Page] [Support] [Documentation] [Community Forums] [Release Notes] [Security] [Mailing List Archive]