Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-3.0.0.FINAL
Roadmap-Fix
New issue 268 by [email protected]: SipServletMessage.addHeader
handles transport badly
http://code.google.com/p/sipservlets/issues/detail?id=268
What steps will reproduce the problem?
1. SipServletResponse.addHeader(
"Contact", "sip:[email protected]:5060;transport=tcp")
What is the expected output? What do you see instead?
When i retrieve the header using getHeader, it is set to: -
<sip:[email protected]:5060>;transport=tcp
where i would expect: -
<sip:[email protected]:5060;transport=tcp>
I am using this for a 302 message.
What version of the product are you using? On what operating system?
2.0.0.FINAL/tomcat 7 on CentOS
Please provide any additional information below.
The workaround for this is to put the <> in myself, but it's annoying that
it tries to be clever and is not quite there.
--
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.
