Emergency Services & 911

Defined Terms

Application within Emergency Services & 911. “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 Emergency Services & 911. “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.

Current Public Scope

Unless expressly provided in an executed service order and technically enabled, ARCAMUSA Wholesale Services are not intended or authorized for 911, E911 or emergency calling.

Customer Responsibilities

Customer must prevent unsupported emergency Traffic, provide appropriate downstream notices, maintain alternative access to emergency services and not represent that emergency calling is available without written and technical confirmation.

Customer is prohibited from placing, allowing or representing emergency calls through the Wholesale Services unless a written service order expressly authorizes that use and ARCAMUSA has confirmed separate activation. Customer must configure its equipment to prevent unauthorized emergency routing.

No Implied Capability

Routing ordinary voice Traffic, accepting a telephone number or supporting SIP interconnection does not establish emergency-service capability, registered-location support, call-back handling or delivery to a public safety answering point.

If Separately Enabled

If emergency services are later offered, the applicable Order and product terms must describe the implemented service, activation, location-data, testing, customer-notice and limitation requirements before use.

Written Authorization Required

Emergency calling may be used only when an executed service order specifically identifies the capability and the required technical provisioning has been completed. No other service description or interconnection behavior creates implied authorization.

Service Boundary

Wholesale voice routing is not represented as emergency-capable unless an accepted service document expressly identifies and implements that capability.

Customer Disclosures

Customer must accurately inform downstream customers and users of service limitations and must not imply emergency availability based on general website language.

Before enabling any downstream user, a reseller must give a clear downstream disclosure that emergency calling is unavailable unless separately contracted and activated, identify an alternative means of reaching emergency assistance, and avoid statements implying that ordinary service activation includes 911 or E911.

Routing Restrictions

Emergency numbers must not be knowingly routed over a service that has not been approved for emergency use. Testing emergency numbers is prohibited except through an authorized coordinated process.

Location and Callback

Where emergency functionality is separately approved, Customer responsibilities may include accurate location, callback information and updates according to applicable requirements.

Customer Systems

Customer is responsible for endpoint, PBX, power, broadband, configuration and failover arrangements within its control.

Customer equipment, power, internet access, LAN configuration, endpoint registration and location records remain under Customer control. A failure, outage or misconfiguration in those components may prevent a separately enabled emergency call and does not convert unsupported service into emergency service.

Alternative Access

Customers should maintain legally compliant emergency-calling arrangements appropriate to their offering and inform users of alternatives during outages or limitations.

Reseller Obligations

Resellers must flow down accurate restrictions and may not market a downstream service as emergency-capable without the required approved implementation.

No Assumed Capability

A completed ordinary voice call, assigned credential or successful test does not establish emergency-service capability.

ARCAMUSA may suspend a separately enabled emergency configuration when location or callback information is invalid, testing is unauthorized, routing is misconfigured or continued operation could create safety risk. Suspension does not relieve Customer of maintaining alternative emergency access.

Contract Hierarchy & Related Documents

This policy controls over any general reference that might otherwise suggest emergency capability. Unless an executed order expressly identifies emergency calling and ARCAMUSA confirms technical enablement, the Wholesale Terms and Voice Product Terms authorize no 911 or E911 use.

When emergency capability is separately enabled, the order and implementation materials define the supported territory, location workflow and callback configuration. The customer-disclosure, equipment, testing and alternative-access duties in this policy remain applicable despite any downstream representation.