auditToken megaco

Carlos Rodríguez Alcalá Villagra <>
Wed Sep 24 19:10:51 CEST 2003


Hi to make this command :
MEGACO/1 [172.16.0.1]:2944
Transaction = 1 {
Context = - {
AuditCapabilities = ui {
Audit{Events}
}}} 
|-----------------------------------------------------------------------------|


I wrote this code:
******************************
auditcapabilities(ConnHandle, Events)->
 AUD=#'AuditDescriptor'{auditToken=Audit}, 
 TermId=ui,
 AUR=#'AuditRequest'{terminationID = TermId, auditDescriptor = AUD},
 CR = #'CommandRequest'{command = {auditCapabilities, AUR}},    
 AR = #'ActionRequest'{contextId = ?megaco_null_context_id, commandRequests = [CR]},
 io:format("AR:~p~n", [AR]),
 {ProtocolVersion, UserReply}=megaco:call(ConnHandle, [AR], [])

****************************

but, auditToken should also be a structure to be able to load Event, rigth?

Because, in the RFC3015 page 89 is written:

AuditDescriptor ::= SEQUENCE
   {
        auditToken      BIT STRING
        {
                muxToken(0), modemToken(1), mediaToken(2),
                eventsToken(3), signalsToken(4),
                digitMapToken(5), statsToken(6),
                observedEventsToken(7),
                packagesToken(8), eventBufferToken(9)
        } OPTIONAL,
        ...
   }

thanks for your time

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20030924/94ddeb3a/attachment.html>


More information about the erlang-questions mailing list