Scott<br><div><br></div><div>In the past we have had a ton of issues exactly as your stating! Dealing with WebEX is like trying to hurd cats. Last issues took over 60 days to resolve so we located another number for them and did some static routes to it. I think we did block them at one<span></span> point but this was years back so I don't recall.<div>
<br></div><div>I hope all is well</div><div>Zak<br><br>On Friday, September 20, 2013, Scott Berkman wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple">
<div><p class="MsoNormal">All,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"> We’ve been getting a number of reports recently from customers about what they are calling “dropped calls” (thanks Cingular commercials) on WebEx TF conference lines, meaning they lose an audio path mid-call. This usually impacts only the one caller (other callers on the bridge are apparently not impacted) and we’re getting these reports for calls traversing a variety of termination carriers with not much of anything else in common.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"> Anyone else getting similar reports or dealt with something similar with WebEx?<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">
Thanks,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"> -Scott<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p></div></div></blockquote></div></div><br>
<br>-- <br><div dir="ltr"><p><span style="font-size:13.5pt;font-family:"Arial","sans-serif"">Zak Rupas</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif"">VoIP Engineer<br>
<b>SimpleSignal</b><br>
Anywhere: 303-242-8606</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""></span></p>
<br></div><br>