Forum Discussion
Unable to make outbound video or voice calls using my ISP (CarryTel)
I have an unusual problem. When I'm connected wirelessly to my ISP (CarryTel) I am unable to make outbound calls via teams to contacts within my organization. Two things happen when I make the outbound calls 1. The people hear my voice and see my video but I can't see them or hear them, and then the call drops. 2. The call connects, it's a blank screen and then drops automatically.
I can receive calls, both voice and video from people within my organization.
When I tether to my phone, I am able to make outbound calls to people within my organization. When I connect to another wireless network (outside of my home) I can make outbound calls.
Obviously, something is wrong with my ISP/Wireless connection. But what? Has anyone noticed this issue before?
10 Replies
- zkleimanCopper Contributor
PGandhi Hey, I never provided an update as forget where this question was posted. It turns out it was the Carrytel modem/hardware issue. I don't know what setting or aspect of the modem was the issue. I bought a new wireless modem and used the one supplied by carrytel as a bridge and my problem was solved.
Regardless, if you have problems or not with making outbound calls, I suggest bridging the carrytel modem to a superior product to boost your wireless speed and reliability.
- Naser735Copper Contributor
zkleiman I have the same problem.
Can you please let me know what model router I should buy?
Also, can you please confirm the steps in order to make the Carry tell modem a bridge.
Should I connect the new modem to the carrytel with a lan cable and transmit internet via wifi from the new modem?
Please let me know. This problem is annoying me and Carrytel has no clue about the solution.
zkleiman I'd try using web client and see if issue persists. Also another device if possible like your phone app on your wifi. Since your initiating the call, either your firewall or ISP may be blocking or doing something with the data that Teams uses. When you take an inbound call it's probably on random ports so it doesn't effect it the same.
- zkleimanCopper Contributor
ChrisWebbTech Thanks for the quick response. The web client worked for outbound calls. It felt good to finally do a successful outbound call!
What do you propose as the next step now that we've somewhat isolated the issue?
Zach Kleiman
- ThereseSolimenoSilver Contributor
Hello zkleiman I'm going to ask ChrisWebbTech to help here