5 — VoIP overview
Alcatel-Lucent 7330/7302 ISAM FTTN R04.02.42a March 2011 5-9
3FE 54199 AAAA TCZZA Edition 01 ONT Product Information Guide
5.4 SIP modes
The 7342 ISAM FTTU supports two SIP modes:
• SIP mode 1: thin client interworking with softswitches, such as Broadsoft
Broadworks (not supported on package D ONTs)
• SIP mode 2: thick client interworking with softswitches, such as Nortel CS2000
When configuring SIP using OMCIv2 via TL1 or CLI, the Softswitch parameter
identifies the SIP gateway softswitch vendor. The format is four ASCII coded
alphabetic characters [A..Z] as defined in [ATIS-0322000]. A value of four null
characters indicates no particular vendor.
Starting in Release 04.02.02, the setting of this Softswitch parameter signals to the
ONT to use various types of SIP. Until all softswitch vendor IDs are identified,
package A, B, and H ONTs interpret some specific settings as follows:
• THIN = legacy SIP 1 - Mode 1 SIP - thin client
• any other setting including null = legacy SIP 2 - Mode 2 SIP - thick client
In the two SIP modes, the SIP switches provide the SIP server functions, while the
ONT provides the SIP user agent functions, including the following.
• controls the analog states of the POTS line to locally invoke call setup and call
tear-down
• generates dial tone locally
• collects dialed digits and send the dialed string to the SIP switch
• plays ringback tone and busy tone
• derives caller ID FSK from headers in signaling messages
• supports NTP date and time for caller ID (not supported on package D ONTs)
• establishes or disconnects an RTP bearer path and RTCP to another VoIP media
gateway
• call statistics with call history (not supported on package D ONTs)
Redundancy in SIP mode 1 or SIP mode 2 is supported if a domain name is
configured for the registrar_route and outbound_proxy parameters in the SIP
provisioning data and a DNS server address is provided through DHCP; see
section 5.6. The ONT automatically contacts the domain name server (DNS) and
obtain a list of A records or SRV records. The ONT uses the records to contact
possible SIP servers according to the methodology outlined in RFC 3263. This is not
supported on package D ONTs.
SIP service features
Table 5-2 lists the service features supported by the two SIP modes and whether the
service feature is configurable using TL1 via OMCIv2.
To Next Page
Loading...
