1. 1 msXmms incorporates the MAAD Tool which carries the Designed for Windows 2000/Windows XP logo Support for Exchange 2003 Server confirmed

2. 2 msXmms F A corporate solution for Microsoft Exchange 2000/2003 customers F Ability to send SMS and eventually MMS messages. Ability to receive SMS & MMS messages into Outlook. F Leverage investments in Active Directory and Exchange Server from Microsoft.

3. 3 msXmms F Why call the product msXmms? –MMS - Multi-Media Messaging for mobile phones is the next generation of rich messaging services between mobile devices and gateways. –SMS is the existing short message service –msXmms will support SMS first then MMS. –By 2006 people will only talk about MMS, SMS will be considered just a part of MMS ie: longer message text.

4. 4 What is MMS F Multi-media messaging (let Optus show you. Follow the url below and click online demo half way down the page) F http://www.optus.com.au/Vign/ViewMgmt/disp lay/0,2627,1008_27846-3_24042-- View_360,00.html http://www.optus.com.au/Vign/ViewMgmt/disp lay/0,2627,1008_27846-3_24042-- View_360,00.html F msXmms provides a well integrated AD/E2K software implementation for Corporate & Government

5. 5 msXmms partners F BNS Group has selected its first partner for interfacing to the existing SMS network.

6. 6 F http://www.mobilemessenger.com.au http://www.mobilemessenger.com.au Click on the globe for a list of SMS destinations serviced

7. 7 Large SMS and MMS Customers requirements? F All authorisation and controls via Active Directory (AD). F Accountability. F File name tracking. (Message tracking in E2K) F Subject filtering to comply with Government requirements for unclassified messages F No client software (unless absolutely necessary) F No extension of AD schema F Nothing installed on Exchange server F Implemented as a back end service

8. 8 Designed for the enterprise

9. 9 Systems Integrators F Minimize risk – msXmms does not install anything on the customers Exchange Server. F Schema is not extended – minimize risk F No client software to deploy. Optional client software will be available. F Supports Exchange 2000 & 2003 servers, Exchange cluster F Runs on Win2K server. Windows 2003 Server will be supported.

10. 10 Runs on msXfax xp fax servers F Co-exists on the same hardware as msXfax XP. YES! F msXfax XP is a world leading enterprise fax solution for Exchange 2000/2003 customers. F More information on msXfax XP can be found at http://www.bnsgroup.com.auhttp://www.bnsgroup.com.au

11. 11 Well integrated F msXmms will use XML and interface where possible using Microsoft.Net web services. F Contacts and public folder contact support. AD Contacts. One off addressing F Selected user calendars accessed for alerts of appointments

12. 12 Typical comments from Systems Integrators "msXmms for Exchange 2000/2003 offers large account customers a low risk installation because no client software is required and it leverages Microsoft Active Directory for authorisation, message restriction controls, cost centre accounting (without extending the schema). For Australian Government accounts, msXmms filters message content to ensure that only messages containing unclassified in subject fields can be sent via SMS or MMS – Warren Prentice, Infrastructure Architect EDS Australia – Australian Taxation Office Account

13. 13 MMS & SMS message flow Note: msXmms is targeted at medium to large enterprise customers deploying Exchange 2000 or Exchange 2003 networks where control and authorisation is a critical business requirement Small account customers should consider client / gateway solutions designed for low end solutions which requires desktop client software to communicate directly with a service provider.

14. 14 Sending MMS messages using Active Directory (global address list)

15. 15 Cut to the chase! Send the message

16. 16 Picture sent from Outlook!

17. 17 Key staff or customers who must be contacted via SMS or MMS can be added to Active Directory

18. 18 Outlook user also defined as an Active Directory Contact Only Gail Buchanan can send to Laurence Buchanan. This is standard security built into Microsoft Active Directory and Exchange 2000/2003 Message size restrictions built into Microsoft Active Directory and Exchange 2000/2003

19. 19 Sending MMS messages using Active Directory (global address list)

20. 20 Outlook user sending MMS & SMS (Enabled via a keyword) All sms and mms messages sent by this user are logged to a database in msXmms. [cc:sales001] is the cost center to be charged for internal billing purposes [if msXfax is installed at the site, [FaxEnabled} keyword can also be defined or a global default to allow ALL users to fax

21. 21 Harness the power of Microsoft Exchange and AD

22. 22 Harness the power of Microsoft Exchange and AD Using Exchange Distribution groups to alert key staff of terrorist alerts is an example of how Exchange/AD can be used effectively with Microsoft Certified Partner solutions to deliver value added services tailored to meet customer requirements

23. 23 Harness the power of Microsoft Exchange and AD Control who can send to the list

24. 24 Harness the power of Microsoft Exchange and AD Fax machines located at home residence can be added to AD in such a manner to ensure that this user is notified via email, MMS (SMS) and by Facsimile transmission

25. 25 Software Architecture ADSI/LDAP refers to Global Catalog server/DC Microsoft.Net framework required

26. 26 SAP and Other application interfaces F SAP Exchange Connector supported similar to fax routing from SAP to msXfax XP and msXmms. F Customers with SAP can therefore route SMS and MMS alerts via Exchange. msXmms will validate application in AD being authorised to send F A file based pickup API will be built into msXmms allowing almost any application to interface to SMS and MMS services

27. 27 Example msXmms Servers 10.1.1.91 (Primary) 10.1.1.92 (Secondary) Dual servers for redundancy Simply configure a Microsoft Exchange SMTP Connector

28. 28 Fail over – Exchange cluster connector will deliver to standby server in the event of a failure in a primary msXmms server failure

29. 29 SMS & MMS Delivery Notifications similar to msXfax notifications – eg: sms sent – original subject

30. 30 SMS & MMS transmission details similar to msXfax Similar to msXfax XP Confirmation of delivery to service provider

31. 31 Reporting F Detailed reporting F Report on SMS & MMS sent

32. 32 msXmms Summary F AD Aware without extending the schema F Does not install ANY components on your Exchange Server. (Subject to CDO/Calendaring performance considerations). F Supports Exchange 2000 and Exchange 2003 servers (including cluster configurations) F Allows message creation using Contacts, Global Address list contacts, one off addresses and Application Interfaces F Nothing to deploy on the desktop (optional client software will be considered) F Allows billing & cost center reporting F Detailed logging & diagnostics built in F MMC management console snap-in F Co-exists with msXfax XP to minimise hardware and support investment. F BNS offering replacement deals for existing fax connector/fax server licences.

33. 33 More information F Sales enquiries sales@bnsgroup.com.ausales@bnsgroup.com.au F Channels & Partnering enquiries Laurence Buchanan Marketing Director LVB@BNSGROUP.COM.AU LVB@BNSGROUP.COM.AU