| United States-English |
|
|
|
![]() |
hp OpenCall SS7 platform Application Developer's Guide: For Release 3.1 on Linux > Chapter 5 Using the SCCP APISCCP Parameters |
|
Each SCCP primitive has associated SCCP parameters that include the necessary information to complete the function corresponding to the primitive. The SCCP level automatically changes the PointCode field of the calledAddress parameter from a local alias used by the network and received by the platform into the LPC. This makes use of local aliases completely transparent to the higher levels such as TCAP. Therefore you should never use a local alias within a local application. Table 5-3 SCCP Parameters and Values
See also the SCCP_recv(3) man page. Table Note 1In xunitdata_req: FALSE: XUDT sent only when segmentation is needed (UDT otherwise). TRUE: force use of XUDT rather than UDT. In xunitdata_ind: FALSE: UDT received. TRUE: XUDT received. Table Note 2In xnotice_req: FALSE: Use UDTS message type. TRUE: Use XUDTS message type. In xnotice_ind: FALSE: UDTS received. TRUE: XUDTS received. The HP OpenCall SS7 SCCP supports all Global Title types as defined in Q.713 §3.4.1. The application identifies the GT type by setting the gtIndicator. Table 5-4 Global Title Type
You must ensure that gt element of SC_ADDRESS contains a pointer to SC_GT_TITLE. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||