extension mark
Per Bergqvist
per@REDACTED
Fri Sep 26 19:42:16 CEST 2003
You can't. everything after an ellipsis is ignored by the decoder.
I proposed earlier this year that the extension data should
be stored in a special '$ellipsis' field.
If we are lucky it will be there in a future release ...
/Per
-------------------
> I have another answers:
> If I have this record:
>
> -record('AuditDescriptor',
> {
> auditToken = asn1_NOVALUE
> }). % with extension mark
>
> How can I use the extension mark????(Sorry if it`s an obvius
question)
>
> ******************
> 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], [])
>
> *******************
> With the code that is above, I'll get this, right?
> MEGACO/1 [172.16.0.1]:2944
> Transaction = 1 {
> Context = - {
> AuditCapabilities = ui {
> Audit}}}
> *****************
> but I want this:
> MEGACO/1 [172.16.0.1]:2944
> Transaction = 1 {
> Context = - {
> AuditCapabilities = ui {
> Audit{Events, Signals}
> }}}
>
> And i don`t know how to use the extension mark, could somebody help
me??
>
=========================================================
Per Bergqvist
Synapse Systems AB
Phone: +46 709 686 685
Email: per@REDACTED
More information about the erlang-questions
mailing list