 |
| |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
|---|
Asterisk RA for Mobicents | | |
- Fill in the IP address, login and password properties in the asteriskra.properties file
- Deployed the RA using the "asteriskradeploy" ant target from the project's build.xml. Much like the SIP RA, in fact.
| |
<
< | [TODO] Write an example how the RA can be used in a practical scenario. | >
> | The Asterisk RA currently works with the Manager Interface of Asterisk, though FastAGI support is also planned eventually. After deployment and activation, it uses the Asterisk-Java library to create a manager connection to an asterisk machine (specified in the asteriskra.properties file). It will then listen for any events or responses originated by asterisk and send them to the SLEE. The RA’s SBB Interface consists of one function, sendAction, which is used to send a manager action object to the asterisk machine.
All types of manager actions implemented by Asterisk-Java ( in net.sf.asterisk.manager.action) are available; this allows a variety of commands to be sent to the asterisk, such as originating calls, redirecting them, hanging up and so on. In addition, through the use of CommandActions (which encapsulate CLI commands) further functionality is available, in particular regarding asterisk configuration and status; this includes several methods of getting information regarding various aspects (codecs, channels, mappings, dialplan, applications…) and also the ability to change some, such as adding or removing extensions “on the fly”.
These various commands allow a number of simple services to be developed, such as redirecting calls or voicemail for example. However, they are not, in general, ideally suited for direct call control in the same manner as would be available through normal FastAGI applications, and the complexity of services that can be developed using just the Manager Interface is limited in this aspect. The main usefulness of the current Asterisk RA lies in the various events it receives, which allow the application server to have a clear picture of what Asterisk is doing by itself, and thus services or applications that use them to monitor this and only intervene when strictly necessary, requiring little to no control of the majority of the call process.
An example of this would be collecting statistical data from an asterisk server; another would be a charging service that used the events to get the necessary data (call duration, calling party…) and only intervened, for instance, to provide a warning message and hangup the call when the caller’s credit ran out in a prepaid scenario. | | | -- Main.ivelin - 29 Apr 2005 | |
>
> |
|
|
>
> |
| META TOPICPARENT | name="MobicentsOpenSLEE" |
|---|
Asterisk RA for Mobicents
To enable the Asterisk RA:
- Fill in the IP address, login and password properties in the asteriskra.properties file
- Deployed the RA using the "asteriskradeploy" ant target from the project's build.xml. Much like the SIP RA, in fact.
[TODO] Write an example how the RA can be used in a practical scenario.
-- Main.ivelin - 29 Apr 2005 |
|