unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: "Pierre Neidhardt" <mail@ambrevar.xyz>
Cc: "Jan" <tona_kosmicznego_smiecia@interia.pl>,
	"guix-devel" <guix-devel@gnu.org>
Subject: Re: Jami: Bug source investigation
Date: Sun, 03 May 2020 15:28:57 +0000	[thread overview]
Message-ID: <171db27993d.cf8754fc1904.4895809640014533332@zoho.com> (raw)
In-Reply-To: <87d07lyr86.fsf@ambrevar.xyz>

 ---- On Sun, 03 May 2020 15:26:33 +0000 Pierre Neidhardt <mail@ambrevar.xyz> wrote ----
 > Jan <tona_kosmicznego_smiecia@interia.pl> writes:
 > 
 > > Calls over WAN are always tricky, I had little luck with that even with
 > > the official Jami binary packages. With some friends everything works
 > > 100%, with other nothing works. I guess that's because of outdated
 > > proprietary router/modem firmware and hostility towards p2p.
 > > Try disabling firewall on your router (yeah I know, sounds bad).
 > 
 > Sadly I can't do that on my friends routers :(
 > As long as this issue persists, this makes Jami not so useful as a
 > communication tool.

Sad :(


  reply	other threads:[~2020-05-03 15:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 23:20 Jami: Bug source investigation Jan
2020-04-13 21:21 ` Jami: Bug source investigation (help needed) Jan
2020-04-15 18:31 ` Jami: Bug source investigation Marius Bakke
2020-04-15 18:54   ` Jan
2020-04-16  8:16     ` Pierre Neidhardt
2020-04-16 11:57       ` Jan
2020-04-17  0:53       ` Jan
2020-05-03  7:54         ` Pierre Neidhardt
2020-05-03 14:05           ` Jan
2020-05-03 14:17             ` Pierre Neidhardt
2020-05-03 14:50               ` Jan
2020-05-03 15:26                 ` Pierre Neidhardt
2020-05-03 15:28                   ` sirgazil [this message]
2020-05-03 16:11                   ` Jan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=171db27993d.cf8754fc1904.4895809640014533332@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    --cc=tona_kosmicznego_smiecia@interia.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).