[asterisk-bugs] [JIRA] (ASTERISK-22349) Behavioral change in Asterisk 11: udptl now requires config file to function

[Jonathan Rose (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ASTERISK-22349 started by Jonathan Rose.

> Behavioral change in Asterisk 11: udptl now requires config file to function
> ----------------------------------------------------------------------------
>
>                 Key: ASTERISK-22349
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22349
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>         Environment: Asterisk 11.3.0
>            Reporter: Jonathan Rose
>            Assignee: Jonathan Rose
>            Severity: Critical
>   Original Estimate: 1.5h
>  Remaining Estimate: 1.5h
>
> On inbound SIP faxes, Asterisk is sending a {{BYE}} about 5 seconds after receiving the {{ACK}}. Looking in the debug output, we're seeing the following:
> {noformat}
> [2013-07-05 11:54:04] DEBUG[1707][C-00000191] res_fax.c: Negotiating T.38 for receive on SIP/sip-lv1.flowroute.com-000003cc
> [2013-07-05 11:54:04] ERROR[1707][C-00000191] udptl.c: Could not access global udptl options!
> [2013-07-05 11:54:04] WARNING[1707][C-00000191] chan_sip.c: UDPTL creation failed - disabling T38 for this dialog
> [2013-07-05 11:54:04] ERROR[1707][C-00000191] res_fax.c: error initializing channel 'SIP/sip-lv1.flowroute.com-000003cc' in T.38 mode
> {noformat}
> It's unclear why we're seeing these messages, and they do have the *t38pt_udptl* setting enabled in {{sip_general_additional.conf}}, so I'm not sure what else we should be trying.
> The customer provides a voicemail-to-email service, so they are basically experiencing a service outage at this point.
> I'm attaching the autosupport info, pcap file and full log.
> The relevant call ID is {{1996637106_69507902 at 4.55.17.35}}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira