TIP: Click on subject to list as thread! ANSI
echo: ftsc_public
to: RICHARD MENEDETTER
from: MARKUS RESCHKE
date: 2017-12-28 13:55:00
subject: Future Applications

Hi Richard!

Dec 28 12:49 2017, Richard Menedetter wrote to Dale Shipp:

 RM> What do we learn from it??
 RM> Simply ... texts should be written in a way that is unambiguous.

Absolutely right! For example, there's a very annoying misinterpretation of the
RFC for SIP. The RFC doesn't state anything on which codecs to use for both
directions (caller/callee), i.e. same or different codecs. Some vendors simply
assume both directions must use the same codec. Other vendors support different
codecs for both directions. So you get one-way audio if you use the wrong
combination of SIP phones/PBXs. It's so  :(

ciao,
Markus

--- 
* Origin: *** theca tabellaria *** (2:240/1661)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.