GNOME Bugzilla – Bug 519098
Provide integration with video relay services
Last modified: 2020-06-06 16:29:16 UTC
Ekiga should provide integration with video relay services. From http://www.fcc.gov/cgb/consumerfacts/videorelay.html: "Video Relay Service (VRS) is a form of Telecommunications Relay Service (TRS) that enables persons with hearing disabilities who use American Sign Language (ASL) to communicate with voice telephone users through video equipment, rather than through typed text. Video equipment links the VRS user with a TRS operator – called a “communications assistant” (CA) – so that the VRS user and the CA can see and communicate with each other in signed conversation. Because the conversation between the VRS user and the CA flows much more quickly than with a text-based TRS call, VRS has become an enormously popular form of TRS. For more information about other forms of TRS, see the FCC’s consumer fact sheet at www.fcc.gov/cgb/consumerfacts/trs.html." From http://www.tdi-online.org/tdi/fs_videorelayservices.html, it appears as though H.323-based video relay services are available, so this 'bug' may be more of a documentation bug on how to connect to them using ekiga.
no bug. feature request. discuss on the devlist. we implement RFC here, not FCC. wrong severity tag.
Could you please clarify on the nature of this feature request?
Yes, I'd like a more detailed description of what you expect us to do -- it does look interesting and important, but I'm not sure exactly what you want.
We had hearing impaired users attempting to use video relay services with Ekiga. The users tried various things, but were ultimately unsuccessful. As a result, we need someone more skilled in the workings of Ekiga to analyze the situation, figure out what the problem is, and then work to resolve it. Thanks!
Having talked to one of the Ekiga Devs (Can't remember exactly which one), it is a codec issue that supposedly will be resolved in 3.0. I have been meaning to test it with the latest SVN, but just am not able to. Essentially, there are two primary video phones in use by the Deaf community nowadays. One is the Sorenson VideoPhone which is similar to D-Link I2Eye device (made by Sorenson.) The other is the OjoPhone. We use it to communicate with each other, as well as connect to relay services where a sign language interpreter relays our calls. Sorenson uses H323, Ojo uses SIP but has H323 compatitibility to call a Sorenson VP. I suspect they're paying a license fee to Sorenson or something. All this is provided for in the United States via a Deaf tax on phone bills. This is a $500 million a year industry now with Sorenson being the largest provider (80%). The FCC administers the program and pays $6.44 a minute for relay services. Sorenson and Ojo are not discussing their codecs with anyone. However, the FCC is coming up with mandatory regulations ensuring compatibility. Sorenson, and a number of other Video Relay Service Providers have come up with software that makes this service possible to use on Windows and OSX. Linux has been left out of the lurch. Perhaps we need to find a way to petition the FCC to make Linux as accessible. Our issue now is that these devices are becoming so prevalent in the community, that each day Linux is incompatible, Linux becomes less and less accessible to the community. I do have both the Sorenson VP and the OjoPhone VP. Contact me directly via email and I'll tell you how you can connect to my devices for testing purposes if you'd like. Thanks, Bryen
Also wanted to add: 1) I am able to dial and connect to the Sorenson VP. However, video does not transmit in either direction. Pertinent information (who is calling) does get displayed. 2) I am able to dial the Ojo and it rings. However, it disconnects upon answering the Ojo. Pertinent information (who is calling) does get displayed. 3) Reason why computer-based VP is needed is because VP is tethered to a wire. People want the flexibility to make calls even on the road, which they can do with OSX and Windows. Wish list: As I understand it, When a call does connect to Ekiga, it only takes voice mail answering machine. If we can support video answering machine, that would truly make Linux a popular alternative for people. Sorenson VP does not have built in answering machine.
Can you provide a packet trace for your other software so we can have a look what protocols and codecs its using? The beginning of the conversation should be sufficient.
Matthias, These are standalone devices. The Sorenson VP is hooked up to a television, and the OjoPhone is a all in one device. www.sorenson.com www.snapvrs.com If there is a way for me to initiate a packet trace from my openSUSE linux box, can you post instructions for me? Thanks, Bryen
Reassigning to Matthias, since he's much more involved than I am.
I am trying to figure out how to do the packet trace on the viable vision software that is being distributed to the deaf customers who are using VRS services. However it is windows based, there is also another software from a different company called hovrs which is offering videosign software that also works on windows platform only. I will have to figure out how to do a packet trace on windows which is not that easy or simple as doing it on linux. However I am happy that Matthias is interested in helping out with this particular issue. If you have any advice of how to do the packet trace using windows such as using wireshark or ethereal. I am happy to do a trace for you for more information to help you to figure out what is happening between the conversations between the customer and the interpreter using VRS services. After doing some testing with ekiga 3.0.1 software with h.264 installed. I am confident that the main issue that is occuring is that the fact that h.264 is not enabled for h.323 protocol. As of right now, it only works with SIP protocol. I believe if somebody is able to merge/configure h.264 video codec that works with h.323 protocol, this issue will be most likely resolved. Again this is my opinion, I could be easily wrong here. Matthias, please do not give up just yet.. Once we are able to resolve this bug/issue, it will be greatly beneficial to the deaf community who does not want to be tied down using windows with proprietary software. I appreciate all of your efforts helping out the deaf community. Feel free to contact me via my email me anytime. I look forward to working with you and resolving this issue for future releases which you will be able to use as a feature and possibly expanding your userbase for ekiga which is an excellent software imho. I am looking forward to hearing from you soon. Sincerely, Dr Consultant
Ekiga is not under active development anymore: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273 Ekiga saw its last release 7 years ago. The last code commits were 4 years ago. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.