[Freeswitch-users] hangup with cause:WRONG_CALL_STATE

[rockxsj]

My client send sip message via udp,so I think the WRONG_CALL_STATE may
product by some package send failure.The most important problem is
client recive "503 System Busy".When I trace the code,I find it is
product in src/mod/endpoints/mod_sofia/sofia.c,and the condition is: if
(switch_queue_size(mod_sofia_globals.msg_queue) > (unsigned
int)critical) { nua_respond(nh, 503, "System Busy",
SIPTAG_RETRY_AFTER_STR("300"), NUTAG_WITH_THIS(nua), TAG_END()); goto end;}

Why will product these?
于 2014年04月28日 11:46, rockxsj 写道:
> Hi guys!
>
> 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...
>
> 28e10f2e-c851-11e3-a146-85a8fadad1b0 2014-04-20 14:01:15.498169
> [WARNING] switch_core_state_machine.c:567
> 28e10f2e-c851-11e3-a146-85a8fadad1b0
> sofia/internal/123456 at sipsj.236.cn Abandoned
> 28e10f2e-c851-11e3-a146-85a8fadad1b0 2014-04-20 14:01:15.498169
> [NOTICE] switch_core_state_machine.c:570 Hangup
> sofia/internal/123456 at sipsj.236.cn [CS_NEW] [WRONG_CALL_STATE]
>
> What does Wrong call state mean and what can I do to fix this issue?
>
> Everything else is working. I can make outgoing calls and call other
> extensions.
>
> Thanks in advance.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20140428/691021d0/attachment-0001.html