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.

To enable fax over G.711 for a SIP subscriber, the following PBX configuration directives must<br />

be followed:<br />

- “Fax 2/3” services associated to the subscriber must be enabled (in OMC, Subscriber<br />

>Services)<br />

- VoIP VAD must be disabled (in OMC, Voice Over IP >DSP)<br />

- If a SIP trunk is configured on the PBX, Fax over G.711 must be configured in gateway<br />

parameters in the ARS (in OMC, Numbering >Automatic Route Selection/Gateway<br />

Parameters). The remote gateway MUST support fax over G.711. (Reminder : the use of<br />

voipnwaddr/inhibit_t38 flag is deprecated).<br />

On the other hand, in the media gateway configuration, the codec to use along with the PBX<br />

must be forced to G.711 (alaw or µlaw), and VAD must be disabled.<br />

6.4.2.3.21 Supplementary Services<br />

Hold<br />

A remote party can put on hold a local user through a public SIP trunk group by:<br />

- Sending a Re-INVITE with an IP address set to 0.0.0.0 or media attribute set to "sendonly".<br />

The local music on hold is played by the Alcatel-Lucent OmniPCX Office Communication<br />

Server to the user put on hold.<br />

- Sending a Re-INVITE with a valid IP address.<br />

The remote party plays its own music on hold. Hold is transparent to the Alcatel-Lucent<br />

OmniPCX Office Communication Server.<br />

A local user can put on hold a remote party through a public SIP trunk group. The local music<br />

on hold is played by the Alcatel-Lucent OmniPCX Office Communication Server to the remote<br />

party put on hold. A Re-INVITE is transmitted with a valid media IP address.<br />

Call Forwarding<br />

Call forwarding is performed by joining the two calls.<br />

Call forwarding with signaling path optimization is not supported.<br />

Media optimization can be performed through the RTP direct mechanism.<br />

The 3xx message is not used:<br />

- The Alcatel-Lucent OmniPCX Office Communication Server does not send a 3xx message.<br />

- The provider must not send a 3xx message. Such a message is rejected with a<br />

503.Service Unavailable message.<br />

Transfer<br />

Transfer is performed by joining the two calls. The Re-INVITE method is used.<br />

Transfer with signaling path optimization is not supported.<br />

Media optimization can be performed through the RTP direct mechanism.<br />

RFC 3515, 3891 and 3892 are not supported on public SIP Trunking.<br />

- The Alcatel-Lucent OmniPCX Office Communication Server does not use the REFER<br />

method<br />

6-69

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

Saved successfully!

Ooh no, something went wrong!