But how TCP is used then in such case ... like i described.

Rockson Li (zhengyli) wrote:
> Hi ,
>
> I think the outbound draft means, you need two edge proxies, one for
> calling party, the other one for called party.
> And the two EPs would insert Record-Route with UA's specific flow token,
>
> But it would only work for incoming request, ie, route the req to UA.
> EP just remove Route(which points itself for outgoing req)
>
> -Rockson
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Ivar Lumi
> Sent: Monday, August 11, 2008 2:57 PM
> To: [email protected]
> Subject: [Sip-implementors] flow-token - draft-ietf-sip-outbound-13
>
> Hi,
>
> Little help needed on understanding about flow-token.
>
> UA1 ---- NAT ----- PROXY/REGISTRAR ---- NAT ----- UA2
>
> Both UA register with TCP.
>
>        Flow 1                          Flow 1
> UA1 ---- NAT ----- PROXY/REGISTRAR ---- NAT ----- UA2
>
> Both UA keep TCP flows alive.
>
>
> UA1 calls to UA2:
>
> INVITE UA2    ---- INVITE ------------------   INVITE
>                    Record-Route: flowToken ...
>
> Dialog:                                        Dialog:
>   Route: flowToke     ------------------------    Route: flowToken
>
>
> Now the part my brain won't get:
>  There are 2 flows involved, but flow token is common ..... .
>  Each UA must have own flow-token or flow-token must contain both flows
> info.
> (Because both UA behind NAT, so proxy must guide/reuse live flows)
>
> Any comments very welcome.
>
> Thanks,
>                         
>
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>   

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to