Tag: VoIP

Routers like the Draytek Vigor 2600N which support VPN endpoint and IP-PBX functionality could benefit from simplified configuration processes for these functions

Increasingly, the virtual private network, virtual local-area network and IP-based voice and video telephony setups are becoming more common as part of ordinary computing.

The VPN is being seen as a tool to protect our personal privacy or to avoid content-blocking regimes imposed by nations or other entities. Some people even use this as a way to gain access to video content available in other territories that wouldn’t be normally available in their home territory. But VPNs are also seen by business users and advanced computer users as a way to achieve a tie-line between two or more networks.

The VLAN is becoming of interest to householders as they sign up to multiple-play Internet services with at least TV, telephony and Internet service. Some of the telcos and ISPs are using the VLAN as a way to assure end-users of high quality-of-service for voice or video-based calls and TV content made available through these services.

… as could the AVM Fritz!Box routers with DECT base station functionality

It may also have some appeal with some multiple-premises developments as a tool to provide the premises occupiers access to development-wide network resources through the occupiers’ own networks. It will also appeal to public-access-network applications which share the same physical infrastructure as private networks such as FON-type community networks including what Telstra and BT are running.

VoIP and similar IP-based telecommunications technologies will become very common for home and small-business applications. This is driven by incumbent and competing telecommunications providers moving towards IP-based setups thanks to factors like IP-driven infrastructure or a very low cost-of-entry. It also includes the desire to integrate entryphone systems that are part of multi-premises buildings in to IP-based telecommunications setups including the voice-driven home assistants or IP-PBX business-telephony setups.

A device like the Amazon Echo could be made in to a VoIP telephone through an easy-to-configure Alexa Skill

In the same context, an operating-system or other software developer may want to design a “softphone” for IP-based telephony in order to have it run on a common computing platform.

What is frustrating these technologies?

One key point that makes these technologies awkward to implement is the configuration interface associated with the various devices that benefit from these technologies like VPN endpoint routers or IP-based telephony equipment. The same situation also applies if you intend to implement the setup with multiple devices especially where different platforms or user interfaces are involved.

This kind of configuration also increases the chance of user error taking place during the process which then leads to the setup failing with the user wasting time on troubleshooting procedures to get it to work. It also makes the setup process very daunting for people who don’t have much in the way of IT skills.

For example, you have to complete many steps to enrol the typical VPN endpoint router with a consumer-facing privacy-focused VPN in order to assure network-wide access to these VPNs. This involves transcribing configuration details for one of these VPNs to the router’s Web-based management interface. The same thing also applies if you want to create a VPN-based data tie-line between networks installed at two different premises.

Similarly, IP-based telephony is very difficult to configure with customers opting for pre-configured IP telephone equipment. Then it frustrates the idea of allowing a customer to purchase equipment or software from different resellers thanks to the difficult configuration process. Even small businesses face this same difficult whether it is to add, move or remove extensions, create inter-premises tie-lines or add extra trunk lines to increase call capacity or provide “local-number” access.

This limits various forms of innovation in this space such as integrating a building’s entryphone system into one’s own telephone setup or allowing Skype, Facebook Messenger, WhatsApp or Viber to permit a business to have a virtual telephone link to their IP-telephony platforms.

It also limits the wide availability to consumers and small businesses of “open” network hardware that can answer these functions. This is more so with VPN-endpoint routers or routers that have IP-based telecommunications functionality which would benefit from this kind of simplified configuration process.

What can be done?

A core requirement to enable simplified provisioning of these technologies is to make use of an XML-based standard configuration file that contains all of the necessary configuration information.

It can be transferred through a download from a known URL link or a file that is uploaded from your computing device’s local file system. The latter approach can also apply to using removable storage to transfer the file between devices if they have an SD-card slot or USB port.

Where security is important or the application depends on encryption for its operation, the necessary binary public-key files and certificates could be in a standard form with the ability to have them available through a URL link or local file transfer. It also extends to using technologies based around these public keys to protect and authenticate the configuration data in transit or apply a digital signature or watermark on the configuration files to assert their provenance.

I would also see as being important that this XML-based configuration file approach work with polished provisioning interfaces. These graphically-rich user interfaces, typically associated with consumer-facing service providers, implement subscription and provisioning through the one workflow and are designed to he user-friendly. It also applies to achieving a “plug-and-play” onboarding routine for new devices where there is a requirement for very little user interaction during the configuration and provisioning phase.

This can be facilitated through the use of device-discovery and management protocols like UPnP or WSD with the ability to facilitate the upload of configuration files to the correct devices. Or it could allow the creation and storage of the necessary XML files on the user’s computer’s local storage for the user to upload to the devices they want to configure.

Another factor is to identify how a device should react under certain situations like a VPN endpoint router being configured for two or more VPNs that are expected to run concurrently. It also includes allowing a device to support special functions, something common in the IP-based telecommunications space where it is desirable to map particular buttons, keypad shortcodes or voice commands to dial particular numbers or activate particular functions like door-release or emergency hotline access.

Similarly, the use of “friendly” naming as part of the setup process for VLANs, VPNs and devices or lines in an IP-telephony system could make the setup and configuration easier. This is important when it comes to revising a configuration to suit newer needs or simply understanding the setup you are implementing.

Conclusion

Using XML-based standard provisioning files and common data-transfer procedures for setup of VLAN, VPN and IP-based-telecommunications setups can allow for a simplified setup and onboarding experience. It can also allow users to easily maintain their setups such as to bring new equipment on board or factor in changes to their service.

Article – From the horse’s mouth

AVM earns more industry recognition for their Fritz!Box devices

AVM

AVM is delighted to win two Connect awards (Press Release)

My Comments

AVM has just earned two Connect awards for their German-designed home-network technology.

The first of these was for the Fritz!Box routers and mesh setup. No wonder they would earn industry recognition for their home-network products especially since they were the first company to break the mould regarding home-network routers by supplying self-updating firmware.

The issue of self-updating firmware became very important due to the fact that most of us aren’t updating our home-network router’s firmware regularly and it was a security hole. This is thanks to the “out-of-the-box” software coming with bugs and weaknesses that can be exploited by hackers against the typical home network.

Another step in the right direction was to implement distributed-wireless networking through a free software update rather than requiring customers to replace their AVM home-network devices. This was about providing a function update to the Fritz!Box modem router’s FritzOS firmware to open up this functionality. There was even the ability to roll out the functionality to Fritz!WLAN Repeaters and Fritz!Powerline access points to bring on the simplified distributed-wireless functionality to them all. It also applied to some recent-model Fritz!Box modem routers to cater for the reality that an older router can be “pushed down” to be an access point while the new router works as the edge of your home network.

But they also earned awards for their IP-based telephony equipment which was considered important as European telcos are moving towards IP-based telephony and away from the traditional telephone system. One of the products was a CAT-iQ DECT cordless handset that worked with their Fritz!Box modem routers that had DECT hase-station functionality for VoIP telephony. This had abilities similar to what you would expect of a mobile phone of the “feature phone” class.

What is being shown here is that the European companies are coming through on functionality innovation when it comes to the home-network “edge” router or infrastructure devices for your home network.

Articles

Google Home – to be an alternative to the landline telephone

(Update: Officially announced) Google Home’s calling feature might be coming soon | Android Authority

Google Home voice calling starts rolling out today | Engadget

From the horse’s mouth

Google Home

Introducing Free Calls With Your Assistant On Google Home (Blog Post)

My Comments

Could Google serve this role?

In May, Amazon launched an “over-the-top” VoIP system to allow you to call other Echo users as part of the Alexa platform. In my coverage of them launching this service, I saw it as another weapon in the battleground between the various voice-driven home assistant platforms.

Now Google have launched in to the USA and Canada a VoIP calling service which allows you to place calls to other USA or Canada phone numbers using your voice. At the moment, it is only an outgoing-call service.

As well, unless you are a Google Voice or Project Fi user, the person on the other end of the line won’t be able to see your number on their Caller-ID-capable telephone, but this will be enabled for other users to have their mobile number displayed by the end of the year. It is seen as a problem with most telephone users because robocalls and telemarketers conceal their Caller ID and users are not likely to answer calls which don’t relate to a person they know.

Here, the Google Home telephony setup works from the user’s Google Contacts phonebook which you could easily build up through your Android phone or through a Web-based user experience if you use an iPhone. There is support for multiple users with the Google Assistant differentiating them via their voiceprint.

Google still has a lot to do with making their Google Home voice-calling service catch up with Amazon Echo, such as supporting inbound calls, text and voice messaging, along with videocalls. In the case of videocalls, it may be about integrating Chromecast in to the equation, perhaps with support for a camera accessory which would be considered if they want to head towards dual-device large-screen videocalling.

But I do see Apple and Microsoft using their established VoIP platforms to make their forays to the voice-driven home assistant become communications devices.

Of course, the idea of integrating this kind of IP-telephony functionality in to Amazon Echo and Google Home platforms could be seen as retrograde by the millennial generation who are used to living without the traditional landline telephone. But such setups could be about maintaining a “catch-all” contact number for a physical location or older-generation users maintaining the idea of the traditional telephone but carrying it forward to the online era. Yet the mobile phones will simply serve as the private communications link while Google Home complements them for short calls where the privacy doesn’t matter.

TV setups with large screens and powerful sound systems could also appeal to videocalls where many people wish to participate

A reality that is surfacing with online communications platforms is the fact that most of us prefer to operate these platforms from our smartphones or tablets. Typically we are more comfortable with using these devices as our core hubs for managing personal contacts and conversations.

But there are times when we want to use a large screen such as our main TV for group videocalls. Examples of this may include family conversations with loved ones separated by distance, more so during special occasions like birthdays, Thanksgiving or Christmas. In the business context, there is the desire for two or more of us to engage in video conferences with business partners, suppliers, customers or employees separated by distance. For example, a lawyer and their client could be talking with someone who is selling their business as part of assessing the validity of that potential purchase.

This is more so when there is that family special moment

But most of the smart-TV and set-top platforms haven’t been engineered to work with the plethora of online-communications platforms that are out there. This is although Skype attempted to get this happening with various smart-TV and set-top platform vendors to allow the smart TV to serve as a Skype-based group videophone once you purchased and connected a Webcam accessory supplied by the manufacturer.

The Skype situation required users to log in to the Skype client on their TV or video device along with buying and installing a camera kit that worked with the TV. This was a case of entering credentials or searching for contacts using a “pick-and-choose” or SMS-style text-entry method which could lead to mistakes. This is compared to where most of us were more comfortable with performing these tasks on our smartphones or tablets because of a touchscreen keyboard or hardware keyboard accessory that made text entry easier.

An Apple TV or Chromecast that has the software support for and is connected to a Webcam could simplify this process and place the focus on the smartphone as a control surface for videocalls

The goal I am outlining here is for one to be able to use a smart TV or network-connected video peripheral equipped with a Webcam-type camera device, along with their mobile device, all connected to the same home network and Internet connection to establish or continue a videocall on the TV’s large screen. Such a goal would be to implement the large-screen TV with its built-in speakers or connected sound system along with the Webcam as the videocalling-equivalent of the speakerphone we use for group or “conference” telephone calls when multiple people at either end want to participate in the call.

Set-top devices designed to work with platform mobile devices

A very strong reality that is surfacing for interlinking TVs and mobile devices is the use of a network-enabled video peripheral that provides a video link between the mobile device and video peripheral via one’s home network.

One of these devices is the Apple TV which works with iOS devices thanks to Apple AirPlay while the other is the Google Chromecast that works with Android devices. Both of these video devices can connect to your home network via Wi-Fi wireless or Ethernet with the Apple TV offering the latter option out of the box and the Chromecast offering it as an add-on option. As well, the Chromecast’s functionality is being integrated in to various newer smart TVs and video peripherals under the “Google Cast” or “Chromecast” feature name.

Is there a need for this functionality?

As I have said earlier on, the main usage driver for this functionality would be to place a group videocall where multiple people at the one location want to communicate with another . The classic examples would be for families communicating with distant relatives or businesses placing conference calls that involve multiple decision makers with two or more of these participants at one of the locations.

Most of the mobile messaging platforms offer some form of videocalling capability

In most cases, the “over-the-top” communications platforms like Facetime, Skype, Viber, Facebook Messenger and WhatsApp are primarily operated using the native mobile client app or the functionality that is part of the mobile platform. This way of managing videocalls appeals to most users because of access to the user’s own contact directory that exists on their device along with the handheld nature of the typical smartphone that appeals to this activity.

It is also worth knowing that some, if not all, of the “over-the-top” communications platforms will offer a “conference call” or “three-way call” function as part of their feature set, extending it to videocalls in at least the business-focused variants. This is where you could have multiple callers from different locations take part in the same conversation. Such setups would typically show the “other” callers as part of a multiple-picture “mosaic” on the screen. Here, the large screen can come in handy with seeing the multiple callers at once.

How is this achieved at the moment?

At the moment, these set-top platforms haven’t been engineered to allow for group videocalling and users would have to invoke screen-mirroring functionality on their mobile devices once they logically associate them with the video endpoint devices. Then they would have to position their mobile device on or in front of the TV so the other side can see your group, something which can be very precarious at times.

How could Apple, Google and co improve on this state of affairs?

Should this still be the way to make group videocalls on your Apple TV or Chromecast?

Apple and Google could improve on their AirPlay and Chromecast platforms to provide an andio-video-data feed from the video peripheral to the mobile device using that peripheral. This would work in tandem with a companion Webcam/microphone accessory that can be installed on the TV and connected to the set-top device. For example, Apple could offer a Webcam for the latest generation Apple TV as an “MFi” accessory like they do with the game controllers that enable it to be a games console.

When users associate their mobile devices with a suitably-equipped Apple TV / Chromecast device that supports this enhancement, the communications apps on their phone detect the camera and microphone connected to the video peripheral. The user would then be able to see the camera offered as an alternative camera choice while they are engaged in a videocall, along with the microphone and TV speaker offered as a “speakerphone” option.

What will this entail?

It may require Apple and Google to write mobile endpoint software in to their iOS and Android operating systems to handle the return video feed and the existence of cameras connected to the Apple TV or Chromecast.

Similarly, the tvOS and Chromecast platforms will have to have extra endpoint software written for them while these devices would have to have hardware support for Webcam devices.

At the moment, the latest-generation Apple TV has a USB-C socket on it but this is just serving as a “service” port, but could be opened up as a peripheral port for wired MFi peripherals like a Webcam. Google uses a microUSB port on the Chromecast but this is primarily a power-supply and network-connection port. But they could, again, implement an “expansion module” that provides connectivity to a USB Webcam that is compliant to the USB Video and Audio device classes.

These situations could be answered through a subsequent hardware generation for each of the devices or, if the connections are software-addressable, a major-function firmware update could open up these connections for a camera.

As for application-level support, it may require that the extra camera connected to the Apple TV or Chromecast device be logically enumerated as another camera device by all smartphone apps that exploit the mobile phone’s cameras. The microphone in the camera and the TV’s speakers also would need to be enumerated as another communications-class audio device available to the communications apps. This kind of functionality could be implemented at operating-system level with very little work being asked of from third-party communications software developers.

User privacy can be assured through the same permissions-driven setup implemented in the platform’s app ecosystem that is implemented for access to the mobile device’s own camera and microphone. If users want to see this tightened, it could be feasible to require a separate permissions level for use of external cameras and audio-input devices. But users can simply physically disconnect the Webcam from the video peripheral device when they don’t intend to use it.

An alternative path for app-based connected-TV platforms

There is also an alternative path that smart-TV and set-top vendors could explore. Here, they could implement a universal network-based two-way video protocol that allows the smart TV or set-top device to serve as a large-screen video endpoint for the communications apps.

Similarly, a smart-TV / set-top applications platform could head down the path of using client-side applications that are focused for large-screen communications. This is in a similar vein to what was done for Skype by most smart-TV manufacturers, but the call-setup procedure can be simplified with the user operating their smartphone or tablet as the control surface for managing the call.

This could be invoked through techniques like DIAL (Discovery And Launch) that is used to permit mobile apps to discover large-screen “companion” apps on smart-TV or set-top devices in order to allow users to “throw” what they see on the mobile device to the large screen. As well, the connection to the user’s account could be managed through the use of a session-specific logical token established by the mobile device.

This concept can be taken further through the use of the TV screen as a display surface, typically for communications services’ messaging functions or to show incoming-call notifications.

Update

Apple has answered this issue with their tvOS-based Apple TV set-top box platform in June 2023. Here, they are implementing a dual-device approach with iPhones or iPads running iOS/iPadOS 16 being linked with Apple TV set-top boxes that run tvOS 17. Here, both devices can be used to handle a videocall on FaceTime, Zoom or an increasing number of other popular platforms with the TV’s screen and audio system handling the picture and sound of the caller at the other end while the iOS device’s microphone and camera picks up your face and voice for the other party to see and hear.

You can start the call on the iPhone’s handheld interface and “throw it over” to the Apple TV or you can start the call from the Apple TV’s lean-back interface and use the iPhone associated with your Apple TV for microphone and camera functionality. Apple is to sell a cradle for the iPhone so that it can be positioned in fromt of the TV with the rear camera facing the participants.

Conclusion

What we still need to think of is to facilitate “dual-device” videocalling with the popular mobile platforms in order to simplify the task of establishing group videocalls using TVs and other large-screen display devices.

Article – From the horse’s mouth

You can use a regular communications tool for in-game chat

Skype

How to use Skype for desktop Gaming

My Comments

Some of us may want to use Skype or similar online communications tools to chat with fellow games players when we play games on our regular computers.

There are some reasons where the software for in-game chat functionality can be difficult to set up and manage and the conversations on most in-game text / voice-chat functions is like a simple party line where everyone and his dog can join in uninvited. This opens the door to Internet trolls and other miscreants who can upset your gaming sessions.

To my knowledge, Skype is the only program that can support group text and voice communication. On the other hand, other online-communications software like Viber, Lync and Pidgin offers varying levels of functionality to allow your gaming clan to chat together. Most will offer group-based text chat with some offering group-based voice chat. But what is common with Skype, Viber and their peers is that you chat with those participants whom you and your mates invite.

Skype – an important part of a gamer’s arsenal

For Skype, you would need to have the latest version of Skype running on your Windows, Macintosh or Linux computer. Then, set up and test your wired or Bluetooth headset to make sure it is working properly with Skype if you want to have voice calls. You do the similar procedure with Viber or other communications software. With your Bluetooth headset, you would need to use the “Hands Free Profile” function for the voice communications and if you are using a stereo Bluetooth headset or Bluetooth headphone audio adaptor like the Sony SBH-52, you may want to make sure that the sound device that your game uses for effects and music is the Bluetooth Headphones or A2DP device if you want others around you not to be hearing the game effects or repeated music loops.

Create a group-chat session by dragging the friends, teammates and others together. If you do want a group voice call, you can create this with Skype but avoid the temptation to create a video call because this takes up the bandwidth.

Then you minimise Skype or your other communications software and start your game. Make sure that other unnecessary programs aren’t running while you are playing so you can dedicate your computer’s resources to the gameplay and communications.  If you are running a multi-screen setup, you may find that you could run text-chats on one of the screens.

Using a regular Internet-communications service rather a game-hosted Internet service gives you that advantage to have better control over how the peer-to-peer games banter turns out so you can all get the most out of the game.

Many social networks and communications apps here

An issue that I am noticing a lot more with the smartphone era is the use of many different communications apps.

The apps provide at least one of various communications methods like text, picture or video messaging or may support real-time voice or video conversation using the Internet as a channel, typically with the communications being without any extra charge and, in most cases, you can subscribe to the service for free. As well, a lot of the social networks, especially Facebook, implement an instant-messaging function as part of their feature set. Some services like Snapchat offer an “ephemeral” communications setup where the communications disappear when you finish reading or viewing the messages, a feature that appeals to the teenage or young-adult user.

What is happening is that our friends coerce each other to install these apps on our phones, typically with them installing the apps and completing the “onboard” process to have us use them. The services have access to our smartphones’ contact directory in order either to send out an invite to another user to join the service or to monitor if one of our contacts have joined the services.

It is made more difficult by the fact that most of these services don’t offer any bridging to competing or complementary services in order to avoid duplication of functionality.

The point of confusion

Viber or Skype can play difficult with your Bluetooth headset accessory

We then find that the same contact is on one or more communications services alongside the regular email and phone services and end up having to think of what path we use to communicate with our contacts.Then we have to use a different app to communicate using the chosen path. This is also made worse by some voice and video communications apps not behaving consistently with Bluetooth-based headsets and hands-free accessories associated with the particular host device such as not working properly with the accessory’s control surface. It can also make the useability of these services with smartwatches and other wearable devices, or integration with the vehicle’s dashboard a lot harder.

Some of us may define a so-called preferred communications “ladder” for each conversation type (text message, multimedia message, voice call or videocall), each location and network for us and our contacts (work with business network, home with home network, home town or country, or overseas) and whatever device they are using. As well, you may have to go through a particular path when you receive a call or message from someone and you may have to close the conversation if you do want to change medium or call type through the conversation flow.

What could be done

Personally, I would like to see support for device-based contact directories to support the concept of preferred communications “ladders” for particular contacts and call types. Even factors such as you or your contact being connected  to particular Wi-Fi networks could allow you to use a particular “lowest-cost” ladder based around VoIP (Viber / Skype) or logging in to a service like Skype from a particular device like a smart TV to advance that service to the “top of the ladder” for videocalls.

This may involve the engineering of various communications services and mobile / desktop operating systems to support different operating conditions on a per-contact basis in order to support “task-focused” operation. Even practices like properly mapping the control surface of Bluetooth accessories for the likes of Viber and Skype could pay dividends to this direction.

Article – From the horse’s mouth

Viber – Free calls, Free text messages, photo and location sharing

My Comments

Previously, we have known of Viber as an “over-the-top” VoIP telephony program that offers a free telephony and SMS path for smartphone users. This has been of strong appeal to overseas travellers who want to escape the horrendous roaming charges that most mobile operators are charging people who use the phone out of their home country.

Now Viber have reached version 3.0 and released a desktop version of the softphone which will run on Windows or Macintosh regular computers. This has provided features like desktop-to-desktop videocalls and the ability to transfer a call between the regular computer and a mobile device. This is a sign that Viber has matured and started to approach Skype.

But for Viber to answer Skype, they have to offer IP-based videocalls on mobile clients. Similarly, they would need to provide the client software “knowhow” to enable the user interface to work on devices other than platform-based regular or mobile computing devices. This is somewhere where Skype has a considerable strength in with the Samsung and Sony smart TVs, the Panasonic Blu-Ray players, the desk phones, and the Logitech TV Cam HD Skype camera.

It can be easy to state that Viber’s free IP telephony model isn’t sustainable but they could offer services like partnership with some of the carriers like the French “n-box” carriers. They can also offer paid-for off-ramp services where a Viber customer could dial a regular phone that isn’t part of the Viber ecosystem. It can extend to a software-based “trunk” or “tie-line” for IP-based business phone systems as a subscription-driven business-to-business service.

Now that Viber has hit the stage of maturity, we could be seeing the opening of lively competition on the “over-the-top” IP-based voice and video telephony front for both consumers and small businesses.