#
# @description Create a routeCall with the a series of P-Assert Identity header parameters present in initial INVITE. Verify that SipConn will take the initiating user identity from the 1st P-Assert Identity header instead of From header to build the callingParty parameter to cse for application logic.  The From header on o/g INVITE will be preserved from i/c INVITE. From header in o/g INVITE includes user-id characters<br />(example:  From: "Anonymous"&lt;sip:Anonymous@10.77.92.46&gt;;tag=[call_number])
# @sincerelease 3.0
#
#SIPp uas_SIPROUTE06.xml dat_NS_csn02.csv
#sleep 1
#SIPp uac_SIPROUTE06.xml dat_NS_csn02.csv
