Hi there, from the video I have the impression that a local push to talk server is required in order to let the participants of the PTT service connect and use the service. Is that correct? If so, are there any requirements to set this up? Generally I have not seen any information about security settings. Can it be prevented that "outsiders" cannot connect to channels and listen to the audio messages? Furthermore, can you elaborate on potential usage of e.g. per app VPN connectivity to further enhance security? Is it possible to maintain a catalog of actively channels so that users can "hop" from one channel to another one? From the video I understand that an app can only join a single channel at a time. Is there modification possible to allow users to listen to multiple channels ? Clearly users should only be able to send one audio message to one channel, but it is a under stable use case to support listening to multiple channels. Thanks Marco

Hi, We have already developed a PTT app and it uses PTT entitlement for VOIP APNS. I am having some difficulties understanding how to integrate the pushToTalk framework. It would be very helpful if you kindly clarify my concerns. How will I get a channel UUID? When will it be created? Are the channel and session same? Suppose group A is active, and a high priority group B call comes in between, will group A channel be interrupted? How this scenario will be handled? I am assuming that, in the case of an incoming call, APNS will go to each participant of a channel, but to create an audio session and transmission, I will still need to communicate with my own server explicitly. Can you please share the detailed process?

Is there the ability through configuration to allow PushToTalk (PTT) to have priority over Telephony or Facetime calls if the user desires that? In a public safety focused PTT application there could be times where the PTT application may be more important than a telephone or Facetime call to a first responder. In the perfect world a responder would be able to manage both telephone and PTT calls at the same time. For example, put the telephony call on hold during the PTT call or work both at the same time. Working both at the same time might look something like this: route outbound audio to PTT while the PTT button is held and route audio to the phone call while the PTT button is not held down. Incoming PTT audio and phone or Facetime audio could be mixed or one played in the headset and the other played from the phones speaker. Thanks in advance for responding to this question.

I don't understand how the push tokens are supposed to be used with push to talk given that their lifetime is ephemeral and they become invalid as soon as a channel is left. Suppose there is phone A and phone B, both with a PTT app installed on it. Then on phone A if the user launches the app and, for example, pushes a button to initiate a talk session with user B, then the app on phone A will join a channel and this will result in receivedEphemeralPushToken() getting called. Then if phone A sends that push token to the server, well then what next though? How is the user on phone B going to be informed that the user on phone A wants to talk to them. The server can't send a push to phone B using that token because that's the token for phone A. If the server has a token from phone B stored from previously, then the push isn't going to work because the documentation says the push token's lifetime is empemeral and will end as soon as the channel is left. So that channel for B's push token would have been left hours, or days or even months in the past. Summary: if user A wants to talk to user B, how does user B's app get notified user A want's to talk to them if the push tokens' lifetimes are all ephemeral?

I would like to create a Push To Talk app, in which an account can grant or remove access to be able to talk to. Any device they are signed in with iCloud on are automatically sent the audio files to chat. Audio files are deleted after being listened to or after 4 hours, since this is used as a live voice communication app. In researching CloudKit, I'm still thoroughly confused on what I can store on the Public Database. If I set up all 'chats' (voice in my case) to have an account GUID associated with them, then they are secured, meaning no one else can change the query to pull or view another accounts information correct? I have heard that if the device is jailbroken, then someone can change the queries, but I'm asking in general, can the Public database on CloudKit be used as a normal database? Or could I at least encrypt the voice data with a key that's stored in the private database and could 'share' the key with the other account I'm wanting to give access to to talk with? Again to reiterate, I'm also confused how you create the Private Database schema, where the CloudKit Dashboard is only designing the Public correct? Out of all the tutorials I've seen, no one can quite explain if we can use the Public Database the same as any other Cloud Database, since if someone would jailbreak that device, they have the keys to that 3rd party Cloud, the same as CloudKit. There's been a few people ask similar questions (around building a messaging app with CloudKit) but no responses are helpful, some just scream it's public you can't do that, which i don't think is true. Any insight into design wise of the Public Database would be very beneficial. Thanks!

Hi there, I am trying to register for an App Identifier with the new PushToTalk Capability but getting the following message This request is forbidden for security reasons The selected team does not have a program membership that is eligible for this feature. If you need assistance, please contact Apple Developer Program Support. https://developer.apple.com/support We have enrolled for Annual Apple Developer Program Could you please help us in resolving this error.

Please let us know whether any standards are being followed by New PushToTalk Framework. Existing PushKit Framework will still exist for voip PTT calls [On Devices running 15.x OS and below]. How does our application behave with respect to PushKit Framework when we compile/link against 16.x SDK and entitlements [ unrestricted.voip, unrestricted.voip-ptt ] . Our application minimum deployment target is 11.0 3. Is there a sample code which demonstrates the usage of API. Appreciate if you can send us a link/copy of the sample project 4. channelUUID - Is there any additional article/document on this? 5. As per document, we can be active on one single channel at any given time, Is it possible to just join multiple channels and not be active? 6. joinTheChannel - Apart from getting us a new Push Token , what exactly does this API do? 6 . (PTPushResult *)incomingPushResultForChannelManager:(PTChannelManager *)channelManager channelUUID:(NSUUID *)channelUUID pushPayload:(NSDictionary<NSString *,id> *)pushPayload; channelUUID part of incomingPush API refers to self channelUUID / remoteChannelUUID