switch_channel_hangup(session->channel, SWITCH_CAUSE_WRONG_CALL_STATE); } } else { ... } } 从代码上看,问题发生在FreeSWITCH的核心状态机,核心状态机是一个循环,里面有个计数器,如果状态机连续有500次处于CS_NEW状态,则打印错误日志WRONG_CALL_STATE,挂机。 switch_yield(20000)是等待20毫秒,因为循环5...
(1)WRONG_CALL_STATE invite ---> 407 <--- ack ---> invite ---> the second invite,FreeSWITCH no have log print,10 seconds later, WRONG_CALL_STATE appears, By capturing the packet file, it can be seen that FreeSWITCH has received the invi...
WRONG_MESSAGE message not compatible with call state or message type non-existent or not implemented. [Q.850] This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the ca...
I found that the some of the incoming call will hangup with case: WRONG_CALL_STATE,but else will be ok.After a hour,almost every incoming call will be hangup with the same cause.Then I will restart the freeswitch,it will server like before:some call will be hangup with the cause.....
SWITCH_CAUSE_WRONG_CALL_STATE = 101, SWITCH_CAUSE_RECOVERY_ON_TIMER_EXPIRE = 102, SWITCH_CAUSE_MANDATORY_IE_LENGTH_ERROR = 103, SWITCH_CAUSE_PROTOCOL_ERROR = 111, SWITCH_CAUSE_INTERWORKING = 127, SWITCH_CAUSE_SUCCESS = 142, SWITCH_CAUSE_ORIGINATOR_CANCEL = 487, ...
freeswitch.consoleLog(NOTICE, s)ifsubclass =="sofia::wrong_call_state"or subclass =="sofia::register_failure"then local cmd="fail2ban-client set freeswitch banip".. ip freeswitch.consoleLog("ERR, cmd ..,:serialize() ..===\n")
WRONG_CALL_STATE RECOVERY_ON_TIMER_EXPIRE MANDATORY_IE_LENGTH_ERROR PROTOCOL_ERROR INTERWORKING SUCCESS ORIGINATOR_CANCEL CRASH SYSTEM_SHUTDOWN LOSE_RACE MANAGER_REQUEST BLIND_TRANSFER ATTENDED_TRANSFER ALLOTTED_TIMEOUT USER_CHALLENGE MEDIA_TIMEOUT ...
So any thought or idea on what can be wrong is welcome, Im also getting the "i_media_error 500 Transport error detected" message in the FS logs: nua_stack.c:271 nua_stack_event() nua(0x7fc960000ca0): event i_state 180 Ringing ...
101 WRONG_CALL_STATE message not compatible with call state [Q.850] This cause indicates that a message has been received which is incompatible with the call state. 102 504 RECOVERY_ON_TIMER_EXPIRE recovery on timer expiry [Q.850] This cause indicates that a procedure has been initiated ...
hangup_call() break end end else -- Callerr entered wrong PIN session:streamFile("ivr/ivr-that_was_an_invalid_entry.wav") tries = tries + 1; end end if (tries > 2) then -- Too many failed attempts to enter PIN session:streamFile("voicemail/vm-abort.wav") hangup_call() break ...