Read the forum guidelines
Nomorobo now lists Cox as a carrier for their service. However, I subsequently signed up for Nomorobo only to find out that simultaneous ring is only available in a few select Cox markets. Any idea when simultaneous ring will be available in the Hampton Roads, VA market? Thanks.
Not available in Virginia so we still get 10's of irritating robo calls daily. I'm poised to just drop Cox's Digital Phone Service given that the "service" has become quite a nuisance-- frankly, the company isn't all that tech savvy either, rather backward on the tech front to be blunt.
Then why when looking to purchase Cox services in Northern VA , does Cox say it is part of the Phone features. It is currently not. This is as of a few minutes ago. I am a current (probably headed to FIOS) Cox customer and have been annoyed about this. I just went to Cox's sales site via a Virtualized instance and used a VPN to hide my COX IP. The website (which I have captured screen shots) says this is a feature. I wonder if the Fairfax county consumer protection agency and VA Attorney General would like to know about this consumer abuse/fraud?
So what do I have to do to get on the list to be migrated? Drop my service, then have it reinstalled (also would be at a lower price). I have the phone interface inside my house. There is no box on the side of my house for Cox phone service.
What a way to run a railroad or a crappy utility. Your answer does not seem like Cox is close to start this for their existing customers, since if it was close, Cox would be communicating with their No VA customers that a service appointment is needed through the bill, web site, etc. I've been through plenty of network and system rollouts, and the communication with the people affected needs to start ASAP to make it effective.
drewmcdan1 said:I have the phone interface inside my house. There is no box on the side of my house for Cox phone service.
The "box" (aka Network Interface Unit, Telephone Network Interface, System Network Interface, Telephone Network Box) has to be outside your house. It's the demarcation point (dividing line) between you and Cox. Meaning, Cox is responsible for everything up to and including the interface and you own everything within your house. If its underground cable gets severed, Cox fixes it; if a wall jack in your house gets damaged, you fix it.
If it was inside your house, your home wiring would be part of the public switched telephone network.
@drewmcdan1 is describing how the wiring inside his/her home interfaces with Cox strictly for phone service. In his/her case, like mine, it is through an eMTA modem. Non-eMTA phone service terminates at an interface unit on the outside of the home as described by Becky. This is usually separate from the termination point for cable bringing video and internet to the premises. It feels like Cox is holding up all eMTA customers until their non-eMTA neighbors are cut-over to eMTA service.
You may be connected via an eMTA now, but converting to packet-switching sounds like a 3-step process. 1) install eMTA, 2) schedule a field technician to configure your demarc and 3) wait for Cox to switchover your market. Until then, your voice service is still circuit-switched.
If you installed an eMTA during this process, it begs a question: is your eMTA creating voice packets? If not, it's probably defaulting to circuit-switch telephone service. If your eMTA is creating voice packets, there must be a gateway routing them on only a dedicated connection. The gateway is either a Session Engine or a Signaling Gateway.
My point was that @drewmcdan1 correctly indicated that his/her phone service was on the eMTA packet-switching service to the premises and not on the old analog service to the premises. How the PSTN handles the call is beyond the purview of the present discussion.
How PSTN currently handles voice should be your purview.
You're assuming just because you have an eMTA, your voice service is now modulated onto the same frequency or channel as your IP bandwidth. You don't know what frequency or channel your eMTA is using on your coaxial cable.
When you initially connected your eMTA, the CMTS probably instructed it to use the voice channel, hence circuit-switch.
Cox abandoned "the old analog service" at least 10 years ago. Since I moved to NOVA in 2005, it has always been Cox Digital Telephone Service.
As Becky updated, you can now assume your voice is IP.
Well, it isn't because it isn't germane to the discussion. Secondly, I made no such assumption that my voice traffic used the same RF carrier and didn't need to. You just made that claim up to serve your own purposes. I do know that eMTA is a digital interface whether IP-based or not. Layer 3 services are not always needed to get the job done for the same reason that some LANs don't require routers. That's probably, in part, how Cox has been able to say for years that it offers digital telephone service. There are some residents near me that still used the old Cox analog service. Hence, they had a separate termination point strictly for phone service and no eMTA indoors.
As an aside, this exchange started by me pointing out that @drewmcdan1had the proper understanding of his/her network topology in spite of your inference that he/she didn't. Now, you're similarly making false claims as to what I understand and am trying to convey here. If you have something you want to share, fine. However, doing so under such false pretense doesn't convey mutual respect for your fellow members. I consider being able to post in these forums a privilege, not a right. I can't speak for you and won't.