Vestalink Call Quality
intelafone:
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I would like some more feedback regarding the g711 vs g729 codec. The g729 codec is what we use standard on our ht701 devices because it uses significantly less bandwidth (8kb). In low bandwidth connections, like dsl you might have a choppiness issue with g711. However g711 will provide you with significantly better call quality.
Should this be a configurable option in the Vestalink account settings?
CLTGreg:
Quote from: intelafone on April 04, 2014, 07:58:08 pm
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I'd like to see the codec selectable as I am too lazy to go in to advanced config. As far as the 404s go I'll try to test over the next few days. None of my outbound calls have used Vestalink. As far as Google Voice goes, I haven't noticed any latency but I haven't been using the service very much.
riptcity00:
Quote from: intelafone on April 04, 2014, 07:58:08 pm
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I would like some more feedback regarding the g711 vs g729 codec. The g729 codec is what we use standard on our ht701 devices because it uses significantly less bandwidth (8kb). In low bandwidth connections, like dsl you might have a choppiness issue with g711. However g711 will provide you with significantly better call quality.
Should this be a configurable option in the Vestalink account settings?
[/quote
I haven't had the latency issues but I tried the 711 codec as suggested since I have a good cable connection and call quality does seem better.
ceg3:
Quote from: BigJim_McD on April 04, 2014, 12:58:18 pm
Thanks PCSguyMD.
I had noticed the same thing looking at "Call Status" of live calls and comparing to "voip.ms" calls. I found that all Vestalink incoming and most outgoing calls defaulted to the G729 voice codec. All incoming and outgoing calls on voip.ms defaulted to G711u voice codec.
Following your lead, I used OBiTALK Expert Configuration Tool to disable the G729 Codec. Now all my Vestalink calls and voip.ms calls default to G711u and the Vestalink audio quality has improved.
-- Specifications --
Codec BitRate Bandwidth (Kilobits)
G729a 8 Kbps 31.2 Kbps Moderate Quality
G711 64 Kbps 87.2 Kbps Better Quality
This codec discussion is very interesting, especially at the bottom line of potentially better call quality, but you guys are over my head in discussing codecs. Can you give specific directions for disabling the G729 codec in ObiTALK? I can get to Profile A, which I assume corresponds with my Vestalink setup on SP1, but what to do when I get there? Thanks!
After a closer look I did see the enable check box. I unchecked the two boxes on the "codec" line and the enable box and a check of an inbound call indicated the G711U codec.
ceg3:
Quote from: intelafone on April 04, 2014, 07:58:08 pm
Hi Everyone:
I appreciate the feedback. I believe we have solved the issues with the 404 calling problems. But I will need more feedback. We have not had any support requests regarding these problems for a while. Furthermore We do not block any calls to the lower 48 states regardless of high cost etc. All other numbers can be reached by dialing 011+the number.
As far as Google voice latency, we are using a different carrier than Google Voice so the calls from Google Voice go over the PSTN before they get to your Vestalink account. The best way to solve this latency would be to port your number to Vestalink.
I would like some more feedback regarding the g711 vs g729 codec. The g729 codec is what we use standard on our ht701 devices because it uses significantly less bandwidth (8kb). In low bandwidth connections, like dsl you might have a choppiness issue with g711. However g711 will provide you with significantly better call quality.
Should this be a configurable option in the Vestalink account settings?
I think that would be a definite yes if it can allow for better call experience, ;D with a notation that the setting is for higher bandwidth connections. My opinion is not based on a real understanding these codecs, though I am aware of coding and decoding in other audio situations.
Navigation
[0] Message Index
[#] Next page
[*] Previous page