[asterisk-bugs] [Asterisk 0009154]: [patch] native bridging support for chan_skinny

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9154 
====================================================================== 
Reported By:                DEA
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   9154
Category:                   Channels/chan_skinny
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4 
SVN Revision (number only!): 56094 
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             02-26-2007 21:07 CST
Last Modified:              08-03-2007 17:56 CDT
====================================================================== 
Summary:                    [patch] native bridging support for chan_skinny
Description: 
Possibly a bit rough, but so far it passes tests for 
core and native bridging.  P2P appears to need some
work, but I thought I might have enough to solicit
feedback.
====================================================================== 

---------------------------------------------------------------------- 
 DEA - 08-03-07 17:56  
---------------------------------------------------------------------- 
Correct on sub->canreinvite, that is a hold over from my first pass before
I decided that decision should be based on the line.

It looks like I can add:
ast_rtp_get_us(rtp, &us);

Below the test:
if (!(l->canreinvite) || (l->nat)){

In skinny_set_rtp_peer.  At that point in the code we know we have
an rtp structure, and there is no point setting it fi we are not going to
use it.

Do you want a patch with these changes? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-03-07 17:56  DEA            Note Added: 0068421                          
======================================================================