The telco has told a parliamentary inquiry into the Australia and New Zealand Closer Economic Relations (CER) trade agreement there were many benefits in a single market.
Telstra regulatory affairs manager Dr Tony Warren said Australian and New Zealand travellers could save more than $30 million a year in international mobile roaming charges.
Mobile charges could fall from an international roaming rate of up to $2.80 per minute to domestic rates - which vary from 36 cents a minute to $1 a minute depending on the plan.
"You could call Coogee or Bondi by mobile like they were suburbs of Auckland," Dr Warren said in a statement.
Other benefits included savings on the rollout of new technology and networks, a single contract and bill for trans-Tasman businesses, cuts in red tape and a trans-Tasman mobile market with operators offering subscribers seamless service on both sides of the Tasman.
Yeah, right. Like all New Zealanders have a reason to call Bondi...
What worries me is that they might as well pull this one off - just check Air New Zealand and QANTAS. They couldn't merge, but they managed to get to the code share point. Where to from here?
We have quite a collection of articles about this topic here on Geekzone, including configuration tips for Windows Mobile AUTD (the original version deployed with Windows Mobile 2003), an overview of Windows Mobile MSFP, and an end-user view of Windows Mobile Direct Push and other features introduced with AKU2.
If you want more detailed troubleshooting steps for Windows Mobile MSFP, I suggest you check this blog entry Direct push is just a heartbeat away.
Exchange 2003 introduced the Always Up To Date notification feature (AUTD) that kept devices up to date by sending SMS triggers to the device. The triggers were sent from the enterprise as SMTP messages to the SMTP front end at the mobile operator. They were then sent through the SMS gateway as SMS messages to the device. This approach had some limitations since not all mobile operators did the SMTP to SMS conversion. Even when they did, there was latency involved with SMS messages and there were end-to-end reliability issues. Also some mobile operators charged for each incoming SMS message so that added an extra dimension to the cost of staying up to date. To alleviate these issues, Exchange 2003 SP2 introduced Direct Push.
Direct Push is a client initiated HTTP connection to the server where the device opens a connection to the Exchange Server and keeps it alive for a duration known as the heartbeat interval. Basically the client sets up the connection, chooses the appropriate heartbeat interval and tears down and reestablishes the connection if and when necessary. The server sends notifications about new items over this connection and the client synchronizes to get the new items.
The blog post contains useful information about server configuration, device configuration, log analysis and more. Worth a read if you are an IT administrator planning or running a Microsoft Exchange Server installation.
I am participating this Sunday 23 April of a lunch session entitled From Spare Room to Board Room: Making great ideas into a successful business. Session description and speakers' profiles available here.
In this discussion Chris Auld, Mauricio Freitas (that's me) & Rod Drury will discuss their successes and learning experiences with their businesses, their plans for the future and where they see IT and software development going. This is an essential session for any budding business leaders wanting to start or grow a business from their passion in software.
In summary Telecom users can get up to 1GB (gigabyte) of cellular data (CDMA EV-DO) for NZ$49/month.
This compares with Vodafone's offering of 1GB on UMTS for the same NZ$49/month.
Other things are similar too: this is a limited time offer, with exipry date set to 9 July 2006 - in both cases.
What is different here? First speed: Telecom's CDMA EV-DO provides a great performance when compared with Vodafone's UMTS technology (and that was shown before). But really, if you are using this for single connections (such as mobile e-mail or FTP) this is not much benefit. But the speed advantage really shines when browsing websites, which is what most people will probably want to do.
After all 1GB/month is more than most New Zealanders use on their dial-up connections (yes, we are a nation of dial-up users), and for this price either option is a great alternative to services such as Woosh, which has been slow in extending coverage and providing better support (according to lots of discussions in our Geekzone Forums).
Another difference: while the Vodafone plan includes a free PC card for use on laptops, the Telecom plan requires users to purchase a card, which is an additional NZ$199. Both Vodafone and Telecom require a 24 month term contract.
While the Vodafone plan applies to new and existing customers, Telecom is offering the deal to new accounts only.
And Telecom is explicitly restricting the use of VoIP software over this connection, exaclty like Vodafone. Interesting, because until now Telecom did not put any restriction in place for this kind of usage.
Which plan is better for you? Really it comes to what are your requirements and since you are locked for 24 months with whatever operator you join make sure you look at this carefully.
If overseas travel is part of your job, then the Vodafone plan should be ok, but remember that data roaming is still charged at exhorbitant prices and not included in the NZ$49 deal. But if you want some good national coverage and perhaps better performance then the Telecom plan is for you.
Of course everything will change in September, when Vodafone New Zealand will launch a new high speed network, based on the HSDPA standard (more on Juha's blog).
The jury is out now.
First in the line was a HSDPA demo. Their current infrastructure supports 1.8Mbps, but they have plans to launch the service with support for 3.6Mbps. When? I was told September 2006 is the planned release date, but until then things can change.
The demo worked ok for streaming video clips, copying large files and such. It seems it adapts (or shape?) bandwidth based on use. Of course it was nice to see it working when you have a single user on a demo cell site. We still have to wait and see how real life load will affect performance on this environment.
The infrastructure is supplied and supported by Nokia. The main obstacle seems to be the availability of handsets and data cards supporting the new standard.
On this note I asked Phil Patel about fallback. Here in New Zealand UMTS users will fallback to GPRS when coverage is marginal or non-existant - but wouldn't be so nice to have EDGE instead of GPRS? Anyway, Patel tells me the initial plan is to have HSDPA covering the same UMTS footprint at least, and perhaps in the future migrate GPRS sites to UMTS for improved service. Nothing is certain though, except for the HSDPA plans.
It looks like the Linksys 3G Wi-Fi router we reviewed before will work just fine with HSDPA cards, so users will be able to have a faster wireless broadband alternative but just swapping cards (that is, if you already have the router). I have used the router for a month, and it impressed everyone: I was doing some consultancy work and the company didn't have wireless infrastructure, so I just brought my own network access point with me for that period.
Of note are the plans to release laptops with built-in cellular data support. The Lenovo T60 was on show, but Vodafone has plans to release at least other brands such as Acer and HP. Not confirmed yet, but under works are deals with Dell, Fujitsu and Toshiba. we can expect to see the first laptops coming out in the next two months or.
In terms of handsets Vodafone is on a roll. They plan to have up to 10 different Windows Mobile devices by the end of this year. This includes new entrants in the New Zealand market, such as Asus and Benq. I was told they are very keen on the Motorola Q as well, because it is such an appealing form factor, in direct competition with BlackBerry handhelds.
Talking about BlackBerry, I was shown the latest BlackBerry 8700 and I have to agree, it is very fast and it does have nice screen. But so is the Nokia N61. The BlackBerry 8700 is one of the new models based on the Intel xScale processors.
Also talked about was the integration of PBX systems and mobile services, including mobile desk phones. They look exactly like the kind of phone you would expect to find in any office, but without wires. Of course this is a transitional form factor, because the whole ide is to have a single device, and in this case the mobile phone form factor is better suited for the job. PBX functionality is provided at network level.
I was disapointed to find out that unlike Vodafone UK, Vodafone New Zealand is not planning to directly provide a push e-mail service based on Microsoft Exchange and Windows Mobile 5.0. Instead, clients who do not have a Microsoft Exchange server will be referred to a parner for a hosted solution. One of the partners is Auckland-based ICONZ for example.
On fixed and mobile convergence, the plan of having mobile phones receiving calls as local numbers (similar to what Vodagone Germany is doing) is still under work, pending some government regulations. As far as they are concerned they would launch this service pretty soon, but alas this will take sometime. The idea is to have a Vodafone number that would be treated as a local phone number when within a certain area (cell site coverage). Of course the main opposition to this idea comes from Telecom New Zealand.
I also asked about live TV. With the recent announcement of live streaming of Prime News it would be interesting to see if any plans of a full live TV channel is in the plans. Of course I asked about satellite broadcast, since streaming over a packet network is not the most effective way. According to Patel this is something that could be looked at, but nothing in the near future - or at least this year.
Overall Vodafone New Zealand showed an interesting and consistent approach to a variety of mobile services, but the most concrete action with most impact is certainly the new 1GB traffic plan for $49/month. For almost everything else we will have to wait a few months and see.
The native and best solution for Windows Mobile e-mail and push e-mail is still a Microsoft Exchange account. But not every company can afford to run their own e-mail infrastructure (both in terms of software costs, administration, hardware infrastructure), but IMAP and POP3 protocols are implemented on mobile devices, and it's interesting to read about someone's experiences in real life.
Our company mail-systems are based on IMAP: our IT department, like many IT departments, knows that allowing POP3 introduces big risks in losing mail. This can be either in one of the many synchronizations to clients or by losing the device which stores the mail alltogether. Therefore we have to use regular IMAP-functionality of the Windows Mobile mail client: Pocket Outlook. According to the specifications of Windows Mobile, it should work. I am using this combination for a year now, so i was pretty confident that it would be a solution without any problems. I am a very technocratic user of e-mail: all mail that is not new should not be on the server. How little did I know about the totally different approaches of my colleagues for reading e-mail and the problems they cause in use on a mobile device...The article goes on to discuss strategies on synchronisation and e-mail management.
Microsofts implementation of the IMAP protocol isn't one of the best, the general impression is that the POP implementation has had a lot more attention. My colleague found out the hard way. He started downloading the messages in his inbox, but the downloading did not complete. It simply stopped halfway. Upon closer investigation, we discovered something: the client tried to download his entire inbox, despite the setting to limit the view only to the mails recieved in the last three days. Pocket Outlook downloaded them anyway. Downloading his entire mailbox became problematic, since his mailbox contained more than 6000 messages and the mobile device simply could not deal with the volume of the mailbox: it took about two hours before the device ran out of the memory and hung itself. So handling one big inbox through IMAP is not really an option, even with limiting the view severly.
Some companies offer hosted Exchange accounts, including push e-mail options. One of these companies is 4Smartphone.net (affiliate link). The synchronisation of a Windows Mobile device with an Exchange server is flawless and performance is greatly improved with Windows Mobile 5.0 AKU2 and Microsoft Exchange 2003 SP2.
David is an IT Coordinator, but he was actually a mechanic before being involved in a car accident that left him with a disability (C4 quadriplegic). His blog tells us about solving problems and getting the most out of life.
And that's why this Tablet PC review is something everyone interested in technology should read.
Via the UberTablet blog.
Help us donate server software to a New Zealand school or charity organisation: we accept suggestions
As part of the worldwide launch of Microsoft Windows Server 2003 R2, thanks to Microsoft and Culminis, I have been given a few copies of Windows Server 2003 R2 Enterprise Edition (25 Cals) for giveaway.
Since we have lots of companies already using this server software in our groups, I thought an interesting way to help others would be by donating two copies of this software to a couple of school or groups with direct actions and impact on the community (one copy each).
Schools could use this fo administrative purposes, or in a tech lab for teaching purposes. Non-profit organisations can use the software for administrative purposes.
The rules are simple: if you want to nominate a New Zealand-based school or non-profit organisation to receive a copy of this software on DVD (NFR), then post your suggestion as a comment on this blog entry.
We will draw two schools or non-profit organisation from all suggestions, contact them and arrange to have the software delivered.
Also, if your suggestion is the lucky one, I will send you a Windows Server water bottle.
We are not donating the hardware. This is the server software only, so you should be sure that the organisation you are suggesting can arrange proper hardware to be used - perhaps someone else reading this blog post can arrange some desktop to be donated to run this software?
I will close the suggestions on Monday 24 April 2006.
Note that we expect suggestions to point to active groups, not some Church of the Flying Spagetthi Monster, sect or political party.
I am just playing around with it now, and I can see they have SMS notification for events, although the list of mobile operators seems to be limited to US-based carriers. It would be interesting if it would allow SMS address in the format [phone]@[operator.com] for example for those with e-mail-to-SMS gateways.
I've read on News.com that Google plans to launch synchronisation tools, including Exchange, Outlook, iCalendar, and even mobile devices, albeit no specific type is listed (no word if this would be with a Palm, Symbian, Windows Mobile or SyncML-compatible feature phones).
Each event can be individual, or with invited guests. Like other solutions, guests are notified through an e-mail, although I tried this using some of my test e-mail accounts and no e-mail was received. Perhaps they are only sending to GMAIL accounts, or having problems at the moment?
The service also sends a daily agenda, every morning at 5am, your local time.
If you want to start using Google Calendar now, it allows you to load a file with iCal or VCAL formatted events.
An interesting feature is the "Event Publisher". If a website mentions events, including shows, bookings, meetings, then an entry can be automatically added to the Google Calendar from an icon on the website. This is done through a specially formatted URL and an icon that looks like this:
Now, back to testing this new feature.
Update: the problem with the e-mail notifications not being received is probably due to overload. The notifications did arrive, some 4 hours after being sent. At the same time, other users report errors while trying to access Google Calendar. I would have thought that Google was going to make sure enough resources were available, after the load of problems experienced before with Google Pages and Google Analytics.
I removed a couple of applications I thought could be causing this problem (task manager, battery meters, etc) but the behaviour was still there.
Next step was to remove all software - short of a hard reset, and the Pocket PC in question is working fine since then.
What is really annoying is that a second Pocket PC (another model though) works perfectly well with the same mix of software.
I am now going to reinstall one by one and see when the problem happens. It may be a slow process, since the lock up used to happen only two or three times a day.
Does anyone know of a better way of finding the culprit?