***Must be comfortable working on a dating website/app project.*** Our React Native iOS app uses WebRTC with Socket.io for signaling. Incoming calls load fine, yet when an iPhone user tries to start an outbound call the flow stops right after the camera/mic permission prompt—no offer is sent. I have not touched the client or server code recently, so the defect likely sits in the current signaling, SDP, or ICE exchange. TURN/STUN servers are running and unchanged. What I need from you • Inspect the existing Swift WebRTC layer and the Node/Socket.io signaling code. • Pinpoint why the offer/answer negotiation never begins once permissions are granted. • Apply concise fixes without breaking the stable Android and web versions that share the same backend. • Hand back a clean patch or pull request together with a short summary of changes. Acceptance check An iPhone on iOS 16+ must be able to place a video call to any other platform, with two-way audio and video establishing in under five seconds and remaining stable for at least two minutes. If you have recent WebRTC debugging experience on iOS and Safari, especially around Socket.io signaling, you should find this a straightforward task. Deliverables include: *Re-enable video call button. *Remove and replace default caller ID name & photo and replace with Inbound Caller name & profile picture. *Missed calls is notated in "Notifications" on menu. *Set permissions to utilize current device notifications, such as ringtone/vibrate/silent for calls and messages. *Upload for iOS app submission. * Set up in-app purchases through Apple Store with current membership packages.