On Feb 17, 2010, at 9:50 PM, Aaron Clauson wrote:
I have a scenario where I want a SIP client to be able to generate
multiple
redirect responses. The redirect responses will be generated based
on user
actions and will have a variable delay between them.
You're going to have to clarify
On Feb 6, 2010, at 10:03 PM, Dale Worley wrote:
On Sat, 2010-02-06 at 21:43 +0530, Rohit Aggarwal wrote:
RFC 3261 also says that although Require is an optional header, it
must not be ignored if present.
In that case, it may be better option to cancel the request.
IMO canceling the
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Mark R Lindsey lind...@e-c-group.com +12293160013 http://e-c-group.com/~lindsey
://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
Mark R Lindsey lind...@e-c-group.com +12293160013 http://e-c-group.com/~lindsey
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu
The example sip:alice;day=tues...@atlanta.com appears in RFC 3261,
section 19.1.3, with this note:
The last sample URI above has a user field value of
alice;day=tuesday. The escaping rules defined above allow a
semicolon to appear unescaped in this field. For the purposes of this
