AEQ
PHOENIX ALIO
86
This working method, supported by external SIP servers, enables the physical position of a
device to be made independent from its logic identifier and, through the use of the SIP protocol,
makes it unnecessary to know more data regarding the called device than its URI.
During the establishment of the communication phase, the encoding algorithm is negotiated
simultaneously, based on the Link Profiles / SIP Codec Profiles defined in each of the devices
at the two ends of the connection circuit.
B4.2. Possible work scenarios.
Depending on the type of network to which the PHOENIX ALIO is connected, the codec will
have one or another type of IP address available to it.
•
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 ALIO 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.
This situation corresponds to use an Internet access by means of a single workstation
router (just one piece of equipment connected) and to hire a fixed IP.
•
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 (4.3).
B4.3. PHOENIX ALIO default SIP configuration.
To simplify operating the unit, AEQ offers, at no additional cost, the services of 2 own
SIP servers.
PHOENIX ALIO is supplied from the factory with both SIP servers preconfigured (SYSTEM
SIP PROVIDERS menu) 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 ALIO is supplied preconfigured with 2 users registered in both servers:
•
PROXY SIP "AEQ" and "AEQ 2" Authentication Users: phxalio_XXX y phxalio_XXY
(where Y=X+1)
•
PROXY SIP "AEQ" and "AEQ 2" Authentication Passwords: 8 digits alphanumeric
passwords
This configuration is the right one for working with any of both AEQ’s SIP servers.