Lucent Technologies 585-310-575 manual Messaging Solutions Release 4 Alarm Log Messages

Preventative Maintenance and Troubleshooting

Table 5-3. User Questions or System Functionality Symptoms — Continued

Question/Symptom	Possible Cause		Answer/Suggested Remedy
Recipient claims s/he did	■	Mailing list not	Check the mailing list for the recipient’s
not get an ELA message.		current	name. Administer, if necessary.
	■	Subscriber’s	■ Check the Subscriber screen for the
		mailbox not	affected user. Look at the Mailbox size.
		administered	Put user in a COS with a larger mailbox,
		correctly	if necessary.
			■ Check the List Measurements
			Subscriber Day screen for the affected
			user. Look at the available mailbox
			space. Advise the user to delete
			unneeded messages and greetings, if
			appropriate.
			■ Check that Community ID is correct.
	■	System delivery	System delivery failures can arise from
		failure	many sources.
			■ Check the Delivery Failure Log (see
			"Checking the Delivery Failure Log" on
			page 5-52).
			■ Check the Administrator’s Log for
			related alarms. If an alarm warrants
			further action, see Lucent INTUITY
			Messaging Solutions Release 4 Alarm
			and Log Messages, 585-310-566.
			■ Verify network capabilities with your
			PC/LAN administrator.
	■	Sending	Administer Community IDs for all Lucent
		Restrictions not	INTUITY machines, if appropriate.
		consistent across
		machines
An enhanced-list member	System feature to		■ From AUDIX Administration, enter
keeps disappearing from	delete non-		ch sys fe. Access page 4 and change
Enhanced Lists.	administered remote		the Even if on Mailing List?
	users is active.		field to n.
			■ Re-administer the remote user.
“I can’t send a message to	User belongs to a		Consider whether to change this user’s
an enhanced-list mailbox.”	community with		community ID to allow her/him to use
	sending restrictions		Enhanced Lists.
	administered.
			Continued on next page

56Issue 1 July 1997