[Freeswitch-users] T.38 with Re-INVITE question

Dorn DJBinter djbinter at gmail.com
Fri Sep 14 19:32:23 MSD 2012


Thank you for your suggestion; however, as mentioned, both CDRs are
a-leg and related to only the T.38 re-INVITE call behavior only.

Sent from my iPad


On Sep 14, 2012, at 2:38 AM, Gabriel Gunderson <gabe at gundy.org> wrote:

> On Thu, Sep 13, 2012 at 5:07 PM, DJB International <djbinter at gmail.com> wrote:
>> I was testing T.38 with Re-INVITE.
>>
>> Call Flow:  Inbound Carrier (1.2.3.4) -> FS (Bypass Media) -> Outbound
>> Carrier that will send T.38 Re-INVITE (6.7.8.9).
>>
>> However, I noticed that FS generated 2 CDRs for the same call, which are: 1)
>> A-leg CDR from inbound carrier, and also 2) A-leg CDR from outbound carrier
>> that send T.38 Re-INVITE.
>>
>> I am wondering whether this is a normal behavior, or there is a way to
>> ignore the 2nd CDR?
>
>
> Does this help?
>
> process_cdr <-- indicates how to process CDR records.
>
> http://wiki.freeswitch.org/wiki/Channel_Variables#process_cdr
>
>
> Good luck.
>
> Gabe
>
> _________________________________________________________________________
> 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



Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users mailing list