megaco_compact_text comparation

Hakan Mattsson hakan@REDACTED
Mon Mar 8 12:55:40 CET 2004

Carlos> We are testing the erlang megaco application with a mp-102 analog
Carlos> gateway, but the ServiceChange fails. Find attached a file that
Carlos> contains images of both ServiceChanges: A valid one and one from the
Carlos> mp-102. The difference is visible.

Have you told AudioCodes that their stack does not comply with the standard?

Carlos> How can we fix this in order to be able to receive a valid transaction
Carlos> from the mp-102?, knowing that it always adds the caracters 00 or \x00
Carlos> to the ServiceChange Command. Do we need to hack the erlang's code at
Carlos> the "handled" libraries?

Yes, if you want to be bug compatible with AudioCodes you need to hack a little.

Add the following rule to megaco/src/text/megaco_text_parser.yrl:

  megacoMessage        -> optSep authenticationHeader message safeToken endOfMessage
			      : #'MegacoMessage'{authHeader = '$2', mess = '$3'} .

directly after this rule:

  megacoMessage        -> optSep authenticationHeader message endOfMessage
			      : #'MegacoMessage'{authHeader = '$2', mess = '$3'} .

and recompile the megaco application. This would allow trailing safeChars in
any text message.


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.

More information about the erlang-questions mailing list