Allied Telesis OmniConnect ISDN - Manual (Page 75)

OmniConnect / ISDN User’s Manual Page 69
Part number 613-10787-00
SOME APPLICATIONS DO NOT RUN WITH OmniNAT CONFIGURED
There are several applications that are incompatible with the Network Address
Translation (NAT) protocol. The OmniNAT implementation is completely
compatible with, and adheres to all the relevant RFCs. However, the NAT
protocol makes some assumptions regarding IP traffic which are not always true,
causing several applications to misbehave when used with NAT.
The OmniConnect implementation of NAT operates by translating LAN-based,
internal IP addresses to the ISP assigned, globally IP addresses. The
implementation tracks a combination of the sending station’s IP address and
TCP/UDP port numbers. In addition, the OmniConnect access device provides
fragmentation support for large packets.
NAT assumes that a given application will not embed the source IP address in a
packet. If an application, such as SNMP, happens to transmit its source address
in a frame this address is used by the receiving station, NAT will not behave
correctly.
TELNET PASSWORD IS LOST
Please contact Allied Telesyn Product Support for assistance.
ISDN DIRECTORY NUMBER SETTINGS ARE BEING IGNORED
OmniConnect provides a flexible scheme that allows complete control over
ringing, Caller ID displays and call forwarding. The access devices allow
control over the phone based upon the incoming Caller ID OR based upon the
assigned ISDN Directory Number. When both an incoming phone call’s calling
ID and the ISDN Directory Number are assigned to the same phone extension,
the Caller ID settings take precedence. An example best describes this situation.