[Freeswitch-users] INCOMPATIBLE_DESTINATION

[Lawrence Conroy]

Hi there,
 Are you sure about fS allowing PCMU?
According to the remote SDP, your incall is proposing PCMU as its top choice; g729 is 2nd best (quite right too :).
Forcing the adtran to offer only PCMU should not make ay difference to that -- it'll still propose PCMU so no change.
Either your setup is somehow blocking PCMU on the b-leg (but I'd expect to see that on the log), OR is trying to transcode because the b-leg requires some (non-PCMU) codec and can't (again, I'd expect that to be logged), OR fS is not accepting PCMU.
Assuming that PCMU is in the fS vars codec lists, does your dialplan do anything funky with the codec list for an incall?
all the best,
  Lawrence

On 16 Aug 2013, at 21:06, Royce Mitchell III wrote:
> My FreeSWITCH is configured to prefer PCMU, and the devices it is talking
> to are Adtran 908e's. The Adtrans are configured for the default codec
> group which is supposed to be PCMU, but I can reconfigure them to
> explicitly allow only PCMU. I will try that and see if it makes a
> difference.
> 
> 
> 
> Royce Mitchell, IT Consultant
> ITAS Solutions
> royce3 at itas-solutions.com
> 
> 
> On Fri, Aug 16, 2013 at 11:04 AM, Steven Ayre <steveayre at gmail.com> wrote:
> 
>> INCOMPATIBLE_DESTINATION means a codec problem.
>> 
>> The remote SDP sends they're offerring PCMU and G729.
>> 
>> What codecs are you allowing, what codecs are you bridging with, and since
>> G729 is on the list are you perhaps trying to transcode without using
>> mod_com_g729+licenses?
>> 
>> 
>> On 16 August 2013 16:07, Royce Mitchell III <royce3 at gmail.com> wrote:
>> 
>>> 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 at 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 at 192.168.1.212:5080 [BREAK]
>>> 2013-08-16 09:08:20.048687 [DEBUG] switch_core_session.c:1006 Send signal
>>> sofia/external/******9333 at 192.168.1.212:5080 [BREAK]
>>> 2013-08-16 09:08:20.048687 [DEBUG] switch_core_state_machine.c:416
>>> (sofia/external/******9333 at 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 at 192.168.1.212:5080) State NEW
>>> 2013-08-16 09:08:20.068687 [DEBUG] sofia.c:5793 Channel sofia/external/
>>> ******9333 at 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 at 192.168.1.212:5080 [CS_NEW] [INCOMPATIBLE_DESTINATION]
>>> 
>>> 
>>> 
>>> Royce Mitchell, IT Consultant
>>> ITAS Solutions
>>> royce3 at itas-solutions.com
>>> 
>>> _________________________________________________________________________
>>> Professional FreeSWITCH Consulting Services:
>>> consulting at freeswitch.org
>>> http://www.freeswitchsolutions.com
>>> 
>>> 
>>> 
>>> 
>>> Official FreeSWITCH Sites
>>> http://www.freeswitch.org
>>> http://wiki.freeswitch.org
>>> http://www.cluecon.com
>>> 
>>> FreeSWITCH-users mailing list
>>> FreeSWITCH-users at lists.freeswitch.org
>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>>> http://www.freeswitch.org
>>> 
>>> 
>> 
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> http://www.freeswitchsolutions.com
>> 
>> 
>> 
>> 
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://wiki.freeswitch.org
>> http://www.cluecon.com
>> 
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>> 
>> 
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> 
> 
> 
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
> 
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org