--
----------------------------------------------------------------------------
Biplab Chattopadhyay
Research Engineer
CDOT-Bangalore
email: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Phone#
Office: 2263399, ext 255
2383951 (direct)
Mobile: 9845378867
----------------------------------------------------------------------------
Hi folks,
In RFC 3261 (Section 17.1.3) the behavior of SIP implementation acting as a
server is clearly mentioned in both cases (when the remote is RFC 3261
compliant and non RFC 3261 compliant). But in case of client, if we allow
sending of non RFC 3261 messages (simply for backward compatiblity with the UA),
then nothing is told about handling of the responses.
The question is, what should be the behavior for an implementation?
*) We use the same key that we were using for server transaction of
non RFC 3261 messages (Thatway we achieve backward compatibility with UA).
*) If we are RFC 3261 compliant, we should not even send non RFC 3261
messages from our implementation and avoid getting non RFC 3261 responses.
The scenario can be put like this:
UAC Stack Remote
| | |
|Non-RFC3261 | |
|Request | |
|----------->| |
| |Non-RFC3261 |
| |Request |
| |---------------->|
| |Non-RFC3261 |
| |Response |
| |<----------------|
| +------+---------+ |
| |What to do??? | |
| +------+---------+ |
| | |
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
