Is there a setting within TTD (IAR version, if that matters) that causes it to stop listening for tones for a period of time when a tone is detected that is NOT in its list?
Recently our comms/dispatch has changed from sending only our tone plus our voice alert message on our alerting channel, to sending the tones for all dispatched stations, then our voice, on our channel (kind of like what you used to hear on *Emergency!*, where several series of tones will be played before the actual voice alert message is sent). It's a configuration change from the alerting end that I'm working with the alerting vendor to try to revert to the previous method.
My problem is that TTD is not detecting my tones when they are played as the second in order, after the first one, before the voice message. What's happening is there is the first tone (for a station that my TTD is not configured to do anything with), about a 1000 ms pause, then my tones, then another pause, then the voice. In situations where my tones are the only tones played, TTD is pretty consistently capturing them and sending the alert notification, making and emailing the recording, etc. What I've found is that when other stations' tones are played before mine, as above, TTD is for some reason NOT recognizing my tones and doing the alerts, recordings, emails, and so on.
If I can't get this reverted to the previous method where my tones and only my tones are played prior to the alert, is there some setting I should be looking for in TTD to make it recognize and capture my tones when they're not the first ones sent?
