[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-users] minimal flexisip proxy configuration?

From: Brian J. Murrell
Subject: Re: [Linphone-users] minimal flexisip proxy configuration?
Date: Wed, 05 Jun 2019 12:28:22 -0400
User-agent: Evolution 3.32.2 (3.32.2-1.fc30)

On Wed, 2019-06-05 at 11:41 -0400, Greg Troxel wrote:
> Thanks for the explanation and discussion.  I am guessing then that
> fromt he point of view of Asterisk the user just registers once,

Well, it's flexisip that registers to Asterisk on behalf of the user
and keeps the registration alive like a local hardwired SIP client
would, rather than the disappearing act that mobile phones do.

> and
> when the user goes actually offline bug logically online the
> connection
> to asterisk, including registration keepalives, continues,

Correct.  Flexisip, with all of it's reliability of being on the same
local network is the actual SIP client to Asterisk.

> and the proxy
> is then responsible for buffering the INVITE and waking up the
> client.


> That is part of why it is confusing, that people and programs talk of
> configuring a "sip proxy" into their client, rather than "server"
> which
> might or might not be a proxy.


> It's flexisip; you can run a web server as a "reverse proxy" fronting
> a
> web server, as opposed to a near-the-user squid which is a "(forward)
> proxy".

Yeah.  In your analogy then, I guess you'd drop the squid proxy.  My
alteration of your analogy could still be pretty much the same except
that instead of it being the web-browser user that stands up an HTTP
2.x -> HTTP 1.x proxy for all of his browsing, it's the web-server
owner standing up the HTTP 2.x -> HTTP 1.x proxy in front his "crufty
old" HTTP 1.x-only-capable web server to provide an HTTP 2.x service to

Presumably this would just be a temporary situation until he could get
a native HTTP 2.x web server stood up much like in the SIP world, we
are waiting for servers (and clients even) to implement native
transient (i.e. mobile phone) SIP client handling.

> As I understand it, "sip proxy" is usually near the server, but could
> also be near the client for firewall traversal.

I think you understanding is correct in both aspects.


Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]