DGIV-A-HOLICS...FAMILY CHIT CHAT ONLY!! Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Microcap & Penny Stocks : DGIV-A-HOLICS...FAMILY CHIT CHAT ONLY!!

DGIV 0.00

Dec 5 4:00 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Moonglow who wrote (16453)	6/30/1998 8:05:00 PM
From: Craig K	Read Replies (4) of 50264

Ok....time to speak....I work in the area of communications...I deal with voice compression and encoding to some degree, although not VO/IP... IP is just the packaging of the data for internet routing...what remains is the voice sampling usually at an 8KHz rate for a good frequency response from 300Hz to 4KHz...The output of this sampling is a high rate data stream about 12bits wide...way to much data to packetize and send over the net...Next step is to encode the data with an algorithm that allows descent reproduction at the other end of the line...Next the results of that encoding is a binary compression to further reduce the bandwidth required....Knowing all of that in simple terms... the key is bandwidth...how little bandwidth can we fit this voice into.... The key to minimizing bandwidth utilization is the algorithms that are used..this is where the argument exists..what algorithms are being used....Standard or proprietary....???? The problems that sometimes exist with standard algorithms is that they are not optimal meaning that the output would require more bandwidth per call...I don't know that this is the case here, but with the OVERIDING significance of bandwidth if DGIV has a proprietary algorithm that requires less bandwidth than the standard, it may be correct to use it.... The other part of the story is; Even if it is proprietary,, it can be converted at the gateway to a standard format....if this conversion is done at the gateway, bandwith is not an issue...You have to realize that we would not have an incompatibility at the IP packaging and routing layer, just the voice encoding format... Another question that may be significant is....Does Digitcom' business plan require any interopability with any other vendors products.....My guess would be no....Digitcom plans to have gateways a both ends of the POP...they will encode and decode their on voice and switch it into analog lines...no compatibility with anything is required....from what I see, this is Digitcoms path even if they do have a standard algorithm..... 1) BANDWIDTH utilization is KEY!!! what ever it takes to minimize this is worth any tradeoff...period... 2) Contracts are the second KEY!!!....contracts with local foreign telcos is most important...... . . a whole list of other important issues including NASDAQ . N) Standard Format....can be converted at the gateway.... Speaking from experience....this is my opinion Craig

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next