Gmail Numeric Code 6922 issue

provides particulars for delivering messages to associated recipients, presently, subscriber 120. For instance, assume subscriber 120 wants all received oral messages to be stored in voice mail and translated into text messages, that

such text messages be sent to an e-mailbox, and that summaries of such text messages be sent to message pager 125.

Translating controller 205, via messaging Gmail Numeric Code 6922 issue controller 210, prompts caller 105 for, and receives, an oral message input representing the body of a message for subscriber 120 (input/output step 340). Translating controller 205 processes

the oral message and translates the same into a proposed text message (process step 345; discussed further with reference to FIG. 5).

According to the present embodiment, translating controller 205 accesses data repository 200 to store the received message input therein and to access the stored data patterns. Controller 205 separates the message input into sub-parts,

at least some of which have one or more measurable characteristics (e.g., phonemes). Translating controller 205 compares such measurable characteristics and the stored data patterns, and generates at least a substantially equivalent

text message in response thereto. The generated text message is a concatenation of data patterns that represent those sub-parts, or groups of sub-parts, separately, or collectively, that compare most favorably. In alternate embodiments,

any conventional speech recognition system, or engine, that can suitably use a vocabulary specific to message paging system 100, such as a vocabulary defined using APPENDIX A, may be used.

Messaging controller 210 transmits, via messaging network 135, at least part of the generated text message to subscriber 120 having message pager 125 (output step 350). According to the present embodiment, translating controller 205, in

Leave a comment

Design a site like this with WordPress.com
Get started