Mastering Infor WMS RF Device Integration: Telnet Session Management, Barcode Scanner APIs, and Voice-Directed Workflow Configuration

In warehouses that process high volumes, RF device performance directly affects picking speed and accuracy. Screen refresh delays, failed barcode scans, or unclear voice prompts increase errors and lower output. These issues occur in many Infor WMS setups that use basic configurations.

Infor Warehouse Management System includes native RF device support. Strong results come from correct Telnet session setup, barcode scanner parsing through screen APIs, and voice-directed workflow configuration. These elements turn standard RF hardware into reliable tools for daily operations.

This article provides exact configuration steps for Telnet sessions, barcode templates, and voice picking. It targets Infor WMS administrators, SCE consultants, and warehouse IT teams that manage 100 or more devices. You will find MetaRF.ini parameters, PuTTY profiles, screen field settings, and Task Manager configurations taken from live Infor WMS 2026.x implementations.

We base the content on current Infor documentation and market data from Grand View Research. By the end you will have tested patterns that reduce session drops, raise scan success rates, and support voice picking with consistent response times.

Why RF Device Integration in Infor WMS Matters: Market Data and Operational Impact

The global Warehouse Management System market was valued at USD 3.38 billion in 2025 and is projected to reach USD 15.95 billion by 2033 at a CAGR of 21.9% from 2026 to 2033. RF and voice technologies grow fastest because they address labor costs (60–70% of warehouse expense) and error-related rework (1–3% of shipment value). These figures come from Grand View Research reports on warehouse automation.

Facilities that complete full RF integration with Infor WMS report 25–40% productivity gains and inventory accuracy above 99.5%. Voice-directed picking reduces cycle times by 15–35% and shortens training for new staff by up to 70%. Many Infor WMS sites still use default Telnet settings, basic barcode rules, and separate voice modules. This limits gains and leaves daily operations exposed to delays and mistakes.

SAMA Consulting has configured RF systems for automotive, pharmaceutical, and 3PL clients. These projects cut session latency by 65%, removed manual re-key errors, and reached 99.7% voice accuracy. The improvements came from targeted changes to Telnet keep-alives, barcode templates, and Task Manager areas. Start here for an overview of the full system: Ultimate Guide to Infor WMS.

Infor WMS RF Architecture: Meta RF, Web RF, and Extension Options

Infor WMS offers two RF client types that connect devices to the core system.

Meta RF uses Telnet or SSH. It runs in character mode and works best with rugged handhelds from Zebra, Honeywell, or similar vendors. The connection uses port 23 for Telnet or port 22 for SSH and routes through the Meta RF server before reaching the Infor WMS application server. This setup gives sub-100ms response times and works offline if the network drops briefly.

Web RF uses an HTML5 browser interface. It suits modern tablets and newer devices that run full browsers. Most high-volume warehouses stay with Meta RF because of its low latency and simple hardware requirements.

The data path is always the same: RF device sends input through the Telnet or web client to the Meta RF server, which forwards it to Infor WMS. Screen files named RF_L1_xx.cfg define every field, label, and navigation step. Task Manager Areas control who can perform which tasks and whether voice is allowed. Enterprise setups add custom Telnet tuning, barcode parsing rules, and voice commands on top of these base files to handle 500 or more devices across multiple sites.

Telnet Session Management: Configuration Steps for Stable Connections

Telnet or SSH sessions form the connection between the RF handheld and the Meta RF server. When a session drops, the picker waits 30 to 90 seconds for reconnect. This downtime adds up quickly in a shift with 200 pickers.

Login Structure

Infor WMS requires two separate logins for every session.

• The device or Telnet login uses a generic account or a device-specific one. This login authenticates only to the Meta RF server and grants basic OS permissions.
• The Infor WMS application login maps to a real user ID inside the WMS database. It records every transaction for traceability, task permissions, and audit reports.

The recommended practice sets a generic device login with an auto-login script on the handheld. After the splash screen loads from RF_L1_xx.cfg, the system prompts for the operator’s individual WMS username and password. This keeps every pick, put, or count traceable to one person without forcing separate device accounts for each worker.

PuTTY Configuration for Testing and Management

Use these exact PuTTY settings when testing sessions from a Windows management station. They match the Infor WMS RF Administrator Guide for version 2026.x.

• Session tab: Host Name equals the Meta RF server IP or fully qualified domain name. Port equals 23 for Telnet or 22 for SSH.
• Terminal tab: Backspace key set to Ctrl-H for Windows clients or Ctrl-? for Linux. Function keys set to Xterm R6.
• Window tab: Bell action set to Beep using the PC speaker so operators hear errors immediately. Bell overload set to disable temporarily after a defined number of bells in a set number of seconds.
• Appearance tab: Font matches the device language. Use FangSong for Chinese GB2312 characters.
• Translation tab: Remote character set set to UTF-8. Treat CJK ambiguous characters as wide.
• Connection → SSH → Environment variables (for Linux Meta RF servers only): Add HH_locale with the correct language code and HH_device set to landscape=8×40 or portrait=16×20 depending on the handheld screen.

Environment variables load in this order: first the user startup file (.profile or .bashrc), then PuTTY variables, and finally metarf.ini. This order prevents conflicts when you tune settings across environments.

MetaRF.ini Parameters

The file metarf.ini sits on the Meta RF server and controls global behavior. Here is a production example with key lines:

text

HH_SERVERLIST=primaryserver,backupserver1,backupserver2

HH_PORT1=10023

HH_PORT2=6874

HH_PORT3=6875

TERM=vt100

HH_KEEPALIVE=60

Edit these lines as follows:

• HH_SERVERLIST lists backup servers separated by commas for automatic failover.
• HH_PORT1, HH_PORT2, HH_PORT3 define the cycling ports used for socket connections. The defaults work in most cases but change them if your firewall blocks the standard numbers.
• TERM must equal vt100 or xterm to match screen rendering on the handheld.
• Add keep-alive packets with ServerAliveInterval in the SSH config file. Set it to 60 seconds to stop idle drops on stable networks.

Further recommendations include monitoring session logs with the Pragma tool on the server. Aim for a disconnect rate below 0.5%. In high-interference RF areas, combine this with proper antenna placement and channel planning. For data flows that link RF events to other systems, see the Infor ION integration guide.

Barcode Scanner APIs and Parsing in Infor WMS

Infor WMS handles barcode input directly inside screen fields. Most common symbologies parse automatically when templates are defined correctly. This removes manual entry steps and cuts transaction time.

GS1-128 (UCC/EAN-128) Parsing

The system recognizes labels that begin with [A1, [B1, or [C1. It then extracts Application Identifiers (AIs) and fills multiple RF fields at once. All templates are stored in Barcode Configuration under the Owner Control tab.

Follow these setup steps:

• Create a new barcode template and list the AIs you expect. Common examples are AI 01 for GTIN, AI 10 for Batch or Lot number, and AI 17 for Expiration Date.
• Assign the completed template to the specific warehouse owner.
• On the RF screen definition (inside RF_L1_xx.cfg), enable the FirstFieldPriority flag. This tells the system which field receives data first when a scan arrives.

When a picker scans one GS1-128 label that contains GTIN plus Lot plus Quantity, the system populates the Item field, Lot Number field, and Quantity field automatically. The cursor then advances to the next input field. This single action replaces 4 to 6 separate keystrokes and reduces errors caused by typing.

Extended Scanner Setup for Custom Devices

Honeywell SDK and Zebra DataWedge devices need extra steps:

• Enable keyboard wedge mode or direct socket input inside the RF client software on the handheld.
• Set the Barcode UOM for Picking option at the item master level or at the zone level. Choose EA for each, Case, or Pallet to enforce the correct unit during validation.
• For symbologies or data outside standard AIs, use the five user-defined fields (UDF1 through UDF5) inside the screen configuration. Write simple parsing logic in the screen file to split the scanned string.

Apply Task Manager Area security rules so only supervisors can override a failed parse. This combination delivers 99.8% first-pass scan accuracy. Basic RF setups without templates reach only 92% accuracy on average. Test every new template with actual GS1 labels before rolling it to the floor.

Voice-Directed Workflow Configuration

Voice picking changes the process from scan-and-confirm to spoken commands. It fits high-volume piece picking and areas where gloves or safety equipment make physical scanning difficult.

Area and Task Manager Setup

Open the Task Manager Area configuration and make these changes:

• Set Allow Voice Picking to Yes.
• Define Allow User to Skip Locations based on your site’s tolerance for exceptions.
• Set the pick method for each zone. Choose voice-directed for inner packs, cases, pallets, or eaches as needed.

Next, activate the Labor Monitor module. This records talk time, error counts, and productivity per operator. Configure supervisor dashboards to show real-time metrics for the shift.

Task Manager then builds voice-directed tasks from existing waves or orders. Each task pulls data from the order line and converts it into spoken prompts. The prompt text includes item description, location, quantity, and catchweight details when the item requires it. The operator replies using short commands such as “Confirm”, “Short”, “Skip”, or “Exception”.

Technical Details for Voice

Set these properties inside each Task Manager Area:

• Prompt language matches the operator’s primary language.
• Speech recognition confidence threshold (start at 85% and adjust after testing).
• Barge-in support so experienced pickers can speak before the prompt finishes.

Voice commands trigger the same backend validation rules as manual RF entry. This keeps data consistent across RF and voice users. For catchweight items, the voice workflow prompts the operator to speak or enter the actual weight after the pick.

Live deployments show 30–50% faster picks compared with RF-only methods. New staff complete voice training in under 2 hours. Add Infor WMS 3D slotting visualization to the same areas for complete directed execution from receipt to shipment.

Integration, Testing, and Optimization Steps

Follow these steps to keep the RF and voice layers reliable:

• High availability: Deploy two or more Meta RF servers. Use the HH_SERVERLIST parameter and set up load-balanced Telnet listeners.
• Security: Force per-user WMS logins for every session. Use SSH key authentication instead of passwords where possible. Restrict environment variables to read-only access.
• Monitoring: Track session duration, barcode parse failures, and voice command success rates inside Infor OS or Birst analytics. Set alerts when disconnects exceed 0.5% or parse failures exceed 1%.
• Extensions: Send real-time RF and voice events to the ERP or external systems through Infor ION.
• Testing: Run load tests with 200 concurrent devices. Validate every barcode template using official GS1 test labels. Record sample voice sessions in the actual warehouse environment and tune recognition thresholds.

Measured Results from Deployments

One 3PL client reduced picking errors by 87% after full voice configuration and lowered overtime hours by 22%. A pharmaceutical manufacturer reached 99.97% inventory accuracy after optimizing Telnet keep-alives and barcode templates. The same site removed $420K in annual inventory discrepancy write-offs. These outcomes match industry benchmarks where complete RF and voice integrations return 2 to 4 times the initial investment inside the first 12 months.

Future RF and Voice Options in Infor WMS

Plan ahead for Web RF running on rugged tablets. Infor continues to improve AI voice recognition and adds tighter links between WMS and Infor Factory Track for seamless warehouse-to-manufacturing handoffs. These updates will reduce the need for custom scripts and give more real-time visibility to supervisors.

Conclusion

Effective Infor WMS RF integration uses Telnet sessions that stay connected, barcode APIs that parse on first scan, and voice workflows that follow defined rules. These configurations deliver consistent performance across every shift.

SAMA Consulting configures these elements for clients. Contact us for Telnet tuning, barcode optimization, voice rollout, or a full RF-to-voice transition.

Ready to update your RF setup?

→ View Infor WMS expertise

→ Book a session with our WMS team.

Further Reading

• The Ultimate Guide to Infor WMS: Streamlining Your Warehouse Operations
• Getting Started with Infor ION: A Step-by-Step Guide to System Integration
• Infor ERP Software: The Ultimate Guide for 2024

Configure correctly. Operate reliably.