Archive for October, 2006

Digital Voice

Friday, October 27th, 2006

Has anyone heard of Digital Voice? I bet you’ve seen the commercials and flyers of a certain cable company promoting their Digital Voice. Did you realize that digital voice is just VoIP, the technology that’s been around for the past 15 years.

I didn’t think too much about this until I was talking to my wives friend who just got digital voice. When I asked how the VoIP service was working out for her all I got in return was a blank confused look. Then it struck me, Comcast are just trying to distinguish themselves from all the other VoIP companies out there by not selling “VoIP”. Good for them as there is no other competitor promoting “Digital Voice”, not so good for the consumer as it became apparent by talking to her that she had no idea there were a lot more options than just the digital voice and Comcast. Not that she is necessarily unhappy with the service but after I explained to her a little about our site and the number of companies offering VoIP she was surprised. Needless to say she is now shopping around to find the plan that suites her budget best – maybe this will be Digital Voice but maybe not. 

Calum

http://www.whichvoip.com

 

  

Share/Save/Bookmark

What is an IP packet?

Friday, October 20th, 2006

An IP packet is simply a the data you want transferred encapsulated in a frame or packet. The packet is typically broken up into smaller chunks to be transmitted over a T1 line. It’s kind of like writing a letter, you could take one line at a time and mail it in separate envelopes, if you lose one envelope then no big deal you could probably understand the message or at least decipher it after you received the rest.

The IP packet can be a rather complex entity with header information such as IP address sent from, destination IP address, header checksums, Identification field, protocol used and many others. Below is pictorial view of a packet. The data itself may also have sending and destination addresses, checksums, flags, etc so deciphering a packet can be like peeling an onion, revealing layer after layer.IP Packet format

Version – static 4 bit value indicating which version of IP is being used.

IHL IP Header Length – 4 bit value indicating the number of 32-bit words that make up the header. 

Type of Service – 8 bit value that is used tell the network how to treat the IP packet. These bits are generally used to indicate the Quality of Service (QoS) for the IP Packet.

Packet Length – 16 bit value indicating the size of the IP Packet in terms of bytes. This gives a maximum packet size of 65536 bytes.

Identification – 16 bit field used for reassembling the packet at the destination.

Flags – 3 bits indicating to network equipment if the IP packet can be further fragmented or not and if the packet is the last fragment or not of a larger transfer.

Fragment offset – 13 bit value used in the reassembly process at the destination.

Time to Live – 8 bit value telling the network how long an IP packet can exist in a network before it is destroyed.

Protocol – 8 bit value used to indicate the type of protocol being used (TCP, UDP, etc).

Header checksum – 16 bit 1’s compliment value designed to indicate errors in the header only. Every node in the network has to check and re-insert a new checksum as the header changes at every node (TTL value is decremented)

Source address – 32 bit value representing the IP address of the sender of the IP packet.

Destination address – 32 bit value representing the IP address of the packets final destination.

Options – variable bit field representing options :-) The actual options requested are not optional in that there are well defined options that can be requested, what is optional is whether to request theses options or not.

Padding -  Variable size bit field. These bits are used to ensure a 32 bit boundary for the header is achieved.

Next time we’ll highlight the main difference between a data transfer and a VoIP call over a network.

WhichVoIP Team   

http://www.whichvoip.com

Share/Save/Bookmark

Data T1 Lines

Friday, October 13th, 2006

First let me state there are no physical differences between a T1 for Voice and a T1 for data. They use the same physical medium, they have the same bandwidth, the same signal coding and the same frame format. The only difference is that it is now data instead of voice.

We’ll confine our discussion to data sent via the internet.

First lets recap on the T1 frame. One frame every 8KHz, 24 DSO’s in a frame and 8 bits in a DS0. This can be seen in the diagram below. If we are talking about a T1 to a PBX then each DS0 carries one voice call, with that call occupying the same DS0 every frame until the call is terminated. T1 frame structure

 

 

 

 

 

 

With data transfers the DS0’s in a frame can be grouped together. If for example we grouped 6 DS0’s together then we would have a bandwidth of 384Kbits per second. This kind of generates it’s own frame inside the T1 frame T1 subframe

 

 

 

 

 

 

Now we have created a second sub frame how do we know when one of these sub frames starts or stops? This is where we need to discuss IP Packets.

Next time round we’ll look at these IP packets and how they are formatted.

WhichVoIP Team 

http://www.whichvoip.com

 

Share/Save/Bookmark

The cost of a T1 and how to get one?

Monday, October 9th, 2006

We have talked a lot about what a T1 is and that the benefits are the increased available bandwidth that it gives your business over say, a buiness class DSL service. But where does it fit in on the bandwidth scale for different bandwidth offerings and how much does a T1 circuit typically cost. Well first of all, here is a brief summary of various bandwidth options available:

33.6 K (Modem)          33,600 bps
56 K (Modem)             56,000 bps
64 K (DS-0)                64,000 bps
128 K (ISDN)             128,000 bps
256 K (DSL)               256,000 bps
640 K (DSL/Cable)     640,000 bps
768 K (DSL/Cable)     768,000 bps
T1, DS-1                     1.544 Mbps
T3, DS-3                     44.736 Mbps
OC-1                           51.840 Mbps
OC-3                           155.520 Mbps
OC-12                         622.080 Mbps
OC-48                         2.488 Gbps
OC-192                       10 Gbps

As you can see, the T1 is the next step up from DSL and they are available as both full and franctional services.

So how do you get a T1? Well unfortunately the process is not quite as simple as getting your DSL going. The first thing you should do is get one or two quotes from service providers. To help you with this, WhichVoIP has partnered with some of the best providers in the business to provide you with competitive quotes. We have them squaring of against each other for your business ;-) Just go to our Business Solutions section and fill out a short request. Simple eh!

But then how long does it take? Well after you are happy with the deal you are getting it will take around 25 to 50 days to actually get your install completed. So plan ahead. This is mainly gated by the local exchange carrier who needs to coordinate the installation.

How much should I pay? Typical costs for a T1 circuit range from around $350 to as high as $650 per month. The reason for the discrepency is that the last mile from the Central Office to your premise has a high weighting in this calculation. So if you are close to the Exchanges Central Office, you could be in luck. However, the best way to make sure you are getting the best deal, is the good old method of getting more than one quote. This is where we hope we can help.

What if I still have questions? Then send us an email at customerservice@whichvoip.com and we will try to assist you.

In summary, small to medium sized businesses should never need anything more than a T1 or multiple T1’s. Some businesses prefer to get 2 T1’s for load-balancing and redundancy, especially if it is running VoIP on its network.

Cheers

Tony

http://www.whichvoip.com

Share/Save/Bookmark

u-law encoding – 8 bits in a DS0

Sunday, October 8th, 2006

The previous blog explained why we have 8 bits in a DS0, here we’ll explain how we get these 8 bits.

When  your voice is digitally sampled the amplitude or how loud you are speaking is captured, this happens 8000 times a second. However this digital sample is not what is sent. For a T1 line an algorithm called u-law is used to compand the data. This is a logarithmic type of algorithm that has the effect of giving greater resolution to lower value samples i.e. when you are talking quietly, and less resolution to higher amplitude samples. This intuitively makes sense, if someone is shouting then you can afford to loose a little differentiation between sounds but when someone is whispering you want to hear or accentuate the different levels so you can make out what they say. Typically when your voice is sampled, an Analog to Digital converter that has a 13 bit output is used, the u-law algorithm as well as performing this logarithmic compression has the effect of reducing the voice sample to the 8 bits that is sent.

Up until now we have confined our discussions to voice T1’s. Next time we’ll take a look at how data is transmitted via a T1 line.

WhichVoIP team

http://www.whichvoip.com

Share/Save/Bookmark

T1 frame rate and DS0 size

Sunday, October 1st, 2006

How did the 8KHz frame rate and the 8 bits per DS0 come about?

I’ll take the easy one first - Why 8 bits per DS0? For digital or telecom engineers 8 or any multiple of 2 is a perfect number. It’s very easy in digital logic to count in multiples of two thus it is very easy to extract these DS0’s, generate the frequencies and clocks required to receive and transmit at these rates and multiplex these T1 streams into T3 streams or higher rates. The trickier question is how do we get our voice to be transferred from one point to another in only 8 bits every 125us(this is the equivalent time of an 8KHz frame rate).

There is a theorem called Shannons theorem or sometimes referred to as Nyquist-Shannons theorem that drives the fundametal basics of all digital communications.  First remember that T1’s were invented long before the advent of the internet or VoIP and they were designed with the specific goal of transferring voice in a digital format. The result of Shannons theorem is that to sample an analog signal(your voice in this case), convert it to a digital format and then reconstitute it as an analog signal(your voice at  the other end) that has lost no or little information(the person you are talking to can understand you) the original analog signal must be sampled at a rate of at least twice the highest frequency you want to transmit.  The typical human voice has a frequency range of about 50Hz to 3500Hz. So if you want to sample that voice and digitize it you have to sample it at a rate of at least 7000Hz. As in all good designs there has to be some design margin, often referred to as a guard band in communication theory, a rate of 8000Hz was chosen. The frame rate of 8KHz became the standard.

Now we know why 8 bits is used in a DS0 and the rate it must be sent at. In the next blog we’ll go into a little more detail on how the 8 bits are generated and what they represent.

WhichVoIP Team

http://www.whichvoip.com

Share/Save/Bookmark