C3.1. Phoenix Mobile Default Configuration; C4. Sip Protocol - AEQ PHOENIX MOBILE User Manual

For complete information on RTP/RTCP protocol, AEQ recommends consulting:
http://tools.ietf.org/html/rfc1889
http://tools.ietf.org/html/rfc1890
http://tools.ietf.org/html/rfc3550
http://tools.ietf.org/html/rfc3551
http://tools.ietf.org/html/rfc3711

C3.1. PHOENIX MOBILE default configuration.

PHOENIX MOBILE is an IP audio coder that operates by using RTP over UDP in IP version 4.
By default, PHOENIX MOBILE is supplied from the factory with the following IP ports defined:
5004 for RTP and 5005 for RTCP if this protocol is used.

C4. SIP Protocol.

Session Initiation Protocol (SIP) is a protocol developed by the IETF MMUSIC Working Group
with the intention of establishing the standard for initiating, modifying and ending interactive
user sessions where multimedia elements such as video, voice and instant messaging are
involved.
SIP is used simply to initiate and terminate voice and video calls. Once the communication is
established, the exchange of voice / video information is conducted only over RTP.
One of the objectives of SIP was to contribute a set of processing functions to apply to calls and
capacities present in the public switched telephone network. Thus, it implemented typical
functions that a common telephone terminal offers, such as: calling a number, making a
telephone ring when called, hearing a dial tone or busy tone. The implementation and
terminology in SIP are different.
SIP requires proxy servers and register elements to give a practical service. Although two SIP
terminals can communicate with each other without the mediation of SIP infrastructures through
the use of URIs of the name@IP-address type (which is why SIP is defined as a point-to-point
protocol), this approach is impracticable for a public service because of the problems inherent in
IP addressing, where obtaining static public addresses is nearly impossible and extremely
costly.
To simplify the operation of the unit, AEQ offers without aftercost for Phoenix Mobile
users the services of proprietary SIP server, though 100 % of the time can neither guarantee
functioning nor make responsible for the disadvantages that could suppose therefore the final
user. The unit goes out of factory preconfigured with the necessary parameters to work using
the resources of this SIP server (see "Default SIP configuration for PHOENIX MOBILE" in this
manual).
SIP makes use of elements called proxy servers to help route the requests toward the user's
current location, authenticate users to give them service, enable call routing policies to be
implemented, and contribute added capabilities to the user.
SIP also contributes register functions that enable the user to inform the proxy servers of his or
her location.
For complete information on the SIP protocol, AEQ recommends consulting:
http://tools.ietf.org/html/rfc3261
91
AEQ PHOENIX MOBILE