Hello
We have recently started providing a VOIP services and at some of our clients, we experience various problems with internet connection. What I would like to know is, whether there is any kind of test we can do, before we start implementing VOIP, that would tell us, if the connectivity at the side of our client is capable of running VOIP on it or if something is wrong (signal attenuation in adsl, some sort of blocking udp protocol etc.)
It would help us really lot if somebody had some tips here.
thank you !
Jakub
Universal connectivity test for implementing VOIP
Re: Universal connectivity test for implementing VOIP
Better late than never for a response on this
VOIP services vary in terms of how they communicate with central servers and peers and thus it is not possible to just run a generic test to ensure connectivity.
Generally it should be possible for most clients to use most services although sometimes specific settings need to be used (STUN for NAT traversal for example). Also for IP dialing a port forward is usually required direct to the device handling the VOIP client.
My advice would be to research the most common configurations used by clients, develop similar setups yourself and get your VOIP client working on each, noting the settings required for each config in an FAQ document or similar.
There is also the option of you writing some software that could be run by a client to check their ability to run VOIP but such a strategy is risky as with config changes it may be possible to get that client on-board but if a test app tells them that they are not able to use the service then it could be a lost client for you.
VOIP services vary in terms of how they communicate with central servers and peers and thus it is not possible to just run a generic test to ensure connectivity.
Generally it should be possible for most clients to use most services although sometimes specific settings need to be used (STUN for NAT traversal for example). Also for IP dialing a port forward is usually required direct to the device handling the VOIP client.
My advice would be to research the most common configurations used by clients, develop similar setups yourself and get your VOIP client working on each, noting the settings required for each config in an FAQ document or similar.
There is also the option of you writing some software that could be run by a client to check their ability to run VOIP but such a strategy is risky as with config changes it may be possible to get that client on-board but if a test app tells them that they are not able to use the service then it could be a lost client for you.
Kieran
"Indeed!"
Invaluable links: Forum Rules | Networking Guides | FAQ | Site Search | Forum Search <-- Use it or feel my wrath!
No support via PM, please ask your questions in the forum!
"Indeed!"
Invaluable links: Forum Rules | Networking Guides | FAQ | Site Search | Forum Search <-- Use it or feel my wrath!
No support via PM, please ask your questions in the forum!
Re: Universal connectivity test for implementing VOIP
I recommend familiarizing yourself with VoIP. There are a lot of factors that dictate the suitability of a connection or CPE routers. the number of phones involved, whether or not they're hosted voip or on premise voip, all these things have to be considered. If you post some of the setup details someone can give you some tips.
1. Is it hosted voip or on premise?
2. Brand of the phones? (yes, this matters)
3. Voip hardware of softswitch? (softswitches are things like asterisk, freeswitch, 3cx, just to name a few common ones)
4. How many phones?
5. How much bandwidth and how many simultaneous calls?
6. What are the nature of the issues? Audio? Registration failures?
VoIP is complex and honestly isn't something you can just plug in and expect everything to go swimmingly.
1. Is it hosted voip or on premise?
2. Brand of the phones? (yes, this matters)
3. Voip hardware of softswitch? (softswitches are things like asterisk, freeswitch, 3cx, just to name a few common ones)
4. How many phones?
5. How much bandwidth and how many simultaneous calls?
6. What are the nature of the issues? Audio? Registration failures?
VoIP is complex and honestly isn't something you can just plug in and expect everything to go swimmingly.