On Dec. 8, 2014, 9:19 a.m., Joshua Colp wrote:
branches/13/res/res_pjsip_outbound_publish.c, lines 1234-1248
https://reviewboard.asterisk.org/r/4178/diff/4/?file=69544#file69544line1234
I'd opt for verbose messages for these.
And a reasonably high level for that. Probably Verbose
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4246/
---
(Updated Dec. 9, 2014, 7:59 a.m.)
Status
--
This change has been
Tonight several community services will have intermittent
availability due to maintenance. This maintenance will begin at
approximately 9:00 PM CST[1] and should last no longer than three
hours, ending around 12:00 AM CST.
The affected services are:
* JIRA issue tracker (issues.asterisk.org)
*
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4243/
---
(Updated Dec. 9, 2014, 9:44 a.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4244/
---
(Updated Dec. 9, 2014, 9:47 a.m.)
Status
--
This change has been
On Dec. 8, 2014, 7:53 p.m., Matt Jordan wrote:
/branches/1.8/main/lock.c, lines 135-141
https://reviewboard.asterisk.org/r/4247/diff/2/?file=69604#file69604line135
Given the code in __ast_rwlock_init, I'm not sure this code should
still be commented out. Going _way_ back in time,
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4247/
---
(Updated Dec. 9, 2014, 11:21 a.m.)
Review request for Asterisk
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4178/
---
(Updated Dec. 9, 2014, 12:35 p.m.)
Status
--
This change has been
During some testing being performed at Digium, a bit of unexpected
behavior was discovered. While testing local RTP native bridging (also
known as packet-to-packet or P2P bridging), RTP packets sent from
Asterisk had an unexpected source IP address. In the configuration,
Asterisk was bound to
Mark Michelson wrote:
snip
I propose the following algorithm as a fix for this issue:
1. If we are sending a media offer, and there is a configured
media_address on the endpoint to which we are sending the offer, then
bind the RTP stream to the media_address. This means that the rtp_ipv6
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4182/#review13932
---
Ship it!
Ship It!
- opticron
On Nov. 14, 2014, 5:03 p.m.,
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4216/
---
(Updated Dec. 9, 2014, 2:01 p.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4245/
---
(Updated Dec. 9, 2014, 2:19 p.m.)
Status
--
This change has been
On 12/09/2014 01:42 PM, Joshua Colp wrote:
Mark Michelson wrote:
snip
more snips
So, yes. In an ICE scenario the code will provide candidates for all
local addresses. If you are bound to only one then all the others will
fail. This should be taken into account - but it ultimately
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4182/
---
(Updated Dec. 9, 2014, 2:46 p.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4232/
---
(Updated Dec. 9, 2014, 2:55 p.m.)
Status
--
This change has been
Mark Michelson wrote:
On 12/09/2014 01:42 PM, Joshua Colp wrote:
Mark Michelson wrote:
snip more snips
So, yes. In an ICE scenario the code will provide candidates for all
local addresses. If you are bound to only one then all the others will
fail. This should be taken into account - but it
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4108/#review13933
---
Summary of this weak ref implementation:
weak_proxy_obj - obj
18 matches
Mail list logo
