A stateless proxy just proxies the requests and responses, letting the UAs
or other proxies handle things. It knows nothing of the state of the
transactions, let alone the call. Even if this was a stateful proxy, it
would never generate a BYE on it's own, this is up to the UAs. The correct
flow for a stateless proxy would be:
A-----Invite------>P B
A P-----Invite------>B
A------Cancel----->P<----200 OK-------B
A<----200 OK-------P-----Cancel------>B (Cancel ignored when recvd after
final response)
A------ACK-------->P B (Invite/200 transaction must
complete with ACK)
A P------ACK-------->B
A-------BYE------->P B (send BYE since 200 received -
Cancel raced 200)
A P-------BYE------->B
A P<----200 OK(Bye)--B
A<-----200 OK(Bye)-P B
John
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 3:49 PM
To: [EMAIL PROTECTED]
Subject: [Sip-implementors] stateless proxy
Hi,
I have the following questions on a statelss proxy(refer the flow)!
If P receives the 200ok from B and Cancel from A at the same time, should
it follow the following flow? If so the stateless proxy is generating
requests on its own (ACK and BYE to B)? Is it ok for the stateless proxy to
generate requests on its own?
A-----Invite------>P B
A P-----Invite------>B
A------Cancel----->P<----200 OK-------B
A P-------ACK------->B
A P-------BYE------->B
A<-----200 OK------P B
A<-----487---------P B
A P<----200 OK-------B
A------ACK-------->P B
Thanks
Sreedhar
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
