Overview
tx edge is a high-performance IP video gateway designed to provide transport protection and monitoring for critical broadcast services. tx edge supports UDP, RTP, SRT, RIST, ZIXI (receiver 1.12), RTMP, VTTP and HLS inputs and UDP, RTP, SRT, ZIXI (feeder 1.12), RIST, HLS and VTTP outputs. tx edge supports 2022-7 input protection from RTP, SRT and ZIXI inputs, dual 2022-7 output creation with independent path delay and threshold based input failover to both active and passive sources. Each service passing through an tx edge is subject to a full ETSI TR 101 290 analysis and has a thumbnail extracted. tx edge can be deployed on bare metal, virtualised or as containers. tx edge Instances are monitored and controlled through by a MWCORE server. tx edge makes spawning hundreds of single-stream light-weight edgelets on demand seamlessly effortless.
Highlights
- Reliable fixed latency ARQ delivery over networks with SRT, RIST* and ZIXI* (1.12)
- SMPTE 2022-7 seamless input with per path statistics RTP header passthrough allowing 2022-7 integrity to be maintained for downstream seamless protection
- BISS-2 scrambling and descrambling with seamless odd/even key transition Threshold based input redundancy with support passive or active backup sources XOR and Output Mute Thresholds ETSI TR 101 290 Priority 1, 2 & 3
Details
Features and programs
Financing for AWS Marketplace purchases
Pricing
Additional AWS infrastructure costs
Type | Cost |
---|---|
EBS General Purpose SSD (gp2) volumes | $0.10/per GB/month of provisioned storage |
Vendor refund policy
Bring your own licenses customers should contact Techex directly with any licensing concerns.
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Version 1.22.1 (24/05/2023)
Fix offline installer
Fix thumbnail process sometimes being orphaned and left running incorrectly
Fix source processes not being killed when stream deleted
Clear "Stream is not valid RTP" error state on SRT sources after 5 seconds of valid RTP
Version 1.22.0 (23/01/2023)
- Option to remove or add RTP headers on SRT sources
- Option to PCAP across all interfaces
- Option to choose frame rate on generated test sources
Update libRIST version to 0.2.7
Increase visibility of Triggered Captures issues
Improve license expiry message when using cloud licensing
Always show backplane option to highlight when next-gen is unsupported
Fix PTS Interval ETR290 monitoring
Fix UDP sources adding RTP headers not choosing random SSRC values by default
Fix possible rare race condition leading to source states not saving
Fix "ip: command not found" in 2022-7 sources
Additional details
Usage instructions
Techex MWEdge is deployed as a part of a larger broadcast workflow, often for playout, distribution or production. The following is a list of prerequisites required for deploying MWEdge in AWS. 1. An AWS Account** 2. Understanding of how to deploy in compute and network infrastructure in AWS 3. A license from Techex (support@techex.co.uk ) 4. Techex MWCore control platform (with MWEdge cloud licensing) 5. MWEdge AMI from Techex support 6. Approximately 15 minutes ** Note, it is our strong recommendation that users do not use the AWS root credentials and instead use access-restricted IAM accounts.
Deployment instructions:
- Navigate to the desired deployment region, e.g. eu-west-1
2. Create network infrastructure: VPC, subnets & NAT gateway if desired 3. Create suitable Security Groups with access as below: a. Allow outbound access to the Techex MWCore control platform – TCP/443 b. Allow inbound and outbound access only for the UDP streams you wish to use: i. E.g: inbound UDP/5000 + outbound UDP/6000 ii. For protocols such as SRT, you may need to define bidirectional access or observe stateful connections. 4. Deploy EC2 using the Marketplace AMI Recommended instance families: 1. C5 2. C5a 3. C6i 4. C6a 5. C6g 6. C7g Once you have successfully deployed an AMI, you will need to connect to the instance over SSH / console to configure some basic parameters: 1. Connect to the instance with user “centos” and the ssh keypair selected at deployment 2. sudo su # To become root user, if needed 3. cd /var/node # Navigate to installation directory 4. nano config.json # Edit MWEdge configuration file 5. Edit the “name” and “mwcore” lines as below: 1. “name”: “Name of the MWEdge”, 2. “mwcore”: “Address of the MWCore”, # Replace the text with correct information Now that you have connected your MWEdge to your MWCore server, you can log in and see it in the interface.
Support
Vendor support
Techex offers three pre-defined support levels as well as basic product support provided free of charge with all new product purchases. We can also offer bespoke support with a mix of features. The support levels have been designed to be straightforward to understand and compare, so that customers can easily select the level most suitable for their specific needs.
Standard: 08:30 : 17:30 Monday : Friday excluding UK public holidays Premium: 08:30 : 17:30 Every day including public holidays Premium24x7: 24x7 on-call support every day of the year.
UK local time
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.