There are numerous reasons for the 500 response. The following are a few: 1) CSeq issue.
2) Proxy changed 503 to 500. 3) Sender needs receiver to delay before trying again; 500 potentially has Retry-After header. 4) New offer received before answer sent. 5) If glare, usually 491 instead of 500 with retry-after unless 491 wouldn't produce the desired results or pre-rfc3261. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of [EMAIL PROTECTED] > Sent: Monday, March 12, 2007 2:06 AM > To: [email protected] > Subject: [Sip-implementors] Scenario for 500 Server internal error > > > > > Hi Folks, > > Can anybody tell me what are the conditions in which an UAS > generates 500 server internal error? > > Quote from RFC 3261: > > If the remote sequence number was not empty, but the sequence > number of the request is lower than the remote sequence > number, the request is out of order and MUST be rejected with > a 500 (Server Internal > Error) response. > > Is it that only if cseq value is out of order w.r.t the cseq > value of the previous request, does an UAS sends 500 server > internal error? > > > Regards, > Dhananjay _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
