[asterisk-bugs] [Asterisk 0012815]: BRIDGEPEER variable not updated on attended transfer when codec translation is used.

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Jun 10 07:49:02 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12815 
====================================================================== 
Reported By:                ramonpeek
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   12815
Category:                   Channels/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.20.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             06-09-2008 07:24 CDT
Last Modified:              06-10-2008 07:48 CDT
====================================================================== 
Summary:                    BRIDGEPEER variable not updated on attended transfer
when codec translation is used.
Description: 
When a call is attended transferred from extension A to C by extension B,
and extension A uses a different codec than B or C (for example g.729,
instead of G.711) the BRIDGEPEER variable is not updated.

I've tested this using a simple setup with SIP channels that have
canreinvite set to no.

I noticed that the BRIDGEPEER variable is set correctly on the first
bridge between extension A and B, but when B attended transfers A to C the
BRIDGEPEER variable is not update upon transfer.
If all peers use G.711 this does happen!


I've attached two traces;
One in which the BRIDGEPEER is set correctly because we are using G.711 on
all peers and the other one where the BRIDGEPEER variable is not updated
because peer A uses G.729.
In this trace SIP/400 is peer A, SIP/401 is peer B and SIP/402 is peer C.

====================================================================== 

---------------------------------------------------------------------- 
 svnbot - 06-10-08 07:48  
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 121445

_U  branches/1.6.0/
U   branches/1.6.0/main/channel.c

------------------------------------------------------------------------
r121445 | file | 2008-06-10 07:48:44 -0500 (Tue, 10 Jun 2008) | 20 lines

Merged revisions 121444 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

................
r121444 | file | 2008-06-10 09:54:39 -0300 (Tue, 10 Jun 2008) | 12 lines

Merged revisions 121442 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r121442 | file | 2008-06-10 09:52:06 -0300 (Tue, 10 Jun 2008) | 4 lines

Update BRIDGEPEER variable before we do a generic bridge in case we just
broke out of a native bridge and fell through to generic.
(closes issue http://bugs.digium.com/view.php?id=12815)
Reported by: ramonpeek

........

................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=121445 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-10-08 07:48  svnbot         Checkin                                      
06-10-08 07:48  svnbot         Note Added: 0088519                          
======================================================================




More information about the asterisk-bugs mailing list