Dialogic 6.2 manual IISDNR2MFCPGROUPB Calledlineconditions, November 347

				Enabling the R2 Protocol
	Table 19. R2 MFC Inter-register Signaling Parameters (Continued)
Name		Description	Units	Range
groupB_LineConditions		Structure of Group B called line		Refer to Table 22
		conditions indexed by enumeration
		IISDN_R2MFCP_GROUP_B_
		CALLED_LINE_CONDITIONS.
		Only a subset of these signals are
		used in a given protocol variant.
		Set those that are not used to the
		“invalid” tone code.
Call Progress Signal Generation
cpSignals		Array of IISDN_CPGEN_MF_		Refer to Table 24
		PARAMS structures that define
		the characteristics of the RING and
		BUSY call progress signals. RING
		must be defined as cpSignals[0]
		and BUSY must be defined as
		cpSignals[1].

The MFC inter-register protocol is specified through a subset of the parameters in Table 17 on page 338 that define the following:

1.Signal meaning definitions (events).

2.Actions associated with a given signal event. These specifications are used to create a set of state transition tables for the desired variant.

3.Protocol control parameters.

The parameter set might require extensions as support is added for variants unidentified at this time. In addition, for a given variant, certain signals and actions might not be defined. This restricts the way in which the protocol can move through the processing states.

November 2009 347