Avaya B179 User Manual Page 25

  • Download
  • Add to my manuals
  • Print
  • Page
    / 90
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 24
Avaya B179 SIP Conference Phone Installation and Administration Guide
21
The conference phone supports three accounts. The secondary and fallback accounts are
automatically used if the phone fails to register to the main account. If the phone fails to
register to the secondary and the fallback accounts, it tries to use the main account again.
Main account, Secondary account, and Fallback account
Enable account It is possible to store account information for future use, but tempo-
rarily disable it.
Account name This is the name displayed on the screen. It can be set according to
company standards.
User The account (customer) name.
Registrar Shall contain the IP address or the public name of the SIP server
where the account is registered (e.g. 10.10.1.100 for a local SIP server
or sip.company.net for a public VoIP service provider)
Proxy Shall contain the proxy server used for Internet communication, if
any. Can be left blank.
Realm The protection domain where the SIP authentication (name and
password) is valid. This is usually the same as the registrar. If marked
with a “*, the phone will respond to any realm. If specied, the phone
will only respond to the specic realm when asked for credentials.
Authentication name The name used for the Realm authentication. This may be the same as
the user name, but must be lled in.
Password The password used for the Realm authentication.
Registration Interval This is a request to the SIP server for when the registration should
expire. Avaya B179 automatically renews the registration within the
time interval if the phone is still on and connected to the server. The
default value is 1800 seconds.
On phone: > SETTINGS > ADVANCED > (PIN) > ACCOUNTS (6,2,1).
Nat traversal
NAT (Network Address Translation) is a rewall or router function that operates by rewriting
the IP addresses in the IP headers as packets pass from one interface to the other. When a
packet, for example, is sent from the inside, the source IP address and port are rewritten from
the private IP address space into the address space on the outside (Internet).
NAT rewrites the addresses but leaves the packets themselves untouched. This kind of transla-
tion works ne for many protocols, but causes a lot of trouble for SIP packets that contain
address information in their content (for example an INVITE request from one IP address to
another).
NAT traversal solves this problem, providing a “view from the outside” that makes it
Page view 24
1 2 ... 20 21 22 23 24 25 26 27 28 29 30 ... 89 90

Comments to this Manuals

No comments