I was just reading NAD’s article about participating in the FCC’s 10-Digit Numbering System and couldn’t help but wonder if we’re not looking at this issue in a more global way. Videophones have not only enabled us to use a better form of relay interpreting service, but also to better connect with loved ones who are hearing and thus don’t qualify for a free videophone from those services that provide one to Deaf consumers.
I have recently installed several non-VRS-provided videophones (i.e., D-Link and such) for hearing members of families that have Deaf members. It has been such a joy to see them connect and build their relationship with their beloved Deaf son, daughter, brother, etc. when in the past often such families had an estranged relationship between Deaf and Hearing members.
Now that these hearing people have a VP, they are taking the time to learn ASL more and connect better. Barriers are fast dropping across the board. With such technology, the dynamic where Deaf and Hearing family members sit down at holiday dinners while being complete strangers to each other may become a thing of the past.
So, I look at “10-Digit Numbering System” and I wonder… what does that mean? Do we each get a toll-free number, or an area code? If it is an area code, is it one area code for all users? Or is it an area code related to where you live? What if you move?
If it is a toll-free number, do I want to give that out to hearing people who might be confused with such an unusual number for personal usage? What if it is a number I give out for prospective employers to contact me for job interviews? I would be uncomfortable giving out a toll-free number or an area code that makes me look like I’m not local to the employer.
And then comes the question, why should such numbers be for the use of Video Relay Services? Shouldn’t we think in broader terms?
Going back to my mention of installing videophones for hearing people, I noticed several interesting challenges for people with non-VRS provided devices, or different devices. For example, I have both a Sorenson VP-200 phone and an OjoPhone provided by SnapVRS. The phone numbers that are tied into each device are obviously not real phone numbers. You can’t dial that number on a regular phone and be connected to a videophone. In fact, both devices have the same phone number, but are connected to different databases. Therefore, if you called me on my phone number from a Sorenson-based VP to my OjoPhone, it won’t connect.
The solution to this problem is obviously to use a Dynamic DNS service and tell people to use that DNS name. But that causes another problem, because when I call them, my domain name does not appear in their Caller ID. Instead, my actual IP address shows up on the screen. What if that person then saves my Caller ID in their phone book, not realizing they need to change it to the DNS name? A few days later, my IP address could change and now they can’t call me.
For me, this is not a huge problem because I don’t have dynamic IP addressing. My IP addresses are permanent static addresses because I pay a higher price for business-class service from Comcast. But not everyone can afford this.
That inability to connect via phone number from one type of VP to another is where there is a huge problem that will potentially get worse as the market share of VP users grows. Parents will be unable to call their son halfway across the country because their son’s IP address changed since the last time they talked. The potential gains we have for bridging the gap between Deaf and Hearing family members could be lost.
So this 10-Digit Numbering System, to me, deflects from the real issue at hand. How do we make our VP’s more globally accessible? Remember, videophone manufacturers are or will be benefitting hugely from the growing market demands that are just around the corner. Just like the Deaf Community was a pioneer in the mass text-paging industry in the cellular world, so too are we pioneers in the home videophone industry. In the 1990’s, we were the first true market segment to fully adopt pager communication as a means of normal communication. Now, in 2008, everyone seems to own a pager device of some kind.
We’re contributing to a new economic market here and someday, every home will have a videophone, regardless of Deaf or Hearing.
So, the question is, should the FCC be focusing on 10-Digit Numbering Systems or looking at ways to unify communication across all Videophones? I think the latter is far more important. A 10-Digit numbering system will slow down the mass adoption of VP’s and continue to cause incompatibilities in ease of reaching people regardless of videophone device.
In the hearing home, telephones are made by many many different manufacturers. Yet, if you call that home from your phone, you can connect with no problem. It doesn’t matter if I have a Sony telephone and you have a GE phone. We will connect. That’s where VideoPhones need to be. NOT restricted to the VideoPhone’s own proprietary directories.
Most of us have Sorenson videophones. Many of us are still waiting for OjoPhones, MVP’s, and VPads. When people start getting all these different devices, we’re going to have some headaches trying to teach people how to make this all work. Explaining IP addressing, Dynamic DNS and hostnames isn’t always an easy task.
In fact, I am working with Linux developers currently to make the Ekiga videoconferencing software compatible with the various Videophone codecs out there. That means yet soon another device will have some difficulty with changing IP addresses.
The technology to achieve this is simple enough. And the FCC can get involved in mandating and regulating such a system. These standards should apply to all videophones marketed in the United States, regardless of whether they are to be used by Deaf users.
- Update existing VP Firmware software to include a new DDNS (Dynamic DNS) client built into the Videophone itself. Too many people don’t understand how to access configurations in a router.
- This DDNS service shall be governed by an independent body of members of both the VideoPhone industry and the consumer industry. If possible, it should be used expressly for videophone usage and not for other IP-based services.
- Give the consumer the ability to optionally link that DDNS name with the 10-Digit number so that when a hearing person calls VRS and gives out the number, VRS will call the DDNS name automatically.
- When we call from one videophone to another videophone, ensure that it is the DDNS name that gets displayed, not the IP address nor the phone number.
- When the receiving VP saves the call into the phonebook, it should recognize that a DDNS name was given and use that to store. Not the IP address.
Then, and only then, do I believe we’ll ensure true global communication by allowing the 10-Digit Numbering System to tap into this potentially huge globally-compatible directory, without impeding on the potential growth of videophones which WILL eventually become ubiquitous in every home, just like it is already ubiquitous in Deaf homes.