[asterisk-bugs] [Asterisk 0008677]: Asterisk does not reinvite peer for G.711 after T.38 negotiated failed with a "488" Event

[noreply at bugs.digium.com]

The following issue has been ASSIGNED. 
====================================================================== 
http://bugs.digium.com/view.php?id=8677 
====================================================================== 
Reported By:                alex-911
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   8677
Category:                   Channels/chan_sip/T.38
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4 
SVN Revision (number only!): 59083 
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             12-27-2006 08:13 CST
Last Modified:              11-02-2007 10:05 CDT
====================================================================== 
Summary:                    Asterisk does not reinvite peer for G.711 after T.38
negotiated failed with a "488" Event
Description: 
I have a linksys ATA connected to asterisk, configured for G.711 fax
passthru. asterisk is connected to a Cisco PSTN gateway. the default fax
protocol of the PSTN gateway is T.38, so if the Cisco media gateway detects
faxtone, there is a reinvite for T.38.
asterisk passes the reinvite down to the ATA. the ATA answers correctly
with a "488 not acceptable here".
instead of passing the 488 up to the proxy, asterisk seems to stop here.
it receives the retransmit of the reinvite and answers with a "503
Unavailable".
I would expect asterisk to pass the 488 up what would trigger another
reinvite for T.30 fax (G.711 passthru).

I'll post the simple call flow and the console log below. let me know if
more details are required.
10.10.10.23: ATA
172.16.16.111: *
172.16.16.155: SIP Proxy
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0009345 Problems
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-02-07 10:05  file           Status                   confirmed => assigned
11-02-07 10:05  file           Assigned To               => file            
======================================================================