Navigation :

map_np_srism

Alarms

The following 13 alarms may be generated by N2SNS Lua Application “map_np_srism”.

Show: Alarm Warning Clear Notice

No alarms found that match search criteria.

n2.n2sns.common

NS-CM-10000
WARNING

Message

SOAP PROXY: Action %s failed differently on N2SNS (%s: %s) and on proxy (%s: %s). EDR fields: %s

Cause: SOAP proxy error differs between N2SNS and the proxy.	%s = The SOAP proxy action being performed. %s = The error code generated by N2SNS. %s = The error message generated by N2SNS. %s = The error code generated by the SOAP proxy. %s = The error message generated by the SOAP proxy. %s = A list of EDR fields generated by the failing request.
Resolution: Check the generated error message.

NS-CM-10001
WARNING

Message

SOAP PROXY: Action %s succeeded on N2SNS but failed on proxy (%s: %s). EDR fields: %s

Cause: Action succeeded in N2SNS but failed on the proxy.	%s = The SOAP proxy action being performed. %s = The error code generated by the SOAP proxy. %s = The error message generated by the SOAP proxy. %s = A list of EDR fields generated by the failing request.
Resolution: Check the generated error message.

NS-CM-10002
WARNING

Message

SOAP PROXY: Action %s failed on N2SNS (%s: %s) but succeeded on proxy. EDR fields: %s

Cause: Action succeded on the proxy but failed in N2SNS.	%s = The SOAP proxy action being performed. %s = The error code generated by N2SNS. %s = The error message generated by N2SNS. %s = A list of EDR fields generated by the failing request.
Resolution: Check the generated error message.

n2sns/lua/svc/map_np_srism.lua

NS-SM-10001
WARNING

Configuration

MAP Logic configuration missing 'IMSI' configuration.

Cause: MAP Logic configuration missing 'IMSI' configuration.	-
Resolution: Check the configuration of the associated Logic application.

NS-SM-10002
WARNING

Configuration

MAP Logic configuration missing 'TRANSFER_HLR_GT' configuration.

Cause: MAP Logic configuration missing 'TRANSFER_HLR_GT' configuration.	-
Resolution: Check the configuration of the associated Logic application.

NS-SM-10003
WARNING

Configuration

MAP Logic configuration missing 'TRANSFER_HNR_GT' configuration.

Cause: MAP Logic configuration missing 'TRANSFER_HNR_GT' configuration.	-
Resolution: Check the configuration of the associated Logic application.

NS-SM-10004
WARNING

Configuration

MAP Logic configuration missing 'OWNED_ROUTING_DESTINATIONS' configuration.

Cause: MAP Logic configuration missing 'OWNED_ROUTING_DESTINATIONS' configuration.	-
Resolution: Check the configuration of the associated Logic application.

NS-SM-10005
WARNING

Message

Received SRISM request with no 'msisdn_digits' present.

Cause: Inbound SRISM request did not contain a 'msisdn_digits' property.	-
Resolution: Check the inbound MAP SRISM request content.

NS-SM-10006
WARNING

Message

Received SRISM request with empty 'msisdn_digits'.

Cause: Inbound SRISM request contained an empty 'msisdn_digits' property.	-
Resolution: Check the inbound MAP SRISM request content.

NS-SM-10007
WARNING

Message

Insufficient digits in MSISDN '%s' to convert to NSN/PMTN format for lookup.

Cause: Insufficient digits in MSISDN digits number to convert to NSN/PMTN.	%s = The failing MSISDN digits.
Resolution: Check the generated error message. Check the inbound MSISDN digits.

NS-SM-10008
WARNING

Message

Database lookup failed.

Cause: N2SNS DB lookup failed.	-
Resolution: Check the associated error message generated by the DB App. Contact N-Squared Support.

NS-SM-10009
WARNING

Message

No matching secondary HOC for '%s'. Returning ERROR_UNKNOWN_SUBSCRIBER.

Cause: MSISDN digits did not match configured N2SNS routing number.	%s = The failing MSISDN digits.
Resolution: Check the generated error message. Check the inbound MSISDN digits. Check the N2SNS routing number configuration. Check the N2SNS routing number secondary HOC configuration.

NS-SM-10010
WARNING

Message

No matching secondary HOC for '%s'. Returning ERROR_UNKNOWN_SUBSCRIBER.

Cause: MSISDN digits did not match configured N2SNS routing number.	%s = The failing MSISDN digits.
Resolution: Check the generated error message. Check the inbound MSISDN digits. Check the N2SNS routing number configuration. Check the N2SNS routing number secondary HOC configuration.

Statistics

The following 2 statistics may be generated by N2SNS Lua Application “map_np_srism”.

No statistics found that match search criteria.

n2.n2sns.common

sns.cli_screening_requests Type: Counter Scope: Job OID: -

Cause:

SNS cli screening requests processed. Details of the request and result are specified in tags.

Tags:	`class`	`local`	Calling party number was a local number.
		`mobile`	Calling party number was a mobile number.
		`nongeo`	Calling party number was a non-geographical number (e.g. TollFree).
		`other`	Calling party number was not classed as any of the other types.
	`proto`	`sip`	Incoming protocol was SIP.
	`result`	`ok`	CLI screening was successful.
		`no_data`	CLI screening failed as no information was found for the calling number.
		`not_allowed`	CLI screening was denied because redirection was not allowed for the subscriber.
		`no_override`	CLI screening was denied because the CAC was not on the allowed list for override.
		`barred`	CLI screening was denied because the called party was barred.
		`no_cac`	CLI screening was denied because the called party CAC was invalid.

sns.number_portability_requests Type: Counter Scope: Job OID: -

Cause:

SNS number portability requests processed. Details of the request and result are specified in tags.

Tags:	`class`	`local`	Calling party number was a local number.
		`mobile`	Calling party number was a mobile number.
		`nongeo`	Calling party number was a non-geographical number (e.g. TollFree).
		`other`	Calling party number was not classed as any of the other types.
	`proto`	`ati`	Incoming protocol was a MAP ATI.
		`sip`	Incoming protocol was SIP.
		`sri_sm`	Incoming protocol was a MAP SRI_SM
	`result`	`ok`	The NP lookup result was successful. HOC returned to network.
		`no_sub_id`	The NP lookup failed because the subscriberIdentity property was missing.
		`bad_lookup`	The NP lookup failed because the destination MSISDN was missing or invalid.
		`bad_moli`	The NP lookup failed because the provided MoLI digits were missing or invalid.
		`no_data`	The NP lookup returned no information for the destination MSISDN.