| United States-English |
|
|
|
![]() |
hp OpenCall SS7 platform Application Developer's Guide: For Release 3.1 on Linux > Appendix B TUP AddendumUsing the API |
|
This section describes how to open, close, and use the SS7 stack connection via the HP OpenCall SS7 TUP API. The equivalent information for HP OpenCall SS7 ISUP is in Chapter 12 “Using the ISUP API ” This is as for HP OpenCall SS7 ISUP, see “Introduction”. This is as for HP OpenCall SS7 ISUP, see “Connections”. This is as for HP OpenCall SS7 ISUP, see “SS7 Stack Access”. This is as for HP OpenCall SS7 ISUP, see “Outline of the Basic Application”. This is as for HP OpenCall SS7 ISUP, see “Initializing the IsupMgr object”. This is as for HP OpenCall SS7 ISUP, see “Creating and Opening a Probe Object”. This is as for HP OpenCall SS7 ISUP, see “Exchanging Messages via Probe Objects”. This is as for HP OpenCall SS7 ISUP, see “Closing and Destroying a Probe”. This is as for HP OpenCall SS7 ISUP, see “Receiving Notifications”. However, the defaultGroup() accessor (referenced in the IsupAdditional::NotifCics row of Table 12-2 “ISUP Receive Notifications ”) is available in CTUP but not available in ITUP. For detailed description of the accessor return types, consult the IsupAdditionalInfo.h file located in the /opt/OC/include/TUP directory. For any IsupAdditionalInfo received, you must:
This is as for HP OpenCall SS7 ISUP, see “Return Status Values”. This is as for HP OpenCall SS7 ISUP, see “Using Dynamic Configuration ”. |
|||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||