AEQ
PHOENIX MERCURY
30
Enter the IP address of the remote unit, either manually or
getting it from the buttons:
By clicking here, the last URI “Calls”, the URIs in the “Contacts” book or the available
“IP” addresses are shown respectively, but only those with formats compatible with
channel and communication type.
•
It is mandatory that the called unit URI is specified in any of the following formats,
adequate for Proxy SIP communications:
o
<equipment’s_name>
, for example: “
phxme_231
” or “
phoenixMaster
”
o
<equipment’s_name>@<SIP_realm>
, for example:
“
” or
”
o
<equipment’s_name>@<SIP_server_IP>
, for example:
“
” or “
” (where
232.168.1.2. is AEQ SIP Server (“sip.aeq.es”) IP address )
o
<equipment’s_name>@<SIP_server>:<Port>
, when SIP port is not 5060 (the
one used by default in SIP SERVER mode). For example:
“
[email protected]:5061
”
VERY IMPORTANT:
<equipment’s_name> must not be longer than 19 characters.
•
Press the green “
Call
”
button on the screen, to make the call.
•
You can observe the changes of status from OK to CONNECTED and synchronized:
•
Verify that the “
SYNC
“ LED beneath the “
CALL
“ button is lighted in green to indicate
that the communication has been successfully established.
•
Press
the
“
ON AIR
“ button associated with that communications channel to enable
audio to be transmitted over that interface in full duplex mode.
•
Send audio from one equipment to another verifying that the “Tx” and “Rx”
audio presence indicators change to green.
•
If the unit is registering in SIP server and the call is being made but no audio comes
through, please check “
NAT TRAVERSAL
” configuration (see section 3.3).
4.5.2.1. Finalizing an IP communication in PROXY SIP mode.
•
In order to hang call, just click on “
CALL
” button in one of both codecs. A confirmation
message will appear and the call will be disconnected after acceptance.