res_pjsip_t38: Fix T.38 failure when peer reinvites immediately.
authorJoshua Colp <jcolp@digium.com>
Tue, 16 Dec 2014 15:44:43 +0000 (15:44 +0000)
committerJoshua Colp <jcolp@digium.com>
Tue, 16 Dec 2014 15:44:43 +0000 (15:44 +0000)
commitb5182a6795d726c87511a2639e58452b9889c054
tree4cf811edc66a63ad0b8634a2edeec2b02dee395e
parent39b54a21dc96f04b2e37143553946089c45b94a2
res_pjsip_t38: Fix T.38 failure when peer reinvites immediately.

If a remote endpoint reinvites to T.38 immediately the state machine
will go into a peer reinvite state. If a T.38 capable application
(such as ReceiveFax) queries it will receive this state. Normally
the application will then indicate so that the channel driver will
queue up the T.38 offer previously received. Once it receives this
offer the application will act normally and negotiate.

The res_pjsip_t38 module incorrectly partially squashed this indication.
This would cause the application to think the request had failed when
in reality it had actually worked.

This change makes it so that no T.38 control frames (or indications)
are squashed.
........

Merged revisions 429612 from http://svn.asterisk.org/svn/asterisk/branches/13

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@429613 65c4cc65-6c06-0410-ace0-fbb531ad65f3
res/res_pjsip_t38.c