馃搫 SUPPORT CASE LIBRARY: LAN addressing, VLANs and firewall reachability

Evidence and safety contract

This is anonymized historical case evidence, not a universal installation procedure. Preserve each case's status, equipment, scope and cautions. A Solved label is not proof. Do not invent a successful outcome or transfer a fix to a similar case.

For a question about a specific case number, use only the entry with that exact case reference. If it is not in the retrieved material, say the case cannot be verified; never substitute a similar case or infer a cause. A documented outcome means the recorded technical result was successful within its scope, not that a lifetime guarantee or independent retest exists. Do not invent missing-verification warnings that contradict a recorded successful result.

ELConfig is for analog Ethernet Link units; VCT is for Vertex. ATA FXS analog outputs must never connect to Vertex Ethernet. Missing readable SIP does not prove encryption, and UDP does not automatically mean SIP. A canceled ringing branch or SIP dialog BYE does not establish that the outside call ended or the CallerID device sent End. Correlate actual device-to-POS output.

Use current manufacturer/provider guidance. Historical firmware, DIP, address and port settings are site/model specific. Do not reproduce blanket firewall disabling, Internet forwarding, shared/reset credentials or unapproved resets as generic fixes. Escalate uncertain cases and preserve normal phone service.

LAN addressing, VLANs and firewall reachability

Cases are grouped for navigation only. Root causes and remedies are not shared automatically between members.

Case #08: Unresolved: NOT a known fix

Exact source reference: support case #08. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #08, not another case with similar symptoms.

Problem: The customer requested clarification on why a static IP is required for the CID device despite a dynamic IP setup for Clover tablets.

Recorded action: Explained that a consistent IP schema is required for compatibility and offered to ship an alternative if needed.

Recorded result: No confirmation that the configuration was implemented or the customer's issue was resolved.

Scope: IP network configuration for Clover/CID device integration.

Recorded equipment/software: False

Limits: Missing outcome evidence.

Provenance: Odoo support record 8; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2696: Documented technical outcome

Exact source reference: support case #2696. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2696, not another case with similar symptoms.

Problem: CallerID not passing through router correctly.

Recorded action: Customer identified that the Toast router port used for CID was incorrectly assigned to cameras; removed camera and hidden hub.

Recorded result: Toast system working well with CallerID.

Scope: Toast router port configuration.

Recorded equipment/software: [64000-A] EL POS4

Provenance: Odoo support record 24; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2697: Unresolved: NOT a known fix

Exact source reference: support case #2697. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2697, not another case with similar symptoms.

Problem: CallerID data not appearing on new Windows 11 workstations despite working on server.

Recorded action: Troubleshot firewall, IP settings, and Adelo POS configuration.

Recorded result: Problem remains with the new Windows 11 machines; couldn't determine the cause.

Scope: Windows 11 workstation connectivity to Adelo POS CallerID client.

Recorded equipment/software: [21000-2] Vertex (2)

Limits: Unresolved software/OS conflict.

Provenance: Odoo support record 25; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2700: Unresolved: NOT a known fix

Exact source reference: support case #2700. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2700, not another case with similar symptoms.

Problem: Vertex connectivity failure across network; CallerID traffic only reaching specific stations.

Recorded action: Review of settings and consultation with senior technician.

Recorded result: Determined that VCT and log methods differ; unresolved installation.

Scope: Network setup with Revel POS.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Outcome evidence missing.

Provenance: Odoo support record 28; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2705: Unresolved: NOT a known fix

Exact source reference: support case #2705. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2705, not another case with similar symptoms.

Problem: Customer switched POS providers; requires reconfiguration.

Recorded action: Advised verifying IP address via VCT.

Recorded result: Pending approval of tech support costs.

Scope: POS system reconfiguration.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Outcome evidence missing.

Provenance: Odoo support record 33; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2714: Unresolved: NOT a known fix

Exact source reference: support case #2714. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2714, not another case with similar symptoms.

Problem: New router installation impacting SIP/CallerID functionality.

Recorded action: Ticket opened for review.

Recorded result: No action taken recorded.

Scope: Router change connectivity.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Outcome evidence missing.

Provenance: Odoo support record 42; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2717: Documented technical outcome

Exact source reference: support case #2717. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2717, not another case with similar symptoms.

Problem: CallerID not showing on POS.

Recorded action: Rebooted iPad and network after verifying line connection.

Recorded result: Calls showing on POS; system working.

Scope: POS system network.

Recorded equipment/software: [62000] POS (2, Ethernet)

Provenance: Odoo support record 45; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2738: Unresolved: NOT a known fix

Exact source reference: support case #2738. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2738, not another case with similar symptoms.

Problem: Complex network environment with OTT phones prevents standard implementation.

Recorded action: Recommended use of VLAN/mirrored ports or dedicated lines.

Recorded result: No viable path identified to implement working solution.

Scope: Networking/Installation.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Support identified no realistic way to implement.

Provenance: Odoo support record 66; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2746: Unresolved: NOT a known fix

Exact source reference: support case #2746. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2746, not another case with similar symptoms.

Problem: Need to configure network for traffic mirroring.

Recorded action: Advised mirroring phone VLAN traffic and running Setup Mode.

Recorded result: Pending IT configuration.

Scope: Network configuration.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: No successful outcome confirmed.

Provenance: Odoo support record 74; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2757: Unresolved: NOT a known fix

Exact source reference: support case #2757. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2757, not another case with similar symptoms.

Problem: Customer did not follow up.

Recorded action: Set Clover IP address.

Recorded result: Closed due to customer non-response.

Scope: Installation.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Incomplete configuration.

Provenance: Odoo support record 85; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2763: Unresolved: NOT a known fix

Exact source reference: support case #2763. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2763, not another case with similar symptoms.

Problem: Intermittent pop-up functionality.

Recorded action: Network layout mapping.

Recorded result: In progress.

Scope: Pop-up issue.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Intermittent issue unresolved.

Provenance: Odoo support record 91; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2764: Documented technical outcome

Exact source reference: support case #2764. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2764, not another case with similar symptoms.

Problem: Setup mode failure.

Recorded action: Manually configured Vertex using windows desktop network connection.

Recorded result: Plugged back into Toast and it worked right away.

Scope: Installation setup.

Recorded equipment/software: [21000-2] Vertex (2)

Provenance: Odoo support record 92; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2771: Documented technical outcome

Exact source reference: support case #2771. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2771, not another case with similar symptoms.

Problem: Firewall configuration error banner in EL Config

Recorded action: Disabled firewall

Recorded result: Communication with device restored

Scope: Firewall settings

Recorded equipment/software: [52000-A] EL WC2 Deluxe

Limits: The historical test disabled a firewall. This is not an approved permanent remedy; identify the necessary application/port rule with site IT and retain protection.

Provenance: Odoo support record 99; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2781: Action recorded: resolution NOT established

Exact source reference: support case #2781. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2781, not another case with similar symptoms.

Problem: CallerID data not appearing on the POS screen.

Recorded action: Configured the device IP address for the customer's network.

Recorded result: Connectivity verified, with customer instructed to enable CallerID on the POS side.

Scope: Device network configuration.

Recorded equipment/software: [64000-A] EL POS4

Limits: Recorded result is diagnostic, limited, administrative or not an explicit completed technical repair.

Provenance: Odoo support record 109; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2790: Action recorded: resolution NOT established

Exact source reference: support case #2790. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2790, not another case with similar symptoms.

Problem: CallerID data takes 4-6 seconds to appear on the screen.

Recorded action: Suggested customer contact POS software provider for latency investigation.

Recorded result: Data is receiving but with delay; support considers device role satisfied.

Scope: Data transmission timing.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Latency issue remains present; resolution pushed to external provider.

Provenance: Odoo support record 118; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2795: Unresolved: NOT a known fix

Exact source reference: support case #2795. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2795, not another case with similar symptoms.

Problem: Device initial installation not completed.

Recorded action: None.

Recorded result: Case remains in waiting status.

Scope: Installation status.

Recorded equipment/software: [21000-2] Vertex (2)

Limits: No activity recorded; case status: Waiting on Customer.

Provenance: Odoo support record 123; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2796: Unresolved: NOT a known fix

Exact source reference: support case #2796. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2796, not another case with similar symptoms.

Problem: Uncertainty regarding existing service type and hardware requirement.

Recorded action: Advised need for consultation to determine service type.

Recorded result: Evaluation incomplete.

Scope: System requirement verification.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: No resolution documented.

Provenance: Odoo support record 124; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2797: Unresolved: NOT a known fix

Exact source reference: support case #2797. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2797, not another case with similar symptoms.

Problem: Incomplete installation.

Recorded action: None.

Recorded result: No resolution confirmed.

Scope: System installation.

Recorded equipment/software: [21000-2] Vertex (2)

Limits: Lack of clarity on resolution; internal inquiry note on timing/result.

Provenance: Odoo support record 125; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2799: Documented technical outcome

Exact source reference: support case #2799. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2799, not another case with similar symptoms.

Problem: Verification of installation success.

Recorded action: Tested via setup mode.

Recorded result: Device successfully reading and passing call data.

Scope: Installation verification.

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 127; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2803: Documented technical outcome

Exact source reference: support case #2803. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2803, not another case with similar symptoms.

Problem: Device misrouted through Comcast network.

Recorded action: Moved management port to correct router and rebooted.

Recorded result: Communication with POS restored.

Scope: Vertex (2) Network Configuration

Recorded equipment/software: [21000-2] Vertex (2)

Provenance: Odoo support record 131; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2804: Unresolved: NOT a known fix

Exact source reference: support case #2804. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2804, not another case with similar symptoms.

Problem: CallerID inquiry

Recorded action:

Recorded result:

Scope: CallerID

Recorded equipment/software: [62000] POS (2, Ethernet)

Provenance: Odoo support record 132; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2817: Documented technical outcome

Exact source reference: support case #2817. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2817, not another case with similar symptoms.

Problem: Garbage data received due to device in setup mode.

Recorded action: Verified and disabled setup mode.

Recorded result: Issue resolved by ensuring mode is off.

Scope: Vertex (4) Configuration

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 145; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2819: Unresolved: NOT a known fix

Exact source reference: support case #2819. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2819, not another case with similar symptoms.

Problem: CallerID data is captured by the PC but the device cannot be accessed for remote configuration.

Recorded action:

Recorded result:

Scope: Vertex device connectivity

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Missing outcome evidence.

Provenance: Odoo support record 147; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2824: Documented technical outcome

Exact source reference: support case #2824. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2824, not another case with similar symptoms.

Problem: Vertex device not appearing in Pulse software.

Recorded action: Set static IP and rebooted.

Recorded result: Device successfully working in Pulse.

Scope: Network settings

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 152; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2830: Unresolved: NOT a known fix

Exact source reference: support case #2830. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2830, not another case with similar symptoms.

Problem: Installation issues reported by on-site technician.

Recorded action: Attempted contact via voicemail.

Recorded result: No contact made.

Scope: Vertex installation

Recorded equipment/software: [21000-4] Vertex (4)

Limits: No resolution.

Provenance: Odoo support record 158; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2832: Action recorded: resolution NOT established

Exact source reference: support case #2832. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2832, not another case with similar symptoms.

Problem: POS software not installed to verify CallerID.

Recorded action: Verified call logging using VCT call monitor and test calls.

Recorded result: Calls correctly logged in VCT.

Scope: Vertex (4) validation

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Prior source review did not establish a reusable end-to-end resolution; retained as case evidence only.

Provenance: Odoo support record 160; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2834: Documented technical outcome

Exact source reference: support case #2834. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2834, not another case with similar symptoms.

Problem: Undiscovered network configuration prevented unit from working.

Recorded action: Correctly connected management port to the POS network.

Recorded result: Unit started working.

Scope: Vertex (4) Networking

Recorded equipment/software: [21000-4] Vertex (4)

Limits: The note indicates a damaged cable latch/tape dependency which requires physical maintenance.

Provenance: Odoo support record 162; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2841: Action recorded: resolution NOT established

Exact source reference: support case #2841. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2841, not another case with similar symptoms.

Problem: Data not visible in Toast.

Recorded action: Pushed issue to be dealt with later.

Recorded result: Data not confirmed in Toast.

Scope: Vertex installation

Recorded equipment/software: [21000-2] Vertex (2)

Limits: Missing confirmed resolution.

Provenance: Odoo support record 169; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2842: Unresolved: NOT a known fix

Exact source reference: support case #2842. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2842, not another case with similar symptoms.

Problem: Setup wizard failed to find SIP packets; potential firewall conflict.

Recorded action: Advised checking firewall settings.

Recorded result: Waiting for customer to configure multiple firewalls.

Scope: Vertex network integration

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Missing confirmed resolution.

Provenance: Odoo support record 170; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2844: Unresolved: NOT a known fix

Exact source reference: support case #2844. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2844, not another case with similar symptoms.

Problem: CID pop-ups work but not communicating with software.

Recorded action: None recorded.

Recorded result: None.

Scope: Vertex software integration

Recorded equipment/software: [21000-8] Vertex (8)

Limits: Missing action and resolution.

Provenance: Odoo support record 172; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2849: Unresolved: NOT a known fix

Exact source reference: support case #2849. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2849, not another case with similar symptoms.

Problem: Unit stopped working after Clover equipment upgrade.

Recorded action: None.

Recorded result: Customer to attempt self-resolution.

Scope: Vertex installation

Recorded equipment/software: [21000-2] Vertex (2)

Limits: No resolution.

Provenance: Odoo support record 177; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2850: Action recorded: resolution NOT established

Exact source reference: support case #2850. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2850, not another case with similar symptoms.

Problem: No CallerID after router reset.

Recorded action: Advised purchase of adapter and firmware update.

Recorded result: Firmware update requested but not yet performed.

Scope: Vertex networking

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Incomplete resolution.

Provenance: Odoo support record 178; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2851: Action recorded: resolution NOT established

Exact source reference: support case #2851. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2851, not another case with similar symptoms.

Problem: Initial installation

Recorded action: Not specified

Recorded result: System working

Scope: Installation

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 179; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2856: Unresolved: NOT a known fix

Exact source reference: support case #2856. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2856, not another case with similar symptoms.

Problem: Unit installed but nothing populates on Toast display.

Recorded action: Scheduled remote session.

Recorded result: Pending.

Scope: Vertex networking

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Missing confirmed resolution.

Provenance: Odoo support record 184; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2864: Action recorded: resolution NOT established

Exact source reference: support case #2864. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2864, not another case with similar symptoms.

Problem: Device not communicating due to laptop firewall blocking connection.

Recorded action: Used device setup mode instead of laptop VCT connection.

Recorded result: Setup mode worked successfully and CallerID is functional in POS.

Scope: Installation methodology

Recorded equipment/software: [21000-2] Vertex (2)

Limits: Prior source review did not establish a reusable end-to-end resolution; retained as case evidence only.

Provenance: Odoo support record 192; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2877: Action recorded: resolution NOT established

Exact source reference: support case #2877. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2877, not another case with similar symptoms.

Problem: Network setup requirement; customer lacked Windows laptop to set IP.

Recorded action: Used custom Python script to set IP address.

Recorded result: Data incoming verified via Wireshark.

Scope: Device networking

Recorded equipment/software: [62000] POS (2, Ethernet)

Limits: Prior source review did not establish a reusable end-to-end resolution; retained as case evidence only.

Provenance: Odoo support record 205; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2882: Unresolved: NOT a known fix

Exact source reference: support case #2882. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2882, not another case with similar symptoms.

Problem: Pop-ups stopped after internet loss.

Recorded action: None recorded.

Recorded result: None recorded.

Scope: Vertex.

Recorded equipment/software: False

Limits: No evidence of successful resolution.

Provenance: Odoo support record 210; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2890: Action recorded: resolution NOT established

Exact source reference: support case #2890. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2890, not another case with similar symptoms.

Problem: Customer unsure if unit received is correct for Avaya PBX.

Recorded action: Advised requirements for Toast-compatible units and phone network investigation.

Recorded result: None; inquiry only.

Scope: Vertex (2).

Recorded equipment/software: [21000-2] Vertex (2)

Limits: No evidence of successful resolution.

Provenance: Odoo support record 218; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2894: Action recorded: resolution NOT established

Exact source reference: support case #2894. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2894, not another case with similar symptoms.

Problem: IP networking questions

Recorded action: Advised on IP settings

Recorded result: Guidance provided

Scope: Networking

Recorded equipment/software: [62000] POS (2, Ethernet)

Provenance: Odoo support record 222; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2903: Documented technical outcome

Exact source reference: support case #2903. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2903, not another case with similar symptoms.

Problem: CallerID data was not reaching the Revel POS system.

Recorded action: Reconfigured the network switch port #9 to assign it to the POS LAN.

Recorded result: The CallerID data began pushing to the POS system successfully.

Scope: Revel POS LAN connectivity.

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 231; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2904: Action recorded: resolution NOT established

Exact source reference: support case #2904. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2904, not another case with similar symptoms.

Problem: CallerID data from analog phone lines was not appearing on the Uniwell POS screen.

Recorded action: The customer finalized Uniwell port settings while the network successfully received incoming call data in ELConfig.

Recorded result: Incoming calls were verified reaching the network, and the customer proceeded to finalize settings on the Uniwell side.

Scope: Uniwell HX 7500 integration.

Recorded equipment/software: [62000] POS (2, Ethernet) 路 HX 2500, HX 5500 / Uniwell Americas, INC.

Limits: The actual POS-side resolution is incomplete as the customer was tasked with finalizing their own settings. Recorded result is diagnostic, limited, administrative or not an explicit completed technical repair.

Provenance: Odoo support record 232; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2907: Action recorded: resolution NOT established

Exact source reference: support case #2907. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2907, not another case with similar symptoms.

Problem: Customer needed a backup unit configured to match the settings of their existing CallerID box.

Recorded action: Applied existing toggles and matched the network IP scheme.

Recorded result: Device configured to customer's network requirements.

Scope: WC Deluxe unit replacement.

Recorded equipment/software: [58000] WC Deluxe (8, Ethernet)

Limits: Recorded result is diagnostic, limited, administrative or not an explicit completed technical repair.

Provenance: Odoo support record 235; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2908: Action recorded: resolution NOT established

Exact source reference: support case #2908. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2908, not another case with similar symptoms.

Problem: Device power light and management port light were unresponsive, failing network requests.

Recorded action: Determined the unit was broken; advised sending it back for evaluation.

Recorded result: Device failure confirmed; requires return for diagnosis.

Scope: Vertex 4 unit hardware

Recorded equipment/software: [21000-4] Vertex (4) 路 RO Writer / Progressive Automotive Systems

Limits: Stage marked as Cancelled, ticket outcome reflects hardware defect.

Provenance: Odoo support record 236; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2915: Action recorded: resolution NOT established

Exact source reference: support case #2915. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2915, not another case with similar symptoms.

Problem: POS CallerID data drops intermittently, typically on Thursdays.

Recorded action: Suggested investigating internet connectivity logs for brownouts.

Recorded result: No identified internal issue; advised customer to check network logs for local interference.

Scope: Cloud relay POS connectivity

Recorded equipment/software: [21000-2] Vertex (2)

Limits: Intermittent issue unresolved; customer tasked with site monitoring.

Provenance: Odoo support record 243; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2928: Action recorded: resolution NOT established

Exact source reference: support case #2928. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2928, not another case with similar symptoms.

Problem: Verizon LTE backup was continuously active, preventing Vertex data connection.

Recorded action: Advised customer to contact Verizon to disable LTE for the Vertex to use primary data.

Recorded result: Customer advised on the dependency issue between LTE and data.

Scope: Verizon LTE/data connectivity

Recorded equipment/software: [21000-2] Vertex (2) 路 Toast / Toast, Inc

Limits: Outcome evidence missing; depends on carrier cooperation.

Provenance: Odoo support record 256; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2948: Documented technical outcome

Exact source reference: support case #2948. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2948, not another case with similar symptoms.

Problem: CallerID not appearing on POS screen after network reconfiguration.

Recorded action: Power cycled switch and workstations; verified CallerID settings in portal.

Recorded result: CallerID signal received on POS display.

Scope: Single POS terminal/network.

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 276; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2951: Unresolved: NOT a known fix

Exact source reference: support case #2951. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2951, not another case with similar symptoms.

Problem: No SIP traffic identified in packet captures.

Recorded action: Attempted packet capture and instructed customer to capture from phone UI.

Recorded result: No SIP traffic detected; customer advised to coordinate with service provider.

Scope: Network VoIP traffic

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Lack of progress; encryption status unknown.

Provenance: Odoo support record 279; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2953: Unresolved: NOT a known fix

Exact source reference: support case #2953. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2953, not another case with similar symptoms.

Problem: Topology issues where following the map caused network/phone outages.

Recorded action: Attempted manual topology changes; requested store number for support.

Recorded result: Support could not proceed without store details; issue persisted.

Scope: Store network topology

Recorded equipment/software: False 路 Pulse - Ethernet Connection / Domino's

Limits: Support request cancelled due to inability to contact customer.

Provenance: Odoo support record 281; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2957: Action recorded: resolution NOT established

Exact source reference: support case #2957. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2957, not another case with similar symptoms.

Problem: Phone data routed around the Vertex device.

Recorded action: Advised customer to isolate phone connection for monitoring.

Recorded result: Customer to modify physical cabling.

Scope: Device signal path

Recorded equipment/software: [21000-4] Vertex (4) 路 Clover / Phone Orders Add on / Clover Network, INC.

Provenance: Odoo support record 285; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2967: Action recorded: resolution NOT established

Exact source reference: support case #2967. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2967, not another case with similar symptoms.

Problem: Unreliable CallerID due to Verizon LTE phone signal.

Recorded action: Identified signal interception limitation.

Recorded result: Customer to explore options with carrier.

Scope: Signal interception

Recorded equipment/software: [21000-2] Vertex (2) 路 HarborTouch / Shift 4 Payments

Limits: Technical limitation of LTE phone service.

Provenance: Odoo support record 295; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2972: Action recorded: resolution NOT established

Exact source reference: support case #2972. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2972, not another case with similar symptoms.

Problem: In-bound call test failed on new installation.

Recorded action: Instructed customer to trace signal path to identify bypass.

Recorded result: Customer to investigate signal source.

Scope: Network integration

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 300; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2977: Unresolved: NOT a known fix

Exact source reference: support case #2977. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #2977, not another case with similar symptoms.

Problem: Reintegrating device on new network

Recorded action: None

Recorded result: Lead created

Scope: Networking

Recorded equipment/software: [21000-4] Vertex (4) 路 Pro Call / Bolt On Technology

Provenance: Odoo support record 305; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2982: Action recorded: resolution NOT established

Exact source reference: support case #2982. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2982, not another case with similar symptoms.

Problem: CallerID data not pushing to POS.

Recorded action: Requested verification of POS and Vertex network switch connectivity.

Recorded result: Customer researching network configuration.

Scope: Network connectivity

Recorded equipment/software: [68000] POS (8, Ethernet)

Provenance: Odoo support record 310; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2983: Documented technical outcome

Exact source reference: support case #2983. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #2983, not another case with similar symptoms.

Problem: Device stopped populating CallerID data after Domino's network/Pulse upgrade.

Recorded action: Adjusted broadcast settings to specific subnet address ([site address omitted]).

Recorded result: CallerID data displayed on POS.

Scope: Device configuration.

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 311; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #2996: Action recorded: resolution NOT established

Exact source reference: support case #2996. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #2996, not another case with similar symptoms.

Problem: Connection issue with Vertex device.

Recorded action: Customer called back to resolve the issue.

Recorded result: Issue resolved.

Scope: Vertex unit connection

Recorded equipment/software: [21000-4] Vertex (4) 路 Heartland (MobileBytes) / Heartland Payment Systems, INC.

Limits: Insufficient evidence of technical resolution.

Provenance: Odoo support record 324; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3000: Action recorded: resolution NOT established

Exact source reference: support case #3000. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3000, not another case with similar symptoms.

Problem: Vertex device is not displaying popup on the POS screen despite receiving call data.

Recorded action: Confirmed data is received in log and referred issue to third-party provider.

Recorded result: Problem attributed to third-party vendor; customer to submit vendor ticket.

Scope: CallerID data transmission to POS.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Confirmed receipt of data but issue remains unresolved on POS side.

Provenance: Odoo support record 328; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3003: Unresolved: NOT a known fix

Exact source reference: support case #3003. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3003, not another case with similar symptoms.

Problem: Customer requested instructions for resetting the IP address on an out-of-warranty analog device.

Recorded action: None recorded.

Recorded result: None recorded.

Scope: IP reset for analog CallerID unit.

Recorded equipment/software: [62000] POS (2, Ethernet) 路 Restaurant Mgmt System / HungerRush

Limits: No outcome evidence provided.

Provenance: Odoo support record 331; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3008: Unresolved: NOT a known fix

Exact source reference: support case #3008. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3008, not another case with similar symptoms.

Problem: Customer wants to confirm CallerID functionality after installing a failover router.

Recorded action: None recorded.

Recorded result: None recorded.

Scope: CallerID compatibility with failover network setup.

Recorded equipment/software: False

Limits: No outcome evidence provided.

Provenance: Odoo support record 336; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3014: Unresolved: NOT a known fix

Exact source reference: support case #3014. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3014, not another case with similar symptoms.

Problem: No data transmission to POS.

Recorded action: None recorded.

Recorded result: None recorded.

Scope: Data transmission to POS.

Recorded equipment/software: [21000-2] Vertex (2)

Limits: No outcome evidence provided.

Provenance: Odoo support record 342; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3021: Unresolved: NOT a known fix

Exact source reference: support case #3021. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3021, not another case with similar symptoms.

Problem: Vertex unit not detected on network.

Recorded action: None recorded.

Recorded result: None recorded.

Scope: Vertex device connectivity.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: No outcome evidence provided.

Provenance: Odoo support record 349; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3028: Documented technical outcome

Exact source reference: support case #3028. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #3028, not another case with similar symptoms.

Problem: Pulse 4.0 software not displaying CallerID popup after firmware update.

Recorded action: Set data output to static IP and configured correctly.

Recorded result: Calls correctly seen on Pulse software.

Scope: Pulse software configuration

Recorded equipment/software: [21000-4] Vertex (4) 路 Pulse - Ethernet Connection / Domino's

Provenance: Odoo support record 356; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3034: Unresolved: NOT a known fix

Exact source reference: support case #3034. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3034, not another case with similar symptoms.

Problem: Unit disconnecting internet; customer wants to return.

Recorded action: Encouraged tech support call and clarified return policy.

Recorded result: None recorded.

Scope: Vertex connectivity troubleshooting.

Recorded equipment/software: [21000-2] Vertex (2) 路 Toast / Toast, Inc

Limits: No outcome evidence provided.

Provenance: Odoo support record 362; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3038: Unresolved: NOT a known fix

Exact source reference: support case #3038. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3038, not another case with similar symptoms.

Problem: Loss of CallerID to POS when using a dedicated device compared to hunt group.

Recorded action: Suggested monitoring SIP traffic via VCT.

Recorded result: None recorded.

Scope: Vertex CallerID with phone hunt groups.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: No outcome evidence provided.

Provenance: Odoo support record 366; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3042: Unresolved: NOT a known fix

Exact source reference: support case #3042. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3042, not another case with similar symptoms.

Problem: Vertex unit stopped working after internet provider change.

Recorded action: None recorded.

Recorded result: None recorded.

Scope: Vertex internet connectivity.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: No outcome evidence provided.

Provenance: Odoo support record 370; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3045: Unresolved: NOT a known fix

Exact source reference: support case #3045. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3045, not another case with similar symptoms.

Problem: Intermittent CallerID on POS due to sharing VoIP and POS networks.

Recorded action: Shared that networks should be separate; requires remote session to diagnose.

Recorded result: None recorded.

Scope: Network topology for POS and VoIP.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: No outcome evidence provided.

Provenance: Odoo support record 373; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3046: Action recorded: resolution NOT established

Exact source reference: support case #3046. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3046, not another case with similar symptoms.

Problem: Pre-installation configuration and CallerID name display issue.

Recorded action: Performed phone setup and verified outbound/simulated calls in VCT.

Recorded result: VoIP sending correct phone number but incorrect name; customer to resolve with VoIP provider.

Scope: Vertex pre-installation connectivity.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Technical resolution regarding name display deferred to VoIP provider.

Provenance: Odoo support record 374; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3062: Unresolved: NOT a known fix

Exact source reference: support case #3062. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3062, not another case with similar symptoms.

Problem: No SIP signal detected

Recorded action: None

Recorded result: None

Scope: VoIP

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 390; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3067: Unresolved: NOT a known fix

Exact source reference: support case #3067. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3067, not another case with similar symptoms.

Problem: Calls log in EL config but not Pulse POS screen.

Recorded action: Set IP to 192.168.20.x, adjusted broadcast settings.

Recorded result: Pulse POS remains unable to broadcast to POS stations.

Scope: Pulse POS Ethernet configuration.

Recorded equipment/software: [68000-A] EL POS8 路 Pulse - Ethernet Connection / Domino's

Limits: POS environment reports IP address as service rather than physical station.

Provenance: Odoo support record 395; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3080: Action recorded: resolution NOT established

Exact source reference: support case #3080. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3080, not another case with similar symptoms.

Problem: Internet connection drops when Vertex installed in-line.

Recorded action: Identified and corrected logic loop where both gateway and phone ports were connected to the same switch.

Recorded result: User instructed on correct cabling to resolve logic loop.

Scope: Logic loop configuration.

Recorded equipment/software: [21000-2] Vertex (2)

Limits: Confirmation of working status following logic loop correction is pending.

Provenance: Odoo support record 408; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3082: Documented technical outcome

Exact source reference: support case #3082. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #3082, not another case with similar symptoms.

Problem: Device undetected following power outage.

Recorded action: Verified connectivity through Toast router during screen share session.

Recorded result: System connectivity restored.

Scope: Networking configuration

Recorded equipment/software: [21000-2] Vertex (2) 路 Toast / Toast, Inc

Provenance: Odoo support record 410; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3087: Unresolved: NOT a known fix

Exact source reference: support case #3087. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3087, not another case with similar symptoms.

Problem: VCT not recognizing device after static IP assignment.

Recorded action: Attempted direct workstation connection; encountered loss of connection after saving static IP.

Recorded result: Pending retry following reboot.

Scope: Static IP assignment.

Recorded equipment/software: [21000-2] Vertex (2) 路 Aloha/Aloha to GO / NCR Corporate

Limits: Configuration remains unresolved.

Provenance: Odoo support record 415; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3125: Unresolved: NOT a known fix

Exact source reference: support case #3125. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3125, not another case with similar symptoms.

Problem: Cloud relay errors due to firewall/WAF changes

Recorded action: Provided technical bulletin for vendor remediation

Recorded result: Contingent on third-party policy change

Scope: Cloud relay security

Recorded equipment/software: False

Provenance: Odoo support record 453; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3128: Action recorded: resolution NOT established

Exact source reference: support case #3128. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3128, not another case with similar symptoms.

Problem: Calls not posting to POS after VoIP provider change; signaling issues identified.

Recorded action: Performed multiple data captures; attempted to isolate network traffic.

Recorded result: Captured data indicates packets may be encrypted by customer/provider configuration; awaiting further action.

Scope: Network/VoIP integration

Recorded equipment/software: [21000-2] Vertex (2) 路 Rezku / Rezku

Limits: No resolution achieved.

Provenance: Odoo support record 456; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3142: Action recorded: resolution NOT established

Exact source reference: support case #3142. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3142, not another case with similar symptoms.

Problem: Unable to open EL-config due to incorrect computer type (MAC vs PC).

Recorded action: Provided instructions to run on PC/MAC on correct subnet without popup software running.

Recorded result: Customer to follow up.

Scope: Configuration

Recorded equipment/software: [64000] POS (4, Ethernet)

Limits: No outcome evidence.

Provenance: Odoo support record 470; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3152: Action recorded: resolution NOT established

Exact source reference: support case #3152. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3152, not another case with similar symptoms.

Problem: Unable to access VCT due to network configuration issues with a Pulse 4.0 system.

Recorded action: Provided power supply troubleshooting and Amazon link.

Recorded result: Customer was going to check a different location for a replacement power supply; no resolution confirmed.

Scope: Pulse 4.0 connectivity

Recorded equipment/software: [21000-4] Vertex (4)

Limits: No confirmed outcome; unit connectivity remains unresolved.

Provenance: Odoo support record 480; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3156: Unresolved: NOT a known fix

Exact source reference: support case #3156. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3156, not another case with similar symptoms.

Problem: No longer communicating with POS.

Recorded action: None.

Recorded result: None.

Scope: N/A

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Missing action and outcome.

Provenance: Odoo support record 484; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3188: Action recorded: resolution NOT established

Exact source reference: support case #3188. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3188, not another case with similar symptoms.

Problem: CallerID unit suspected of blocking lines.

Recorded action: Advised user to disconnect unit to test lines.

Recorded result: User will call back if needed.

Scope: Phone line connectivity

Recorded equipment/software: [38000-A] POS8

Limits: No confirmed resolution; issue likely with phone provider.

Provenance: Odoo support record 516; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3196: Action recorded: resolution NOT established

Exact source reference: support case #3196. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3196, not another case with similar symptoms.

Problem: CallerID not reporting to POS.

Recorded action: Screen share troubleshooting.

Recorded result: None.

Scope: POS/Vertex configuration

Recorded equipment/software: [21000-4] Vertex (4) 路 Micro$ale POS / Microsale POS

Limits: No confirmed resolution.

Provenance: Odoo support record 524; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3200: Unresolved: NOT a known fix

Exact source reference: support case #3200. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3200, not another case with similar symptoms.

Problem: Unit stopped working after an upgrade to Pulse 4.0.

Recorded action: None recorded.

Recorded result: Ticket is waiting on customer follow-up.

Scope: Post-software upgrade connectivity failure.

Recorded equipment/software: [21000-2] Vertex (2)

Limits: No outcome evidence.

Provenance: Odoo support record 528; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3204: Documented technical outcome

Exact source reference: support case #3204. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #3204, not another case with similar symptoms.

Problem: Vertex device lost power/connectivity and could not be detected by the configuration tool.

Recorded action: Authorized a courtesy RMA, reprogrammed the unit, updated firmware to V-142, and replaced the power supply.

Recorded result: The device was repaired and confirmed to work after firmware update and power supply replacement.

Scope: Hardware repair

Recorded equipment/software: [21000-2] Vertex (2) 路 Aldelo Express / ALDELO Pos Software

Provenance: Odoo support record 532; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3215: Action recorded: resolution NOT established

Exact source reference: support case #3215. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3215, not another case with similar symptoms.

Problem: Customer reported CallerID not pushing to POS for second call.

Recorded action: Performed simultaneous call tests during a screenshare session.

Recorded result: Confirmed both calls showed up correctly on the call record and POS screen; no problem found.

Scope: Vertex (2) connectivity verification

Recorded equipment/software: [21000-2] Vertex (2) 路 Heartland (MobileBytes) / Heartland Payment Systems, INC.

Limits: Prior source review did not establish a reusable end-to-end resolution; retained as case evidence only.

Provenance: Odoo support record 543; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3217: Action recorded: resolution NOT established

Exact source reference: support case #3217. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3217, not another case with similar symptoms.

Problem: POS locked on stale call record despite Vertex receiving CallerID correctly.

Recorded action: Verified signal reception and instructed customer to reboot POS.

Recorded result: System remained locked on stale call after reboot.

Scope: POS call log synchronization

Recorded equipment/software: [21000-2] Vertex (2) 路 rPower Resturant POS / RPower Holdings, LLC

Provenance: Odoo support record 545; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3218: Action recorded: resolution NOT established

Exact source reference: support case #3218. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3218, not another case with similar symptoms.

Problem: CallerID working on one terminal but not the second.

Recorded action: Instructed customer to verify CallerID settings on the POS dashboard.

Recorded result: Pending verification.

Scope: POS multi-terminal configuration.

Recorded equipment/software: [21000-4] Vertex (4)

Limits: Outcome evidence missing.

Provenance: Odoo support record 546; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3220: Unresolved: NOT a known fix

Exact source reference: support case #3220. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3220, not another case with similar symptoms.

Problem: CallerID stopped populating.

Recorded action: Provided quote for new unit.

Recorded result: None recorded.

Scope: Hardware replacement.

Recorded equipment/software: [21000-4] Vertex (4) 路 Heartland (MobileBytes) / Heartland Payment Systems, INC.

Limits: No outcome evidence.

Provenance: Odoo support record 548; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3226: Action recorded: resolution NOT established

Exact source reference: support case #3226. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3226, not another case with similar symptoms.

Problem: Inability to connect via screenshare; different subnets between office PC and POS terminal.

Recorded action: Requested RPower technician to assist in working the problem.

Recorded result: None recorded.

Scope: Network connectivity/remote access.

Recorded equipment/software: [21000-4] Vertex (4) 路 rPower Resturant POS / RPower Holdings, LLC

Limits: Outcome evidence missing.

Provenance: Odoo support record 554; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3233: Unresolved: NOT a known fix

Exact source reference: support case #3233. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3233, not another case with similar symptoms.

Problem: Unable to connect to CallerID device via configuration tool.

Recorded action: Advised user to reset switch after hours and configure using laptop.

Recorded result: Pending customer follow-up.

Scope: Network/configuration tool integration.

Recorded equipment/software: [64000] POS (4, Ethernet)

Limits: Outcome evidence missing.

Provenance: Odoo support record 561; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3284: Action recorded: resolution NOT established

Exact source reference: support case #3284. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3284, not another case with similar symptoms.

Problem: Customer needed assistance with device configuration and believed they had to change IP addresses.

Recorded action: Clarified that the analog device uses broadcast mode and requires no IP changes.

Recorded result: Customer advised they would follow up if needed.

Scope: WC Basic installation.

Recorded equipment/software: [62000] WC Basic (2, Ethernet)

Limits: Unresolved pending customer testing.

Provenance: Odoo support record 612; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3291: Unresolved: NOT a known fix

Exact source reference: support case #3291. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3291, not another case with similar symptoms.

Problem: Device communication failure following third-party switch change.

Recorded action: Customer advised to contact switch vendor.

Recorded result: Customer to initiate contact.

Scope: Third-party network configuration

Recorded equipment/software: [21000-4] Vertex (4)

Provenance: Odoo support record 619; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3293: Unresolved: NOT a known fix

Exact source reference: support case #3293. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3293, not another case with similar symptoms.

Problem: CallerID data is not populating in the Pulse POS, and remote access to the Pulse switch is unavailable.

Recorded action: Provided documentation on updating gateway and data output IP addresses.

Recorded result: Unable to troubleshoot because the remote connection to the Pulse switch was not possible.

Scope: Vertex (4) on Domino's Pulse.

Recorded equipment/software: [21000-4] Vertex (4) 路 Pulse - Ethernet Connection / Domino's

Limits: Device was incorrectly plugged into a router; remote troubleshooting was impossible.

Provenance: Odoo support record 621; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3298: Action recorded: resolution NOT established

Exact source reference: support case #3298. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3298, not another case with similar symptoms.

Problem: Vertex unit had power issues and intermittent connectivity.

Recorded action: Authorized an exchange as a courtesy to the POS partner.

Recorded result: Device successfully replaced via RMA process coordinated with Toast.

Scope: Hardware warranty RMA

Recorded equipment/software: [21000-2] Vertex (2) 路 Toast / Toast, Inc

Limits: Recorded result is diagnostic, limited, administrative or not an explicit completed technical repair.

Provenance: Odoo support record 626; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3311: Documented technical outcome

Exact source reference: support case #3311. Evidence classification: Documented technical outcome. This paragraph and the following fields concern only case #3311, not another case with similar symptoms.

Problem: Device stopped receiving inbound details and required reboots.

Recorded action: Performed phone setup and directed customer to SIP signal documentation.

Recorded result: Setup completed; functioning verified.

Scope: Setup

Recorded equipment/software: [21000-2] Vertex (2)

Provenance: Odoo support record 639; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3316: Action recorded: resolution NOT established

Exact source reference: support case #3316. Evidence classification: Action recorded: resolution NOT established. This paragraph and the following fields concern only case #3316, not another case with similar symptoms.

Problem: Device stopped working after POS hardware replacement.

Recorded action: Provided instructions for local IP update via computer on same network.

Recorded result: Instructions delivered to user.

Scope: Network configuration

Recorded equipment/software: [62000] WC Basic (2, Ethernet)

Provenance: Odoo support record 644; case evidence reviewed 04NOV26. Historical result, not a fresh site test.

Case #3320: Unresolved: NOT a known fix

Exact source reference: support case #3320. Evidence classification: Unresolved: NOT a known fix. This paragraph and the following fields concern only case #3320, not another case with similar symptoms.

Problem: Unable to connect to configuration tool for setup.

Recorded action: Directed user to reset switch after hours.

Recorded result: Pending customer troubleshooting.

Scope: WC Basic (4, Ethernet).

Recorded equipment/software: [64000] WC Basic (4, Ethernet) 路 Pulse - Ethernet Connection / Domino's

Limits: Unable to connect to unit.

Provenance: Odoo support record 648; case evidence reviewed 04NOV26. Historical result, not a fresh site test.