Talk:Voice over IP
|This is the talk page for discussing improvements to the Voice over IP article.|
|This article is of interest to the following WikiProjects:|
|This article has been mentioned or used by a media organization. The reference is in:
- 1 VoIP is not IP Telephony (although they are similar!)
- 2 How Do You Properly Spell Voice Over Internet Protocol
- 3 Definition in the Introduction section
- 4 advantages of softphone over VoIP phone and ATA
- 5 Requested move 1
- 6 References flag still needed?
- 7 about section: Fax handling
- 8 Historical milestones section
- 9 Voice Over IP
- 10 Comcast hatnote
- 11 gary turd
- 12 External links
- 13 IP telephony
- 14 Edit request from , 16 November 2011
- 15 Requested move 2
- 16 Definitions and other nits
- 17 Merger proposal
- 18 Pronunciation
- 19 Outdated informations
- 20 VoDSL
VoIP is not IP Telephony (although they are similar!)
Before anyone bites my head off I would just like to mention that I am a telecoms professional with over 22years experience in Legacy AND IP Communications.
Please refer to the Eupac IP Network Solutions site [] for a lovely simplistic description of the difference between the two.
"Yet it is important to distinguish between VoIP, which is a digital transport vehicle for phone calls, and IP telephony, which is a digital phone system based on internet standards. This is important, because business stands to benefit from both VoIP and IP telephony – in substantially different ways. VoIP is a method of digitising your voice so that it can be transmitted across the Internet to save call charges. Whereas IP Telephony is a way of digitising your phone system so that it can leverage the Internet, your computer, and your other business software applications (CRM, CTI, Outlook) to increase productivity within the Business. VoIP is actually a subset of IP Telephony."
Or put even more simply:
- IP Telephony is the carriage of telephone calls over IP based networks.
o Voice quality target is telephone call quality, no better, no worse o Attempt at making calling procedure and dialing same as PSTN o Attempt at supporting various PSTN features and functionality
- VoIP is the carriage of any voice signal over IP based networks.
o Voice quality can be designed according to the applications need. o Design for features and functionality as needed by the application o Next step to Multi-media over IP o Definition can be extended to include all audio, e.g., music
Some of us "dinosaurs" have been around long enough to know where both technologies began, where they came from and where they are going ;-)
OK, I'm going to try to post my feelings on this issue because it really matters to me.
I agree & disagree with Bluemavryk at the same time. There is a distinction between VoIP and IP Telephony in the industry as it stands today. The way I see it:
IP Telephony Refers to:
- A coherent implementation of an IP-based telephony system that consists of endpoints, and their related infrastructure.
- Said Implementation is intended to provide direct access to telephony services to an end-user community
- Can be used to replace traditional (TDM, POTS) telephony services.
VoIP Refers to:
- The constellation of protocols and methodologies that provide for the transmission of voice across IP networks.
- The set of generally accepted practices used in accomplishing said transmission.
- Any hardware necessary to accomplish said transmission.
In general: If you are utilizing IP-based transmission methods to deliver voice to an endpoint, you are using VoIP. If your transmission method is VoIP end-to-end within a given implementation, you are using IP Telephony.
I would like to see less of the discussion of commercial VoIP and how it is provided (or at least a re-org) and more discussion of the underlying technologies behind VoIP. I think we can structure this article better in this fashion:
- Signalling Protocols
- Proprietary/Vendor Specific (NEC, Nortel, etc.)
- Speech Protocols
- iLBC (Skype, among others, uses this particular method of encoding voice for transmission across the Internet)
- Signalling Protocols
- Home/SoHo Use
- Replacing PABX Leased-Line Ties (Network Convergence)
- Replacing Traditional PABX's Wholesale
- CO Use (Softswitches/Interoffice Ties)
- Sound Quality vis-a-vis Lossy Codecs
I'm sure there's more fertile ground to be found somewhere. This is all I can come up with for right now on this subject, I know I'll think of something more to add later.
I agree QuackCD, this article is in serious need of a complete rewrite. I can see where you are going with your proposed TOC, however I would say that many subjects like protocols and codecs are already covered in detail on wikipedia and don't need repeating here (just listing and linking would be enough).
VoIP is a concept (sending voice over IP networks) not a protocol (I would state that the misunderstanding between a concept, protocol and architecture is the main reason the current page is so poor). The page should concentrate on what VoIP means (voice communication over IP networks) and cite examples of how to achieve this with relivant links to other articles. Rather than delving deep into each technique, it should state the different methods of VoIP (SIP & RTP, MSN messenger, Skype, H.323, etc.) and show the various UA devices which are used (like TopCom Skype phones, CISCO ATA 186s, CISCO 7960s, x-lite softphones, etc.).
At the moment the page is a random discussion of anything and everything that might be covered by the term VoIP... I'm happy to help you work on a new page. Just drop me an email or contact me through my talk page.
I’ve just finished a major copy-edit of the VoIP page. I tried (as much as possible) to keep the original content of the page – I don’t agree that all of the content is necessary, however I didn’t want to be a one-man jury on what was and wasn’t needed.
I tried to improve and increase the number of inter-wiki links to other articles (and where possible reduced the amount of information repeated which was available via the links) and also removed obvious commercial spam and advertisements that had crept into the page.
I also rearranged the article into a more logical pattern; placing the adoption of VoIP at the top, followed by the benefits and challenges. All other information I moved to the bottom of the article. I hope this arrangement will help other wiki-editors to sift through the article and correct anything I missed.
There was also a large amount of repetition between the sections (mainly caused by the lack of organization). I removed the repetition wherever possible and concatenated the information into the relevant sections.
There is still a lot of citation gathering to be done for this article so I placed ‘citation required’ tags next to the ‘statement of facts’ that I saw (although there a probably quite a few that I missed).
I have not touched the legal section, nor the section on Japanese VoIP as I do not know enough about these topics.
Here is my list of questionable content remaining in this article. If there are no objections I will rewrite/delete the following text (note: my reasoning is in-line):
"A tragic example of a miscommunication with VoIP is the death of 18-month-old Elijah Luck in Calgary, Canada. In an emergency, 911 services were called. An ambulance was sent to the former home of the Lucks. The VoIP telephone company knew the correct address, as they were paying their bill from the correct current billing address the company had on record. "It's up to subscribers to ensure the company has up-to-date contact information" was the response from the VoIP company. After about a half hour wait, the Lucks called from a neighbor's land line, whereupon emergency services arrived in six minutes. Elijah Luck was pronounced dead at the Alberta Children's Hospital."
-- Although citated this doesn't really add anything to the VoIP discussion. The linked article even goes on to state that this was the failing of the owner of the subscription to update his E911 record rather than a problem with VoIP
"A voice call originating in the VoIP environment also faces challenges to reach its destination if the number is routed to a mobile phone number on a traditional mobile carrier. VoIP has been identified in the past as a Least Cost Routing (LCR) system, which is based on checking the destination of each telephone call as it is made, and then sending the call via the network that will cost the customer the least. This rating is subject to some debate given the complexity of call routing created by number portability. With GSM number portability now in place, LCR providers can no longer rely on using the network root prefix to determine how to route a call. Instead, they must now determine the actual network of every number before routing the call.
Therefore, VoIP solutions also need to handle MNP when routing a voice call. In countries without a central database, like the UK, it might be necessary to query the GSM network about which home network a mobile phone number belongs to. As the popularity of VoIP increases in the enterprise markets because of least cost routing options, it needs to provide a certain level of reliability when handling calls."
-- VoIP has never (to my knowledge) been identified as a least cost routing system by any definition of LCR. While it might make LCR decision making harder (like any other available route would) this statement is misleading and wrong. The complexity of LNP and MNP are no more pronounced for VoIP than any other voice communication method. This should be deleted.
"MNP checks are important to assure that this quality of service is met; by handling MNP lookups before routing a call and assuring that the voice call will actually work, VoIP companies must give businesses the reliability they look for in an Internet telephony provider."
-- MNP is important to ensure the called party receives calls... it is not really a 'quality of service' issue (QoS is usually more associated with voice quality). This statement should be rewritten or removed.
"In countries such as Singapore, the most recent Mobile number portability solution is expected to open the doors to new business opportunities for non-traditional telecommunication service providers like wireless broadband providers and voice over IP (VoIP) providers."
-- This statement is nonsense, MNP is not a value add in the network, it is a reglatory requirement to protect consumers. Perhaps LNP would be more correct in this case since it allows consumers to move to VoIP networks from the PSTN without changing numbers?
"While the wired public switched telephone network (PSTN) and mobile phone networks share a common global standard (E.164) which allocates and identifies any specific telephone line, there is no widely adopted similar standard for VoIP networks. Some allocate an E.164 number which can be used for VoIP as well as incoming and external calls. However, there are often different, incompatible schemes when calling between VoIP providers which use provider-specific short codes."
-- Most (if not all) VoIP service providers support E.164 numbering (and routing), otherwise they could not connect to the PSTN or route inbound PSTN calls. I suspect this comment is out of date and historical at best.
In the History section, consider crediting the inventors or VoIP: Alon Cohen and Lior Haramaty, US Patent 5,825,771 filed November 10, 1994 RTP is not a voice protocol, but a protocol that insures real-time delivery. T.48 is the FAX over VoIP standard To codecs, you can add these: GSM-full rate, GSM-half rate and GSM-amr. 184.108.40.206 (talk) 21:05, 29 August 2011 (UTC)
How Do You Properly Spell Voice Over Internet Protocol
I know this seems like a inane question, but for the sake of transcribing webcasts and webinars correctly, what is the correct or most accepted way to spell voice over internet protocol? We have seen: voice over internet protocol; Voice over Internet Protocol; Voice over internet protocol; voice-over internet protocol; Voice Over Internet Protocol; voiceover internet protocol. There has been much heated debate among staff about one or two words; which letters are capped if at all, etc. GHKWells (talk) 04:06, 9 March 2009 (UTC)GHKWells
- Although this is not a help forum, the article title has the proper format. The next best version would be to capitalize 'Over' as well, but this is usually not done in any of the 'something over another' protocol names Kbrose (talk) 04:57, 9 March 2009 (UTC)
- The correct capitalisation is to have the o lower case, the acronym therefore is VoIP, I dont think it matters in the text if you have Voice over Internet Protocol, or voice over internet protocol. Stuart Ward UK (talk) 21:35, 9 March 2009 (UTC)
- To be precise here, as the word spells-out an acronym, Stuart Ward is largely right in saying VoIP (most common usage by IT professionals and usual publications [eg. newspapers/magazines/many news websites] stylistic choice to have lowercase letter o), however in the English language, acronyms are supposed to be all in caps, so you can also use VOIP as another option, as per your own preference. As for the first letter capitalisation, the same is true, and as it's a noun (the name of a group of protocols) it should be cap'd; either non-"o" as Voice over Internet Protocol (usual IT/publications spelling), or all as Voice Over Internet Protocol (proper English language capitalisation rule spelling).
- Notice there are four separate words, as "Voice-over" or "Voiceover" means an actor (re-)talking over pre-filmed material in a studio or similar, which is something completely different. (ie. in this four word noun, it would mean doing some kind of talking over pre-filmed material, sent over the internet! lol. Ironically many actors do this on animation feature films; literally studio recording in one city their voiceover parts, and sending by internet to another city where the film is being put together!) Jimthing (talk) 00:10, 5 January 2011 (UTC)
Definition in the Introduction section
The previous content wasnt correct:
advantages of softphone over VoIP phone and ATA
The article reads:
- An advantage of using a softphone with a VoIP service provider is the ability of having a fixed phone number which can be moved to any country or location (This is also possible with ATAs and VoIP phones, although it requires the physical relocation of the hardware.)
Any voip solution is identical in this respect: they are agnostic about their geographical location. You don't have to physically relocate a voip phone or ATA to enjoy these advantages. You can alternately just use a second ATA in a second location. And a softphone is no different: you have to either relocate your computer or install the softphone on a second computer.
Requested move 1
Just for the record this change had no discussion nor consensus. For a general audience full name are better than dubious abbreviations they may not know precisely, especially since many use IP instead of IP address. Kbrose (talk) 20:52, 12 December 2011 (UTC)
- Maybe so but Voice over IP is now the established title and reverting the move is not uncontroversial. Please use WP:RM before reverting again. --Kvng (talk) 23:39, 12 December 2011 (UTC)
References flag still needed?
- Just noticed this thread. As of today there are 12 specific facts needing citations (see the  throughout the article) and the Japan section is entirely unreferenced. The question of citations can't really be answered with a number, but there's some good reading at WP:V and WP:Citing sources. --Pnm (talk) 01:19, 5 January 2011 (UTC)
about section: Fax handling
The voice codec is not the primary reason of fax transmission failures. True, if you're using something highly compressed such as g.729, but as long as you're using G.711 - a or u law, which is the exact same codec as used in the PSTN. The problem with faxing over common internet based VoIP providers is the packetization of the internet. That along with your call audio getting handed off to distant wholesale provider's PSTN interconnets over the internet, and with many routers along the way to the PSTN interconnect don't always provide good enough QoS. Some very good VoIP providers do the PSTN coversion in-house so that your calls are sent to the wholesale provider off-internet, so providers like these can provide very good QoS. 220.127.116.11 (talk) 11:39, 10 January 2011 (UTC)
Historical milestones section
2004 — Commercial VoIP service providers proliferate
Why just 2004? Have they not proliferated in other years? This historical milestone, or at least the date to which it is confined, seems rather dubious to me. —Preceding unsigned comment added by 18.104.22.168 (talk) 20:24, 21 January 2011 (UTC)
Voice Over IP
VoIP or Voice over internet protocole also called internet telephony enables users to speak to other users over the internet. That is VoIP uses the internet (instead of the public switched tgelephone network) to connect a callling party to one or more local or long distance call. —Preceding unsigned comment added by 22.214.171.124 (talk) 14:41, 1 February 2011 (UTC)
- Actually, no. When first coined, we used the term to refer to carrying voice over IP for some leg of a call: at that time typically through a modified PABX to a private internet gateway plugged directly into the PSTN over PBX trunks. — Dgtsyb (talk) 22:04, 1 February 2011 (UTC)
- I think part of the problem is that this article has been reworked bit-by-bit since 2002 without a major, unifying overhaul. As technologies converge, the technical and popular distinctions between IP telephony and consumer VoIP are growing faint. As the ILECs extend fiber networks throughout the middle mile and, in some places, the last mile, people with "analog" or PSTN POTS phones really only have copper until it hits the little box in their backyards. The national trend is moving towards an all-IP network, in which case "VoIP" will be nothing more than a telephony service provided by the non-LECs and IP telephony will be anything provided by the RLECs, CLECs, and ILECs. Alphachimera (talk) 15:27, 20 May 2011 (UTC)
The header of this article lists "Comcast Digital Voice", which is a blatant advertisement by Comcast. VoIP protocols are utilized by many companies and this article should remain neutral where patents are not a consideration.
- The hatnote is there because the article about Comcast's VoIP product is at Comcast Digital Voice – even though the product was called Digital Voice – Digital voice redirects to Voice over IP. Looks like the product is called Xfinity Voice now. --Pnm (talk) 05:25, 10 February 2011 (UTC)
The first paragraph of this article has these two words -- typos? mpeder
How does VOIP work? — Preceding unsigned comment added by Sabincb (talk • contribs) 06:38, 8 June 2011 (UTC)
Voip on cell phone - mVoip or Mobile Voip — Preceding unsigned comment added by Freecallshub (talk • contribs) 21:08, 18 September 2011 (UTC)
Some things I don't get on the project though:
- is the old telephone number kept (ie 00 33 51 123456 or something like that; 00 --> prefix, 33 --> country code, 51--> area code, last 6 numbers the actual phone number OR
does a entirely new (VOIP) telephoen number needs to be taken ?
- is the data tranferred via the old telephone line (POTS) or via a seperate internet access line (ie 56k, ISDN, ADSL or even cable, ...)
Edit request from , 16 November 2011
|This edit request has been answered. Set the
I would like to add http://www.modulis.ca as an external source in this article. Modulis is a leading Canadian VoIP Provider. Thanks.
- Not done: External links should have additional information about the article subject matter. This is just a company that does VOIP installation. — Bility (talk) 00:53, 17 November 2011 (UTC)
Requested move 2
Definitions and other nits
Very good informative article so please excuse me for the tiniest of nits.
"Premise" should be "premises". I know that using "premise" this way has become the technical vernacular, but it grates a bit.
The article takes care to define acronyms at the first use but there are a few exceptions (DSL, ADSL, QoE, PBX (although identifying PBX as Private Branch Exchange may not add clarity), PVC and TCP). Morganstein (talk) 03:19, 3 July 2012 (UTC)Morganstein
I propose that Web-based VoIP and Cloud telephony be merged into Voice over IP. I think that the all three articles really describe various aspects/stages of the same thing, and having three separate articles is unnecessary. Bensci54 (talk) 03:00, 1 February 2013 (UTC)
- Question Where do you intend to put the merged material? Although it does not come out and say so, the current article is about replacing POTS with VoIP. The merges will expand the scope of the article. -—Kvng 14:44, 4 February 2013 (UTC)
- I plan to add them into new sections, unless the current section affords an opportunity for information to be inserted within. Bensci54 (talk) 03:32, 6 February 2013 (UTC)
- I don't think it as simple as that. For example, a lot of the material in the top-level Voice_over_IP#Legal_issues section applies only to POTS replacement. When you merge these topics in, we have to somehow clarify which types of VoIP these issues apply to. Similar issues exist in the Challenges and Adoption sections. I'm generally in favor of merges such as you've proposed but I also like to see improvement with every change we make. Just moving the source articles into this one as new sections would not be an improvement. Are we ready to do the work required to actually integrated the merged material? -—Kvng 15:32, 10 February 2013 (UTC)
- I plan to add them into new sections, unless the current section affords an opportunity for information to be inserted within. Bensci54 (talk) 03:32, 6 February 2013 (UTC)
- Support the merger. I'm not sure what the best title is for a merged article, but Voice over IP is the best-developed article with the longest history, so the proper thing to do would be a merge to that article and then, if necessary, a subsequent rename to whatever we think is best. — Æµ§œš¹ [ãːɱ ˈfɹ̠ˤʷɪ̃ə̃nlɪ] 19:00, 5 February 2013 (UTC)
- Support— the former is just a stub on an aspect of this article, and the latter is about the business around the former. Shirudo talk 02:01, 6 February 2013 (UTC)
- Support different aspects of same topic. Article sizes don't warrant separate ones. Widefox; talk 17:35, 11 February 2013 (UTC)
- Oppose None of the supporters have adequately addressed my question (above) about how this merge will be executed. I can't support until there is an answer. Mine is not a rhetorical question; I don't have an answer. -—Kvng 18:45, 13 February 2013 (UTC)
- "Partial support" - Can't refute Kvng. Not usually a fan of merging, but in this case, I definitely am. So, what about a step-wise approach? First merge Cloud telephony into both and then see what you've got? Cloud telephony is linked from Cloud computing and I felt that, like many links in Cloud computing, it just sort of wasn't worth the click. It might have been worth it the click if Cloud telephony was merged with Voice over IP, though! Definite fan of merging Cloud telephony!!! Maura Driscoll (talk) 21:03, 10 April 2013 (UTC)
- Cloud telephony is a subset of Cloud communications; it means third-party, off-site VoIP services in general. This includes both web-based and non-web-based VoIP (it could just integrate with conventional telephones as a PBX replacement).
- Web-based VoIP simply uses a web page running a multimedia applet or whatever instead of dedicated non-web VoIP software
There is no section in Voice over IP into which to merge Web-based VoIP, since it defines a class of client software; though I did add an awkward link from the "Protocols" section. Clients are described at Comparison of VoIP software. Web-based software is included there but not necessarily marked as such. That's another potential merge target, but I don't have any problem leaving web-based VoIP as its own article for a while and letting it grow. It may be handy to just be able to link there from several other articles. I removed the merge tag from Web-based VoIP for now, but feel free to rekindle the debate if you see fit. -- Beland (talk) 04:21, 6 May 2013 (UTC)
- (And a good reason to have separate articles on specific aspects of VoIP is that Voice over IP is already at the maximum desirable length; there is not really the room to go into detail on either of these subtopics.) -- Beland (talk) 04:26, 6 May 2013 (UTC)
In addition to the given statements under the "pronunciation" section, I knew a French-Canadian guy for whom French was his native tongue, and he would pronounce it "vwahp" ("-oi-" is pronounced something like "-wah-" in French.) Should a note be made in that section about this? — Preceding unsigned comment added by 126.96.36.199 (talk) 01:42, 7 August 2013 (UTC)
In this article, under Legal Issues -> European Union in last paragraph at the end there is quote "A review of the EU Directive is under way and should be complete by 2007." It should be either updated with the directive if it is completed, or update the date since it has passed 6 years since 2007. — Preceding unsigned comment added by 188.8.131.52 (talk) 22:02, 28 August 2013 (UTC)
- It looks like VoDSL can be VoIP over DSL or it can be something more akin to VoFR. Maybe convert VoDSL (back) to a stub. Here's a ref to get started with  ~KvnG 14:53, 12 July 2014 (UTC)