8 Monitoring Service Controller

This chapter describes how to monitor Oracle Communications Service Controller.

About Monitoring Service Controller

You can monitor how Service Controller operates by receiving the following information:

Statistics on messages and sessions that Interworking Modules (IMs) and the Orchestration Engine (OE) handle. See "Monitoring the Processing Domain" for more information.
Status of the network entities with which Signaling Server Units (SSUs) communicate. See "Monitoring the Signaling Domain" for more information.
Availability of the SIP ports.

Monitoring the Processing Domain

A deployment of Service Controller might involve the following components:

Orchestration Engine
IN interface:
- IM-SCF (CAP1-4, INAP CS-1, WIN, AIN)
- IM-SSF (CAP1-3, INAP CS-1, WIN, AIN)
- IM-PSX MAP
SS7 interface:
- IM-SCF (CAP1-4, INAP CS-1, WIN, AIN)
- R-IM-SCF (CAP1-3, INAP CS-1, WIN, AIN)
SIP interface:
- IM-ASF SIP
- R-IM-ASF SIP
SMPP interface:
- IM-UIX-USSD SMPP
- IM-UIX-SMS SMPP

Using runtime MBeans, you can gather statistics on sessions and messages that these IMs send and receive through their interfaces.

Monitoring the IN Interface

IM-SCF, IM-SSF, and IM-PSX MAP modules provide the IN interface. You can get counters of the following:

Dialogs initiated by the network and IM. See "Getting Counters of Dialogs" for more information.
Messages that the IM handled. See "Getting Counters of Messages" for more information.

Getting Counters of Dialogs

Using DialogRuntimeMBean, you can get the counters of dialogs initiated by the IM and the network.

Service Controller creates a separate instance of DialogRuntimeMBean for each instance of IM-SCF, IM-SSF, and IM-PSX MAP.

The object name of this MBean is com.convergin:Type=DialogRuntime,Version=MBean_Version,Location=<server-name>,Name=IM_Instance_Name.Dialog.protocol

Table 8-1 describes the counters that DialogRuntimeMBean provides.

Table 8-1 DialogRuntimeMBean Counters

To Get Total Number of...	Use...
Dialogs initiated by the network	NetworkInitiatedDialogCount
Dialogs initiated by the IM	ServiceInitiatedDialogCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Counters of Messages

Using MessageRuntimeMBean, you can get the counters of messages that the IM sent and received.

Service Controller creates a separate instance of MessageRuntimeMBean for each instance of IM-SCF, IM-SSF, and IM-PSX MAP.

The object name of this MBean is com.convergin:Type=MessageRuntime,Version=<version>,Location=<server-name>,Name=<module-instance-name>.Message.MAP

Table 8-2 describes the counters that MessageRuntimeMBean provides.

Table 8-2 MessageRuntimeMBean Counters

To Get Total Number of...	Use...
Messages that the IM sent to the network	SndCount
Messages that the IM received from the network	RcvCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on the TCAP Interface

All IM-SCF and IM-SSF modules provide the TCAP interface. You can get statistics on the following:

TCAP transactions. See "Getting Counters of TCAP Transactions" for more information.
TCAP Abort messages. See "Getting Counters of TCAP Abort Messages" for more information.
TCAP messages. See "Getting Counters of TCAP Messages" for more information.
TCAP components. See "Getting Counters of TCAP Components" for more information.

Getting Counters of TCAP Transactions

Using TcapRuntimeMBean, you can get the counters of TCAP transactions.

Service Controller creates a separate instance of TcapRuntimeMBean for each instance of IM-SCF, IM-SSF, and IM-PSX MAP.

The object name of this MBean is com.convergin:Type=TcapRuntime,Version=<version>,Location=<server-name>, Name=<module-instance-name>.Tcap.

Table 8-3 describes the counters that TcapRuntimeMBean provides.

Table 8-3 TcapRuntimeMBean Counters

To Get Total Number of...	Use...
Opened TCAP Transactions initiated by the application	AppInitiatedTransCount
TCAP transactions that have been closed on the IM	DestroyTransactionCount
Opened TCAP transactions initiated by the user	NetworkInitiatedTransCount
TCAP transactions that the IM handled	TransactionCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Counters of TCAP Abort Messages

Using TcapPAbortCountMBean, you can get the counters of TCAP Abort messages.

Service Controller creates a separate instance of TcapPAbortCountMBean for each instance of IM-SCF, IM-SSF, and IM-PSX MAP.

The object name of this MBean is com.convergin:Type=TcapPAbortCountRuntime,Version=<version>, Location=<server-name>,Name=<module-instance-name>.TcapPAbortCount

Table 8-4 describes the counters that TcapPAbortCountMBean provides.

Table 8-4 TcapPAbortCountMBean Counters

To Get Total Number of...	Use...
P-ABORT messages received from the network with the Reason header set to Abnormal	NoCommonDialoguePortionCount
P-ABORT messages received from the network with the Reason header set to BADLY_STRUCTURED_DIALOGUE_PORTION	BadlyFormattedTransactionPortionCount
TC-P-ABORT messages received from the network with the Reason header set to Incorrect Transaction Portion	IncorrectTransactionPortionCount
TC-P-ABORT messages received from the network with the Reason header set to INCONSISTENT_DIALOGUE_PORTION	NoCommonDialoguePortionCount
TC-P-ABORT messages received from the network with the Reason header set to Resource Limit	ResourceLimitationCount
TC-P-ABORT messages received from the network with the Reason header set to Unrecognized Message Type	UnrecognizedMessageTypeCount
TC-P-ABORT messages received from the network with the Reason header set to 'Unrecognized Transaction ID	UnrecognizedTransactionIDCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Counters of TCAP Messages

Using TcapMessageCountMBean, you can get the counters of the following messages:

UniFromApplication
UniFromNetwork
BeginFromApplication
BeginFromNetwork
ContinueFromApplication
ContinueFromNetwork
EndFromApplication
EndFromNetwork
UAbortFromApplication
UAbortFromNetwork
Notice

Service Controller creates a separate instance of TcapMessageCountRuntimeMBean for each direction of each message for each instance of IM-SCF, IM-SSF, and IM-PSX MAP.

The object name of this MBean is com.convergin:Type=TcapMessageCountRuntime,Version=<version>,Location=<server-name>,Name=<module-instance-name>.<tcap-message>

Table 8-5 describes the counters that TcapMessageCountMBean provides.

Table 8-5 TcapMessageCountMBean Counters

To Get Total Number of...	Use...
Messages that the IM received but failed to process successfully	ReceiveFailedCount
Messages that the IM received and processed successfully	ReceiveSuccessCount
Messages that the IM failed to send to the SS7 network	SentFailedCount
Messages that the IM successfully sent to the SS7 network	SentSuccessCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Counters of TCAP Components

Using TcapComponentRuntimeMBean, you can get the counters of TCAP components.

Service Controller creates a separate instance of TcapComponentRuntimeMBean for each instance of IM-SCF, IM-SSF, and IM-PSX MAP.

The object name of this MBean is com.convergin:Type=TcapComponentRuntime,Version=<version>,Location=<server-name>,Name=<module-instance-name>.TcapComponent

Table 8-6 describes the counters that TcapComponentRuntimeMBean provides.

Table 8-6 TcapComponentRuntimeMBean Counters

To Get Total Number of...	Use...
Invoke component timer expiry count	ComponentInvokeTimerExpiryCount
Reject component timer expiry count	ComponentRejectTimerExpiryCount
TCAP Error components that the IM received from the network	ReceivedErrorCount
TCAP Invoke components that the IM received from the network	ReceivedInvokeCount
TCAP ResultL components that the IM received from the network	ReceivedResultLCount
TCAP ResultNL components that the IM received from the network	ReceivedResultNLCount
received TCAP TimerReset components that the IM received from the network	ReceivedTimerResetCount
TCAP UCancel components that the IM received from the network	ReceivedUCancelCount
U-REJECT components that the IM received from the network	ReceivedURejectCount
TCAP Error components that the IM sent to the network	SentErrorCount
TCAP Invoke components that the IM sent to the network	SentInvokeCount
TCAP LReject components that the IM sent to the network	SentLRejectCount
TCAP ResultNL components that the IM sent to the network	SentResultNLCount
TCAP RReject components that the IM sent to the network	SentRRejectCount
TCAP LCancel components that the IM sent to the network	SentLCancelCount
TCAP ResultL components that the IM sent to the network	SentResultLCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on IM-SCF

In addition to the TCAP interface, you can get the counters of sessions that the IM-SCF handles on a specific interface. Depending on the interface that you want to monitor, different runtime MBeans should be used.

Table 8-7 describes the IM-SCF counters.

Table 8-7 IM-SCF Counters

To Get Total Number of...	Use...	In the Runtime MBean…
Fully controlled sessions that the IM-SCF handled in the last measurement period. Full control means that the IM-SCF handled the session during the session setup and continues to handle this session after the session is established	FullControlCount	CAP: ImscfCapRuntimeMBean WIN: ImscfWinRuntimeMBean CS-1: ImscfInapCs1RuntimeMBean AIN: ImscfAinRuntimeMBean
Non-fully controlled sessions. Non-full control means that the IM-SCF handled the session only during the session setup.	InitialControlCount	CAP: ImscfCapRuntimeMBean WIN: ImscfWinRuntimeMBean CS-1: ImscfInapCs1RuntimeMBean AIN: ImscfAinRuntimeMBean
Sessions that the IM-SCF handled	SessionCount	CAP: ImscfCapRuntimeMBean WIN: ImscfWinRuntimeMBean CS-1: ImscfInapCs1RuntimeMBean AIN: ImscfAinRuntimeMBean
Messages that the IM-SCF received from the network	RcvCount	MessageByOpRuntimeMBean InitialDpByEventTypeRuntimeMBean (for CAP and CS-1 only) ErbByEventTypeRuntime MBean (for CAP and CS1 only) InitialDpByServiceKeyRuntimeMBean (for CAP and CS1 only) MessageRuntimeMBean
Messages that the IM-SCF sent to the network	SndCount	MessageByOpRuntimeMBean InitialDpByEventTypeRuntimeMBean (for CAP and CS-1 only) ErbByEventTypeRuntime MBean (for CAP and CS-1 only) InitialDpByServiceKeyRuntimeMBean (for CAP and CS-1 only) MessageRuntimeMBean

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on IM-SSF

In addition to the TCAP interface, you can get the counters of sessions that the IM-SSF handles on a specific interface. Depending on the interface that you want to monitor, different runtime MBeans should be used.

Table 8-8 describes the IM-SSF counters.

Table 8-8 IM-SSF Counters

To Get Total Number of...	Use...	In the Runtime MBean…
Fully controlled sessions that the IM-SSF handled in the last measurement period. Full control means that the IM-SSF handled the session during the session setup and continues to handle this session after the session is established	FullControlCount	CAP: ImssfCapRuntimeMBean WIN: ImssfWinRuntimeMBean AIN: ImssfAinRuntimeMBean
Non-fully controlled sessions. Non-full control means that the IM-SSF handled the session during the session setup only.	InitialControlCount	CAP: ImssfCapRuntimeMBean WIN: ImssfWinRuntimeMBean AIN: ImssfAinRuntimeMBean
Sessions that the IM-SSF handled	SessionCount	CAP: ImssfCapRuntimeMBean WIN: ImssfWinRuntimeMBean CS-1: ImssfInapCs1RuntimeMBean AIN: ImssfAinRuntimeMBean
Messages that the IM-SSF received from the network	RcvCount	MessageByOpRuntimeMBean InitialDpByEventTypeRuntimeMBean (CAP and CS-1 only) ErbByEventTypeRuntimeMBean (CAP and CS-1 only) InitialDpByServiceKeyRuntimeMBean (CAP and CS-1 only) MessageRuntimeMBean
Messages that the IM-SSF sent to the network	SndCount	MessageByOpRuntimeMBean InitialDpByEventTypeRuntimeMBean (CAP and CS-1 only) ErbByEventTypeRuntime MBean (CAP and CS-1 only) InitialDpByServiceKeyRuntimeMBean (CAP and CS-1 only) MessageRuntimeMBean

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Monitoring the SIP Interfaces

You can gather statistics on the SIP interface by using counters provided by IM-ASF SIP and R-IM-ASF SIP. In addition to IM-specific counters, both these modules also have the SIP interface which is common for all IM-ASF and R-IM-ASF modules.

Getting Statistics on the SIP Interface

You can get the counters of sessions that the IM-ASF or R-IM-ASF handles on the SIP interface.

Table 8-9 describes attributes that enable you to monitor the SIP interface.

Table 8-9 SIP Interface Counters

To Get Total Number of...	Use...	In Runtime MBean...
SIP sessions that the IM handled	SessionCount	SipRuntimeMBean
SIP requests that the IM received from the network	RcvCount	SipRequestRuntime MBean SipRequestByMethod RuntimeMBean SipResponseByRequest MethodRuntimeMBean
SIP requests that a module sent to the network	SndCount	SipRequestRuntime MBean SipRequestByMethod RuntimeMBean SipResponseByRequest MethodRuntimeMBean

To Get Total Number of...

Use...

In Runtime MBean...

SIP sessions that the IM handled

SessionCount

SipRuntimeMBean

SIP requests that the IM received from the network

RcvCount

SipRequestRuntime MBean

SipRequestByMethod RuntimeMBean

SipResponseByRequest MethodRuntimeMBean

SIP requests that a module sent to the network

SndCount

SipRequestRuntime MBean

SipRequestByMethod RuntimeMBean

SipResponseByRequest MethodRuntimeMBean

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on IM-ASF SIP

Using ImasfSipRuntimeMBean, you can get the counter of sessions that the IM-ASF SIP handles.

Service Controller creates a separate instance of ImasfSipRuntimeMBean for each instance of IM-ASF SIP.

The object name of this MBean is com.convergin:Type=ImasfSipRuntime,Version=<version>,Location=<server-name>,Name=<module-instance-name>.ImasfSip

Table 8-10 describes the counter that ImasfSipRuntimeMBean provides.

Table 8-10 ImasfSipRuntimeMBean Counter

To Get Total Number of...	Use...
Sessions that the IM-ASF SIP handled	SessionCount

For more information on how to access runtime MBeans, see a discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on R-IM-ASF

Using RimasfSipRuntimeMBean, you can get the counter of sessions that R-IM-ASF SIP handles.

Service Controller creates a separate instance of RimasfSipRuntimeMBean for each instance of R-IM-ASF SIP.

The object name of this MBean is com.convergin:Type=ImasfSipRuntime,Version=<version>,Location=<server-name>,Name=<module-instance-name>.RimasfSip

Table 8-11 describes the counter that RimasfSipRuntimeMBean provides.

Table 8-11 RimasfSipRuntimeMBean Counter

To Get Total Number of...	Use...
Sessions that the R-IM-ASF SIP handled	SessionCount

For more information on how to access runtime MBeans, see a discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Monitoring the SMPP Interfaces

You can gather statistics on the SMPP interfaces by using counters provided by IM-UIX-SMS SMPP and IM-UIX-USSD SMPP.

Getting Statistics on the SMPP Interface

Both IM-UIX-SMS and IM-UIX-USSD use the SMPP interface. Using SmppRuntimeMBean, you can get counters of sessions that the IM sent and received through this interface.

Service Controller creates a separate instance of SmppRuntimeMBean for each instance of IM-UIX-SMS and IM-UIX-USSD.

The object name of this MBean is com.convergin:Type=SmppRuntime,Version=<version>,Location=<server-name>, Name=<module-instance-name>.Smpp

Table 8-12 describes the counters that SmppRuntimeMBean provides.

Table 8-12 SmppRuntimeMBean Counters

To Get Total Number of...	Use...
Sessions that the IM-UIX-SMS handled	SessionCount
Requests that the IM-UIX-SMS handled	RequestCount
Responses that the IM-UIX-SMS handled	ResponseCount
submit_sm operations that the IM-UIX-SMS handled	SubmitSmCount
deliver_sm operations that the IM-UIX-SMS handled	DeliverSmCount
submit_sm_resp operations that the IM-UIX-SMS handled	SubmitSmRespCount
deliver_sm_resp operations that the IM-UIX-SMS handled	DeliverSmRespCount
submit_sm success responses that the IM-UIX-SMS handled	SubmitSmRespSuccessCount
submit_sm error responses that the IM-UIX-SMS handled	SubmitSmRespErrorCount
deliver_sm success responses that the IM-UIX-SMS handled	DeliverSmRespSuccessCount
deliver_sm error responses that the IM-UIX-SMS handled	DeliverSmRespErrorCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on IM-UIX-SMS SMPP

Using ImUixSmsSmppRuntimeMBean, you can get the counters of sessions that the IM-UIX-SMS SMPP handles.

Service Controller creates a separate instance of ImUixSmsSmppRuntimeMBean for each instance of IM-UIX-SMS SMPP.

The object name of this MBean is com.convergin:Type=ImuixSmsRuntime,Version=<version>,Location=<server-name>,Name=<module-instance-name>.ImuixSms

Table 8-13 describes the counters that ImUixSmsSmppRuntimeMBean provides.

Table 8-13 ImUixSmsSmppRuntimeMBean Counters

To Get Total Number of...	Use...
SMS sessions initiated by the network.	NetworkInitiatedSessionCount
SMS sessions initiated by the application	ApplicationInitiatedSessionCount
SMSC delivery receipts which are carried over deliver_sm operations, that IM-UIX-SMS received	SmscDeliveryReceiptRcvCount
delivery_sm operations with the Message Type parameter set to 0	SmsOverDeliverSmRcvCount
Delivery ACK messages which are carried over deliver_sm operations, that IM-UIX-SMS received from an SME	SmeDeliveryAckRcvCount
User/Manual ACK messages which are carried over deliver_sm operations, that IM-UIX-SMS received from an SME	SmeUserManualAckRcvCount

For more information on how to access runtime MBeans, see a discussion on monitoring Service Broker using Runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on IM-UIX-USSD SMPP

Using ImuixUssdRuntimeMBean, you can get the counters of sessions that the IM-UIX-USSD SMPP handles.

Service Controller creates a separate instance of ImuixUssdRuntimeMBean for each instance of IM-UIX-USSD SMPP.

The object name of this MBean is com.convergin:Type=ImuixUssdRuntime,Version=<version>,Location=<server-name>,Name=<module-instance-name>.ImuixUssd

Table 8-14 describes the counters that ImuixUssdRuntimeMBean provides.

Table 8-14 ImuixUssdRuntimeMBean Counters

To Get Total Number of...	Use...
Sessions initiated by the mobile subscriber that the IM handled	MSInitiatedSessionCount
Sessions initiated by the application server that the IM handled	ServiceInitiatedSessionCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on IM-PSX Plugin

Using ImpsxPluginRuntimeMBean, you can get the counters of sessions that the IM-PSX Plugin handles.

Service Controller creates a separate instance of ImpsxPluginRuntimeMBean for each instance of IM-PSX Plugin.

The object name of this MBean is com.convergin:Type=ImpsxPluginRuntime,Version=<version>,Location=<server-name>,Name=<module-instance-name>.ImpsxPlugin.

Table 8-15 describes the counters that ImpsxPluginRuntimeMBean provides.

Table 8-15 ImpsxPluginRuntimeMBean Counters

To Get Total Number of...	Use...
Sessions that the IM handled	getSessionCount()
Sessions initiated by application server that the IM handled	getASInitiatedSessionCount()
Sessions initiated by the network that the IM handled	getNetworkInitiatedSessionCount()

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Getting Statistics on the Orchestration Engine

Using OeRuntimeMBean, you can get the counters of sessions and application triggers.

The object name of this MBean is com.convergin:Type=OeRuntime,Version=MBean_Version,Location=Server_Name,Name=IM_instance_name.Oe

Table 8-16 describes the counters that OeRuntimeMBean provides.

Table 8-16 OeRuntimeMBean Counters

To Get Total Number of...	Use...
Sessions that the OE handled	SessionCount
Successful application triggering that the OE performed	SuccessfulApplicationTriggeringCount
Unsuccessful application triggering that the OE attempted to perform	UnsuccessfulApplicationTriggeringCount
2xx and 3xx responses that the OE received	SuccessfulUAServerTriggeringCounter

Using OlpRuntimeMBean, you can get the counter of triggering a specific Orchestration Login Processor (OLP).

The object name of this MBean is com.convergin:Type=OlpRuntime,Version=MBean_Version,Location=Server_Name,Name=IM_Instance_Name.Olp.Olp_Name

Table 8-17 describes the counter that OlpRuntimeMBean provides.

Table 8-17 OlpRuntimeMBean Counter

To Get Total Number of...	Use...
Times that the OE triggered the specific OLP	ExecutionCount

Using OprRuntimeMBean, you can get the counter of queries that the Orchestration Logic Processor (OLP) executed.

The object name of this MBean is com.convergin:Type=OprRuntime,Version=MBean_Version,Location=Server_Name,Name=IM_Instance_Name.Opr.Opr_Name

Table 8-18 describes the counters that OprRuntimeMBean provides.

Table 8-18 OprRuntimeMBean Counters

To Get Total Number of...	Use...
Successful queries that an OPR executed	SuccessfulQueryCount
Unsuccessful queries that an OPR attempted to execute	UnsuccessfulQueryCount

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Monitoring the Signaling Domain

A deployment of Service Controller might involve the following SSUs:

SS7 SSU. See "Checking the Status of SS7 Network Entities" for more information.
SMPP SSU. See "Checking the Status of SMPP Network Entities" for more information.
SIP SSU. See "Checking the Status of SIP Network Entities" for more information.

Using runtime MBeans, you can check whether the network entity with which the SSU communicates is active.

Checking the Status of SS7 Network Entities

Using SsuLocalPointCodeRuntimeMBean, you can get the status of the local point code. Table 8-19 describes the attributes that SsuLocalPointCodeRuntimeMBean provides.

Table 8-19 SsuLocalPointCodeRuntimeMBean Attributes

Attribute	Description
getValue()	Specifies the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.
getStatus()	Specifies the point code status. Possible values: 1 - Inaccessible 2 - Congested 3 - Accessible

Attribute

Description

getValue()

Specifies the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.

getStatus()

Specifies the point code status. Possible values:

1 - Inaccessible
2 - Congested
3 - Accessible

Using SsuLocalSubSystemRuntimeMBean, you can get the status of the subsystem. Table 8-20 describes the attributes that SsuLocalSubSystemRuntimeMBean provides.

Table 8-20 SsuLocalSubSystemRuntimeMBean Attributes

Attribute	Description
getSSN()	Specifies the subsystem number
getInService()	Specifies a subsystem status. Possible values: True: the Subsystem is in service False: the Subsystem is out of service

Attribute

Description

getSSN()

Specifies the subsystem number

getInService()

Specifies a subsystem status. Possible values:

True: the Subsystem is in service
False: the Subsystem is out of service

Using SsuRemoteSubSystemRuntimeMBean, you can get the status of the remote subsystem. Table 8-21 describes the attributes that SsuRemoteSubSystemRuntimeMBean provides.

Table 8-21 SsuRemoteSubSystemRuntimeMBean Attributes

Attribute	Description
getValue()	Specifies the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.
getStatus()	Specifies a remote subsystem status. Possible values: 0 - Remote subsystem is unavailable 1 - Remote subsystem is available

Attribute

Description

getValue()

Specifies the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.

getStatus()

Specifies a remote subsystem status.

Possible values:

0 - Remote subsystem is unavailable
1 - Remote subsystem is available

Using SsuRemotePointCodeRuntimeMBean, you can get the status of the remote point code. Table 8-22 describes the attributes that SsuRemotePointCodeRuntimeMBean provides.

Table 8-22 SsuRemotePointCodeRuntimeMBean Status Attributes

Attribute	Description
getValue()	Specifies the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.
getStatus()	Specifies a point code status. Possible values: 0 - Remote SCCP is unavailable 1 - Remote SCCP is available

Attribute

Description

getValue()

Specifies the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.

getStatus()

Specifies a point code status.

Possible values:

0 - Remote SCCP is unavailable
1 - Remote SCCP is available

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Checking the Status of SMPP Network Entities

Using SmppAdapterMBean, you can get the status of all SMPP connections. Table 8-23 describes the attribute that SmppAdapterMBean provides.

Table 8-23 SmppAdapterMBean Status Attribute

Attribute	Description
getlistSmscConnectionStatus[]	Specifies the status of all SMSC connections. Possible values: 0 - Inactive 1 - Active

Attribute

Description

getlistSmscConnectionStatus[]

Specifies the status of all SMSC connections. Possible values:

0 - Inactive
1 - Active

Using NetworkEntityRuntimeMBean, you can get the status of the network entity. Table 8-24 describes the attributes that NetworkEntityRuntimeMBean provides.

Table 8-24 NetworkEntityRuntimeMBean Status Attributes

Attribute	Description
getValue()	Specifies the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.
getStatus()	Specifies a network entity status. Possible values: 0 - Network entity is unavailable 1 - Network entity is available 2 - Status of the network entity is unknown

Attribute

Description

getValue()

Specifies the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.

getStatus()

Specifies a network entity status. Possible values:

0 - Network entity is unavailable
1 - Network entity is available
2 - Status of the network entity is unknown

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Checking the Status of SIP Network Entities

Using NetworkEntityRuntimeMBean, you can get the status of the network entity. Table 8-25 describes attributes that NetworkEntityRuntimeMBean provides.

Table 8-25 SIP SSU Monitoring Attributes

Attribute	Description
getValue()	The attribute contains the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.
getStatus()	Specifies a network entity status: 0 - Network entity is unavailable 1 - Network entity is available 2 - Status of the network entity is unknown

Attribute

Description

getValue()

The attribute contains the address of the network entity in the URI format where with the colon character (:) is replaced with the underscore.

getStatus()

Specifies a network entity status:

0 - Network entity is unavailable
1 - Network entity is available
2 - Status of the network entity is unknown

For more information on how to access runtime MBeans, see the discussion on monitoring Service Broker using runtime MBeans in Oracle Communications Service Broker System Administrator's Guide.

Checking Availability of the SIP Port

To ensure a stable communication between entities in a SIP network and Service Controller, you can check whether the UDP SIP port of Service Controller is up. This check is known as healthcheck.

To perform a healthcheck for a UDP SIP port:

Configure the load balancer to send to Service Controller a raw UDP package with the following data bytes (hex): 70 69 6e 67.

Service Controller recognizes this package as a healthcheck and does not parse the package.