AEQ Phoenix Mobile Toepassingsnotitie

Blader online of download pdf Toepassingsnotitie voor {categorie_naam} AEQ Phoenix Mobile. AEQ Phoenix Mobile 8 pagina's. Audio codec system
Ook voor AEQ Phoenix Mobile: Toepassingsnotitie (8 pagina's)

Pagina afdrukken

AEQ PHOENIX AUDIOCODECS. APPLICATION NOTE 0-D

Connecting AEQ Phoenix Mobile units via Internet, complex-

Through LOCAL network(s), DHCP not used, manual NAT. Making use of AEQ

Proxy SIP. Adapted to Phoenix Mobile User Interface

The most convenient and reliable way to connect an IP codec to a remote one through

Internet is by means of a dedicated, exclusive Internet access (DSL, cable modem). In

this application note, a way to achieve the same result will be proposed when this is not

possible as Internet access is shared with other equipments connected within a

managed, LOCAL LAN and DHCP is not available or convenient. This application note

also describes the recommended procedure when AEQ SIP Proxy is used, where both

equipments involved in the communication are registered, easing the task of finding the

remote IP address when it is variable or unknown.

As we need to get access to Internet, a shared resource in this case, it is mandatory to

contact the network administrator in order to have the required resources enabled and

gather all the necessary information.

This document shows the specific steps to make this connection possible in the most

general way possible, although some verification procedures have been omitted in

order to ease the reading, and some particular situations may be easier to solve that

the presented one.

For a detailed explanation of every step, and for details on how to configure other

options that may be more convenient for other cases, the reading of the rest of

application notes, as well as User Manual's chapter 4, is recommended.

1. NETWORK ADMINISTRATION INVOLVEMENT

We will need that the Network Administrator...

1. Provides us with a valid internal IP within the local network, for example

172.26.5.59, for sending SIP signaling as well as audio using RTP protocol.

Both IP will be the same in both cases, and we will refer to it as LOCAL IP.

2. Indicates us the Network Mask, for example 255.255.0.0

3. Tell us the DNS server IP address, for example 172.26.1.1 or a valid external

DNS server for the country we are working at. If it is not provided, we will still be

able to operate provided that we know the IP address of the SIP Proxy

(although it is always recommended to specify it by its DNS name)

4. Provides the Gateway IP address, as an example 172.26.1.1

5. Indicates us the network Public IP address. In most cases, there will be a

single public IP for SIP signaling and RTP traffic. We will refer to it as PUBLIC

IP, for example, 212.170.180.170

APLICACIONES ELECTRONICAS QUASAR S.A.

TEL: (34) 91 686 13 00 - FAX: (34) 91 686 44 92 - E-mail: [email protected] - Web:

scenario configuration