Inter-Tel AXXESS Manual page 1432

Appendix A — Networking
® ®
INTER-TEL AXXESS
•
•
•
•
Page A-30
MANUAL VERSION 11.0 – May 2008
SMDR: Each node has its own SMDR programming, SMDR output port, and SMDR
output port backup. (See
for programming information.) You can enable or disable network call records on each
node. When network calls are enabled, the following applies:
— The system generates SMDR records for outgoing calls on the node where each
trunk used resides. For example, if a caller on Node A places a call using a trunk
group on Node B, the SMDR report for Node A will show the outgoing call to
Node B and the SMDR reports on Node B will show the incoming call from Node
A and the outgoing call on the trunk group.
— The call record type for network SMDR records is NET.
— If a node's SMDR output port is a node, the network sends SMDR records to the
specified node.
— You cannot select a node as the SMDR output port backup.
— If SMDR output programming forms a loop, the system will send the SMDR out-
put to the node's backup SMDR port. For example, if the SMDR port on Node 1
routes to Node 2 and the SMDR port on Node 2 routes to Node 1, the configura-
tion will cause an infinite loop of SMDR routing. SMDR reports for Node 1
would be printed to the backup serial port on Node2 and vice versa.
Voice Mail Messages: To correct for time zone differences when message notification
is sent from the Voice Processing Unit on one node to stations on other nodes, there is a
Time Zone setting in each mailbox. If set properly, the voice mail message envelope
will indicate the time the message was received using the mailbox's programmed time
zone.
SMDR Buffering: The Voice Processing Unit will buffer SMDR records that are sent
from other nodes in the network.
Message Print: Each node has its own message print programming, message print out-
put port, and message print output port backup. There should be a message print termi-
nal at each node to monitor node and network performance and aid in troubleshooting.
(See page 5-313 for more information about message print.)
— If a node's Message Print output port is a node, the network sends Message Print
records to the specified node.
— You cannot select a node as the message print output port backup.
— If Message Print output programming forms a loop, the system will send the out-
put to the node's backup Message Print port. For example, if the Message Print
port on Node 1 routes to Node 2 and the Message Print port on Node 2 routes to
Node 1, the configuration will cause an infinite loop. Message Print reports for
Node 1 would be printed to the backup serial port on Node2 and vice versa.
— A two digit node number is inserted in front of the sequence number to indicate
the node where the message originated. The following is an example of the new
message print string format for a message that originated on node 3:
-03:001- 15:30 03-20 M6009 WRN EG CP Corrupted Queue Was Cleared: HIS-
TORY QUEUE
— Message Print will not route diagnostic messages that apply to another node,
except during manual Message Print requests.
— Message Print will not send messages during a startup or reset. The system will
wait one minute before starting to send messages. Startup messages will only be
printed locally.
page 5-308 for complete details about SMDR and
Network Operation of System Features
page 6-276