text telephony Requirements

Nancy-M Greene ngreene at NORTELNETWORKS.COM
Mon May 3 23:49:52 EDT 1999


Gunnar, thanks for reviewing the requirements document. I have incorporated
the changes you suggested. See below for the relevant references in the new
draft-ietf-megaco-reqs-03.txt document.

Nancy
--------------------------------------------------------------------------
Nancy M. Greene
Internet & Service Provider Networks, Nortel Networks
T:514-271-7221 (internal:ESN853-1077) E:ngreene at nortelnetworks.com

> ----------
> From:         Gunnar Hellstrom[SMTP:gunnar.hellstrom at OMNITOR.SE]
> Sent:         Thursday, April 22, 1999 5:38 PM
> To:   MEGACO at standards.nortelnetworks.com
> Subject:      Re: Media Gateway Control Requirements
>
>  Previously sent to ITU-T Q13/16:
>
> I checked the Megaco requirements mainly from the point of view of how
> well
> it covers gatewaying between different forms of real time text
> conversation
> facilities. The most apparent need is between the current analogue network
> based text telephones and IP text phones that are in the process of being
> defined in SG16. The current textphones are working with different types
> of
> modem-like signalling ( that all can be joined by the V.18 modem in the
> gateway) while in IP networks it is T.140 carried by a data protocol.
>
> With the current efforts in the US to arrange some kind of gateway between
> land based text telephony and mobile text telephony, work in this
> direction
> is already going on.
>
> I found very little influence. And that might pose a question: Is Megaco
> too vague, does it need to get more specific in its requirements to really
> imply something?
> But that might be the next step - the protocols and functions.
> I want to suggest the following modifications to specifically mention the
> important real time text gatewaying:
> --------------------------------------------------------------------------
> ---
> 5.2 d : insert "text" together with the other media, to read "e.g. audio,
> text, video, T.120 )
ok

> 5.3 d : insert "text telephony" before FAX
ok

> 11. Table 1. I am not sure what this table indicates. All multimedia
> protocols are missing. Is it some kind of very basic mandatory media
> requirements?
> Without really knowing, I recommend:  For ISDN, add Multi-media to the
> applications.
Multimedia added for Trunk+ISUP, Trunk+MF, and ISDN.

>     For Analogue, and Restricted, add Text telephony after FAX.
Text Telephony added for Analogue, but I missed adding it to Restricted -
will do this for next revision.

> Insert a new section 11.2.4 ( pushing the existing down one step)
> 11.2.4 Trunking/Access Gateway with text telephone access ports
ok, but this section will only survive if someone lists specific
requirements that belong here that are not covered elsewhere. Same goes for
all other sections with no text in them.

> 11.2.10 IVR Unit
> Insert a requirement: IVR should never be the only way to control the MG.
> Text based and web based control are important alternatives.
11.2.11 r) added:
r.   Be able to support an IVR unit that provides text-based and/or
     web-based prompts instead of audio-based prompts.


> Accepted?
yes, thanks.

> Gunnar Hellström
>
>



More information about the sg16-avd mailing list