Critical Communications: Dispatch

Question How can I mute my transmit audio coming back as receive on another line?   Answer In some radio systems, when several RF channels are the same to each other in frequency, transmitting on one channel can cause others to break squelch and make noise. Although this is in reality likely an RF problem that is best dealt with by addressing the root causes—antenna proximity, orientation, and TX power output levels, etc., Telex C-Soft can help mask these symptoms by providing audio RX blocks for selected adjacent channel lines. RX blocks programmed into C-Soft will automatically mute the lines selected in the list during console transmit. (Other Telex "hard" consoles also have this feature.) For example, if Line 1, a VHF channel is randomly causing three other nearby VHF channels, Line 2, Line 3 and Line 4 to unsquelch during transmit, RX block should be programmed for those channels as shown in Figure 1. This screen is found in Edit/Set up per line parameters/Frequency. Note: per-line mute buttons must be present in the design for RX Block to work. Figure 1 RX Block delay time RX Block delay, found in Edit/Global parameters/Audio, sets the amount of time in milliseconds, that the muting time is continued after console ptt stops.  This can be useful for masking repeater squelch tails and network latency of parallel line RX traffic, see Figure 2.   Figure 2                   © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question How do I change Zones/Channels on a Kenwood radio with Telex Dispatch products?   Answer The Telex consoles do not have the ability to directly change zones on a radio, this would be done in either the IP-223 or IP-224. The frequency you select on the console would correspond to the F-Tone on the Per Line Setup page in the IP-223/4. In that same section look at the far right hand side and you will see two columns labeled system and channel. The system column is the zone that you want the radio to change to when the console selects that channel. In turn the IP-223/4 will also change to that channel in that zone. So in practice let’s say the IP-223/4 has F1, F2, F3 set to zones 1,2,and 3 for the channels 1,2,3 respectfully. Now if this is submitted and saved to eeprom, the IP-223/4 will now change channels to zone 1 channel 1 when the IP-2002 selects F1. If the console selects F2 then the radio will change to zone 2 channel 2. If the console selects F3 then the radio will change to zone 3 channel 3.             © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question Where can I download the latest version of software/firmware and manuals for Telex Dispatch products?   Answer Software, firmware and manual downloads are only available to authorized users at http://www.telex.com/us/dispatch/downloads/s               © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question How can I cancel a page once its started in Dispatch consoles?   Answer Pressing any PTT button during the page sequence will cancel the page.             © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question How can I troubleshoot IP Console and Gateway Audio Transport Across a Network?   Answer On initial set up of a console system, often the most frequent problem is the failure of Consoles and IP-223s to communicate across the network.  Common causes of this are: Typos in addressing, such as multicast addresses and port numbers not matching on end to end devices. Firewall turned "ON" in console computers Multicast being blocked across the network due to router settings, etc Use of the Telex “VU Meter” program (download at http://www.telex.com/us/dispatch/file?i=97544&lg=eng) is an excellent and quick way to determine if data is present on the correct port numbers. Open VU Meter with the appropriate multicast address and port number entered in the blanks. Turn the program on. Send a test call on the TX or RX port numbers and see if VU Meter indicates digital audio activity. You may open multiple instances of VU Meter to simultaneously monitor TX and RX port numbers.  Verification that audio data is being sent out on the correct address, but not arriving at the far end of the network may indicate a problem with network configurations, that is, blocking of multicast traffic. Please note that some newer switches are intelligent enough to contain routing functions, which can be unintentionally enabled in some situations.           © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question What are possible causes of poor audio in Telex Radio Dispatch Systems?   Answer Telex Radio Dispatch systems have operating requirements which need to be established and verified, in order to insure good quality audio across a system.  Here are some fundamental parameters that installers and technicians need to be aware of, which, if not properly ascertained, may be causes of poor quality audio in the system. Levels are a foundational issue with Telex radio systems. Improper digital audio levels are one of the most common defects that impair system audio quality.  This means that the digital transmit audio and digital receive audio must be “proportional”.  “Proportional” means that the sampling and conversion of the analog signals must be in the proper binary value “window”.  Generally this would be indicated by a VU Meter bar graph deflection of about 2/3 to ¾ scale at voice peaks.  Improper digital audio levels are the result of improper analog levels going into the CODEC. Digital audio that is too low or too high will degrade re-constitution of digital back to analog audio at the end points.  The Telex “VU Meter” program allows measurement of the digital audio levels at different points in the network. (See the Knowledge Based articles on Optimal Analog to Digital Conversion in the IP-223, and Telex Dispatch VU Meter Program) VU Meter gives a graphic and numeric indication of digital sampling with multicast traffic. Microphones The quality of the transmit audio of the entire system depends heavily upon the quality of the signal originating from the microphone.  The microphone is where the “tires touch the road” in the system, and a poor quality microphone cannot be compensated for by any external means. The highest quality radio system will not sound good if the microphone is of poor quality, improperly adjusted, or improperly used.  The microphone is the last component in the system that should be a low price based selection. Poor microphone audio is often caused by improper use of the microphone, or the wrong type of microphone for the application.  Without a doubt, the headset mic is the best choice for any dispatching application, whether pubic safety, or not. The headset mic is always at a consistent distance from the dispatcher’s mouth, and the close proximity minimizes background noise, and promotes a very consistent voice transmit level.  Keep in mind that although some dispatchers do not like to wear headsets, no other type of mic will produce as consistently good sound quality as well as a headset mic. Desktop and gooseneck microphones are designed to be used at a specific distance from the dispatcher’s mouth, and when that distance is exceeded, audio quality degrades, and more background noise is picked up along with the voice.It is common to find a desk mic used at a much greater distance than intended, and this creates less than optimal voice audio quality. Obviously, a microphone gain setting that is too high can also create a similar problem, with excessive pickup of background noise, and excessive voice amplitude.  Too low of gain setting, and the voice amplitude will be too soft and accompanied by noise. Again console mic audio in a RoIP system is adjusted by watching the VU Meter deflection at the console, using a loud talk test.Once the best deflection is attained, further gain adjustments at the radio end ensure proper transmitter modulation, and optimal audio quality.  Voice peaks are a recommended reference point for calibration. Tones may not be as accurate for modulation calibration, as digital conversion does not reproduce single frequency sine waves as well as voice modulation. Control Stations Control station radios need to be run across the test bench to insure that they meet all performance specifications.  Once installed on site, transmit modulation levels need to be re-verified, once the overall system alignment is completed. Mic Jack Audio Some radios use the mic jack as the TX audio interface. Be aware that such low level signals are susceptible to local sources of electrical noise, and shielded cables should always be used. RF Most installations use multiple control stations in a single rack or shelf arrangement. RF leakage can infiltrate wiring of all kinds, so it is important to minimize any radiation that may occur in the vicinity of the system equipment.  Keep lead lengths as short as possible. Using outside antennas located as far away from equipment as possible is important, especially when using high power base stations. Use double shielded RF antenna cables to insure that minimal RF radiation is occurring locally at the rack. iDen phones and similar can generate all kinds of pulse mode interference, especially if the antenna is not cabled to an external location. A loose antenna cable connector can create a lot of RF radiation near the radio. When in doubt, shield everything. Make sure connections are tight. Amplified speaker cables and microphone cables are very susceptible to pulse mode RF interference. High Noise Floor Areas For example, if you are planning a power company dispatch center installation, and you have 345,000 volt transmission power lines next to the building, you may have a noise problem.  Similarly, areas near commercial radio and television broadcasting towers may also have a very high RF noise floor that must be considered. Control station interfaces should be located out of the area of these types of noise sources if possible. If installation away from these noise sources is not possible, extra care should be used to shield all wiring.  Faraday shielding is the best method of eliminating electrical noise induced from radiating sources. Noise Present via Supplied AC Power Variations and transients in AC power can contribute to system noise.  Using UPS power supplies or power conditioners can help eliminate AC power noise present on the supply lines. Verifying that the equipment room supply outlets are properly wired and correctly grounded is good practice.  Improper grounds can be a significant factor in noise. Telex equipment should always have case grounds installed. DC Power Telex equipment in racks should have a common DC power supply, rather than each one on a separate power supply.  A power supply plugged into an improperly grounded outlet will almost always cause AC noise. Network Network topology can cause VoIP audio problems if there are bandwidth restrictions, or if shared services are causing packet queuing, or data collisions. If operating on a shared network, use VPN Tunnels. Many Telex customers have had good results with products such as DCB (Data Communications for Business) tunnel boxes.           © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question How can I troubleshoot IP Console and Gateway Audio Transport Across a Network?   Answer On initial set up of a console system, often the most frequent problem is the failure of Consoles and IP-223s to communicate across the network.  Common causes of this are: Typos in addressing, such as multicast addresses and port numbers not matching on end to end devices. Firewall turned "ON" in console computers Multicast being blocked across the network due to router settings, etc Use of the Telex “VU Meter” program (download at http://www.telex.com/us/dispatch/file?i=97544&lg=eng) is an excellent and quick way to determine if data is present on the correct port numbers. Open VU Meter with the appropriate multicast address and port number entered in the blanks. Turn the program on. Send a test call on the TX or RX port numbers and see if VU Meter indicates digital audio activity. You may open multiple instances of VU Meter to simultaneously monitor TX and RX port numbers.  Verification that audio data is being sent out on the correct address, but not arriving at the far end of the network may indicate a problem with network configurations, that is, blocking of multicast traffic. Please note that some newer switches are intelligent enough to contain routing functions, which can be unintentionally enabled in some situations.           © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question How do I activate paging sidetone on the VoIP consoles?   Answer If your VoIP console does not generate sidetone with paging or DTMF, check the DTMF sidetone box in the System 1 Setup page of the web browser.            © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question Multicast doesn't seem to be working on my Telex Dispatch system - what are good next steps to troubleshoot for possible network issues?   Answer The problem can come from many reasons, the two most common are the following: 1. The TTL value entered isn't high enough for the number of router hops and Multicast packets are being pruned by the network before reaching the end point unit.  Try increasing the TTL value. 2. By default WAN or Layer 3 networks will not pass multicast traffic, a good next step to test overall port number addressing.  Configure a number of devices for "point to point" Unicast instead of "point to multi-point" Multicast.   Enter the IP address of the far end IP unit into the Multicast address field of the local IP unit.  Do this for both ends. If console and radio traffic now work using Unicast the network is not configured correctly for Multicast traffic an you need to work with the IT manager for resolution.          . © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question The time change occured and now is off one hour on my C-6200, IP-1616, and IP-2002.  How can I change the time on these consoles?   Answer To change the time on the IP-1616 follow these steps: To set the console clock in quick mode, do the following: 1. On the IP-1616 keypad, press and hold the MUTE button, F16 button, and the XP button in that order. 2. Follow steps 3-17 in “CLK Menu” . To change the time on the IP-2002 follow these steps: To set the console clock in quick mode, do the following: 1. Press and hold Line 1’s MUTE button, Softkey 1,  and the * button, in that order. 2. Follow steps 3-17 in “CLK Menu” . To change the time on the C-6200 follow these steps: To set the console clock in quick mode, do the following: 1. On the C-6200 keypad, press and hold the MUTE button, the F16 button, and the C1 button, in that order. 2. Follow steps 3-17 in “CLK Menu” . The Programming Mode menu appears. 3. Press the CLK softkey. The clock menu appears. Options Edit, A/P, 12/24, and back appear. 4. Press the 12/24 softkey until 12hr displays. The 12-hour clock mode is selected. In the upper-right corner of the display, 12hr appears OR    Press the 12/24 softkey until 24hr displays. The 24-hour clock mode is selected. In the upper-right corner of the display, 24hr appears. 5. Press the A/P softkey to set the 12-hour clock time to AM or PM, if 12-hours clock mode is selected. The time appears with AM or PM on the right. 6. Press the Edit softkey. The clock settings appear on the display. 7. Press the Hours softkey. The Hours menu appears and displays the current setting. 8. Press the 12 softkey. The clock resets to 12 hours or 1200 hours depending on selected mode 9. Press the dwn or up softkey until correct hours displays. The hour setting changes. 10. Press the back softkey after setting the hours. The edit clock menu appears. 11. Press the Mins softkey. The minutes menu appears and displays the current settings. 12. Press the 0 softkey. The clock reset to 0 minutes. 13. Press the dwn or up softkey until correct minutes displays. The minutes setting changes. 14. Press the back softkey after setting the hours and minutes. The hour and minutes setting menu appears. 15. Press the back softkey. The edit clock menu appears. 16. Press the back softkey. The Programming Menu appears. 17. Press the EXIT softkey. The console displays, Resetting console. Changes are saved.         © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question What does Dispatch products due in the cases of missed packets (lost due to jitter or errors)?   Answer The products have a jitter buffer that allows for packets to be reordered if delivered out of sequence, if this buffer empties due to lost packets the unit will stop and restart once the "Packet delay before playback" buffer is filled.   The product looks at the source and destination address, when a correct incoming port number is recognized the unit will lock in on that source address an ignore packets coming from another source address until the first source stops sending then the second source has access. There is no protection against multiple packets from the same source address with the same multicast and port numbers as this shouldn't happen.  Add to this the same sequence bit in the packet (echoes) should never be allowed. Packets not received or lost before their play sequence (bit) time in the buffer are lost and next packets in the buffer pulled in.           © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question How do I set up EF Johnson Series 5300 Mobile Radio Alias and User ID Operation?   Answer See attached.           © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question  How do I update Telex Dispatch IP products with Telex System Manager?   Answer Uploading VoIP Hardware Firmware Once Telex System Manager (TSM) is installed and your new .tfb file is downloaded, you are ready to upload the VoIP hardware’s firmware. To upload the VoIP hardware’s firmware, do the following: 1. Click the TSM shortcut on your desktop. OR From your taskbar, click Start|Programs|Telex Communications|Telex System Manager. The Telex System Manager window opens. 2. Click Tools|Firmware Update The Firmware Update Tool opens. 3. To locate the .tfb file for upload, click the folder icon . The Open window appears. 4. Select the.tfb file you want to upload. The file is highlighted. 5. Click Open. The selected file appears in the File field. NOTE: If the device does not appear in the list, enter the VoIP hardware’s IP Address in the Manual Entry field and click the Add button. The IP Address appears in the left navigation pane. 6. In the left navigation pane, select the device’s IP Address. The Write Firmware button is active. 7. Click the Write Firmware button. Firmware update messages are shown in the Status column which provides feedback on the firmware update progress. Once the progress reaches 100%, the firmware is updated. NOTE: If an error occurs, the Progress column is reset and an error message appears in the Status column. NOTE: Once the firmware is uploaded, the device resets. 8. Click Close.   The Firmware Update Complete window closes. 9. Click Close. The Firmware Update Tool window closes.         © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question How do I connect Telex VoIP Dispatch Systems to Analog Recorder Solutions?   Answer See attachment  

Question Does Telex Dispatch support UDP Unicast addresses instead of UDP Multicast addresses?   Answer Yes. Place opposite ends static ip address into the multicast address field, see example below: Note: You will now be operating in point to point mode (ie...ip-223 to single console), point to multi point (ie...ip-223 to multiple consoles) will not work.  

Question What are the part numbers for replacement power supplies?   Answer The listed inline power supplies will require an additional power cord, order one for each unit if needed. Part Number F.01U.117.972, Power Cord US 115V For the following products order this power supply: Part Number F.01U.110.313, Power Supply, 12 VDC, 1.25 A 90-260vac C-2000 Series C-2002 Series C-1610 Series C-1616 Series IP-2002 HB-3 and 3+ Series ADHB-4 Note: The above 2 part numbers are listed on the Dispatch Price List and available using the normal Customer Order Desk at: Phone: 877-863-4168 Email: buv.orders@us.bosch.com For the following products order this replacement power supply from After Sales Service: Part Number F.01U.153.075, Power Supply, 12 VDC, 72W Desktop 90-260vac C-6200 Series IP-1616 Please contact our Parts and Repair department for pricing and availability at: Bosch Security Systems After Sales Services (ST-ASA/SRA1-AM) 8601 Cornhusker Hwy Lincoln, NE 68507 Tel: +1 800 553-5992 Fax: +1 800 366-1329 Web: www.boschsecurity.com Email: repair.lincoln@us.bosch.com           © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question Can I connect a secondary power source to the Dispatch console?   Answer The Dispatch consoles have an Auxiliary Power connector and a primary power supply connector on the rear of the unit. These connectors are internally connected but not designed to supply power to the unit at the same time (either one but not both at the same time). If both sources are required a switch must be implemented on the backup power source requiring a manual switch over from primary to the backup source if the primary power source fails. Power should not be supplied simultaneously to both connectors as hum and noise could be introduced. When primary power is restored, the switch should then be returned to the normal position.                 © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question What Addressing and Port numbers are in use by Dispatch products? What is the Multicast address range for Telex IP Dispatch products?   Answer The products support both Unicast and Multicast addressing. Class A, B and C private addresses are supported Class D Multicast is in an address range starting at 224.0.0.0 and goes to 239.255.255.255 Acceptable Ports range from 1054 to 65535 for each address. Some IP Addresses and Port numbers are currently in use by our products and should be avoided,  TSM - Telex System Manager (used system wide): 233.15.18.22 Ports 7635/7636 Network Recorder and Remote Database Reviewer: Static IP address of Network Recorder, port # 12343 - by default - can be changed. My SQL Server port 3306 IP-223: 4235 - Telex devices connect to this port for  generating tones.  Specifically 5/6 tones and some DTMF tones. 4245 - Telex devices connect to this port for phone mode control, Remote Cross Patching, Scan List updates, and Cloning.           © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question How do I change Zones/Channels on a Kenwood radio with Telex Dispatch products?   Answer The Telex Consoles do not have the ability to directly change zones on a radio, this would be done in either the IP-223 or IP-224. The frequency you select on the console would correspond to the F-Tone on the Per Line Setup page in the IP-223/4. In that same section look at the far right hand side and you will see two columns labeled System and Channel. The System column is the zone that you want the radio to change to when the console selects that channel. In turn the IP-223/4 will also change to that channel in that zone. So in practice let’s say the IP-223/4 has F1, F2, F3 set to zones 1,2,and 3 for the channels 1,2,3 respectfully: Now if this is submitted and saved to eeprom, the IP-223/4 will now change channels to zone 1 channel 1 when the IP-2002 selects F1. If the console selects F2 then the radio will change to zone 2 channel 2. If the console selects F3 then the radio will change to zone 3 channel 3.         © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.  

Question What are possible causes of poor audio in Telex Radio Dispatch Systems?   Answer Telex Radio Dispatch systems have operating requirements which need to be established and verified, in order to insure good quality audio across a system.  Here are some fundamental parameters that installers and technicians need to be aware of, which, if not properly ascertained, may be causes of poor quality audio in the system: Levels are a foundational issue with Telex radio systems. Improper digital audio levels are one of the most common defects that impair system audio quality. This means that the digital transmit audio and digital receive audio must be “proportional.” “Proportional” means that the sampling and conversion of the analog signals must be in the proper binary value “window.”  Generally this would be indicated by a VU Meter bar graph deflection of about 2/3 to ¾ scale at voice peaks. Improper digital audio levels are the result of improper analog levels going into the CODEC. Digital audio that is too low or too high will degrade re-constitution of digital back to analog audio at the end points. The Telex “VU Meter” program allows measurement of the digital audio levels at different points in the network, (see the Knowledge Base articles on Optimal Analog to Digital Conversion in the IP-223, and Telex Dispatch VU Meter Program.) VU Meter gives a graphic and numeric indication of digital sampling with multicast traffic. Microphones The quality of the transmit audio of the entire system depends heavily upon the quality of the signal originating from the microphone.  The microphone is where the “tires touch the road” in the system, and a poor quality microphone cannot be compensated for by any external means. The highest quality radio system will not sound good if the microphone is of poor quality, improperly adjusted, or improperly used.  The microphone is the last component in the system that should be a low price based selection. Poor microphone audio is often caused by improper use of the microphone, or the wrong type of microphone for the application.  Without a doubt, the headset mic is the best choice for any dispatching application, whether pubic safety, or not. The headset mic is always at a consistent distance from the dispatcher’s mouth, and the close proximity minimizes background noise, and promotes a very consistent voice transmit level.  Keep in mind that although some dispatchers do not like to wear headsets, no other type of mic will produce as consistently good sound quality as well as a headset mic. Desktop and gooseneck microphones are designed to be used at a specific distance from the dispatcher’s mouth, and when that distance is exceeded, audio quality degrades, and more background noise is picked up along with the voice.It is common to find a desk mic used at a much greater distance than intended, and this creates less than optimal voice audio quality. Obviously, a microphone gain setting that is too high can also create a similar problem, with excessive pickup of background noise, and excessive voice amplitude. Too low of gain setting, and the voice amplitude will be too soft and accompanied by noise. Again console mic audio in a RoIP system is adjusted by watching the VU Meter deflection at the console, using a loud talk test. Once the best deflection is attained, further gain adjustments at the radio end ensure proper transmitter modulation, and optimal audio quality. Voice peaks are a recommended reference point for calibration. Tones may not be as accurate for modulation calibration, as digital conversion does not reproduce single frequency sine waves as well as voice modulation. Control Stations Control station radios need to be run across the test bench to insure that they meet all performance specifications. Once installed on site, transmit modulation levels need to be re-verified, once the overall system alignment is completed. Mic Jack Audio Some radios use the mic jack as the TX audio interface. Be aware that such low level signals are susceptible to local sources of electrical noise, and shielded cables should always be used. RF Most installations use multiple control stations in a single rack or shelf arrangement. RF leakage can infiltrate wiring of all kinds, so it is important to minimize any radiation that may occur in the vicinity of the system equipment. Keep lead lengths as short as possible. Using outside antennas located as far away from equipment as is possible is important, especially when using high power base stations. Use double shielded RF antenna cables to insure that minimal RF radiation is occurring locally at the rack. iDen phones and similar can generate all kinds of pulse mode interference, especially if the antenna is not cabled to an external location. A loose antenna cable connector can create a lot of RF radiation near the radio. When in doubt, shield everything and make sure connections are tight. Amplified speaker cables and microphone cables are very susceptible to pulse mode RF interference. High Noise Floor Areas For example, if you are planning a power company dispatch center installation, and you have 345,000 volt transmission power lines next to the building, you may have a noise problem. Similarly, areas near commercial radio and television broadcasting towers may also have a very high RF noise floor that must be considered. Control station interfaces should be located out of the area of these types of noise sources if possible. If installation away from these noise sources is not possible, extra care should be used to shield all wiring.  Faraday shielding is the best method of eliminating electrical noise induced from radiating sources. Noise Present via Supplied AC Power Variations and transients in AC power can contribute to system noise. Using UPS power supplies or power conditioners can help eliminate AC power noise present on the supply lines. Verifying that the equipment room supply outlets are properly wired and correctly grounded is good practice. Improper grounds can be a significant factor in noise. Telex equipment should always have case grounds installed. DC Power Telex equipment in racks should have a common DC power supply, rather than each one on a separate power supply. A power supply plugged into an improperly grounded outlet will almost always cause AC noise. Network Network topology can cause VoIP audio problems if there are bandwidth restrictions, or if shared services are causing packet queuing, or data collisions. If operating on a shared network, use VPN Tunnels. Many Telex customers have had good results with products such as DCB (Data Communications for Business) tunnel boxes.           © Copyright Bosch Security Systems All rights reserved. Text, images, graphics, sound, animations and videos as well as the arrangement of the same in Bosch offline knowledgebase (help file) are protected by copyright and other intellectual property rights. The content of these offline knowledgebase may not be copied, disseminated, altered or made accessible to third parties for commercial purposes. Some Bosch web sites may also contain text, images, graphics, sound, animations and videos subject to third party copyrights. Warranty Note This information is provided by Bosch Security Systems ''AS IS'' and without warranty of any kind, expressed or implied, including (but not limited to) any implied warranties of merchantability, fitness for any particular purpose or non-infringement. While the information provided in believed to be accurate, it may include errors or inaccuracies. Bosch Security Systems will not be liable for any damages of any kind arising from use of this tool, including, but not limited to, direct, indirect, incidental, punitive and consequential damages.