29.06.2015 Views

Expert Documentation

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6 <br />

As of R9.0, Alcatel-Lucent OmniPCX Office Communication Server allows the registration of<br />

public Direct Dial In (DDI) numbers available in the public dialing plan. A maximum of 60 DDI<br />

numbers can be registered. Public DDI registration is configured in OMC (<strong>Expert</strong> View), in<br />

System > Numbering > Automatic Routing selection > Gateway Parameters.<br />

6.4.2.3.7 Keep Alive Mechanism<br />

The Alcatel-Lucent OmniPCX Office Communication Server supports two keep-alive<br />

mechanisms for controlling the up/down status of the remote gateway.<br />

"Stateless" Monitoring<br />

At a regular time interval, the PCX sends an IP packet to the remote gateway and monitors the<br />

reception of the awaited answer.<br />

OMC configuration is used to select the keep-alive type of message emitted by the PCX which<br />

can be either an ICMP message (ping) or a SIP Option message.<br />

By default, the Alcatel-Lucent OmniPCX Office Communication Server uses ICMP message<br />

(ping). A message is sent every 300 s.<br />

Note:<br />

The keep-alive mechanism is inhibited when DNS SRV is enabled.<br />

To configure the keep alive mechanism:<br />

1. By OMC (<strong>Expert</strong> View), select Numbering > Automatic Routing Selection > Automatic<br />

Routing: Prefixes<br />

2. Review/modify the following attributes:<br />

Gateway Alive Protocol<br />

Gateway Alive Timout/s<br />

Select ICMP or SIP Option<br />

Enter the periodicity (in seconds) of keep alive message<br />

emission.<br />

Enter 0 to inhibit the keep alive mechanism.<br />

Active Session Monitoring (During a Call)<br />

In the context of SIP sessions, the Alcatel-Lucent OmniPCX Office Communication Server<br />

uses a session timer to check the activty of the remote party.<br />

To keep the SIP session alive, UAs exchange periodic refreshing requests.<br />

Two refreshing method are available using INVITE (with SDP) or UPDATE (without SDP)<br />

requests in conformity with RFC 4028. A negotiation mechanism allows to define the<br />

appropriate method depending on the context.<br />

To configure the keep alive mechanism for SIP sessions:<br />

1. By OMC (<strong>Expert</strong> View), select System Micellaneous > Memory Read/write > Debug<br />

Labels > VOIPnwaddr<br />

2. Enter the appropriate address Session timer value (see Public SIP Trunking -<br />

Configuration procedure - Session Timer ).<br />

3. Enter the appropriate address Do not Allow UPDATE value to enable/disable the<br />

UPDATE method depending on the context (see Public SIP Trunking - Configuration<br />

procedure - Do not Allow Update ).<br />

6.4.2.3.8 Authentication<br />

6-48

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!