Megaco and controlling processes

Micael Karlberg micael.karlberg@REDACTED
Tue Feb 3 09:34:51 CET 2004

It was pointed out to me that I might have misread your question. 

In case you want to start the mg/mgc from a (unix) shell, see
the Makefile of the simple example (targets mg and mgc).


Samuel Tardieu writes:
 > In the Megaco example, it is recommended to started the simple_mgc by
 > doing:
 > % 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,
 >                  [megaco_udp_stats,
 >                   {{send_handle,#Port<0.68>,{127,0,0,1},3877},
 >                    medGwyGatewayNumInMessages},
 >                   1]},
 >             {megaco_udp_server,incCounter,2},
 >             {megaco_udp_server,handle_info,2},
 >             {gen_server,handle_msg,6},
 >             {proc_lib,init_p,5}]}
 > 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.
 >   Sam
 > -- 
 > Samuel Tardieu -- sam@REDACTED --

Micael Karlberg          Ericsson AB, Älvsjö Sweden
Tel:  +46 8 727 5668     EAB/UHK/KD - OTP Product Development
ECN:  851 5668           Mail: micael.karlberg@REDACTED
Fax:  +46 8 727 5775    

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