Commit 3f46e75d authored by saiu's avatar saiu
Browse files

I've fixed the @desc statements and have added new comments.

parent 2deb423a
Loading
Loading
Loading
Loading
+94 −48
Original line number Diff line number Diff line
/*
 *	@author 	STF 366
/**
 *	@author 	STF 369
 *  @version    $Id$
 *	@desc		This module contains the module parameters given in 
 *              "SIP-ISUP Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks; PICS"
@@ -11,241 +11,287 @@ group PICS_Module_Parameters
{
  modulepar {
// Roles  Table 1
    /* @desc	Does the SUT implement Profile A?
    /**
     * @desc	Does the SUT implement Profile A?
    ** @remark	PICS Reference: Table 1, Item 1
    */
    boolean	PC_IMPL_PROF_A;

    /* @desc	Does the SUT implement Profile B?
    /** 
     * @desc	Does the SUT implement Profile B?
    ** @remark	PICS Reference: Table 1, Item 2
    */
    boolean	PC_IMPL_PROF_B;

    /* @desc	Is the SUT connected to a BICC Network?
    /** 
     * @desc	Is the SUT connected to a BICC Network?
    ** @remark	PICS Reference: Table 1, Item 4
    */
    boolean	PC_CONN_BICC;

    /* @desc	Is the SUT connected to an ISUP Network?
    /** 
     * @desc	Is the SUT connected to an ISUP Network?
    ** @remark	PICS Reference: Table 1, Item 5
    */
    boolean	PC_CONN_ISUP;

    /* @desc	Is the SUT connected with a �-law network?
    /** 
     * @desc	Is the SUT connected with a �-law network?
    ** @remark	PICS Reference: Table 1, Item 6
    */
    boolean	PC_CONN_MULAW;

    /* @desc	Is the SUT connected with an outgoing international exchange?
    /**
     *  @desc	Is the SUT connected with an outgoing international exchange?
    ** @remark	PICS Reference: Table 1, Item 7
    */
    boolean	PC_CONN_OUT_INTERNAT;

    /* @desc	Is the SUT connected with an incoming international exchange?
    /**
     *  @desc	Is the SUT connected with an incoming international exchange?
    ** @remark	PICS Reference: Table 1, Item 8
    */
    boolean	PC_CONN_INC_INTERNAT;

    /* @desc	Is the SUT an implementation according ETSI EN 383 001?
    /** 
     * @desc	Is the SUT an implementation according ETSI EN 383 001?
    ** @remark	PICS Reference: Table 1, Item 9
    */
    boolean	PC_IMPL_383_001;

// ForwardAddressSignalling Table 3
	/* @desc	Does the SIP implementation use the en bloc operation in the forward address signalling (sending)?
	/**
	 *  @desc	Does the SIP implementation use the en bloc operation in the forward address signalling (sending)?
	** @remark	PICS Reference: Table 3, Item 1
	*/
    boolean	PC_USE_SIP_TX_ENBLOCK;

    /* @desc	Does the SIP implementation use the overlap operation in the forward address signalling (sending)?
    /**
     *  @desc	Does the SIP implementation use the overlap operation in the forward address signalling (sending)?
	** @remark	PICS Reference: Table 3, Item 2
	*/
     boolean	PC_USE_SIP_TX_OVERLAP;

    /* @desc	Does the SIP implementation support the overlap operation in the forward address signalling (receiving)?
    /**
     *  @desc	Does the SIP implementation support the overlap operation in the forward address signalling (receiving)?
	** @remark	PICS Reference: Table 3, Item 4
	*/
     boolean	PC_SUPP_SIP_RX_OVERLAP;

    /* @desc	Does the ISUP implementation support the overlap operation in the forward address signalling (receiving)?
    /**
     *  @desc	Does the ISUP implementation support the overlap operation in the forward address signalling (receiving)?
    ** @remark	PICS Reference: Table 3, Item 8
    */
    boolean	PC_SUPP_ISUP_RX_OVERLAP;


// RoleIndependentCapabilities Table 4
    /* @desc	Does the SUT use the Continuity check procedures during call setup?
    /**
     *  @desc	Does the SUT use the Continuity check procedures during call setup?
    ** @remark	PICS Reference: Table 4, Item 1
    */
    boolean	PC_USE_CONT_CHK;

	/* @desc	Does the SUT support the Continuity check procedures during call setup?
	/**
	 *  @desc	Does the SUT support the Continuity check procedures during call setup?
	** @remark	PICS Reference: Table 4, Item 2
	*/
	boolean	PC_SUPP_CONT_CHK;

    /* @desc	Does the SUT support internal resource reservations (preconditons used)?
    /**
     *  @desc	Does the SUT support internal resource reservations (preconditons used)?
    ** @remark	PICS Reference: Table 4, Item 4
    */
    boolean	PC_SUPP_INT_RESOURCE;

    /* @desc	Is the SUT able to support the reliability of provisional responses?
    /**
     *  @desc	Is the SUT able to support the reliability of provisional responses?
    ** @remark	PICS Reference: Table 4, Item 5
    */
    boolean	PC_SUPP_RELY_PROV;

    /* @desc	Does the SUT perform the automatic repeat attempt?
    /**
     *  @desc	Does the SUT perform the automatic repeat attempt?
    ** @remark	PICS Reference: Table 4, Item 6
    */
    boolean	PC_PERF_AUT_REPEAT;

    /* @desc	Does the SUT send an ACM message after determination of end of address signalling?
    /**
     *  @desc	Does the SUT send an ACM message after determination of end of address signalling?
    ** @remark	PICS Reference: Table 4, Item 9
    */
    boolean	PC_SEND_ACM_EOA;

    /* @desc	Does the SUT map the REL cause value into the reason header field of a SIP message (BYE, CANCEL or SIP final response)?
    /**
     *  @desc	Does the SUT map the REL cause value into the reason header field of a SIP message (BYE, CANCEL or SIP final response)?
    ** @remark	PICS Reference: Table 4, Item 10
    */
    boolean	PC_MAP_REL_CAUSE;

    /* @desc	Does the SUT map a received reason header field included in a SIP message (BYE, CANCEL or SIP final response) to the ISUP cause value in the sent REL?
    /**
     *  @desc	Does the SUT map a received reason header field included in a SIP message (BYE, CANCEL or SIP final response) to the ISUP cause value in the sent REL?
    ** @remark	PICS Reference: Table 4, Item 11
    */
    boolean	PC_MAP_REASON_REL;

    /* @desc	Does the SUT interwork the SIP Failure response to ISUP?
    /**
     *  @desc	Does the SUT interwork the SIP Failure response to ISUP?
    ** @remark	PICS Reference: Table 4, Item 12
    */
    boolean	PC_INTERW_SIP_FAIL;

    /* @desc	Does the SUT derive the Display-name in the "From header field" from the "additional calling party number" or "calling party number"?
    /**
     *  @desc	Does the SUT derive the Display-name in the "From header field" from the "additional calling party number" or "calling party number"?
    ** @remark	PICS Reference: Table 4, Item 13
    */
    boolean	PC_DERIV_DISPL_FROM;

    /* @desc	Does the SUT control the exchange for the Suspend procedure?
    /**
     *  @desc	Does the SUT control the exchange for the Suspend procedure?
    ** @remark	PICS Reference: Table 4, Item 14
    */
    boolean	PC_CTRL_SUSP;

    /* @desc	Does the SUT use internal resource reservations (preconditons used)?
    /**
     *  @desc	Does the SUT use internal resource reservations (preconditons used)?
    ** @remark	PICS Reference: Table 4, Item 15
    */
    boolean	PC_USE_INT_RESOURCE;

    /* @desc	Does the SUT satisfy the call using a new address provided in a Contact header field received in a 3xx response?
    /**
     *  @desc	Does the SUT satisfy the call using a new address provided in a Contact header field received in a 3xx response?
    ** @remark	PICS Reference: Table 4, Item 17
    */
    boolean	PC_USE_NEW_ADDR_CONTACT;

    /* @desc	Does the SUT refuse an offer with a 415 Unsupported media type response if more than one media typs are received in a SDP?
    /**
     *  @desc	Does the SUT refuse an offer with a 415 Unsupported media type response if more than one media typs are received in a SDP?
    ** @remark	PICS Reference: Table 4, Item 19
    */
    boolean	PC_REFUSE_415_OFFER;

    /* @desc	Does the SUT derive the Display-name in the "P-Asserted-Identity header field" from the "calling party number" or "additional calling party number"?
    /**
     *  @desc	Does the SUT derive the Display-name in the "P-Asserted-Identity header field" from the "calling party number" or "additional calling party number"?
    ** @remark	PICS Reference: Table 4, Item 20
    */
    boolean	PC_DERIV_DISP_P_ASS;

    /* @desc	Does the SUT redirect to a new destination according the BICC/ISUP requirements if a REL is received with cause 23?
    /**
     *  @desc	Does the SUT redirect to a new destination according the BICC/ISUP requirements if a REL is received with cause 23?
    ** @remark	PICS Reference: Table 4, Item 21
    */
    boolean	PC_REDIR_CAUSE_23;

	/* @desc	What is the value of PICS item 23 in table 4?
	/**
	 *  @desc	What is the value of PICS item 23 in table 4?
	** @remark	PICS Reference: Table 4, Item 23
	*/
	boolean	PC_TABLE4_23;

	/* @desc	What is the value of PICS item 23 in table 4?
	/**
	 *  @desc	What is the value of PICS item 23 in table 4?
	** @remark	PICS Reference: Table 4, Item 24
	*/
	boolean	PC_TABLE4_24;

// SupplementaryServiceMajorCapabilities Table 5
    /* @desc	Does the SUT support the service Call Hold (HOLD)?
    /**
     *  @desc	Does the SUT support the service Call Hold (HOLD)?
    ** @remark	PICS Reference: Table 5, Item 5
    */
    boolean	PC_SUPP_HOLD;

    /* @desc	Does the SUT support the service Terminal Portability (TP)?
    /**
     *  @desc	Does the SUT support the service Terminal Portability (TP)?
    ** @remark	PICS Reference: Table 5, Item 6
    */
    boolean	PC_SUPP_TP;

    /* @desc	Does the SUT support the service Conference Call, add-on (CONF)?
    /**
     *  @desc	Does the SUT support the service Conference Call, add-on (CONF)?
    ** @remark	PICS Reference: Table 5, Item 10
    */
    boolean	PC_SUPP_CONF;

    /* @desc	Does the SUT support the Three-Party (3PTY) service?
    /**
     *  @desc	Does the SUT support the Three-Party (3PTY) service?
    ** @remark	PICS Reference: Table 5, Item 18
    */
    boolean	PC_SUPP_3PTY;

// CLI Table 6
    /* @desc	Does the SUT include a network provided E.164 calling party number if the P-Asserted -Identity header field has not been received or not in the format "+"CC+NDC+SN; address signal: network provided?
    /**
     *  @desc	Does the SUT include a network provided E.164 calling party number if the P-Asserted -Identity header field has not been received or not in the format "+"CC+NDC+SN; address signal: network provided?
    ** @remark	PICS Reference: Table 6, Item 1
    */
    boolean	PC_INCL_E164_P_ASS_NTWK;

    /* @desc	Does the SUT include an addtional calling party number if a From header field has been received in the format "+"CC+NDC+SN; address signal: derived from the From header field?
    /**
     *  @desc	Does the SUT include an addtional calling party number if a From header field has been received in the format "+"CC+NDC+SN; address signal: derived from the From header field?
    ** @remark	PICS Reference: Table 6, Item 3
    */
    boolean	PC_INCL_ADD_CLD_FROM;

    /* @desc	Does the SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "presentation allowed" if no P-Asserted -Identity header field has not been received or not in the format "+"CC+NDC+SN?
    /**
     *  @desc	Does the SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "presentation allowed" if no P-Asserted -Identity header field has not been received or not in the format "+"CC+NDC+SN?
    ** @remark	PICS Reference: Table 6, Item 9
    */
    boolean	PC_SEND_CLI_ALLOWED_NO_P;

    /* @desc	Does the SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "address not available" if no P-Asserted -Identity header field has not been received or not in the format "+"CC+NDC+SN?
    /**
     *  @desc	Does the SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "address not available" if no P-Asserted -Identity header field has not been received or not in the format "+"CC+NDC+SN?
    ** @remark	PICS Reference: Table 6, Item 11
    */
    boolean	PC_SEND_CLI_NOT_AVAIL_NO_P;

    /* @desc	Does the SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "resentation restricted by the network" if no P-Asserted -Identity header field has not been received or not in the format "+"CC+NDC+SN?
    /**
     *  @desc	Does the SUT send a Calling Party Number with an Number Presentation restriction Indicator set to "resentation restricted by the network" if no P-Asserted -Identity header field has not been received or not in the format "+"CC+NDC+SN?
    ** @remark	PICS Reference: Table 6, Item 12
    */
    boolean	PC_SEND_CLI_RESTR_NTWK_NO_P;

// HOLD Table 8
    /* @desc	Does the SUT support that a party can put the other party on hold after alerting has commenced?
    /**
     *  @desc	Does the SUT support that a party can put the other party on hold after alerting has commenced?
    ** @remark	PICS Reference: Table 8, Item 1
    */
    boolean	PC_SUPP_HOLD_AFTER_ALERT;

    /* @desc	Does the SUT support that a party can put the other party on hold after the calling user has provided all of the information necessary for processing the call?
    /**
     *  @desc	Does the SUT support that a party can put the other party on hold after the calling user has provided all of the information necessary for processing the call?
    ** @remark	PICS Reference: Table 8, Item 2
    */
    boolean	PC_SUPP_HOLD_NEC_INFO;

// MCID Table 9
    /* @desc	Does the SUT return an IRS with bit A of the MCID response indicator set to 0 "MCID not included", if the network does not support the MCID service?
    /**
     *  @desc	Does the SUT return an IRS with bit A of the MCID response indicator set to 0 "MCID not included", if the network does not support the MCID service?
    ** @remark	PICS Reference: Table 9, Item 1
    */
    boolean	PC_RET_IRS_MCID_NOT;

// UUS Table 11
    /* @desc	Does the SUT understand an explicit user-to-user request?
    /**
     *  @desc	Does the SUT understand an explicit user-to-user request?
    ** @remark	PICS Reference: Table 11, Item 1
    */
    boolean	PC_IMPL_EXPL_USER_USER;

    /* @desc	Does the SUT support the rejection procedure of an explicit service request or discarding of user-to-user information as described in 1.1.5.x.5.2/Q.737?
    /**
     *  @desc	Does the SUT support the rejection procedure of an explicit service request or discarding of user-to-user information as described in 1.1.5.x.5.2/Q.737?
    ** @remark	PICS Reference: Table 11, Item 2
    */
    boolean	PC_SUPP_REJ_UUI_Q737;

	/* @desc	Does the SUT reject a user-to-user request service 3 not essential after call set-up using the FRJ message?
	/**
	 *  @desc	Does the SUT reject a user-to-user request service 3 not essential after call set-up using the FRJ message?
	** @remark	PICS Reference: Table 11, Item 3
	*/
	boolean	PC_REJ_UUS3ESSENTIAL_FRJ;

// ECT Table 12
    /* @desc	Does the SUT return a LOP (response) message with the indication "insufficient information"?
    /**
     *  @desc	Does the SUT return a LOP (response) message with the indication "insufficient information"?
    ** @remark	PICS Reference: Table 12, Item 1
    */
	boolean	PC_RET_LOP_INSUFF;