Visitor
•
13 Messages
Voice and Data gateway offline 10 days after in-building move - is the voice provisioning still bound to the old unit?
My Voice and Data gateway has been fully offline for 10 days after moving between two apartments in the same building, so my home phone line is down as well as internet. I want to raise the voice side specifically because it has not been acknowledged once in any of my support contacts.
Setup: same gateway, coax connected to the wall outlet in the new unit, powered. Account address updated correctly. Xfinity's status page reports "Voice and Data Modem Offline." No area outage. The previous tenant of this exact unit had working service on this exact wiring shortly before I moved in.
Xfinity opened an "Install Appointment" instead of activating remotely. Two appointments have failed:
- Fri Sep 5: no technician, no call, no text.
- Mon Sep 7, 1:00-3:00pm PT: no technician. A chat agent told me during the window that the tech had arrived and would call. The order notes show the job was placed ON HOLD at 1:07pm PT on a technician note claiming he was unable to access the apartment and got no answer on the callback. Someone was inside the unit the entire window and the number was answered all day.
Questions on the voice side:
1. Is the voice line provisioned to the new service address, or is it still bound to the old unit? If the voice EMTA provisioning did not migrate with the move order, that could be part of why the gateway will not come online at all.
2. What happens to calls placed to my home number during this outage? Is there any call forwarding fallback that can be enabled remotely while this is unresolved?
3. Losing a home phone line for 10 days is a safety issue, not just an inconvenience. Does that change the priority on the dispatch?
The next self-service slot is Friday Sep 11, day 14. I am asking for a dispatch Tuesday Sep 8 between 2:00 and 5:00pm PT, or Wednesday Sep 9 at the latest.
If anyone from the team can check whether the voice provisioning migrated correctly with the move order, that may be the actual fault here.




No Responses!