Page 581 / 998 Scroll up to view Page 576 - 580
iMG SIP Overview
VoIP SIP
6-17
iMG/RG Software Reference Manual (Voice Service)
FIGURE 6-1
Phone --> iMG(A) --> iMG(B) --> Phone
A user makes a call with the phone connected to an iMG, which in turn contacts another iMG, which completes
the connection to the phone that is attached to it.
6.2.1.3 Calls Involving a Terminal and a SIP Endpoint
The following examples illustrate how a phone connected to an iMG terminal can communicate with a LAN SIP
endpoint on the IP network. Such endpoints could be:
A Soft Phone
An IP phone directly connected to the IP network
A user makes a call with the phone connected to an iMG, which reaches the corresponding LAN SIP endpoint
on the IP network (
Figure 6-2
).
Unit
SIP Server
Unit
Analog
Phone
VOIP IP
Network
Analog
Phone
A
B
Page 582 / 998
VoIP SIP
VoIP SIP Servers, Users & the Forwarding Data-
iMG/RG Software Reference Manual (Voice Service)
6-18
FIGURE 6-2
Phone --> iMG(A) --> SIP IP Phone
6.2.2
VoIP SIP Servers, Users & the Forwarding Database
The VoIP SIP subsystem on iMG residential gateways is based on the concept of SIP servers, local users, call for-
warding rules and access ports.
The following section describes SIP servers, local users and forwarding database.
SIP servers are servers where local users register themselves (Location Servers) and where calls are routed
(Proxy Servers) when an outgoing call is going to be set up.
Users are entities uniquely identified in the system by a name with an associated phone number. The User's
phone number represents the user's address on the local system.
Forwarding rules are local call routing rules used to forward an incoming call from a local user to a remote
system or to a remote user. Forwarding rules are also used for locally originated calls when the called party
SIP IP Phone
SIP Server
Unit
Analog
(or Digital Phone)
VOIP IP
Network
A
Page 583 / 998
VoIP SIP Servers, Users & the Forwarding Database
VoIP SIP
6-19
iMG/RG Software Reference Manual (Voice Service)
is not a local user and the call must be routed to a specific contact that typically is different from the proxy
server.
Definition of SIP servers, users and optionally forwarding database rules, are three basic steps in correctly con-
figuring the VoIP SIP subsystem (see Figure 8).
FIGURE 6-3
VoIP subsystem configuration - basic steps
6.2.2.1 SIP servers
6.2.2.1.1 Location servers
The SIP module needs to know where locally defined users attempt to register their contact in the network.
The VOIP SIP LOCATIONSERVER CREATE command is used to set the location servers used to register users.
It is possible to define more that one location server in order to increase system reliability in case the first loca-
tion server cannot be reached.
Default
Configuration
Signaling Protocol
Config. (SIP)
Access Port
Creation
Access Port
Configuration
Forwarding
Database
Users
Creation
User
Binding
Incoming/Outgoing
Calls
Page 584 / 998
VoIP SIP
VoIP SIP Servers, Users & the Forwarding Data-
iMG/RG Software Reference Manual (Voice Service)
6-20
The system will attempt to register the local users on all the location servers available in the location server list
(see VOIP SIP LOCATIONSERVER LIST command) until the first registration phase achieves a positive result.
Once a successful registration with a server has been achieved no further registration requests will be per-
formed even if other location servers are defined.
In the case that more than one location server is defined in the system, it's possible to set a location server as
Master: all
registration requests will start with the master location server, independently of the position of that
server in the location servers list. In the case where registration with the master location server fails, the Loca-
tion Server list will be used examined to find alternative location server(s) to which registration requests will
then be sent.
Note:
If no location servers are defined, the iMG uses the server addresses defined in the
Proxy Server list
instead.
Note:
If users are defined without specifying a user domain (see VOIP SIP USER CREATE command), the
user domain will automatically be associated with the location server address where the user is
registered.
6.2.2.1.2 Proxy servers
When an outgoing call cannot be handled by a local number or a well defined forwarding rule it must resolved
by an external proxy server. In this case the SIP module needs to know which proxy server should be used.
The VOIP SIP PROXYSERVER CREATE command is used to inform the system of the proxy servers that can be
contacted when an outgoing call is to be established.
Similarly to location servers, it is possible to define more that one proxy server in order to increase system
reliability.
The system will attempt to contact all the proxy servers available in the proxy server list (see VOIP SIP PROX-
YSERVER LIST command) until the first server answers to the INVITE request. In that case no further INVITE
requests are sent to the other proxy servers even if the called user cannot be reached.
In the case that more than one proxy server is defined in the system, it is possible to set a proxy server as Mas-
ter. All INVITE requests will start with the master proxy server, independently of its position in the proxy serv-
ers list. In the situation where the Master proxy server cannot be reached, the Proxy Server list will be
examined to find alternative proxy server(s) to which INVITE requests will be sent.
Note:
The
Proxy Server
is also used as registration server if no location servers are defined.
Note:
If users are defined without specifying a user domain (see VOIP SIP USER CREATE command) and no
Location Servers
are defined, the user domain will automatically be associated with the proxy server
upon which the user is registered.
6.2.2.2 Users
The system is designed to support up to 100 entries, shared between users and forwarding rules.
Users are defined by the VOIP SIP USER CREATE command.
Page 585 / 998
VoIP SIP Servers, Users & the Forwarding Database
VoIP SIP
6-21
iMG/RG Software Reference Manual (Voice Service)
Each user must have an associated user number, composed of a address number and, optionally, an area code
number if a complete E.164 number must be defined. Users may also have a pseudonym associated with their
numeric address (see the VOIP SIP USER CREATE command).
Note:
In any given system, there cannot be more than one user with the same area code and address. In other
words: The combination of area code and address number uniquely identifies a user within a system.
Note:
In any given system it is allowable to have two or more users with the same address but different area
code or no area code at all.
Users may inform the VoIP network about the location (IP address) where they can be contacted by registering
themselves on the location server defined in the VOIP SIP LOCATIONSERVER CREATE command. In this way
other endpoints on the VoIP network can contact each user by simply using the user address.
The domain where users are members is the domain defined in the VOIP SIP USER CREATE command. If the
DOMAIN is not defined, users will be implicitly associated with the address of the Location Server (or Proxy
Server if no location servers are defined) where they are registered.
To establish a user's registration status use the VOIP SIP USER SHOW command.
The user number used in registration messages is the complete user number: area code + address number.
6.2.2.2.1 Users and access ports
A user needs to be ‘attached’ to at least one physical telephone port in order to receive or to make calls. To
attach a user to a physical port use the VOIP SIP USER ADD command. When a user receives a call, only the
access port(s) where the user is attached are engaged by the communication. The same user may be attached to
more than one access port. In this case when a call is made to that user, all the ports to which the user is
attached will be used to signal the incoming call.
To list all physical ports where a user is attached, use the VOIP SIP USER SHOW command
Note:
Note that physical access ports don’t have their own fixed phone number. They inherit the phone
numbers from the user numbers of attached users.
More than one user may be attached to the same physical access port and therefore more than one phone num-
ber can be associated to the same physical access port.
If a user receives a call but the physical port where the user is attached is already involved in another communi-
cation (because it is used by another user), the call is rejected.
When an outgoing call is made to the VoIP network and more than one user is attached on the access port
being used to make the call, the identity of calling user is deemed to be the first user defined in the list of users
attached to that port.
To which which users are attached to a particular physical port, use the VOIP EP SHOW command.
When an access port is deleted from the system, all attached users are automatically detached from the port.

Rate

4 / 5 based on 3 votes.

Popular Allied-Telesis Models

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top