Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-3.0.0.FINAL
Roadmap-Fix
New issue 264 by [email protected]: SipSessionKey parsing breaks on ":"
in CallId
http://code.google.com/p/sipservlets/issues/detail?id=264
What steps will reproduce the problem?
1. Send an INVITE with ":" in the Call Id (this is valid according to the
RFC)
2. Store the SipSession id using getSession().getId()
3. Try to retrieve the SipSession using
SipApplicationSession.getSipSession(id)
What is the expected output? What do you see instead?
The expected output is the SipSession object corresponding to the id.
Instead we see null, even though the SipSession exists. This can be
confirmed by iterating through the SipSessions using
SipApplicationSession.getSessions()
What version of the product are you using? On what operating system?
MSS 2.1.0 on Linux
Please provide any additional information below.
The reason this happens is that ":" is used as a session key separator.
When ':' appears in the Call Id, wrong values are assigned to the various
components of the SipSessionKey.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
