<div dir="ltr">I'm trying to track down why Google Voice isn't working for me. When it stopped working a couple months ago, I learned that I needed to disable the video codec in autoload_configs/dingaling.conf.xml. That fixed things for a while, but for the past month it has been failing again.<div>
<br></div><div>In my debug log for an INCOMING call, I see this:<div><br></div><div><div>2013-04-19 14:30:37.154689 [DEBUG] mod_dingaling.c:1584 Send rtp Candidate <a href="http://mysubdomain.dyndns.com:17554">mysubdomain.dyndns.com:17554</a> [27Pe5xE7PiNurvTC]</div>
<div>2013-04-19 14:30:37.154689 [DEBUG] mod_dingaling.c:1584 Send rtcp Candidate <a href="http://mysubdomain.dyndns.com:17555">mysubdomain.dyndns.com:17555</a> [mnwhL1eq9SKrduUQ]</div><div>2013-04-19 14:30:37.154689 [DEBUG] mod_dingaling.c:1627 Accepted 0 of 0 rtp candidates.</div>
<div>2013-04-19 14:30:37.154689 [DEBUG] mod_dingaling.c:1629 Accepted 0 of 0 rtcp candidates.</div><div>2013-04-19 14:30:37.154689 [DEBUG] mod_dingaling.c:1632 Accepted 0 of 0 video_rtp candidates</div><div>2013-04-19 14:30:37.154689 [DEBUG] mod_dingaling.c:1635 Accepted 0 of 0 video_rctp candidates</div>
</div><div><br></div><div><br></div><div style>The domain is correct, but where is mod_dingaling getting those random port numbers? Those ports are not available on my network. </div><div style><br></div><div style>Shouldn't mod_dingaling use the port range that is specified in autoload_configs/switch.conf.xml? How do I give mod_dingaling a range of ports to use?</div>
<div style><br></div><div style>To put this in context, I'm trying to track down why Google Voice is no longer working for me. I got the "Accepted 0 of 0 candidates" errors a few months ago, but I removed the video codec from autoload_configs/dingaling.conf.xml, and the problem went away. Now those error messages are back, and I can't send or receive calls via Google Voice. Updated to the latest git on April 15th. (1.5.1b+git~20130415T194750Z~be248879ae (git be24887 2013-04-15 19:47:50Z)), and still the same problem as on the February build that I was running before.</div>
<div style><br></div><div style><br></div><div style><br></div></div></div>