On 10/29/2009 11:48 AM, Tony Graziano wrote: > > 4.0.4 has three outstanding issues right now according to the tracker. > > http://track.sipfoundry.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10130&fixfor=10640 > <http://track.sipfoundry.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10130&fixfor=10640> > > > I'm not sure any of these address your issue or contribute to your CDR > issue. > > I do know that since 4.0 I have seen many CDR related issues that > describe your issue unless your are running Polycom firmware 3.2.1. > > If you make changes to your dialplan, siptrunking, mediarelay while > calls in progress I suppose a call might get stuck in CDR. You can > restart the CDR services from the server page in sipxconfig to clear the > CDR "stuck' calls too. > > I am also pretty confused at how to read the CDR right now, because in > 4.0.0-4.0.3 I see a lot of calls marked as "failed" that should not be, > especially if they go through a hunt group, get placed on hold, or go > through an AA. I just haven't made it a priority to figure out why.
It appears that if the call goes to voicemail it is marked as failed, or any unanswered call. -- Regards -------------------------------------- Gerald Drouillard Technology Architect Drouillard & Associates, Inc. http://www.Drouillard.biz _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
