Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Call collision
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{multiple issues| {{tone|date=September 2015}} {{no footnotes|date=March 2013}} }} In the field of [[telecommunications]], a '''call collision''', commonly referred to as a '''glare''', can occur in two situations:<ref>{{Cite web |title=call collision β Glossary |url=https://glossary.atis.org/glossary/call-collision/ |access-date=2022-06-05 |website=[[Alliance for Telecommunications Industry Solutions]] |language=en-US |archive-date=2023-08-13 |archive-url=https://web.archive.org/web/20230813212323/https://glossary.atis.org/glossary/call-collision/ |url-status=live }}</ref> # Terminal and Data Circuit-Terminating Equipment ([[Data Communications Equipment|DCE]]) [[Resource contention|Contention]]: This type of call [[collision]] arises when both a [[terminal (telecommunication)|terminal]] and a [[data]] [[Telecommunication circuit|circuit]]-terminating equipment (DCE) simultaneously designate the same [[communication channel]] to initiate a call request and handle an incoming call. In such cases, the [[Data Communications Equipment|DCE]] prioritizes the call request and proceeds with it, resulting in the cancellation of the incoming call. # Trunk or Channel Seizure at Both Ends: The second scenario involves a call collision when a [[trunking|trunk]] or channel is seized simultaneously at both ends. This situation can lead to conflicts and disruptions in the communication flow. Glare can sometimes be experienced when attempting to make an outgoing call on a private branch exchange ([[Business telephone system|PBX]]) system but getting connected to an incoming call instead. This occurrence can also happen in residential settings if an outgoing call is initiated at the precise moment when an incoming call is about to start ringing. To mitigate the risk of glare, [[Multi-line hunting]] techniques are employed. These techniques involve selecting circuits in the opposite preference order, ensuring that the highest numbered line, which is typically the last choice for incoming calls, becomes the first choice for outgoing calls. The following example illustrates the sequence:<pre>incoming -->1 2 3 4 5 6 7 8<-- outgoing</pre> With [[Primary Rate Interface|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 signaling 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]] signaling, which offers a 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. ==References== {{Reflist}} {{FS1037C MS188}} [[Category:Teletraffic]] {{telecom-stub}}
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Templates used on this page:
Template:Cite web
(
edit
)
Template:FS1037C MS188
(
edit
)
Template:Multiple issues
(
edit
)
Template:Reflist
(
edit
)
Template:Telecom-stub
(
edit
)
Search
Search
Editing
Call collision
Add topic