On Thu, Jan 21, 2010 at 10:59:38AM +0500, Timur Irmatov wrote:
We have build a small and simple call center using FreeSWITCH and mod_erlang_event. My erlang process keeps track of available agents and routes incoming calls to them. Calls are sent to my application via:
<action application="erlang" data="switch_event:! erlswitch@localhost" />
switch_event is a registered process, which spawns a new process for each incoming call and returns new pid when it receives {get_pid, UUID, Ref, From} message from FreeSWITCH.
That all looks fine.
The problem is, that pretty frequently processes which handle incoming calls receive messages like {'EXIT', <5406.48.0>, noconnection} from FreeSWITCH. As I understand from googling, this happens when remote C node disconnects (and I see TCP connections from FreeSWITCH to epmd daemon being torn down and reestablished). FreeSWITCH drops calls at that moment.
Does it drop ALL calls being handled in erlang, or just that one?
Have anyone seen this? Is there any fix/ advice?
I haven't seen this before, how many calls are involved? I'm willing to help you troubleshoot though. Is there anything relevant in the logs (even at DEBUG)?
My system is Debian Lenny (5.0.3), 64-bit system, erlang installed from Debian packages, no backports.
What OTP release does that equate to, R12 or R13? Andrew (mod_erlang_event author)