About: Call collision

Facets (new session)
Description
Metadata
Settings
- Rule:
- Inverse Functional Properties:
- "Same As":

About: Call collision Goto Sponge NotDistinct Permalink

An Entity of Type : dbo:Agent, within Data Space : dbpedia.org associated with source document(s)
QRcode icon

http://dbpedia.org/describe/?url=http%3A%2F%2Fdbpedia.org%2Fresource%2FCall_collision

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.

Attributes	Values
rdf:type	agent
rdfs:label	Call collision (en)
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. (en)
dcterms:subject	Teletraffic
Wikipage page ID	40830 (xsd:integer)
Wikipage revision ID	1124234598 (xsd:integer)
Link from a Wikipage to another Wikipage	Resource contention Call transfer Collision Communication channel Primary Rate Interface Time Data Teletraffic Telecommunication circuit Information and communications technology Terminal (telecommunication) Business telephone system Ground start Data Communications Equipment Telephone call Loop start Multi-line hunting Trunking
sameAs	Call collision Call collision Call collision
dbp:wikiPageUsesTemplate	dbt:Multiple_issues dbt:No_footnotes dbt:Reflist dbt:Tone dbt:FS1037C_MS188 dbt:Telecom-stub
has 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. (en)
gold:hypernym	Things
prov:wasDerivedFrom	wikipedia-en:Call_collision?oldid=1124234598&ns=0
page length (characters) of wiki page	2932 (xsd:nonNegativeInteger)
foaf:isPrimaryTopicOf	wikipedia-en:Call_collision
is Link from a Wikipage to another Wikipage of	Index of electronics articles Glare Business telephone system Ground start Race condition Loop start
is foaf:primaryTopic of	wikipedia-en:Call_collision

Faceted Search & Find service v1.17_git139 as of Feb 29 2024

Alternative Linked Data Documents: ODE Content Formats:

RDF

ODATA

Microdata

About

OpenLink Virtuoso version 08.03.3330 as of Mar 19 2024, on Linux (x86_64-generic-linux-glibc212), Single-Server Edition (378 GB total memory, 56 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software