search

nexcra / sipservlets

Automatically exported from code.google.com/p/sipservlets
0 stars 0 forks source link

SipServletMessage.addHeader handles transport badly #268

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. SipServletResponse.addHeader(
       "Contact", "sip:1234@127.0.0.1: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:1234@127.0.0.1:5060>;transport=tcp

where i would expect: -
<sip:1234@127.0.0.1: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.

Original issue reported on code.google.com by peterja...@googlemail.com on 29 Apr 2014 at 4:04

GoogleCodeExporter commented 9 years ago 
Moved to https://github.com/Mobicents/sip-servlets/issues/15

Original comment by jean.deruelle on 17 Dec 2014 at 9:33