[asterisk-bugs] [Asterisk 0012078]: [patch] T38 passthru broken in trunk
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Feb 26 19:03:04 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12078
======================================================================
Reported By: dimas
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 12078
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!): 104215
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 02-26-2008 16:26 CST
Last Modified: 02-26-2008 19:03 CST
======================================================================
Summary: [patch] T38 passthru broken in trunk
Description:
People are reporting broken T38 passthru in the trunk.
It appears that my patch for issue 11630 while fixes the problem desctibed
in the issue introduces new one. To remind the issue 11630 was about
t38state receiving wrong value when 200 OK for our T38 reinvite is
received. The problem is that the passthru code depends on that wrong
value.
Attached patch fixes the problem.
======================================================================
----------------------------------------------------------------------
dimas - 02-26-08 19:03
----------------------------------------------------------------------
Almost forgot. It looks like when the new AST_CONTROL_T38 frame is read
when in the native bridging, it aborts the loop and following output on the
console is seen:
[Feb 17 21:41:10] DEBUG[12822]: rtp.c:3391 bridge_native_loop: Got a
FRAME_CONTROL (19) frame on channel SIP/2000-08c9fb18
[Feb 17 21:41:10] DEBUG[12822]: channel.c:4418 ast_channel_bridge:
Returning from native bridge, channels: SIP/2000-08c9fb18,
SIP/lab3-08cb44e0
However next line says
-- Native bridging SIP/2000-08c9fb18 and SIP/lab3-08cb44e0
and things actually do work. But if it is good idea to avoid this
behavior, than the secons pacth (v1-12078-2.patch) must be applied too.
Issue History
Date Modified Username Field Change
======================================================================
02-26-08 19:03 dimas Note Added: 0082997
======================================================================
More information about the asterisk-bugs
mailing list