Megaco and controlling processes

Samuel Tardieu <>
Fri Jan 30 19:11:47 CET 2004

In the Megaco example, it is recommended to started the simple_mgc by

% erl -s megaco
1> megaco_simple_mgc:start ().

Indeed, doing:
% erl -s megaco -s megaco_simple_mgc

does not work. The MGC gives:

** Reason for termination == 
** {badarg,[{ets,update_counter,

which is right, the megaco_udp_stats table does not show up in ets:i().

I couldn't find in the Megaco 2.0 documentation a place where it says
which processes have to be alive.

Could anyone explain whether this is a bug, or which function must be
called by a process which stays alive?

Thanks in advance.

Samuel Tardieu --  --

More information about the erlang-questions mailing list