search

RestComm / sip-servlets

Leading SIP - IMS - WebRTC Application Server
http://www.restcomm.com/
GNU Affero General Public License v3.0
239 stars 181 forks source link

Invalidation of derived sip sessions #75

Open akozlovcodeminders opened 9 years ago

akozlovcodeminders commented 9 years ago

Scenario:

  1. Application is B2BUA
  2. Call to some test@example.com to server that supports forking
  3. Server returns 2 forked responses
  4. My application receives 2 responses one in usual session and one in derived session
  5. My application receives 200 OK from the second client and derived session become confirmed
  6. Application receives the second 200 OK, but since we already have established call, it sends ACK and BYE Result: Original SIP session become TERMINATED and derived become CONFIRMED. SIP container marks original session as ready to invalidate and invalidate it, but because of https://code.google.com/p/sipservlets/issues/detail?id=279 fix it also invalidates derived session with active call

Log Time

deruelle commented 9 years ago

This should be fixed by https://github.com/Mobicents/sip-servlets/issues/41. Which version are you using ?

akozlovcodeminders commented 9 years ago

I'm using sip-servlets 3.0.564

deruelle commented 9 years ago

Can you retry on the latest version from https://mobicents.ci.cloudbees.com/job/MobicentsSipServlets-Release/ ?