24 Feb
2003
24 Feb
'03
4:47 a.m.
On Mon, Feb 24, 2003 at 01:07:14AM +0100, Jiri Kuthan wrote:
Just passing on what I'm seeing. If there's more information that I can
provide I'd be happy to.
Right now, the phones are configured on the two destination servers.
So, these servers can send calls directly to the phones. However, for
things to work properly (outbound calls and such), the server needs to
see the incoming request as originating from the phone's IP address,
which is why the stateful forwarding is currently a problem.
--
Jamin W. Collins
At 12:30 AM 2/24/2003, Jamin W. Collins wrote:
I'm just passing on what I'm seeing. If I forward the request with
forward("192.168.1.16"), the server shows the connection as the IP
address of the originating phone. However, if I use
t_relay_to("192.168.1.16", "5060"), the server shows the connection
as
coming from the SER server and the connection never truly completes.
I've also tried different variations with append_branch and t_relay,
these have led to similar results as the t_relay_to.
It's something of a catch-22. If I use a
stateless forward, the
server that it's forwarded to sees the connection as originating
from the actual phone's IP.
There is some disconnect here -- be a request forwarded by a proxy
statefuly or statelessly, it arrives always in the same shape to the
destination. In particular, proxy server's address is in IP packet's
source address and in Via. If I use a
stateful forward, the connection is seen as coming from
the SER server itself, and as a result the audio path fails.
Audio is sent to the address advertised in SDP, which is not
manipulated by SER. Is there a way
to configure it so the phones are not required to
register with the SER proxy?
You don't need to configure your server so that phones do not
regsiter with it -- that's a phone configuration issue. however,
it will not be easy to route requests to your phones if they do
not register.