NicV
@shawcable.net | Digital phone not accepting Telus and Bell Cell Phone calls
has anyone else had this problem? Digital phone not accepting Telus and Bell Cell Phone calls
We have switched to shaw digital 1 week ago and still havent been able to receive a cell phone call from either cell phone servers |
|
cableguy84
join:2006-09-12
Alberta | what to they get when they call you?
because you really have no troubleshooting ability with the phone other then resetting the DPT i suggest calling shaw as this is not normal at all. |
|
ninnpwint
join:2008-02-28
| reply to NicV
i have been using shaw digital phone since it came out, no problem getting calls from telus, telusmobility, bell cell phone calls and or any other countries calls.
did you accidentally activated the block calls features
--
ASUS P4P800SE, Intel P4 3GHz, 2GB RAM, XP-Pro(SP3), IE7 (default), FireFox, 80G disk, Symantec AntiVirus, PC Tools Spyware Doctor(non AV). |
|
NicV
@shawcable.net
| reply to NicV
I am in Chilliwack BC. When we try dialing we get a recording to check the number we dialed and call back again. It doesn't even ring on the Shaw landline. We are having the exact same problem with my husbands work lines as well. Both systems were installed on the same day. I ported a number from Telus and my husband received a new number from Shaw. |
|
rodst
Premium
join:2002-10-06
Victoria, BC | Call Shaw. |
|
AnonShawUser
join:2006-06-17
Calgary, AB | reply to NicV
Call Shaw. I remember reading a notice about some issues with Bell Mobility numbers being unable to contact Shaw Digital Phone customers, for some reason. I'm not in digital phone training yet so I don't have all the particulars. |
|
NicV
@shawcable.net | reply to NicV
We have called Shaw. They say it isnt their problem and to call Telus... I believe this is shaws problem, the phone line is through shaw not telus. |
|
cableguy84
join:2006-09-12
Alberta | when you call shaw ask them to push the number through the switch again (don't know if that's the tech term any more its been a while) but it sounds as if the number was not fully activated on the back end... also have them re provision your DPT's |
|
tlhIngan
join:2002-07-08
Richmond, BC
| reply to NicV
One thing to check would be to see if you have the "block anonymous calls" or other thing activated on your Shaw account. Telus and Bell phones may not report Caller ID information, which could cause Shaw to block the calls.
(The option is nominally enabled to keep telemarketers at bay, but some phone lines and cell phone providers don't provide that information. Instead, you get "Blocked" or "Number not available", which is what Shaw can block as a Digital Phone option.) |
|
playboy2000
join:2005-05-30
Calgary, AB | reply to NicV
It sounds like an issue with number portability, but with some sort of odd twist... |
|
stolen
join:2004-04-12
Calgary, AB
| reply to NicV
said by NicV :
We have called Shaw. They say it isnt their problem and to call Telus... I believe this is shaws problem, the phone line is through shaw not telus.
While it may be Telus' problem, Shaw should be handling it, since if you call Telus, they'll just tell you to pound sand since you're not their customer. Call shaw back and escalate until you get someone who can fix it. |
|
MattBC
In the gym, paying my dues
join:2006-02-01
Victoria, BC
| reply to NicV
It's a normal problem when Telco's get behind on their homework during number ports.
Think of it as DNS, as it essentially works in a very similar fashion. Say that ISP A and ISP B host their own DNS. Someone moves their hosting from one company to another, and makes the appropriate contact to their host. The host sends out the info, and then it is every ISP's responsibility to load the DNS onto their servers. ISP A has no issue with this, and ISP B does.
Customer on ISP A is able to route to the website in question, and customer on ISP B isn't. The issue lays with the ISP that has not updated the DNS issue on their servers, and has not done the DNS reload.
The Phone issue is the exact same thing, except with a Routing Table. While Shaw might be the provider, Shaw cannot "force" the reload on Telus's end.
However, there should be an escalation that occurs within Shaw to speak with Telus at a "higher level", as both Telus and Shaw are mandated by the CRTC to have these actions completed in a certain time frame.
I've dealt with this way too many times, and seen Telus drag their feet in so many cases. Not trying to deflect the blame, but guaranteed that if you can receive calls from any other provider other than Shaw (Any other cell, PBX, or major Telco's) and not from one particular provider, it is that providers issue and responsibility to resolve.
Matt
--
LIFT. EAT. REST. REPEAT. SERIOUSMUSCLE.NET |
|
R0acH
join:2006-05-17 | reply to NicV
Did you get this resolved yet? |
|
dougdougdoug
@shawcable.net | Had the same problem. It was shaw's error in not porting the number correctly.
»www.underdoug.ca/ |
|
shaner
Premium
join:2000-10-04
Calgary, AB
| reply to NicV
Is this a brand new exchange for Shaw? The first 3 numbers after the area code is what I mean.
The reason I ask is because many times, new exchanges are not loaded into other providers database as soon as those exchanges are active. And since you're in BC, it would be a Telus database issue, even for the Bell cell phones. Essentially, the Telus Mobility network doesn't recognize your exchange even exists.
--
The opinions in this post are wholly my own and in no way reflect the opinions of, or are influenced by my employer. |
|
NicV
@shawcable.net | reply to NicV
I has been resolved finally.. It was telus/bell mobility they never "hit the switch" Im not sure, But it is nice to know that I wasnt the only person in this area with this problem. (this only took about 3 weeks) |
|
solidus
@shawcable.net
| reply to NicV
translation issue on telus's end. what happens after shaw ports a number is that telus's phone switches dont always update and they keep routing phone calls from their customers back to the telus line because the switches still have the old info for that phone number. It's common unfortunately with telus and rogers  glad you got it sorted out though sometimes telus can be real dicks when admitting that it's really their fault. bell seems to be a lot faster to respond to these problems |
|
CR123
join:2006-11-04
Vancouver, BC
| The only caveat is that Shaw (or whoever) has to place the order to port the number correctly, or it will not be acted on / fail. There's a procedure that needs to be followed, like anything else in the five nines POTS system. So it's not always the ILEC's fault.
That said, I have no idea what happened in this case. |
|
docsis3
join:2008-08-24
| reply to NicV
What happened was OP ported his number from Telus to Shaw and Telus did not update there switch to direct all Telus/Bell calls to Shaws switch to get connected with OP. They were most likley endlessly ringing or into a provisioned Telus voicemail inbox. Shaw should be able to escalate this to Telus and let them know whats going on but it is not up to Shaw to correct.
In these cases its best to call Telus with this issue, get a reference number for your cal generated, call Shaw and let them know and Shaw should be able to escalate this with the Telus reference number. |
|
CR123
join:2006-11-04
Vancouver, BC
| Good to know you have all the backend details of the OP's problem in your hand. 
Like I says, don't want to start a flame war, but CLEC's and the like sometimes f*** up too, and often tell their customers it was the ILEC's fault.
And it is up to Shaw to correct, as Shaw is the originator of the porting request, and if something is wrong with the porting, the originator should follow the ticket.
--
- The content of the preceding post is my opinion, and does not necessarily reflect the opinions of my employer. - |
|
