This HTML5 document contains 38 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dctermshttp://purl.org/dc/terms/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n10https://global.dbpedia.org/id/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
freebasehttp://rdf.freebase.com/ns/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
wikipedia-enhttp://en.wikipedia.org/wiki/
provhttp://www.w3.org/ns/prov#
dbphttp://dbpedia.org/property/
dbchttp://dbpedia.org/resource/Category:
xsdhhttp://www.w3.org/2001/XMLSchema#
wikidatahttp://www.wikidata.org/entity/
goldhttp://purl.org/linguistics/gold/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Call_collision
rdf:type
dbo:Agent
rdfs:label
Call collision
rdfs:comment
In telecommunications, a call collision (commonly known as glare) is one of two things: 1. * The contention that occurs when a terminal and data circuit-terminating equipment (DCE) specify the same communication channel at the same time to transfer a call request and handle an incoming call. When call collision occurs, the DCE proceeds with the call request and cancels the incoming call. 2. * The condition that occurs when a trunk or channel is seized at both ends simultaneously.
dcterms:subject
dbc:Teletraffic
dbo:wikiPageID
40830
dbo:wikiPageRevisionID
1124234598
dbo:wikiPageWikiLink
dbr:Call_transfer dbr:Telecommunication dbr:Data dbr:Time dbr:Trunking dbr:Primary_Rate_Interface dbr:Terminal_(telecommunication) dbr:Telephone_call dbr:Collision dbc:Teletraffic dbr:Business_telephone_system dbr:Telecommunication_circuit dbr:Multi-line_hunting dbr:Data_Communications_Equipment dbr:Resource_contention dbr:Ground_start dbr:Communication_channel dbr:Loop_start
owl:sameAs
freebase:m.0b5nb n10:4esEV wikidata:Q5021612
dbp:wikiPageUsesTemplate
dbt:Reflist dbt:Tone dbt:Telecom-stub dbt:FS1037C_MS188 dbt:Multiple_issues dbt:No_footnotes
dbo:abstract
In telecommunications, a call collision (commonly known as glare) is one of two things: 1. * The contention that occurs when a terminal and data circuit-terminating equipment (DCE) specify the same communication channel at the same time to transfer a call request and handle an incoming call. When call collision occurs, the DCE proceeds with the call request and cancels the incoming call. 2. * The condition that occurs when a trunk or channel is seized at both ends simultaneously. Glare can sometimes be experienced as trying to make a call out on a PBX, and instead being connected to an incoming call. This can happen at home too, if a call out is made at the exact second that a call is about to start ringing in. Multi-line hunting attempts to avoid glare by selecting circuits in opposite preference order so the highest numbered line, which is last choice for incoming calls, is first choice for outgoing calls, like so: incoming -->1 2 3 4 5 6 7 8<-- outgoing With PRI circuits, the channel selection sequence is specified when the circuit is provisioned. Common practice is to have the PBX use descending channel selection, and the carrier to use ascending. Glare is not common on PRI circuits because the signalling is so fast, however it is not impossible (especially if there are subtle differences in the timers at either end, and the circuit is being used at near-capacity). The users will not experience a connection to an unexpected call (as would be the case with analog circuits), because glare causes protocol errors that generally prevent any sort of successful connection. Instead, one or both of the call attempts might fail, and ideally an error would appear in the logs (this depends on the logging capabilities of the systems at either end of the circuit). Glare is quite rare on PRI circuits, and can be difficult to troubleshoot. For old, analog PBX trunks, glare can be reduced by using ground start signalling, which offers better answer and disconnect supervision. IE: Nortel BSP discouraged using loop start trunks for this and other reasons. Long Distance exchanges in the 1950s and 60s incorporated Glare Detectors to alleviate the problem.
gold:hypernym
dbr:Things
prov:wasDerivedFrom
wikipedia-en:Call_collision?oldid=1124234598&ns=0
dbo:wikiPageLength
2932
foaf:isPrimaryTopicOf
wikipedia-en:Call_collision