Hi,

 

I am on fs 1.0.trunk (12530M) testing G.722 and found that when using a ‘broken’ configuration from a softphone configured for G.722,  I get the warning on the cli:

 

“We were told to use ptime 20 but what they meant to say was 820

This issue has so far been identified to happen on the following broken platforms/devices:

Linksys/Sipura aka Cisco

ShoreTel

Sonus/L3

We will try to fix it but some of the devices on this list are so broken who knows what will happen..

“

when fs gets the invite, but then does a core dump when it tries to:

 

<anti-action application="bridge" data="sofia/${regext_sipprofile}/${dialed_extension}%${domain_name}"/>

 

 

Below are some of the traces and info output from before the core dump happens.

 

I see this when I run gdb on the dumpfile.

 

#0  0xb7e194d4 in switch_ivr_originate (session=0xb74640a8, bleg=0xb572b0b0, cause=0xb572b0ac, bridgeto=0xb74a1b18 "sofia/voxwan/8154%172.16.1.3", timelimit_sec=30,

    table=0xb7efcfc0, cid_name_override=0x0, cid_num_override=0x0, caller_profile_override=0x0, ovars=0x0, flags=<value optimized out>) at src/switch_ivr_originate.c:1609

1609                                            if (switch_core_codec_init(&write_codec,

 

(gdb) frame 1

#1  0xb6df48f5 in ?? () from /usr/local/freeswitch/mod/mod_dptools.so

 

 

I wonder if anybody else has seen this behavior?

 

This happens when the destination phone is also  G.722 capable (policom).

If I change the “frame per packet” setting in the  softphone to 2 – All works OK (but the default is 1 – so cant risk allowing G.722 if it’s going to core dump fs if a user make a wrong configuration)

 

 

Best Regards

 

Keith