FreeSWITCH

FreeSWITCH doesn't passthru T38 offer from destination

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Incomplete
  • Affects Version/s: 1.0.7
  • Fix Version/s: None
  • Component/s: freeswitch-core, mod_sofia, mod_spandsp
  • Labels:
    None
  • Environment:
    CentOS 5.6, FreeSWITCH Version 1.0.head (git-8a8b70b 2011-06-26 13-30-05 +0000)
  • Platform:
    Linux x86_64/gcc
  • CPU Info:
    Hide
    System hostname blie-fs.blie-ent.com
    Operating system CentOS Linux 5.6
    Webmin version 1.550
    Time on system Sun Jun 26 22:06:36 2011
    Kernel and CPU Linux 2.6.24-23-xen on x86_64
    Processor information Quad-Core AMD Opteron(tm) Processor 2350 HE, 1 cores
    System uptime 1 hours, 25 minutes
    Running processes 103
    CPU load averages 0.05 (1 min) 0.02 (5 mins) 0.00 (15 mins)
    CPU usage 0% user, 0% kernel, 1% IO, 97% idle
    Real memory 256.21 MB total, 123.96 MB used
    Show
    System hostname blie-fs.blie-ent.com Operating system CentOS Linux 5.6 Webmin version 1.550 Time on system Sun Jun 26 22:06:36 2011 Kernel and CPU Linux 2.6.24-23-xen on x86_64 Processor information Quad-Core AMD Opteron(tm) Processor 2350 HE, 1 cores System uptime 1 hours, 25 minutes Running processes 103 CPU load averages 0.05 (1 min) 0.02 (5 mins) 0.00 (15 mins) CPU usage 0% user, 0% kernel, 1% IO, 97% idle Real memory 256.21 MB total, 123.96 MB used
  • GCC Version:
    4.1.2
  • FreeSWITCH GIT Revision:
    FreeSWITCH Version 1.0.head (git-8a8b70b 2011-06-26 13-30-05 +0000)
  • Reproduced with GIT HEAD?:
    yes

Description

ATA set to T.38 Autodetect. FreeSWITCH set to T38 Enable and T38 Passthru.

If the Destination accepts T.38, the carrier offers T.38. FreeSWITCH is not passing the offer through to the ATA and the call is timing out.

Siptrace and pcap's are provided.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Rob Morin added a comment -
This might be related to FS-3371, which is the behavior when T38 is disabled on FreeSWITCH.
Show
Rob Morin added a comment - This might be related to FS-3371 , which is the behavior when T38 is disabled on FreeSWITCH.
Hide
Permalink
Rob Morin added a comment -
This is ATA independant - have tried calls with both Grandstream 502 and Cisco/Linksys SPA 2102. Same results.
Show
Rob Morin added a comment - This is ATA independant - have tried calls with both Grandstream 502 and Cisco/Linksys SPA 2102. Same results.
Hide
Permalink
Anthony Minessale II added a comment -
If you think its related then why are you opening more than one bug.
Also, why do you keep attaching zip files? Our policy is to attach readable files in text format individually so they can be easily accessed into the browser.
Show
Anthony Minessale II added a comment - If you think its related then why are you opening more than one bug. Also, why do you keep attaching zip files? Our policy is to attach readable files in text format individually so they can be easily accessed into the browser.
Hide
Permalink
Anthony Minessale II added a comment -
Description:
ATA set to T.38 Autodetect. FreeSWITCH set to T38 Enable and T38 Passthru.

We do not support both of these options at once you must choose only 1.
Show
Anthony Minessale II added a comment - Description: ATA set to T.38 Autodetect. FreeSWITCH set to T38 Enable and T38 Passthru. We do not support both of these options at once you must choose only 1.
Hide
Permalink
Rob Morin added a comment -
I submitted more than one bug because while the behavior was the same, the expected behavior was not. In the case of FS-3370, FreeSWITCH is expected to pass the T38 request to the A leg. It doesn't. In the case of FS-3371, FreeSWITCH is expected to respond with a 488, T.38 not accepted here. Again it does not. But, in both cases, it is receiving a request for T.38 from the destination and not performing as expected. So, it MIGHT be related (if the same fix solves both issues), or it might not. I'm just trying to help by providing as much potentially relevant information as I can.

As for the zip files, I apologize. The jira interface did not provide the 'policy' and it wasn't clear to me that I would be allowed to upload more than one file. So I was combining them into one file. I'll know better next time.

Re: "FreeSWITCH set to T38 Enable and T38 Passthru. We do not support both of these options at once you must choose only 1. "

I didn't realize that these were exclusive operating conditions. I deleted the line enabling T38 and kept the T38 Passthru. There was no change in the performance; it's still not connecting.

I'll re-prepare the test environment, collect and submit the same information. As separate files this time.
Show
Rob Morin added a comment - I submitted more than one bug because while the behavior was the same, the expected behavior was not. In the case of FS-3370 , FreeSWITCH is expected to pass the T38 request to the A leg. It doesn't. In the case of FS-3371 , FreeSWITCH is expected to respond with a 488, T.38 not accepted here. Again it does not. But, in both cases, it is receiving a request for T.38 from the destination and not performing as expected. So, it MIGHT be related (if the same fix solves both issues), or it might not. I'm just trying to help by providing as much potentially relevant information as I can. As for the zip files, I apologize. The jira interface did not provide the 'policy' and it wasn't clear to me that I would be allowed to upload more than one file. So I was combining them into one file. I'll know better next time. Re: "FreeSWITCH set to T38 Enable and T38 Passthru. We do not support both of these options at once you must choose only 1. " I didn't realize that these were exclusive operating conditions. I deleted the line enabling T38 and kept the T38 Passthru. There was no change in the performance; it's still not connecting. I'll re-prepare the test environment, collect and submit the same information. As separate files this time.
Hide
Permalink
Jeff Lenk added a comment -
Please reopen if you have more followup
Show
Jeff Lenk added a comment - Please reopen if you have more followup
Hide
Permalink
Auto Admin added a comment -
Due to a long period of inactivity (13 or more days), this issue is due to be automatically close within 24 hours.
If this issue is not actually resolved, please reopen it and add appropriate comments to help developers fix the issue.

Thanks,
  Jira Admin
Show
Auto Admin added a comment - Due to a long period of inactivity (13 or more days), this issue is due to be automatically close within 24 hours. If this issue is not actually resolved, please reopen it and add appropriate comments to help developers fix the issue. Thanks,   Jira Admin
Hide
Permalink
Auto Admin added a comment -
Since there has been no change to the status of this issue, it is being closed for inactivity

Thanks,
  Jira Admin
Show
Auto Admin added a comment - Since there has been no change to the status of this issue, it is being closed for inactivity Thanks,   Jira Admin

People

  • Assignee:
    Anthony Minessale II
    Reporter:
    Rob Morin
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: