Talk:Compelled signalling
Appearance
This article was nominated for deletion on 13 April 2021. The result of the discussion was keep. |
This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||
|
If no example is important besides R2 signalling, then why isn't this a section of that article? Jim.henderson 04:22, 31 January 2007 (UTC)
- R2 is not the only example of compelled signalling. The other significant signalling system that is at least partly compelled is #5. I am however not authoritative on that so am reluctant to add this information to any of the articles that reference compelled signalling. —The preceding unsigned comment was added by JanCeuleers (talk • contribs) 15:21, 31 January 2007 (UTC).
- Specifically, the line signalling element of #5 is compelled, the register signalling element is non-compelled (i.e. pulsed). JanCeuleers 15:28, 31 January 2007 (UTC)
- Perhaps it is due to a Bell System mindset, but I find compelled interregister signaling easy to understand, whilst the explanation of compelled off-hook and on-hook signals escapes my current comprehension. Jim.henderson 15:22, 4 February 2007 (UTC)
- I think of compelled as a synonym of acknowledged in the specific context of signalling using discrete signals. This way it can apply both to line and to register signalling. (I mention the discrete signals bit because I've not heard the term used in the context of message-oriented signalling protocols such as SS7 or Q.931, not that you were suggesting it is). Getting back to compelled line signalling: I guess this would be true for line signalling types where each signal (or signal change) is explicitly acknowledged (e.g. seize/seize-ack, release/release-ack, ...). JanCeuleers 16:01, 4 February 2007 (UTC)