Re: An issue about encoder for MEGACO

George,

As per ABNF grammar, 1 or more of ((transactionRequest
/ transactionReply / transactionPending
/
transactionResponseAck /

segmentReply)
are allowed in a message. Here Stack has encoded 1 TransactionReply and
1 TransactionResponseAck
in a H.248 message. This TransactionResponseAck
is for any previous transaction (with id 1) sent by this entity.

I think this should be fine as per H.248 encoding rules.

Thanks

Ashish

Redback Networks Inc.

San Jose, CA

George Quan wrote:

Hi
all:

I found the
following encoder in some vendor. I am not sure whether it is right or
not. Please
help me.

=====================================

MEGACO/1
[10.136.1.95]:2944

Reply=186002{Context=-{Modify=ROOT}}

TransactionResponseAck{1}

==========================================

In
the packet, Both TransactionRequest
and TransactionResponseAck are embedded in one message, is it right?

I
look into ITU H.248.1
V3, it seems that it don't allow encoding.

Pls
give me some guide.

BTW:
the following is
defined in P98, ITU H.248.1 V3.

transactionList
=
1*(transactionRequest / transactionReply /

transactionPending
/
transactionResponseAck /

segmentReply)

thanks

George

Best Regard

-------------------------------------------

Juniper Network CN R&D Co. Ltd.

George Quan

Tel: 8610-5874-7167

Location: 7.1.301

----------

_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco