How to send non-standard Content-Type header ?


hello,

my custom client developed send custom content-type header "xyz" (with out "/"). message gone in lcs 2005.

after have upgrade lcs 2005 ocs 2007 r2 in test environment. custom client not able send same custom content-type in ocs 2007 r2 used possible send in lcs 2005.

below cut ocs 2007 r2 accessedge log file.

tl_warn(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de7 (sipstack,ccontenttypeheader::parse:contenttypeheader.cpp(118))( 00000000036249f0 ) exit - media-type syntax error in getting "/"  tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de8 (sipstack,csipmessage::parseallheaders:sipmessage.cpp(6408))( 0000000003566a50 ) exit. failed while parsing header.  tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de9 (sipstack,csiprequest::validateinboundheaders:siprequest.cpp(1391))( 0000000003566a50 ) exit - failed while parsing header. returned 0xc3e93f51(sipproxy_e_invalid_content_type_header)  

fixing custom client not best solution because released customer. wonder why ocs 2007 r2 cannot parsing lcs 2005 could. there configuration bypass parsing?

thanks,
lertwut



Lync Server  ,  Unified Communications  >  Microsoft Lync Server SDK and Office Communications Server SDK



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts