Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 2468 by [email protected]: Don't treat updated 180 responses
http://code.google.com/p/mobicents/issues/detail?id=2468
What steps will reproduce the problem?
1. Sending INVITE with "Supported: 100Rel" header
2. I receive correctly first 180 ringing response and I send prack
3. Sip Servelet don't notify me any other 180 ringing responses although
they have RSeq header with an incremental value
This issue is very to fixed issue 2251.
What is the expected output? What do you see instead?
Next updated ringing should be notified to listener. From rfc3262:
"Once a reliable provisional response is received, retransmissions of
that response MUST be discarded. A response is a retransmission when its
dialog ID, CSeq, and RSeq match the original response. The UAC MUST
maintain a sequence number that indicates the most recently received
in-order reliable provisional response for the initial request. This
sequence number MUST be maintained until a final response is received for
the initial request. Its value MUST be initialized to the RSeq header
field in the first reliable provisional response received for the initial
request."
What version of the product are you using? On what operating system?
mss-1.5.0.FINAL-jboss-jdk6-5.1.0.GA
Attachments:
ignored updated ringing.txt 3.0 KB
