Critical Communications: Dispatch

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 and 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   What Kenwood radio features can the IP-223 control?   Answer   The IP-223 supports basic channel change, TX/RX audio and PTT  for most radios.  We also offer serial control of some Kenwood radios (TK-x80, -x90, -x150, -x180 and TK-5x10) that enable additional features listed below. ANI Channel Change (up to 99 frequencies) Scan ON/OFF Emergency Decode ***Scan Mode channel update*** Only on x150/x180 and TK-5x10 **Add/Delete channels from scan list** Only on x150/x180 The following optional Telex cables can help speed installation: • P/N F.01U.117.822      Description IP223CAB150/180 - IP223-Kenwood TK-150/180 and TK-5x70 cable. • P/N F.01U.117.823    Description IP223CAB90 - IP223-Kenwood TK-90 cable. If attaching two (2) serially controlled devices to a single IP-223, a serial port splitter cable is required: • P/N F.01U.117.818    Description IP223DB9Splitter - Serial Port splitter cable DB-9.         © 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 EFJohnson radios can the IP-223 serially control?   Answer   The IP-223 can control the following EFJohnson radios: 5300R and 5300ES. Serial control of these radios is accomplished when using the IP-25300 interface in addition to the IP-223. The IP-25300 will interface with the radio and connect to the IP-223 as a RS-485 serial converter. The radio features controlled are listed below: Monitor Clear/Secure operation Radio PTT ID for incoming calls are decoded and displayed on the console. EMERGENCY PTT ID for incoming calls are decoded and displayed on the console.   Please note that with the EFJ5300SLES radio requires a special pig tail connector for proper operation. You'll need to purchase from EFJohnson: P/N 5975357-746-01 - Description- Accessory Pigtail Connector.         © 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   I'm having issues trying to transport MSK (MDC or FleetSync) data across IP links (IP-223 to IP-223), and only works half the time reproducing the MSK at the far end - what can I do to fix this?   Answer   There is no good answer to your question - when you look at Audio sampling rates, VOCODER algorisms/compression rates, audio packetizing for network transport, physical network transport and the regeneration of audio, these all play a part in the units ability to recreate inserted audio at the far end of IP transport.  The operation you require is not supported, we only decode MDC in the IP-223 and display it on consoles as a special ANI packet because of these known issues.             © 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 do the modes of operation support?   Answer   The IP-223 is capable of six different modes of operation.  Here are some explanations to help you understand the basics of how each mode works: Console Mode - Console mode is used to adapt an analog, tone controlled console so that it's signaling and voice audio can be transported across an IP network.  At the far end (radio end) of the network, a second IP-223 converts the data back into analog voice and regenerates the analog MSK tones.  The radio end IP-223 (in Tone Mode) can control a tone remote adapter panel, or tone controlled radio.  The radio end IP-223 is also capable of controlling a radio locally.  (See more on Local and Tone modes below)  The Console Mode IP-223 also converts receive packets back into analog audio for the receive side of the console radio traffic. Note: Console mode also supports E&M input logic to generate remote radio keying when control tones are not present.  Tone Mode - A Tone Mode IP-223 normally controls a radio at the remote end of the network.  It receives data from the network that originates from IP console or an analog tone generating device, such as a legacy console connected to an IP-223 in Console mode.  The IP-223 at the radio end of the system converts the digital IP information back into voice and tone signaling, which drives a tone remote adapter, or tone controlled radio.  Receive audio is also sent back to the console in a similar manner. Local Mode -  This mode is normally used at the radio (remote) end of the system and controls the radio with PTT, COR, TX and RX audio, via a direct connection to the radio auxiliary connector.  In some systems, channel control is used via the IP-223 BCD logic or by using serial control methods. Phone Mode - Phone Mode allows the IP-223 to interface to a POTS line via a Telex TDI adapter.  It allows basic telephone line functions to be provided through a C-Soft console. iDEN Mode - iDEN mode allows the IP-223 to interface with a Falcon class POC (Push to Talk over Cellular) mobile phone system.  An NI-223+ is required to interface the radio handset with the IP-223.  The radio can be operated as a cellular phone, or POC phone. TETRA Mode - TETRA Radio Mode Tetra Radio Mode allows interface to the Sepura SRM-2000/3500 mobile radio.  Similar to the iDEN Mode, the TETRA radio can be operated as a POC mobile, or cellular phone.             © 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 you troubleshoot parasitic RF problems in Telex RoIP equipment racks?   Answer   In some installations, stray RF energy can infiltrate audio lines and data lines, causing erratic operation of RoIP devices. Certain modes of radio frequency transmission can be especially prone to causing interference. Pulse type modulation that occurs in cellular TDMA systems, certain types of trunking system modulation, as well as high power transmitters, are common sources of problems. For example, a typical symptom of this phenomenon is PTT dropout. When the transmitter comes up to full power, it’s controlling IP-223 may drop the PTT, as a result of RF getting into the data stream and corrupting it. Eliminating locally radiated RF energy is the first step in determining the cause of the problem. Put a dummy load on the transmitter and retest it. If the problem ceases, chances are you have found the problem. Steps can then be taken to eliminate radiation of the RF from cables, nearby antennas, etc. In this case the antenna was too close to the equipment rack, and once it was mounted further away, the problem disappeared.   Similar procedures can identify other sources of radiating RF energy as the cause of the problem. Antenna cables with poor grounds, bad connectors, cables being too close together, etc, can cause simillar problems.           © 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 better understand IP-223 jumper settings?   Answer   IP-223 jumper settings allow a great deal of flexibility in regards to the range of uses for the device.  Correct jumper settings are critical to every application.  Although many Telex application notes specify the required jumper settings for certain types of radio models, some radios are not covered and the technician must determine which settings are correct for their particular application. Explanations on the purpose of the settings are expanded upon here to assist in determining the best configuration.  Refer to the jumper chart in the IP-223 manual to idenfity specific jumper numbers based on the PCB revision.  2 Wire vs. 4 Wire Four wire mode consists of two pairs of conductors, one for TX, one for RX.  In the 2 wire form, the TX and RX signals are summed onto the same wire pair, which conserves resources but can also create problems in certain circumstances, and is generally more difficult to obtain a stable alignment with.  4 wire mode generally produces better quality audio than 2 wire mode. Balanced vs. Single Ended Locally controlled mobile radios are typically high impedance, single ended input and output lines.  Single ended refers to an unbalanced signal pair, in which one conductor is grounded and the other carries the AC signal above ground potential.  Radio audio impedances are generally considerably higher than 600 ohms, and may be 10K or greater.  Balanced audio refers to two conductors that provide forward and return paths, neither of which is referenced to ground.  Check specifications on your radio to determine which mode of connection is applicable. RX Input Impedance RX impedance may be 8 ohms, 600 ohms, or 10K ohms, depending on the source used.  A connection to a speaker for example would be 8 ohms.  Again, check the radio specifications to confirm the optimal value to be used. TX Output The transmit output level range has two options:  High or Low.  High is the most common value, but low may be required in certain systems requiring lower output levels.  Digital I/O Pull Up Voltage This jumper determines the pull up voltage for BCD (Binary Coded Decimal) channel steering bit lines.  It may be set for +5 volts, or floating (jumper set to hang on center pin).  This setting is determined by the radio requirements.  This jumper is only applicable to radios requiring BCD control. J23 This jumper needs to stay in the "B" position.  (It is intended for a future feature in the IP-223)           © 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 integrate a legacy analog console into a Telex RoIP system?   Answer   Legacy TRC (Tone Remote Control) consoles send analog voice and signaling tones down copper pairs to control remote radios.  In a system conversion from copper to RoIP, the IP-223 is able to convert the console signals into data, which is sent across the network to a far end IP-223 in Tone mode. This IP-223 re-constitutes the data back into analog signals, and sends them to the tone remote adapter/control station transmitter.  (The console end IP-223 must be configured for Console mode to perform this conversion) Receive audio is likewise digitized by the radio end IP-223, and sent across the network back to the Console mode IP-223, which again converts the data back into analog audio that is played back as console receive audio. Configuration of the IP-223s Note: Jumpers MUST be configured correctly for the unit to work.  An incorrect jumper setting can waste hours of unnecessary troubleshooting time.  Consult your application notes and manual to determine the correct jumper settings for your application. We recommend that you double check them. It is also important to be sure that the Console mode IP-223 2175 Hz PTT Notch filter is ON.  This prevents two sets of 2175 tones being sent to the radio end of the system (one from the Console mode IP-223 and one from the Tone mode IP-223), which will create a beat frequency, and thus create impossibly unstable tone decoding. Crossover: When converting a legacy tone console to a Telex RoIP system, it is necessary to connect the console outbound audio (TX pair) to the IP-223 RX pair (dB-25 pins 12 and 24), and the console inbound audio (RX pair) to the IP-223 TX pair (dB-25 pins 13 and 25). Software Settings The Parallel Console checkbox in Per Line settings must be checked when using Console Mode. All Function Tones that will be used need to be enabled. Tone and Frequency durations, frequencies and magnitudes must match the radio end TRC decoder requirements Connection in 2 Wire or 4 Wire? If a choice of 2 Wire or 4 Wire configuration is available, there is no doubt that 4 Wire is the best option.  With separate TX and RX audio paths, the possibility of  random loud RX signals audio causing TX decoder to falsely recognize as a TRC tone burst, is eliminated.  This problem is commonly manifested by erratic momentary mode changes from RX to TX modes while receive traffic is active.  This can even cause the radio to change channels randomly as decoder thinks it is supposed to change channels. 4 Wire also normally provides better audio quality and more stable levels over time, especially when long runs of copper leased lines are used, and the false decoding issue is not a factor in 4 Wire.  Figure 1 - Tone Remote Control (TRC) Burst Level setting Most consoles use standard TRC levels and frequencies based on a LLGT (Low Level Guard Tone, sometimes called Hold Tone) of -20 db.  The voice audio portion of the signal normally occupies a level window of approximately -20 to 0.0 dB. Motorola consoles often use a slightly lower TRC level window…a LLGT of about -30 dB.  The voice window will also be correspondingly lower.  This will require a slightly lower LAM level setting in the IP-223 than the typical -35 dB.  The IP-223 is normally able to work reliably with a Motorola legacy console if aligned carefully. If you are unable to obtain consistent TRC keying, verify that your console is sending standard tone frequencies, durations and levels that match what the radio is expecting. Dead key the console (PTT with no voice) and measure the LLGT with a Transmission Test set or TIMS Test Set on the console TX pair.The LLGT should be stable at approximately -20 dB, or with some Motorola consoles, -25 dB to -30 dB.  Adjust accordingly to present this level to the input of the IP-223. Perform a loud voice test and see that the peaks do not exceed approximately 0.0 dB.  The IP-223 should consistently display “CTX F1” at all voice levels from quiet to maximum peak.If the levels peak at greater than 0.0 dB, the IP-223 “CTX F1” display may drop out.  This can be caused by excessive peak levels at the input of the IP-223 CODEC.  If this happens, slightly reduce the input level.The IP-223 gains may be adjusted via software, or a hardware pot. It is good practice to do a quick check of the digital output level going out onto the network with the Telex “VU Meter” program.  The bar graph deflection should be peaking in the range of about ½ to ¾ of full scale. Transmitter deviation should be checked for correct values with a console voice test.  Receive levels should be in approximately the same level range as transmit, to provide acceptable volume at the console.           © 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 are IP-223s interfaced with Tone Controlled Radios?   Answer   In 2 wire mode the wires are connected to the DB-25 connector at pins 13 and 25. In 4 wire mode the TX pair is connected to DB-25 pins 13 and 25, and the RX pair is connected to pins 12 and 24. The corresponding radio connections will be specified by the manufacturer. Some models have built in tone remote adapter boards, and some may require a tone remote adapter board between the IP-223 and the radio.           © 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 you convert Voting Systems from Analog to IP Based with Telex Equipment?   Answer   Conversion of an analog voting system to IP transport is a common mode of system upgrade being successfully done in many locations.  Careful consideration must be given to several aspects of the change in the system configuration in order to achieve good results. The first consideration is planning the network topology to have minimal bandwidth constrictions and packet delays. Ideally, packets moving across the network carrying audio will need to have the most logically direct path possible from port to port…ideally an isolated flat network. The network should be designed with enough bandwidth so that all lines of the IP-223s should be able to function simultaneously without restrictions. It is necessary to configure network timing parameters so that all receiver audio traffic arrives at the voter with nearly the same propagation time, regardless of which receiver site it originates from…something on the order of plus or minus 10 ms. Some latency is acceptable, as long as it is virtually uniform, from all sites. Obviously the audio level characteristics from each receiver site would also need to be matched as closely as possible. Analog audio levels need to be very consistent from site to site. Example: GE Analog Voter system conversion to IP based audio: A typical GE “valley voted” system uses a 1950 Hz status tone to determine when receive traffic is present, and that the receiver and transmission line are functional. The status tone is continuous when no signal is present. The voter cards also use the status tone for line level compensation to provide consistent audio levels regardless of which line is in use. Status Tone Transmission A continuous status tone cannot be used with the IP-223, as packets from receiver to receiver will become largely out of sync over time. Also the CODECs are designed for voice audio rather than a continuous tone and thus a tone will have distortion. One possible workaround is to generate the 1950 Hz locally, just ahead of the voter, and gate it with received audio from the IP-223. A circuit would have to be installed at the voter that generates the status tone the voter is looking for, and passes voice audio during receive activity. Such devices are available from third party vendors. The second change needed to the voter system would be to re-configure it for “vote and hold”, rather than continuous voting during mobile PTTs. The first receiver voted locks in until the mobile PTT drops. This avoids problems that would occur with continuous voting, which can create echoes from audio streams not being in sync.           © 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 set up iDEN Radio Control on Legacy Tone Systems using IP-223s?   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 configure the IP-223 to operate in Console mode?   Answer   Programming the IP-223 to operate in Console mode: For either 2 or 4 wire set J3, J9, J11, J16 and J21 (Line 1) or J19, J20, J25, J28 and J29 (Line 2) to "B" position. For 2-Wire; set J33 and J34 (Line 1) or J5 and J6 (Line 2) to "A" position, set J14 (Line 1) or J24 (Line 2) to "B" position. For 4-Wire set J33 and J34 (Line 1) or J5 and J6 (Line 2) to "B" position, set J14 (Line 1) or J24 (Line 2) to "A" position. Close unit   Now connect your 2 or 4-Wire control line to the correct IP-223 DB-25 I/O port. For 2-Wire connect the (TX/RX) wires to Pins 13 and 25 For 4-Wire connect the TX (Out to console) wires to Pins 13 and 25, connect the RX (In from console) wires to Pins 12 and 24. Once your jumpers and wire connections are set you will need to place the IP-223 line into Console mode. To do this, follow the steps below: Log into the web page of the IP-223. Click on the Multicast address setup picture at the top of the page. Use the Line Type drop down for line 1 or line 2 and set it to Console mode. Now Click on the Submit button at the bottom of the page. Click on the Per-Line setup picture at the top of the page. Go to individual Lines being configured for Console mode, scroll down to "Options" section. Check "Parallel Tone Console" checkbox. Now Click on the Submit button at the bottom of the page. Now click on the Save To EEPROM and click on Save Parameters. Now that line of the IP-223 is set to Console mode will decode PTT tones. The next steps you need to take is to set levels. To set levels do the following: Using a transmission test set or similar device, measure the audio on the front panel RX test point of the IP-223 to ground. Key up the attached tone console, with no voice (only 2175 tone present) Using a small screw driver, adjust the RX pot on the front of the IP-223 for the line under test.  Set the Low Level guard tone to the level you desire, typical is -20dbm into a loaded circuit (looking for 0 gain) Key up the tone console, measure the voice audio on the RX pins of the IP-223, typical is 0dbm peaks into a loaded circuit. You should see "CTX F1" displayed on the front of the IP-223 when you PTT from the tone console, TX packets are now being sent to the network.           © 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.