Roberto, Would there be any indication as to why behaviour may have changed between iOS4 and iOS5? I'll review the REGISTER config on the server and see what I need to do to get it to reuse the same socket for all future connections. I had a hunch that may be the issue but I was pretty much flummoxed that the version that had worked in the past had changed. I'll review and try getting it connecting ASAP. Appreciate the help. Cheers, Dan On Thursday, 20 October 2011 at 6:49 PM, Roberto Perez wrote: > Hi Dan, > > I'm using iOS5 and background socket is working without any problems. > We had some issues in the past though. Those issues were related with the different TCP sockets used by pjsip and server when registering and when receiving the INVITE. > > We use kamailio, and we had to configure the server to reuse the same TCP connection which was used to receive the REGISTER message, the default behaviour is to create a new connection. If a new connection is made, the "background" socket is not used and therefore, the call is not received. > > If you have access to your server, try to sniff the traffic (using tcpdump) in order to see which TCPconnection the server is using to send the INVITE. > > Regards. > Roberto. > > On Thu, Oct 20, 2011 at 9:33 AM, Dan Nolan <dan.james.nolan at gmail.com (mailto:dan.james.nolan at gmail.com)> wrote: > > Hi Evan, > > > > I was aware of the notifications issues and had changed them. I assume you're using it with your system. I think it may be a change in the version of Asterisk but I've held everything else static. Could you outline what config you're using on the device when you create a user account if at all possible? Any help to diagnose this issue would be awesome. > > > > Regards, > > > > Dan > > > > On Thursday, 20 October 2011 at 6:02 PM, Even Andr? Fiskvik wrote: > > > > > Hi Dan. > > > > > > We have it working fine in iOS 5. For compilation we used the approach I've mentioned in my earlier posts. > > > One funny thing that we didn't understand straight away though was that the notification setting for our app had been disabled > > > on a mobile, so the app couldn't trigger any notifications to the user. > > > > > > Since you say that you don't get any logging even when in background, I assume this is not the case for you. > > > But still I thought it would be a good idea to mention it for the list. > > > > > > Check that notifications are listed in "Notification Center" and enabled on for your app in: > > > Settings > Notifications. > > > > > > > > > Best regards, > > > Even Andr? > > > > > > On 20. okt. 2011, at 07:57, Dan Nolan wrote: > > > > Hi Guys, > > > > > > > > Sorry to bother again but I've come to the end of my tether. The same system that worked under iOS 4 to do backgrounding simply isn't working on iOS 5. I've recompiled pjsip from trunk, I've recompiled using the 1.10 tarred version, I've also tested iPJSUA and am having the same issues with background sockets receiving data. The Asterisk-based PBX I'm testing against has had no changes made to it between iOS 4 and iOS 5. It was working fine and TCP is working perfectly on it. > > > > > > > > If there is a call event in the background I simply get no logging whatsoever. Keepalives are firing in the background and the account is re-registering but it looks like, for whatever reason, that the socket is caching the data until I bring it back to the foreground. Has anyone been able to get pjsip working with backgrounding under iOS 5 - what settings did you change or things did you modify, if any? Are there any asterisk configuration changes I have to make, if any? I've noticed the inclusion of the ;ob parameter on the registrations but that shouldn't have any impact on the socket creation and setup, should it? > > > > > > > > I've gone through all of the mailing lists, played around with iPJSUA and its configuration, defaulted it to TCP and had registration working and am still struggling to get any feedback as to what needs to be tweaked or modified. I've tried a range of devices as well, an iPhone 4, an iPhone 4S, an iPhone 3GS and an iPod touch 4th generation just in case it is device specific. The socket is being created as a voip backgrounding socket but for some reason it's caching data that's sent to it. Any help at all would be hugely appreciated and I'm more than willing to help on any patches or put together any documentation that's needed to make sure other users don't have any issues with this system in the future. > > > > > > > > Regards, > > > > > > > > -- > > > > Dan Nolan > > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > > > > _______________________________________________ > > > > Visit our blog: http://blog.pjsip.org > > > > > > > > pjsip mailing list > > > > pjsip at lists.pjsip.org (mailto:pjsip at lists.pjsip.org) > > > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > > > _______________________________________________ > > > Visit our blog: http://blog.pjsip.org > > > > > > pjsip mailing list > > > pjsip at lists.pjsip.org (mailto:pjsip at lists.pjsip.org) > > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > > > _______________________________________________ > > Visit our blog: http://blog.pjsip.org > > > > pjsip mailing list > > pjsip at lists.pjsip.org (mailto:pjsip at lists.pjsip.org) > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > > > -- > http://zbutton.wordpress.com/ > blog sobre programaci?n y tecnolog?a > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org (mailto:pjsip at lists.pjsip.org) > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20111020/2d6bbd4b/attachment-0001.html>
