[Asterisk-Users] MFC/R2 errors

[Guillermo Freige]

MFCR2 is hanging under heavy load in my configuration. It always segfaults 
in the same point. This is the coredump debug.
During segfaults, the "call" structure points to an invalid area.

(gdb) list
584         uc_log(uc, UC_LOG_FLOW, "Far end disconnected - state 0x%X\n",
call->state);
585
586         /* Don't stop the tone detector here. */
587
588         if (call->chan >= 0)
589             uc->chan[call->chan].state = UC_STATE_FAR_DISCONNECTED;
590         /*endif*/
591         call->state = UC_STATE_FAR_DISCONNECTED;
592
593         ev.fardisconnected.e = UC_EVENT_FARDISCONNECTED;
(gdb) bt
#0  0x4081c81d in start_far_disconnected (uc=0x8128058, call=0x81dd1f0) at
mfcr2.c:589
#1  0x405c91ad in uc_schedule_run (uc=0x8128058) at simplesched.c:124
#2  0x405b3378 in unicall_read (ast=0x40c05590) at chan_unicall.c:2081
#3  0x0805c26d in ast_read (chan=0x40c05590) at channel.c:1304
#4  0x405b8901 in unicall_bridge (c0=0x8202350, c1=0x40c05590, flags=0,
fo=0xbb5faaa4, rc=0xbb5faaa8)
    at chan_unicall.c:1794
#5  0x0805fe16 in ast_channel_bridge (c0=0x8202350, c1=0x40c05590,
config=0xbb5fb334, fo=0xbb5faaa4, rc=0xbb5faaa8)
    at channel.c:2611
#6  0x4038e775 in ast_bridge_call (chan=0x8202350, peer=0x40c05590,
config=0xbb5fb334) at res_features.c:348
#7  0x40892b24 in dial_exec (chan=0x8202350, data=0x50) at app_dial.c:1006
#8  0x0807476f in pbx_exec (c=0x8202350, app=0x40905e08, data=0xbb5fd864,
newstack=1) at pbx.c:469
#9  0x0807c803 in pbx_extension_helper (c=0x8202350, context=0x82024a8
"operador", exten=0x820259c "s", priority=11,
    callerid=0x0, action=135093791) at pbx.c:1277
#10 0x080767d8 in ast_pbx_run (c=0x8202350) at pbx.c:1758
#11 0x0807ce31 in pbx_thread (data=0xc0436a10) at pbx.c:1981
#12 0x40024e51 in pthread_start_thread () from /lib/libpthread.so.0
#13 0x401ec6ca in clone () from /lib/libc.so.6

Also I'm having trouble with the MFC dialog. Under load, I have a lot of T1 
and T2 timeouts, mostly because I never hear the Rx off event in outgoing 
calls in the 3rd digit of a group of 4, and it generates a Protocol Error. 
After that the line keeps a "Call" flag rendering it unusable for further 
calls. When the number of blocked lines or the load makes the outgoing lines 
reach the incoming lines, so the same line is used for both incoming and 
outgoing calls, asterisk blocks the line and enters in a CPU intensive loop, 
locking the line.

Guillermo

_________________________________________________________________
MSN Amor: busca tu ½ naranja http://latam.msn.com/amor/