From: Roman Shpount [ro...@telurix.com]
UA opens a new TCP connection to the SIP proxy. This TCP connection will use a
new source port (this is normal for TCP). It will go through NAT again, which
will probably assign different public port to this connect
UA opens a new TCP connection to the SIP proxy. This TCP connection will use
a new source port (this is normal for TCP). It will go through NAT again,
which will probably assign different public port to this connection. This
means connection to proxy will come from a different source port and
poten
From: Roman Shpount [ro...@telurix.com]
4. A SIP messages for this dialog arrives to this edge proxy. New flow from UA
is very likely to have different source IP and port (and even if ti does it
should not be re-used since it can be a completely different
Let me try to explain this better:
1. There is a sip-outbound enabled UA behind NAT. UA registers through an
outbound enabled edge proxy with some registration server by sending
REGISTER message over TCP. This creates a TCP flow between the proxy and the
UA.
2. UA starts a call through the same e
From: sip-implementors-boun...@lists.cs.columbia.edu
[sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Roman Shpount
[ro...@telurix.com]
>From what
I understand, if TCP connection between the client and an edge proxy fails
for any reason (prox
I was trying to figure out if RFC 5626 defines a recovery mechanism for TCP
flow failure which occurs in the middle of an established dialog. From what
I understand, if TCP connection between the client and an edge proxy fails
for any reason (proxy crash, for instance) and there is a dialog establi
