Caller ID & CLI Policy

Defined Terms

Application within Caller ID & CLI Policy. “ARCAMUSA,” “we,” “us,” and “our” mean Arcamusa, Inc., operator of ARCAMUSA Wholesale. “Customer” means the business entity authorized to use the Wholesale Services. “Traffic” means calls, signaling, metadata and related activity submitted to or received from the Wholesale Services. “Caller ID” or “CLI” means calling-party identification information. “Downstream Customer” and “End User” mean persons or entities using services through Customer.

Application within Caller ID & CLI Policy. “Agreement” includes applicable online terms and policies together with any signed MSA, Order Form or Rate Sheet. “CDR” means a call detail record used for operational, billing, reconciliation, security or compliance purposes. Defined terms apply consistently across the Legal & Trust Center unless a document expressly provides a narrower meaning.

Authority Requirement

Customer-supplied CLI is permitted only where technically supported and when the number is assigned to Customer or Customer has documented lawful authority from the number holder. Authority must cover the actual calling use.

Evidence & Validation

ARCAMUSA may request number assignment records, LOA or equivalent authorization, enterprise or third-party authority, business identity, use case and downstream records. Dynamic CLI requires the same lawful authority for every presented number.

Prohibited Presentation

Fraudulent spoofing, impersonation, number hijacking or deceptive local presence.
Unauthorized third-party, government, bank, carrier or emergency-service numbers.
CLI designed to frustrate traceback, misstate origin or evade fraud and spam protections.

STIR/SHAKEN & Attestation

Customer may not select or demand an attestation level. Authentication depends on provider role, verified customer identity, number authority, technical implementation and applicable standards. Supplying a number does not establish a right to A-attestation.

Remediation & Restriction

ARCAMUSA may reject or normalize invalid CLI, request evidence, restrict numbers or Traffic, require remediation or suspend service where authority or integrity cannot be established.

Lawful Authority

Customer must own, control or have documented permission to use each submitted calling number and must provide evidence when reasonably requested.

Accuracy and Presentation

Calling-party information must accurately support the approved use and must not mislead recipients about identity, location, purpose or return contact.

Dynamic CLI

An authorized dynamic set may be evaluated where the customer can document authority, inventory controls, assignment logic and ongoing governance.

Prohibited Models

Unverified, random, fabricated, impersonating or unlawfully spoofed caller ID is prohibited, as is selection designed to evade blocking or induce deceptive local familiarity.

Number Status

Customer must manage reassignment, revocation and loss of authority and promptly stop using numbers it no longer controls.

Authentication Treatment

Attestation and signing depend on verified relationships, applicable rules and technical implementation. No particular level or downstream display is guaranteed.

Recordkeeping

Customer should retain number inventories, authority evidence, downstream assignments and relevant call records sufficient for investigation and traceback.

Monitoring and Remediation

CLI anomalies, complaints or validation failures may result in evidence requests, restriction, suspension or removal of affected numbers.

Downstream Use

Resellers must impose equivalent requirements and remain capable of identifying the party that selected and used a calling number.

Recipient and Network Treatment

Downstream carriers, analytics services, devices and recipients control some display, labeling and blocking decisions outside ARCAMUSA control.

Contract Hierarchy & Related Documents

This policy controls the numbers and identity information presented with wholesale traffic. The Voice Product Terms address transport, the Robocall policy addresses authentication and mitigation duties, and Traffic Integrity addresses patterns suggesting spoofing, evasion or compromised credentials.

A service order enabling customer-supplied or dynamic CLI provides technical permission only. It does not prove number authority, guarantee an attestation level, or override the customer’s duty to stop using a number after assignment or authorization ends.