Hi,
My client has been running FreeSWITCH with low call volume and has been stable for several months now. This Tuesday morning we switched all call volume over to FreeSWITCH and everything was running fine until this morning.
Out of the blue, *all* calls started rejecting with INCOMPATIBLE_DESTINATION.
Restarting FreeSWITCH fixed the problem. The version of FreeSWITCH is a trunk build from approximately 7/11/2013. Is this an issue that an update could fix? Could this be port starvation? Please assist, thanks.
Here's a snippet from the freeswitch log where the first occurrence of that error:
2013-08-16 09:08:20.048687 [NOTICE] switch_channel.c:1030 New Channel sofia/external/******9333@192.168.1.212:5080 [bfa3419b-0f79-4220-8807-773e3f680751]
2013-08-16 09:08:20.048687 [DEBUG] switch_core_session.c:1006 Send signal sofia/external/******9333@192.168.1.212:5080 [BREAK]
2013-08-16 09:08:20.048687 [DEBUG] switch_core_session.c:1006 Send signal sofia/external/******9333@192.168.1.212:5080 [BREAK]
2013-08-16 09:08:20.048687 [DEBUG] switch_core_state_machine.c:416 (sofia/external/******9333@192.168.1.212:5080) Running State Change CS_NEW
2013-08-16 09:08:20.048687 [DEBUG] switch_core_state_machine.c:434 (sofia/external/******9333@192.168.1.212:5080) State NEW
2013-08-16 09:08:20.068687 [DEBUG] sofia.c:5793 Channel sofia/external/******9333@192.168.1.212:5080 entering state [received][100]
2013-08-16 09:08:20.068687 [DEBUG] sofia.c:5802 Remote SDP:
v=0
o=- 1376662098 1 IN IP4 192.168.1.193
s=-
c=IN IP4 192.168.1.193
t=0 0
m=audio 0 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=silenceSupp:off - - - -
2013-08-16 09:08:20.068687 [NOTICE] sofia.c:6093 Hangup sofia/external/******9333@192.168.1.212:5080 [CS_NEW] [INCOMPATIBLE_DESTINATION]
Royce Mitchell, IT Consultant
ITAS Solutions