Von: Scherer Wolfgang
Gesendet: Dienstag, 04. Dezember 2007 17:11
An: Product Unit News
Cc: Bauer Franz; Pösenhofer Manfred; Driza Karl-Heinz
Betreff: JAIN/SLEE Application Demo Proposal: "Voice Home Page"

Dear All,

I would like to propose an application idea for the JAIN/SLEE environment.

Unfortunately, I didn't manage up to now to conduct any talks with people from the JAIN/SLEE team, but I found it worthful to deposit the idea here:

Name: The Voice Home Page

Concept: An Individual or organisation shall be enabled to have a "Voice Home Page" compared to a Web Home page.

This is actually a bunch of small ideas, brought together under a common hood. This collection has been already discussed in KCC-AWISC, then carrying the name "personal voice portal" but nothing has come from it back then.

As the web page is a presentation of information provided by the owner and is addressed to the visitors, the "voice home page", abbreviated as VHP is the same, only the access method is different:

A visitor calls a certain phone number. This phone number is not the phone of the recipient but rather her/his VHP.

As with the web page, the visitor gets a certain amount of information as response, only that the information is presented in voice.

What is presented shall be determined by the owner by a "voice page editor". This tool may be a web-application supporting the owner to model her or his VHP much like the way "Home Page Generators" could do.

The CLI (Calling Line Identification) Feature of the phone network can be used to modify the presented information depending on the identity of the caller. 

But not only the identity of the caller can be used to control the information presented, but also other parameters like
  - time of day
  - current status of the owner
	-- status of the owner's mobile or fixed line phone 
	-- presence status on other telecomms services (IRC, skype, ...)
	-- schedule status taken from PIM or MS exchange, lotus domino etc
  - etc..

All these parameters shall be able to be used in a "presentation rule", like in active web pages, to determine where the voice call shall be routed and what information shall be fed back to the caller.

Information fed back to the caller can be:
  - recorded messages
  - text-to-speech translations of data content, e.g. from pages of the owner's "real" web page
  - absentee information ("I'm on hodilday until xx.xx.xxxx")

The presented information is always a compilation of voice "snippets".

Destinations where the call shall be routed can be:
  - another phone number
  - a voice mail recorder
  - the owner's real fixed or mobile phone
  - the owner's or any other VoIP account (regardless of being SIP or skype, etc ..)
  - another "Voice web page", presenting different information

Any "voice web page", in addition to presenting the information configured into it, may accept user interaction in the form of:
  - DigiTone input (phone keypad DTMF)
  - voice recognition, e.g. voice comands like "forward" "back" "repeat" ...

Implementation:

- voice snippets could be played as announcements by an appropiate media peripheral the the NGIN environment. 
- voice and DTMF recognition shiould be avalailable as IVR-peripherals in an existing NGIN environment.
- voice mail recording may be already existing as building blocks in existing NGIN requirement
	the whole machinery of a voice mail including replaying, managing, prompt recording etc may be implemented as
	a "voice web page" itself

Important side concept:

As the name says, the "voice home page" and the "web home page" should ideally be partners and present the same information. They should complement each other to form a pair of "multi-modal" access to a set of applciations, services and information.

One example for this is the management of voice mail messages:
By implemetning the voice mail service as a "voice web page" with an accompanying "web page", management of voice mail can be done either from the phone of via a web page:
- recording welcome message
- retrieving messages
- deleting messages
- forwaring messages as e-mails
- recording messages for specific callers
- marking received messages

Demo extent:

All the above looks like much work. For a Demo and somehow a feasibilty test, only a very small subset of all the functionality may need to be implemented. I wiuld, therefore, suggest the implementation of a basic "voice home page" for a selective "do not disturb" scenario:

1) all callers are greeted with a welcome message informing the owner is not available immediately
2) a list of callers (identified by the caller IDs) are nevertheless cut through to the fixed line of the owner
3) another list of callers (identified by the caller IDs) are given the opportunity to enter a 
	secret pass code given to them by the owner. If they provide the code in time, 
	they're cut through to the owner mobile phone
4) OPTIONAL: for another set of callers (identified by the caller IDs), there may be recorded messages by the owner. These are played to them.
5) OPTIONALLY, the messages of (4) may be protected by secret codes (to be entered via phone buttons) to make sure 
	the caller really is who she or he seems to be.
6) all other callers are played an announcement about when the owner will be available again and are forwarded to the voice mail 

Dear JAIN/SLEE experts:

If you now say: "This all is already existing", you would make me more than happy and the Demo could be set up like a breeze.

Kind Regards,

Wolfgang


--
Ing. Wolfgang SCHERER | Solution Architect | OSS/BSS Phone +43 (0)50811 3937 | Mobile +43 (0)664 6283937 Fax +43 (0)50811 3903 | E-Fax +43 (0)50811 983937 mailto:wolfgang.scherer@kapsch.net

Kapsch CarrierCom AG | Am Europlatz 5 | A-1120 Vienna | Austria www.kapschcarrier.com | www.kapsch.net Registered at Commercial Court in Vienna FN 223804z Registered Office Vienna