[CRTech] Christian Radio Tech [MSG 82832]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
RE: TIE LINE AND COMREX COMPATIBILITY
To: 'CRTech' <crtech@crtech.org>
Subject: RE: TIE LINE AND COMREX COMPATIBILITY
From: nathaniel.steele@icloud.com
Date: Tue, 01 May 2018 10:08:22 -0500
Content-language: en-us
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1525187307; bh=qE2iFCNLKebOr+/8cmPT2AeEP03sFFAI/3k1J0+FdEQ=; h=From:To:Subject:Date:Message-id:MIME-version:Content-type; b=0GYs1+H2ueglGzQ4Hf0SAfGs0DIITmXk211OWTPRXQMgI9pKD4SHuYHAdQ3ITXWok 2kgmCSChWYqqrqRUS464NEs+6BXPmEcpndjsZB25EBlmujgCK9qU3jHls1/eLSrKVN KkM4HprYtWbL9NltxEwUU4LBwhBHkOIe3oogwDNzYjEGKb91Iu/5JL1IShC367cA4D 04FcZPp51Jv56VrpDQINXVpNts/QcU1kTQ52hHT35PxdC7iHv8+ypkC6+D6ENYu5o9 eYDz3dP6EO0TRMlWfBba+i+qIlngub4IiA4WJXXQ13vPxoZhJRqJbPYTYBlfZ7MBhk AyZ2VPmPZRdaw==
In-reply-to: <CALf5f27tWC53G0TMPd0bLQqrwHXH4aG69r0QRmMeW7PpLQc7Jw@mail.gmail.com>
References: <CALf5f27Cek-=g3R=FHE+T01XO4EcK2JkWV_WmrtkLGyCB+bkmg@mail.gmail.com> <001e01d3e0b6$bca7a750$35f6f5f0$@icloud.com> <CALf5f26KrJXR9tCtAbgZky4M9aBMb1AS5J6hbK-5AZ723vTJGQ@mail.gmail.com> <DM2PR0701MB1247D385AA9A9F31869E1D0DA9810@DM2PR0701MB1247.namprd07.prod.outlook.com> <CALf5f27tWC53G0TMPd0bLQqrwHXH4aG69r0QRmMeW7PpLQc7Jw@mail.gmail.com>
Thread-index: AQJLk9/+o1jZFUbCOf1/7FmGqNPj5wChImHGAmY299gB0XW00QGUL1MlovgsRtA=

Yes much like  AoIP standards, you can make wheatnet and axia talk via AES65, but you loose gpio….

Going this route with codecs you lose some proprietary features. Always best to pick one and stick to it, But they CAN be made to talk to each other.

 

From: Dan Hatfield <dan@refugeradio.com>
Sent: Tuesday, May 01, 2018 8:19 AM
To: CRTech <crtech@crtech.org>
Subject: Re: [CRTech] TIE LINE AND COMREX COMPATIBILITY

 

Thanks Brian

 That is what I needed to know.

Dan

 

On Mon, Apr 30, 2018 at 9:07 PM, Gullikson, Brian F <bfgullikson@unwsp.edu> wrote:

My main caution on anything related to interoperability between codecs and different brands of equipment is this:  While you may be able to "get them to work together", you may only have one single, bare-minimum WAY that they will work together. 

 

For example, to connect into our Comrex Access from a Telos Z/IP One, the only method we've found successful is G.722 via SIP.  It works, and sounds better than a phone line, but you don't get all the "auto-breathing" bitrate adjustment and forward error correction, etc. that you would get using a native Comrex-to-Comrex or Z/IP One-to-Z/IP One connection.

 

TL/DR:  It's best to match brands of Codecs for the most features and best results.

 

Thanks,

Brian

 

 

Brian Gullikson, CBRE               98.5 KTIS-FM | Faith 900 KTIS

                                            Life 97.3 KDNW | Faith 90.5 KDNI

Chief Engineer                                     3003 Snelling Ave. North

KTIS, KDNW, KDNI                                       St. Paul, MN  55113

bfgullikson@unwsp.edu                        Phone:  (651) 631-5094

 

From: Dan Hatfield <dan@refugeradio.com>
Sent: Monday, April 30, 2018 3:14 PM
To: CRTech <crtech@crtech.org>
Subject: Re: [CRTech] TIE LINE AND COMREX COMPATIBILITY

 

that is very helpful, thank you for the info!

Dan

 

On Mon, Apr 30, 2018 at 2:09 PM, <nathaniel.steele@icloud.com> wrote:

I asked a similar question, the answer is Yes I believe for comrex. Below the response, note that I sked about “Calling in” to  a telos VX.

 

“Short answer: If the receiving codec is set to answer a SIP call, we have codec interoperability utilizing the SIP Standard.  I'll detail further below, but I do not have any information on the specific codec you've specified.

 

You can make IP connections to other manufacturer’s codecs if the SIP protocol is used on both ends and the codec you are connecting to is EBU N/ACIP Tech 3326 compliant. The following parameters will need to be set on both codecs. Try the following setting, once connected; you can try other settings as desired.

Profile     mono

Bit rate   64k

Algorithm   G.722

Session port  5060 TCP

Audio port    5004 UDP

Below are links to information about compatibility to other manufacturer’s codecs using SIP and ISDN for the G5 family of codecs including the Merlin and Genie codecs as well as the G3 family of codecs.

 

G5 Codecs: IP (SIP) and ISDN Codec Compatibility (1.31 MB pdf)  http://www.tieline.com/files/files/1285_Tieline_G5_IP_and_ISDN_compatibility_v.1.1_20170104.pdf

 

G3 Codec Interoperability with other codec manufacturers (5.46 MB pdf) http://www.tieline.com/files/files/949_Tieline_G3_Compatibility_v1.0.pdf

 

-Bryan”

 

 

From: Dan Hatfield <dan@refugeradio.com>
Sent: Monday, April 30, 2018 1:38 PM
To: CRTech <crtech@crtech.org>
Subject: [CRTech] TIE LINE AND COMREX COMPATIBILITY

 

We have 2 Comrex / Brics at our Studio and use a Comrex Access for an occasional remote. ( the Access is the older unit with the small screen and stylus).

we have been considering purchasing a second Comrex Access and I saw the new Access NX ( newest Version) at NAB. I like this unit much better but I also looked at the TIE LINE VIA. WOW!
 

I really Like the Tie Line features much better for what we have planned however I cannot afford to purchase the Tie line Merlin that goes with it.

Does anyone know is there any possible way a Tie Line can Communicate with a ( Comrex)  Bric. I realize these are competing companies and no one would support it, But I need to decide which of these units I'm going to purchase soon.

 

Dan Hatfield
Refuge Radio

WJRF Duluth, MN
KRFG Nashwauk/Hibbing

KRGM Marshall/ Sioux falls

 

 

References: TIE LINE AND COMREX COMPATIBILITY
(Dan Hatfield <dan@refugeradio.com>, 30 Apr 2018 18:37:47 -0000)
RE: TIE LINE AND COMREX COMPATIBILITY
(nathaniel.steele@icloud.com, 30 Apr 2018 19:09:28 -0000)
Re: TIE LINE AND COMREX COMPATIBILITY
(Dan Hatfield <dan@refugeradio.com>, 30 Apr 2018 20:14:04 -0000)
RE: TIE LINE AND COMREX COMPATIBILITY
("Gullikson, Brian F" <bfgullikson@unwsp.edu>, 1 May 2018 02:07:45 -0000)
Re: TIE LINE AND COMREX COMPATIBILITY
(Dan Hatfield <dan@refugeradio.com>, 1 May 2018 13:19:20 -0000)
Prev by date: Re: SBE Regulatory Alert - Apr 23, 2018
(Steve Tuzeneu, 1 May 2018 14:40:07 -0000)
Next by date: Re: TFT 5290 STL Transmitter
(John Stortz, 1 May 2018 15:11:59 -0000)
Prev by thread: Re: TIE LINE AND COMREX COMPATIBILITY
(Dan Hatfield, 1 May 2018 13:19:20 -0000)
Next by thread: Re: TIE LINE AND COMREX COMPATIBILITY
(Pat Wahl, 30 Apr 2018 19:12:19 -0000)
CRTech.org