Open Radar

 
The deprecation of the kCFStreamNetworkServiceTypeVoIP in favour of PushKit notifications precludes the possibility for applications/solutions which need to work where no Internet connection exists, such as remote locations without mobile or hardwired connections (or even slow or unreliable connections).

Applications which provide VoIP services (via dedicated hardware and local WiFi) are unable to provide VoIP/SIP services to Apple devices as they can not generate a Remote Notification without having accessing to the Internet and with the deprecation of kCFStreamNetworkServiceTypeVoIP, devices no longer guarantee the life of the service while the app is in the background, making the use of Apple devices unreliable.

The move towards PushKit is not an issue, the inability to generate a Remote Notification without access to a Internet connection is.

Steps to Reproduce:
1. Create a server which generates Remote Notifications.
2. Register a device for Remote Notifications from the server
3. Connect both to the same WiFi network
4. Remove Internet access from the WiFi network
5. Generate PushKit notifications from the server

Expected Results:
1. A remote notification

Actual Results:
1. Nothing.  No body seems to know that nothing has happended

Version:
iOS9+

Notes:
We are open to any reliable solution which helps us solve this issue, including, but not limited to:

1. An embedded APNs server which can run the hardware device locally and serve Remote Notifications over the local WiFi network
2. Guarantees over the reliability of services like Bluetooth based notifications, while the App is in the background
3. Some other mechanism which would allow our SIP based hardware to generate a notification to the Apple Device while the app is running in the background in a guaranteed and reliable manner

Configuration:
Apple devices supporting iOS 9+, localised WiFi with no Internet Access