topic Long distance not working in Get Support

Long distance not working

Kkahwu — Wed, 05 Jan 2022 12:34:07 GMT

I have the $25 for 30 days plan, which includes Unlimited Canada-wide Talk. I'm currently living in Ontario, and just tried calling my nan who's in Newfoundland, and I got a message saying that I do not have the correct add on for long distance calling. Now, unlimited Canada wide talk means I can call any province, correct? If so, why isn't it working?

Re: Long distance not working

GR — Mon, 14 Oct 2019 19:28:35 GMT

@Kkahwu try again and put a 1 in front of the number or let it go after you hear that message and it should connect! I just put 1 in front of all my saved numbers in my contacts

Re: Long distance not working

totalUser — Mon, 14 Oct 2019 19:38:13 GMT

Hi @Kkahwu

Could you please check if you dialed correctly.

Every time this happens to me I ended up dialing USA number accidentally.

@Kkahwu wrote:
I have the $25 for 30 days plan, which includes Unlimited Canada-wide Talk. I'm currently living in Ontario, and just tried calling my nan who's in Newfoundland, and I got a message saying that I do not have the correct add on for long distance calling. Now, unlimited Canada wide talk means I can call any province, correct? If so, why isn't it working?

Re: Long distance not working

computergeek541 — Mon, 14 Oct 2019 20:00:31 GMT

@Kkahwu wrote:
I have the $25 for 30 days plan, which includes Unlimited Canada-wide Talk. I'm currently living in Ontario, and just tried calling my nan who's in Newfoundland, and I got a message saying that I do not have the correct add on for long distance calling. Now, unlimited Canada wide talk means I can call any province, correct? If so, why isn't it working?

The message about long distance charges possibly applying can be bypassed entirely but dialing a 1 in front of the area code.

The message about needing a long distance add-on or that talk is not included in the plan cannot be fixed by simply inserting a 1. If the number is being dialed correctly, this might be an account provisioning issue.