Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #37711
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: sending a "beep" from computer to mobile phone? |
| Date | 2023-04-03 20:30 +0200 |
| Message-ID | <oiirfjx736.ln2@Telcontar.valinor> (permalink) |
| References | (4 earlier) <u02beo@dont-email.me> <f93f84f5dab0f33528d02438caba3cde@msgid.frell.theremailer.net> <u0csdl$2l9ii$1@dont-email.me> <4enpfjxksc.ln2@Telcontar.valinor> <u0ebe4$2uh60$1@dont-email.me> |
On 2023-04-03 12:57, Pancho wrote: > On 03/04/2023 02:40, Carlos E.R. wrote: >> On 2023-04-02 23:34, Pancho wrote: >>> On 4/1/23 23:06, Fritz Wuehler wrote: >>>> Pancho <Pancho.Jo...@Proton.Me> [P]: >>>> P> The problem with android VoIP softphones is that they tend to >>>> P> deregister. So the ring isn't reliable. >>>> >>>> You just don't get it, do you? Calling a device by its (LAN) IP has >>>> no need for registration. Try it some time and see how it goes. >>>> >>> >>> Yes, that is a good point. But difficult to test, reliably. VoIP >>> already works, most of the time. >>> >>> Also, I don't know if my IP address does change regularly. Obviously, >>> it does when the phone moves between my wlan and the mobile/cell >>> network, >> >> You forget we are talking of LAN alone. > > No, I understand that, but I have 10 years experience of Android VoIP > softphones being unreliable. I'm not sure why they are unreliable, just > a history of mild interest, and consequent prejudice. > > Someone can say my issues are due to changing external IP, that it won't > happen in a LAN environment, and they may be right, but I don't have > evidence of that. > > Suggesting one potential failure mechanism does not exclude other > mechanisms. You haven't excluded the possibility that aggressive power > saving requirements, and consequent sleep states, cause the problem. > > If someone could point to real life experience of an Andorid VoIP > clients working reliably on a LAN, with direct IP calls, or probably > more tractably via a LAN base PBX such as Asterisk, I would be more > convinced. Have you tried to setup a phone VoIP client without a registrar, on the LAN? It is a different beast altogether. Yes, of course it can fail, that is not the point. And I am not going to use for my use case, but that is not the point either. -- Cheers, Carlos.
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
sending a "beep" from computer to mobile phone? "Carlos E.R." <robin_listas@es.invalid> - 2023-03-27 14:53 +0200
Re: sending a "beep" from computer to mobile phone? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-03-27 18:13 +0000
Re: sending a "beep" from computer to mobile phone? "Carlos E.R." <robin_listas@es.invalid> - 2023-03-28 00:33 +0200
Re: sending a "beep" from computer to mobile phone? Andreas Kohlbach <ank@spamfence.net> - 2023-03-27 17:08 -0400
Re: sending a "beep" from computer to mobile phone? "Carlos E.R." <robin_listas@es.invalid> - 2023-03-28 00:31 +0200
Re: sending a "beep" from computer to mobile phone? "27E.G756" <27E.G756@noq24u.net> - 2023-03-28 22:08 -0400
Re: sending a "beep" from computer to mobile phone? Fritz Wuehler <fritz@spamexpire-202303.rodent.frell.theremailer.net> - 2023-03-28 00:37 +0200
Re: sending a "beep" from computer to mobile phone? Pancho <Pancho.Jones@proton.me> - 2023-03-28 16:16 +0100
Re: sending a "beep" from computer to mobile phone? Fritz Wuehler <fritz@spamexpire-202303.rodent.frell.theremailer.net> - 2023-03-29 01:16 +0200
Re: sending a "beep" from computer to mobile phone? Pancho <Pancho.Jones@Proton.Me> - 2023-03-29 22:43 +0100
Re: sending a "beep" from computer to mobile phone? Rich <rich@example.invalid> - 2023-03-29 22:16 +0000
Re: sending a "beep" from computer to mobile phone? Pancho <Pancho.Jones@proton.me> - 2023-03-30 09:19 +0100
Re: sending a "beep" from computer to mobile phone? Rich <rich@example.invalid> - 2023-03-30 13:04 +0000
Re: sending a "beep" from computer to mobile phone? Fritz Wuehler <fritz@spamexpire-202303.rodent.frell.theremailer.net> - 2023-03-30 15:01 +0200
Re: sending a "beep" from computer to mobile phone? Fritz Wuehler <fritz@spamexpire-202304.rodent.frell.theremailer.net> - 2023-04-01 19:33 +0200
Re: sending a "beep" from computer to mobile phone? Fritz Wuehler <fritz@spamexpire-202304.rodent.frell.theremailer.net> - 2023-04-02 00:06 +0200
Re: sending a "beep" from computer to mobile phone? Pancho <Pancho.Jones@Proton.Me> - 2023-04-02 22:34 +0100
Re: sending a "beep" from computer to mobile phone? "Carlos E.R." <robin_listas@es.invalid> - 2023-04-03 03:40 +0200
Re: sending a "beep" from computer to mobile phone? Pancho <Pancho.Jones@proton.me> - 2023-04-03 11:57 +0100
Re: sending a "beep" from computer to mobile phone? "Carlos E.R." <robin_listas@es.invalid> - 2023-04-03 20:30 +0200
Re: sending a "beep" from computer to mobile phone? Pancho <Pancho.Jones@proton.me> - 2023-04-03 20:10 +0100
Re: sending a "beep" from computer to mobile phone? Fritz Wuehler <fritz@spamexpire-202304.rodent.frell.theremailer.net> - 2023-04-03 21:07 +0200
Re: sending a "beep" from computer to mobile phone? Pancho <Pancho.Jones@proton.me> - 2023-04-03 20:35 +0100
Re: sending a "beep" from computer to mobile phone? Fritz Wuehler <fritz@spamexpire-202303.rodent.frell.theremailer.net> - 2023-03-28 03:26 +0200
Re: sending a "beep" from computer to mobile phone? Joe Beanfish <joebeanfish@nospam.duh> - 2023-03-28 14:12 +0000
Re: sending a "beep" from computer to mobile phone? "Carlos E. R." <robin_listas@es.invalid> - 2023-03-28 18:01 +0200
Re: sending a "beep" from computer to mobile phone? Rich <rich@example.invalid> - 2023-03-28 17:07 +0000
Re: sending a "beep" from computer to mobile phone? "Carlos E. R." <robin_listas@es.invalid> - 2023-03-28 21:00 +0200
Re: sending a "beep" from computer to mobile phone? "27E.G756" <27E.G756@noq24u.net> - 2023-03-28 23:10 -0400
Re: sending a "beep" from computer to mobile phone? "27E.G756" <27E.G756@noq24u.net> - 2023-03-28 22:07 -0400
csiph-web