• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Webex Users Call In Options

BarkingGhostar

Diamond Member
I have been suspecting something dark and seedy in how the Cisco Webex is setup in my wife's place of employment. She is employed by the University System of Georgia and is faculty at Georgia State University. This means not only is her place of employment treated as government (USG) but also academic (GSU.edu).

During the last two weeks I have been helping her on a variety of things as the institution moves from the congregated form of instruction to online instruction. During the Webex testing my wife would send me an invite at a throwaway Gmail account and while booted into my Linux play box I would join the Webex conference. The only Call-In option is a Long Distance number. Now the wife, her students, the institutions staff and administration are all in the state of Georgia, but to Call-In every freaking one of them dials a Long Distance Toll number for telephone audio. Also, the form of Webex installed doesn't provide Webex system Call-Me option, where Webex will call you at a number you provide. This is something my own employer offers and I use everyday.

Initially, I thought that maybe the problem was just in the way my wife's Webex account is setup. So, we went investigating and discovered Webex meeting invites she has received over the years for school-only related events reflected the only telephone option was a Call-In Long Distance Toll call. Made no difference everyone was in the same city, they were all going to be placing long distances calls. Worse yet, no one on my wife's level within the institution or on the government level seems to care. It is--being cynical here--almost as if there is some arrangement taking place between the LD operators and Webex and USG/GSU and money is exchanging hands for making all of those unnecessary long distance calls when they should have been local numbers.

So, for those of you using Webex what are the Call-In option setup like for you? Is the Call-In number local, or toll/LD? Does your employer pay Cisco for a level of Webex that includes a Call-Me option?
 
What do you mean "long distance toll?" You mean they are charging users who call in? I have never paid a toll calling in to a webex meeting. I'm guessing the number is long distance because webex is a nationwide company and no one really pays extra for long-distance calling anymore, that's mostly a thing of the past.
 
You think money isn't being counted and changing hands within the telephone system for toll calls? You are wrong. Whether its inclusive or not someone is paying for it. If LD calls were truly free then no one, including big businesses, would bother with 800#. Even I work for the phone company and they provide us with a toll-free number to call in, but since my employer pays for the Call-Me option then I ain't making any calls.
 
I am in 916 (Sacramento), my main office is in 530 (Marysville). When I call into our WebExs, it's 408 (San Jose).
 
There are still charges for long distance calls?
I always use the Call-Me option, and for the rare instances when I need to call in, I use my cell phone.
 
I'm pretty sure it's her employer's fault. Our WebEx has options for a local area code, 800 number, and directly through the computer.
 
Folks, I work in telecom. Imagine you dialing in or even Webex calling you and it crosses multiple LD carriers. You think the receiving carrier isn't going to take the call for free? The United States has not given up on its LATA infrastructure and to this day continues to bill toll calls. Just because you do not see it on your end bill, broken down in all Crayola that you obviously need, doesn't mean it doesn't continue to exist. The only way around this, I think, is a pure VoIP solution because unlike Layer-2 LATA constructs, Layer-3 IP telephony is treated as a data service, not a voice service by the regulatory authorities.

But I believe that my's institution and the USG at large must be the culprit. Whether this is due to ignorance (and there is a lot of that out there, and in this thread) because why would you force people to tie up the national telephone grid when everyone is in the same city/toll region? Its just stupid, not bad design. Even when I asked my fellow telecom network designers they were shocked because it makes zero sense.
 
Back
Top