I've been using pjsip in an iOS app and am running into an issue where the TCP socket used for the SIP command channel gets closed after 5m by the device when the app is put in the background. (This doesn't happen if the device is plugged into a power source, btw) For the first 5m of running in the background though the app works fine and wakes up when data arrives on the TCP socket. Because of this bug I raised the issue with Apple Developer Technical Support and they basically said that pjsip plays "played fast'n'loose with the VoIP infrastructure" and that they have seen this before from developers using pjsip; I think this is because BSD sockets are used instead of CFStreams to manage the SIP command channel traffic. I'm wondering if any other developers have found a work-around or developed a strategy for shimming CFStreams into the equation? One suggestion from Apple DTS was to use a socketpair (ie: give pjsip one half of the pair, and then have a "bridge" data pump that would use the other half to read/write data to a CFStream). cheers, - John
