With the transition from MobileMe to iCloud some valued service are dropped. The one I’ll miss the most is the keychain sync between all the machines. That frankly was the reason in the first place, why I bought MobileMe. But a good friend of mine felt the same pain and created a perfect replacement, which is called Keychain2Go.
Since 10.7.2 it is possible not only find my iPhone, but also to find my Mac. I’ve added all of them to the iCloud service and used the sosumi php scripts to get the data.
Since today the iCloud is available to the public and you can use it to find your iPhone. The location service I described also works with iCloud accounts.
This is part 3 of the DIY Location mapping. This time we will integrate with google earth to see live updates from our devices, we tracked with part 1.
Therefore I have had the tracking running for some days with an update interval of 15 minutes, so that I does not drain my battery too much. By enhancing the update frequency you will get fine grained location data.
We need to add the following PHP script to deliver a valid KML file, which is loaded by another KML file. The second KML file is loaded into Google Earth and does poll data via the PHP scripts to enable the live updates. Continue reading
Inspired by the question in the http://fanbóys.org/ podcast, I will write down, what I have up and running for over two years now.
Goal: Have a background method running, which collects your location during the day and displays it on a map and has some export functionality.
Ingredients: An Apple iPhone, an Apple ID, activated Find My iPhone, a LAMP system and additional Google Maps. Continue reading
After being bugged with yearly broken headphones. I invested a bit more money and got these awesome metal rugged ones. They are perfect.
The idea of behind the way multitasking is handle in iOS, is to keep the battery life in a good shape and just keep the tcp sockets so far connected to wake the application, when something is happening on the connection.
The most VoIP application are using SIP, which is normally running on udp. And udp is not available for backgrounded application. So you might also get SIP via tcp, which has it‘s own merits and caveats.
SIP uses udp for the low latency and jitter purpose. It usually is okay for a listener, if some of the packets never made it to you and are dropped. We are all used to bad lines, we do not rely on perfect transmission. Means, it‘s fine to get crystal clear lines, but we also understand the opposite, if the drops are below a certain limit. udp is just build for that purpose.
Tcp on the other hand does retransmit packets until they reached the target, even if it has to stop the transmitting until this one piece of information has travelled. So with sip over tcp, the problem is not that we hear a bad line, but we could hear paused conversation, like stop and go on the highway.
If these stops getting above a level, our communication breaks down.
Technically there are some ways around this problem.
- Easiest way would be, not to stop the application. No background, no multicast, but working VoIP phone.
- Next idea: Use the tcp variant, which works perfect in public reachable networks. It will not work through nat or double nat setups and although not in vpn setups. But, we have multicast. And you should not leave the wifi you logged into the VoIP application, as the socket keeps that IP. So if you fallback to 3G or GSM, the connection is broke.
- Use of push notification. That could solve this disconnection bug of the previous idea. But you still need to have a public visible for VoIP server. No nat, double nat or vpn setups. And the biggest problem of all, you are going to give the push notification provider (aka your sip app programmer) your login in credentials to your sip account to be your proxy.
- So this is the setup I‘ll use to have a work around. My asterisk box notifies me via XMPP (jabber) of incoming phones calls. These jabber messages are using push notification to get to my jabber app (IM+). For privacy concerns, I have setup an extra account just for this. When I tap on the dialer number, I‘ll copy‘n‘paste them into the voip application, which uses my already discussed secure vpn sip connection. Not perfect, but working.
- One future way out of this would be IPV6, as there are no need for nat-ing and we could use IPSEC for encryption. iOS4.x supports IPV6 already….
this is an update to my previous entry, and does explain the architecture and all the steps you’ll need to set it up.
We make use of the pptp capabilities of iOS and build an pptp tunnel to a fixed server @.
From there we have an openvpn tunnel to our asterisk box *, which has ISDN links to the PSTN.
Routing makes shure, that all SIP traffic is shoveled between the endpoints.
Voilà encrypted calls, with your favourite SIP app.
Visited the iPhonedDevCamp in Munich today. Very nice.
Finally after the launch of OS 3.0 for the iPhone, the Application IM+ updates to Version 3.1. push notifications are not done via email anymore, they now use Apples push notification service. Continue reading
Part 1 of Geocaching with the iPhone
How to use Maps to find your cache
Maps does not have any direct support with the geocaching.com site. Nor any support for paperless geocaching. But if you have your coordinates with you, you are not lost. Maps accept the following as a valid coordinate entry:
48 09.423 11 23.648 (which translates into N 48° 09.423′ and E 11° 23.648′)
I generated a small presentation on how to connect an IPhone with an Asterisk server through pptp VPN.
Watch this short presentation Secure IPhone
or see the complete story with tutorial videos: I generated a small presentation on how to connect an IPhone with an Asterisk server through pptp VPN.
Watch this short presentation Secure IPhone
or see the complete story with tutorial videos: Continue reading