better still,

1) update to trunk with "make current"

2) Try to reproduce, if you can:
 a) open a new shell
 b) make sure you have gdb and gcore installed
 c) run ./support-d/fscore_pb gcore
 d) report the URL




On Tue, Oct 20, 2009 at 8:48 PM, Michael Jerris <mike@jerris.com> wrote:
REPORTING is the state that it writes to CDR.  If you have calls stuck
in this state, take one and try to use uuid_kill on it and see if it
goes away, then get a core off of it and pastebin the thread apply all
bt (with no other calls up).  What modules are you using for cdr and
with what configuration?

Mike

On Oct 20, 2009, at 11:47 AM, Dome Charoenyost wrote:

> Dear All
> What's CS_REPORTING state ?
> I found many channels not hang up  ans state is CS_REPORTING
> e264f84a-bd87-11de-9a90-2320c02172de,outbound,2009-10-20
> 21:50:26,1256050226,sofia/external/xxxxxxxxxxxx@xxx.xxx.xx.
> 191:7050,CS_REPORTING,FreeSWITCH,xxxxxxxxxxxxxxxxxxxx,xx.xxx.xxx.xxx,
> 7050,,,XML,public,,,,,





--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400