[asterisk-bugs] [Asterisk 0011630]: [patch?] SIP t38state is not properly set
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Jan 22 09:25:56 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11630
======================================================================
Reported By: dimas
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11630
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 94396
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 12-23-2007 18:52 CST
Last Modified: 01-22-2008 09:25 CST
======================================================================
Summary: [patch?] SIP t38state is not properly set
Description:
There is a bug in the current implementation of process_sdp when it finds
T38 UDPTL information. The code sets state to either T38_PEER_REINVITE or
T38_PEER_DIRECT depending on if it is a reinvite or not.
However the process_sdp is also called to process 200 OK message we
receive in reply to our T38 INVITE. As result, when we reinvite for T38,
t38state just changed to T38_LOCAL_REINVITE will be reset to
T38_PEER_something upon receipt of OK and never reaches T38_ENABLED.
======================================================================
----------------------------------------------------------------------
oej - 01-22-08 09:25
----------------------------------------------------------------------
Sorry that no one has answered you. I'll assign this to file as our T.38
expert :-)
Issue History
Date Modified Username Field Change
======================================================================
01-22-08 09:25 oej Note Added: 0081015
======================================================================
More information about the asterisk-bugs
mailing list