AEQ
PHOENIX MERCURY
50
•
Static public IP addresses offer the ideal situation, since they guarantee that the IP
interface of the codec will always be assigned to a fixed address (regardless of whether
it is turned off and then powered up again) and directly accessible to the rest of the
network users. PHOENIX MERCURY operates perfectly with an associated SIP server
and equipment identifiers of the name@domain type (PROXY SIP), and even without
an associated SIP server with a URI of the name@IP-address type (DIRECT SIP) if the
device on the opposite end of the communication circuit also has an IP address of the
same type.
•
Dynamic public IP addresses, corresponding to use an Internet access by means of a
single workstation router and a dynamic IP (the most usual). Allows the use of URIs of
the name@domain (PROXY SIP) or name@IP-address (DIRECT SIP) type, but it is
advisable always to work with an associated SIP server (PROXY SIP), since the IP
address assigned to the equipment may change each time the user powers up the unit.
•
Private IP addresses, both static and dynamic, corresponding to connections in a local
network with several workstations, that access to the Internet through a router with
NAT. Those do not allow the use of URIs of the name@IP-address type because the IP
address of the identifier is not public, and is only valid in the section of the network to
which it has been assigned; it lacks a universal meaning. In this case the use of an
associated SIP server and a STUN server is imperative to get past the NAT (Network
Address Translation) implemented in the router that acts as an interface between the
private network and the public one. See section NAT TRAVERSAL (3.1.5.2.4).
C4.3. PHOENIX MERCURY default configuration.
To simplify operating the unit, AEQ offers, at no additional cost, the services of 2 own
SIP servers.
PHOENIX MERCURY is supplied from the factory with both SIP servers preconfigured
(“Configuration”
Æ
“General”
Æ
“INTERFACE”: “Net1 SIP, Proxy based”
Æ
“I/F Setup”
Æ
“SIP
Parameters”
Æ
“Proxy Provider”) defined as “AEQ” and “AEQ 2” with the following configuration:
•
PROXY SIP “AEQ” Host: sip.aeq.es
•
PROXY SIP “AEQ 2” Host: sip2.aeq.es
•
PROXY SIP “AEQ” and “AEQ 2” Port: 5060
•
PROXY SIP “AEQ” and “AEQ 2” Domain: sip.aeq.es
•
PROXY SIP “AEQ” and “AEQ 2” Register Expires: 60 min.
PHOENIX MERCURY is supplied preconfigured with a user registered in both servers:
•
PROXY SIP “AEQ” and “AEQ 2” Authentication User: phxmercury_XXX
•
PROXY SIP “AEQ” and “AEQ 2” Authentication Password: 8 digits alphanumeric
password
This configuration is the right one for working with any of both AEQ’s SIP servers.
C5. STUN protocol.
STUN
(
S
imple
T
ransversal of
U
DP over
N
ATs) is a network protocol of the client /server type
that allows NAT clients to find their public IP address, the type of NAT where it is located and
the Internet port associated with the local port through NAT. This information is used to
configure a UDP communication between two hosts located behind NAT routers.
NAT (Network Address Translation) is a mechanism used by IP routers to exchange packets
between two networks that assign each other incompatible addresses. It consists of converting,
in real time, the addresses used in the transported packets. It is also necessary to edit the
packets to enable the operation of protocols that include address information within the protocol
conversation. It is most commonly utilized to enable the use of private addresses and still
provide connectivity with the rest of the Internet.
