[asterisk-dev] Advice of Charge project
Klaus Darilion
klaus.mailinglists at pernau.at
Fri Mar 12 10:14:31 CST 2010
Hi David!
Nice, that AOC support is getting reality.
Some comments:
> ; This option turns on and off AOC support for the SNOM specification. This can be applied in
> ; the general section as well as for each individual peer/user. Off by default
> snom_aoc_enabled=yes/no
I would call it aoc_snom_enable=...
Regards AOC passthrough. When we first implemented AOC
(https://issues.asterisk.org/view.php?id=7494) we had the problem with
pass-through of AOC-E, because if the AOC consumer hangs up first, the
AOC-E message sent by the AOC producer could not be forwarded as the
consumer's channel is not more available. We worked around it by faking
AOC-E using the value received in the last AOC-D. But this is of course
just a bad workaround.
Do you have ideas how to solve the problem, e.g. introducing something
like a "delayed release" and keep the hanging up channel alive until the
AOC information is available?
regards
klaus
Am 09.03.2010 23:10, schrieb David Vossel:
> Howdy!
>
> I am currently working on an implementation of Advice of Charge into the Asterisk core. If you are interested in keeping up with the project's progress or reviewing the current AOC design document, please check out the AOC group branch. The design document is named AOC_architecture.pdf and is located within the branch's root directory. I look forward to any input you may have to offer!
>
> AOC group development branch: http://svn.digium.com/svn/asterisk/team/group/aoc
>
> AOC Project Initial Requirements:
> 1. Pass-through Support: Asterisk must allow for pass-through of AOC-D and AOC-E data between supporting technologies.
> 2. Events: Asterisk must generate notifications for every AOC event that occurs. AOC events include any time AOC data is sent or received on a channel as well as specifically what the data represents. These events must be presented in a way in which they are capable of being monitored from an external application and directed to a log file.
> 3. Service Request and Grant Support: Asterisk must be capable of both requesting and granting AOC services on supporting technologies.
> 4. Message Creation: Asterisk must be capable of creating and sending AOC-D and AOC-E messages through supporting technologies. These operations must be capable of executing through an external script.
> 5. Technology Support: Asterisk must support AOC pass-through, AOC events, and AOC request/grant support for ETSI DSS1 in chan_dahdi. Asterisk must support sending AOC messages in chan_sip according to the the Snom AOC specification.
>
> David Vossel
> Digium, Inc. | Software Developer, Open Source Software
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> Check us out at: www.digium.com& www.asterisk.org
> The_Boy_Wonder in #asterisk-dev
>
More information about the asterisk-dev
mailing list