I'm using Sangoma A108 board in my FS installation and my log is full of warnings as: 2011-03-01 00:18:14.947380 [WARNING] mod_freetdm.c:434 [s17c22][17:22] VETO state change from PROGRESS_MEDIA to PROCEED 2011-03-01 00:18:53.151673 [WARNING] mod_freetdm.c:434 [s3c11][3:11] VETO state change from PROGRESS_MEDIA to PROCEED 2011-03-01 00:19:23.001140 [WARNING] mod_freetdm.c:434 [s23c29][23:29] VETO state change from RINGING to PROCEED 2011-03-01 00:19:40.862103 [WARNING] mod_freetdm.c:434 [s3c21][3:21] VETO state change from PROGRESS_MEDIA to PROCEED 2011-03-01 00:19:46.022154 [WARNING] mod_freetdm.c:434 [s3c21][3:21] VETO state change from PROGRESS_MEDIA to PROCEED 2011-03-01 00:19:50.608224 [WARNING] mod_freetdm.c:434 [s22c24][22:24] VETO state change from PROGRESS_MEDIA to PROCEED 2011-03-01 00:19:52.422221 [WARNING] mod_freetdm.c:434 [s3c21][3:21] VETO state change from PROGRESS_MEDIA to PROCEED 2011-03-01 00:21:36.461338 [WARNING] mod_freetdm.c:434 [s3c31][3:31] VETO state change from PROGRESS_MEDIA to PROCEED 2011-03-01 00:21:36.981455 [WARNING] mod_freetdm.c:434 [s3c30][3:30] VETO state change from PROGRESS_MEDIA to PROCEED Another kind of messages that are in my log file are: 2011-03-01 00:53:14.427853 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:760 [SNGISDN Q931] s16: Protocol: Unknown Event Code(2): Incomp Msg(276) 2011-03-01 00:53:18.428846 [CRIT] ftmod_sangoma_isdn_stack_hndl.c:557 [s16c23][16:23] Received DISCONNECT in an invalid state (TERMINATING) 2011-03-01 00:53:18.428846 [WARNING] ftmod_sangoma_isdn_stack_hndl.c:562 [s16c23][16:23] Why bother changing state from TERMINATING to TERMINATING 2011-03-01 00:54:08.607351 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:760 [SNGISDN Q931] s17: Protocol: Unknown Event Code(2): Incomp Msg(276) 2011-03-01 00:54:12.607389 [CRIT] ftmod_sangoa_isdn_stack_hndl.c:557 [s17c20][17:20] Received DISCONNECT in an invalid state (TERMINATING) 2011-03-01 00:54:12.607389 [WARNING] ftmod_sangoma_isdn_stack_hndl.c:562 [s17c20][17:20] Why bother changing state from TERMINATING to TERMINATING 2011-03-01 00:56:45.595869 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:760 [SNGISDN Q931] s16: Protocol: Unknown Event Code(2): Incomp Msg(276) 2011-03-01 00:56:49.596913 [CRIT] ftmod_sangoma_isdn_stack_hndl.c:557 [s16c23][16:23] Received DISCONNECT in an invalid state (TERMINATING) 2011-03-01 00:56:49.596913 [WARNING] ftmod_sangoma_isdn_stack_hndl.c:562 [s16c23][16:23] Why bother changing state from TERMINATING to TERMINATING 2011-03-01 00:59:23.036314 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:760 [SNGISDN Q931] s17: Protocol: Unknown Event Code(2): Incomp Msg(276) 2011-03-01 00:59:27.037327 [CRIT] ftmod_sangoma_isdn_stack_hndl.c:557 [s17c20][17:20] Received DISCONNECT in an invalid state (TERMINATING) 2011-03-01 00:59:27.037327 [WARNING] ftmod_sangoma_isdn_stack_hndl.c:562 [s17c20][17:20] Why bother changing state from TERMINATING to TERMINATING I'm using latest git of Freeswitch, Wanpipe 3.5.18 and lib Sangoma isdn 7.3.0. Attached to this email the .pcap related to the call that generate the critical error (to me it seems that is missed a CALL_PROCEEDING message). Stephen