[Freeswitch-users] T.38 with Re-INVITE question
DJB International
djbinter at gmail.com
Fri Sep 14 03:07:31 MSD 2012
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?
Example of 2 FS CDRs below:
1 : caller_id_name = +16193301897
2 : caller_id_number = +16193301897
3 : aniii = 0
4 : destination_number = +12133456789
5 : context = routing
6 : start_stamp = 2012-09-13 21:12:13
7 : answer_stamp = 2012-09-13 21:12:13
8 : end_stamp = 2012-09-13 21:14:06
9 : duration = 113
10: billsec = 113
11: hangup_cause = NORMAL_CLEARING
12: channel_name = sofia/fs/+16193301897 at 1.2.3.4:5060
13: bridge_channel =
14: network_addr = 1.2.3.4
15: remote_ip_last_arg = sofia/fs/2133456789 at 6.7.8.9
16: bleg_network_addr = 6.7.8.9
17: sip_hangup_disposition = recv_bye
18: endpoint_disposition = ANSWER
*****************************************
1 : caller_id_name = 2133456789
2 : caller_id_number = 2133456789
3 : aniii =
4 : destination_number = mod_sofia
5 : context = routing
6 : start_stamp = 2012-09-13 21:12:13
7 : answer_stamp = 2012-09-13 21:12:13
8 : end_stamp = 2012-09-13 21:14:06
9 : duration = 113
10: billsec = 113
11: hangup_cause = NORMAL_CLEARING
12: channel_name = sofia/fs/2133456789 at 6.7.8.9
13: bridge_channel =
14: network_addr = 6.7.8.9
15: remote_ip_last_arg =
16: bleg_network_addr =
17: sip_hangup_disposition = send_bye
18: endpoint_disposition = INBOUND CALL
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20120913/37ca1fa9/attachment-0001.html
Join us at ClueCon 2011 Aug 9-11, 2011
More information about the FreeSWITCH-users
mailing list