Devices

What you see here is our acceptance test environment. We have different tables with different functionality.

Let´s start here with our analogue and ISDN infrastructure.

As you know telecom operators don’t need analogue and ISDN telephony any more. But there are a lot of CPEs in the market which still have this technology inside and people use it. In order to test it end to end, we would need to connect an analogue phone to this CPE and automatically dial, but unfortunately these old phone types don’t support remote control.

Therefore, we have implemented analogue cards and ISDN cards in this tower PC. This is connected to our test infrastructure and from there we can control this PC and these cards. This emulates an analogue telephone and an ISDN telephone.

So, we can do everything with this PC and these cards that a human being can do with an analogue phone or ISDN phone.

And we can test the CPE. We can also connect some Voice over IP phones and so on and we can test everything.

There are also some configuration activities which can be done here on this CPE. Therefore, we have a UI automation of web services where we can also control the graphical user interface.

Here, as you see, we have iPhones and Mac minis. This is the Apple environment, the Apple infrastructure.

Here we also remotely control these devices and can make calls and send SMS and this kind of stuff.

This table is used for Android phones. Here we have Android phones. They have an open interface, and we can do everything a human being can do with these phones.

We can automate everything. We can run apps, we can make basic calls, we can send SMS, we can do the USSD activities. Everything that is possible can be automated.

We have an IPS here, this is the intaQt phone service.

Like the Mac mini there, we can control this environment via the gateway. We can also connect some IT systems to this box and then remotely control and do something with the IT infrastructure as well.

Then we have here our own phone hub. This is our own hardware. With this we connect to the audio jacks of the phones so that we can inject audio, or we can record announcements and tones in order to validate the speech channel on one side, and on the other side we have the capability to control the charging of these phones.

We can control the signal, the charging strength and limit it, so the phones do not permanently charge, and the batteries are not destroyed.

The newer models of Android don’t support an audio jack, they don’t have it any more. They work purely with Bluetooth.

In order to overcome the missing audio jack, we have also developed a small box which we call Bluetooth adapter where we have three Bluetooth antennas inside, so we can connect to three different Android phones.

We don’t need the audio jack any more; we can do the audio via Bluetooth.

Finally, this is the environment which we use for Voice over IP testing. Fix network functionality is covered here.

All these phones also have an HTTP interface and via this interface we can control these phones.

We have a Raspberry Pi-USB combination in order to record announcement, tones in the same way we did with Android. So, we can call from here to a mobile device and verify the speech channel in both directions.

And finally, we have here our SIM array. This is a box where the SIM cards are stored in these boards and the SIM information is mapped via internet to one of these boxes and from these boxes it goes into this phone. The phone thinks there is a SIM card inside one time rebooting and the phone is available for service. Without touching the phone, we can change the SIM cards inside these boxes.

And here you also see some Bluetooth modules. These are single adapters where you can also connect it with one single phone and do audio exchange.

So, this is basically our acceptance test environment.

Interested in more? Visit us online! www.qitasc.com