Comment #18 on issue 2269 by o.migrin: Wrong Contact header scheme URI in
case TLS call with 'sip:' scheme
http://code.google.com/p/mobicents/issues/detail?id=2269
I've retested your fix, and noticed that sips scheme URI still exist on
stage before B2B-ing (after B2B-ing it's all OK you fixed it):
------------------------------------------------------------------------------
REGISTER sip:192.168.252.60 SIP/2.0
To: "test1" <sip:192.168.252.60>
From: "test1" <sip:192.168.252.60>;tag=610ba44f0ee3
Contact: "test1"
<sips:192.168.252.151:5061>;+sip.instance="<urn:uuid:B292977C-B768-11DF-A82D-4530D98C9388>"
Call-ID: [email protected]
CSeq: 1 REGISTER
.....
------------------------------------------------------------------------------
REGISTER sip:192.168.252.50:5061;transport=TLS SIP/2.0
To: "test1" <sip:192.168.252.60>
From: "test1"
<sip:192.168.252.60>;tag=24454706_c5f60b3f_0c839d16-21d0-4d13-ad14-30a9a22e9533;epid=C485055AA4
Contact: "test1"
<sip:192.168.252.60:5061;transport=tls>;+sip.instance="<urn:uuid:B292977C-B768-11DF-A82D-4530D98C9388>"
CSeq: 1 REGISTER
......
