diff options
author | Joshua Colp <jcolp@digium.com> | 2015-06-10 20:28:26 -0300 |
---|---|---|
committer | Joshua Colp <jcolp@digium.com> | 2015-06-11 17:04:04 -0500 |
commit | 7230ee2efe33083d036fa8de7bc1c431900f2bd8 (patch) | |
tree | 3ef505544a8e7d1842e8ab09348e036d2e22209c /CHANGES | |
parent | b23f33e7e5bc1524d3e2b3536174590db575055e (diff) |
bridge: When performing a blonde transfer update connected line information.
When performing a blonde transfer the code uses the old masquerade
mechanism to move a channel around. As a result of this certain information,
such as connected line, is moved between the channels involved. Upon
completion of the move a frame is queued which is supposed to update the
connected line information on the channel. This does not occur as the
code considers it a redundant update since the masquerade operation
updated the channel (but did not inform it of the new connected line
information). The code also does not queue a connected line update
to be handled by the thread handling the channel. Without this any
other channel that may be loosely involved does not know it is
talking to a different caller.
This change does the following to resolve this:
1. The indicated connected line information is cleared upon
completion of the masquerade operation when doing a blonde transfer.
This prevents the connected line update from being considered
redundant.
2. A connected line update frame is now queued upon the completion
of the masquerade operation so any other channel loosely involved
knows that there is a different caller.
ASTERISK-25157 #close
Reported by: Joshua Colp
Change-Id: Ibb8798184a1dab3ecd35299faecc420034adbf20
Diffstat (limited to 'CHANGES')
0 files changed, 0 insertions, 0 deletions