Skip to content
iOS 27 lets you use two iPhones with the same phone numberMappleCare Community ↗

iOS 27 lets you use two iPhones with the same phone number

By admin • • 3 min read

iOS 27 introduces a carrier‑agnostic NumberShare framework that decouples the telephone number from a single physical SIM or eSIM instance. The architecture leverages the existing IMS (IP Multimedia Subsystem) registration path, allowing the Home Subscriber Server (HSS) to maintain a single IMSI‑to‑MSISDN binding while presenting multiple device‑specific public identities (GRUUs) to the network. Each iPhone registers independently with its own device certificate, yet the core network routes inbound sessions to all registered GRUUs simultaneously, preserving call state, SMS/MMS delivery, and visual voicemail synchronization across devices without requiring a proprietary carrier‑side multiplexer.

The engineering change is realized through an extension of the eUICC provisioning API (GSMA SGP.22) that accepts a “shared‑number” flag during profile download. When the flag is set, the SM‑DP+ server issues a single subscription profile containing a shared private key and a list of authorized device identifiers. The Secure Enclave on each iPhone stores the corresponding private key fragment, enabling mutual authentication with the IMS core. This design eliminates the previous need for a primary/secondary SIM hierarchy and removes the 30‑second registration latency observed when swapping a physical SIM between devices.

Key Engineering Takeaway: iOS 27 enables true multi‑device number sharing by extending the IMS registration model with shared GRUUs. The solution is carrier‑transparent and relies on standard eUICC provisioning extensions.
← Scroll table horizontally on small screens →
Subsystem / Parameter Baseline / Previous Updated Implementation
IMS Registration Single GRUU per subscription; secondary devices required call forwarding Multiple simultaneous GRUUs per MSISDN; inbound sessions forked to all registered devices
eSIM Profile Provisioning One profile per device; no shared‑number flag Shared‑number flag in SGP.22 profile; common private key material distributed to authorized devices
Call Continuity / Handoff Manual handoff via Call Forwarding or Wi‑Fi Calling Seamless session continuity using IMS session transfer (RFC 7395) across devices

Actionable Diagnostic & Implementation Steps

  1. On each iPhone, open Settings → Cellular → Add Cellular Plan and scan the carrier‑provided QR code that includes the shared-number=true parameter.
  2. Verify profile activation via Terminal (macOS) or the Console app: log show --predicate 'subsystem == "com.apple.CommCenter"' --info | grep "NumberShare" – confirm “Registration successful” for both device UDIDs.
  3. Initiate a test call to the shared number; use networkQuality -v on each device to confirm simultaneous RTP streams and zero packet loss during handoff.

Ecosystem Compatibility & Support Notice

  • iOS 27 or later on all participating iPhones (iPhone 15 series and newer).
  • Carrier must support GSMA SGP.22 v3.0 with NumberShare extension and IMS core capable of multi‑GRUU routing.
  • Both devices signed into the same Apple ID with iCloud Keychain enabled for secure key sync.
  • eSIM‑only hardware; physical SIM slots are ignored for the shared number.
  • Enterprise MDM profiles must not restrict com.apple.managedconfiguration.cellular payloads.

Source and technical reference: 9to5Mac.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Still running into this issue on your iPhone or Mac?

Share your OS version, device model, and exact error code in our independent peer Q&A rooms.

Ask in Community Forum →
Ağ Bağlantıları:MacBook • Teknoloji • Donanım Rehberi • Elektronik • Soru Cevap
\n\n