-some templates were adopted
-logs were introduced to help tester in case of verdict fail
-correct Origin-Host AVP and Destination-Host AVP values were set in awaiting message requests
-few issues were solved due to different values as specified in TSS/TP
-some test case postambles were changed and some deregistrations were removed due to already performed administrative deregistration
-introduction of new constants related to SIP-Authentication-Scheme values
-Test Cases TC_CX_HSS_ER_01 - 03 removed due to TSS/TP change - removed because of wrong interpretation of standard

-	Name of PIXIT PX_NoRoamPublicIdentity was changed into PX_NotAllowedPublicIdentity 
      This new PIXIT was used in f_TC_CX_HSS_UA_21_I and f_TC_CX_HSS_UA_23_I
-	Type of pixit PX_VisitedNetworkId was changed from octetstring to charstring (conversion char2oct was done on TCFunction and Steps level)

DiameterCxDx_Steps:
-	Char2oct(PX_VisitedNetworkId) used instead PX_VisitedNetworkId(comment: easier to set PIXIT in the meantime of validation)
-	vc_VisitedNetworkId was set in all UAR messages due to the fact that this AVP shall be mandatory

DiameterCxDx_Cx_TCFunctions:
-	vc_VisitedNetworkId was set in all UAR messages due to the fact that this AVP shall be mandatory
-	Char2oct(PX_VisitedNetworkId) used instead PX_VisitedNetworkId(comment: easier to set PIXIT in the meantime of validation)
-	Few corrections were done in call flow sequence in some tests from TC_CX_HSS_UA_01 to TC_CX_HSS_UA_23 due to validation reason

Start Dx validation

 - Add backup of vc_session_Id in TC_CX_HSS_RT_01..06
   (Other to be done during next session)

 - Move mw_user_Data_dummy into DiameterCxDx_Templates
 - Bug fixed in template SCSCF_Restoration

 - Bug fixed on f_s_SAR_SAA
 - LI validation with Spectra2

  - Validation Cx/HSS: Add full Cx register/de-register
  - Validation Cx/CSCF: Add full Cx register/de-register
  - Bug fixed in Codec

Bug fixed in f_TC_CX_HSS_SA_01_I() & f_TC_CX_HSS_SA_02_I

Enhancement of preamble/postamble for TC_CX_HSS_SA_01

SIP-Authentication-Schema type is defined as union and either RFC or 3GPP type definition can be used.

SIP-Authentication-Schema type is defined as union and either RFC or 3GPP type definition can be used.

No commit message

SIP-Authenticate, SIP-Authorization, SIP-Auth-Data-Item types are defined as union and either RFC or 3GPP type definition can be used.

Modifications done during STF500 validation week47

add answer messages for HSS postamble steps