[bbs-revival] Plans for #36C3 / Status Report

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/bbs-revival@lists.osmocom.org/.

Ingo Jürgensmann ij at amigaxess.de
Mon Oct 21 06:01:36 UTC 2019


Am 21.10.2019 um 07:40 schrieb Christian Berger <christian at clarke-3.de>:

> On 20.10.19 23:14, Ingo Jürgensmann wrote:
>> So, basically it is working. Cisco documentation for fax setup in voice routers states that no more than 14.4k is supported. 
> Cisco is probably referring to T.38 which is something completely
> different. Cisco is actually one of the worst companies in regards to
> SIP. They speak weird edge-cases of the protocol and force G.729 onto
> their users.
> T.38 actually is a protocol you could have a lot of fun with as it's
> fairly complicated, but flexible and has lots of broken implementations
> even on devices like the AVM Fritz!Box. There are Fax machines which
> will refuse to work with T.38 on a Fritz!Box as they will reliably
> trigger that bug.

Well, the main argument in my previous mail was not Cisco but that modem connections are basically working via SIP connections, although you might not get your desired connection speed. Distance between both locations were >450km. 
So, as previously stated: I think it’s worth to collect some more experience on 36c3, although I know as well that many BBS/FTN sysops are still receiving calls via phones lines (behind IP) and it’s working. 

:-)

-- 
Ciao...          //        http://blog.windfluechter.net
      Ingo     \X/     XMPP: ij at jabber.windfluechter.net
	
gpg pubkey:  http://www.juergensmann.de/ij_public_key.asc






More information about the bbs-revival mailing list