Alcatel OmniPCX 4400 Rel. 8.0 using SIP via Cisco Unified Communications Manager–Session ...

64 Pages·2011·2.41 MB·English

Application Note

Alcatel OmniPCX 4400 Rel. 8.0 using SIP via Cisco Unified
Communications Manager–Session Manager Edition 8.5(1) to
Cisco Unified Communications Manager 8.5(1)

April 6, 2011 – Rev. 4
Table of Contents
Introduction .............................................................................................................................................................................................................. 2
Network Topology .................................................................................................................................................................................................... 2
Capabilities ............................................................................................................................................................................................................... 2
Limitations ................................................................................................................................................................................................................ 3
System Components ................................................................................................................................................................................................. 4
Hardware Requirements ...................................................................................................................................................................................... 4
Software Requirements ....................................................................................................................................................................................... 4
Features Supported ................................................................................................................................................................................................... 4
Features Not Supported ............................................................................................................................................................................................ 5
Configuration ............................................................................................................................................................................................................ 5
Configurating the Alcatel Omni PCX 4400 ......................................................................................................................................................... 5
Configuring the Cisco Unified Communications Manager – Session Manager Edition .................................................................................... 26
Configuring the Cisco Unified Communications Manager ............................................................................................................................... 39
Acronyms ............................................................................................................................................................................................................... 62

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 1 of 64
EDCS-1001103 Rev 4
Introduction
 This application note describes the necessary steps and configurations for connectivity between Alcatel OmniPCX 4400 Rel. 8.0, and a
Cisco Unified Communications Manager (Cisco UCM) version 8.5(1) with Cisco Unified Communications Manager-Session
Management Edition (Cisco UCM-SME) Version 8.5(1).
 The network topology diagram (Figures 1) shows the test setup for end-to-end interoperability between Cisco Unified Communications
Manager (Cisco UCM) Release 8.5(1) connected to the Alcatel PBX via a Cisco UCM-SME using SIP trunks (between Cisco UCM-
SME and Alcatel PBX) and SIP trunks (between the Cisco UCM-SME and Cisco UCM). Features tested are basic call, 3-way (ad-hoc)
conference, call transfer (attended and unattended), call forward (all, busy and no answer), hold/resume, fax transmission, and DTMF
interworking.
Network Topology
Diagram of the network topology setup
Figure 1. Network Topology
Alcatel Omni PCX 4400
Phone PBX1
Phone PBX2
SIP
Cisco UCM-SME
Rel. 8.5(1)
FAX PBX3
SIP
FAX C3
Cisco ISR – for IOS
MTP requirement
Phone C1
Cisco UCM
Rel. 8.5(1)
Phone C2

Capabilities
 Voice calls including supplementary services can be successfully established between endpoints controlled by the Alcatel PBX and
endpoints controlled by the Cisco Unified Communications Manager. Fax calls can successfully be established when Cisco UCM fax
end points initiate fax transmissions towards Alcatel fax end points. Fax calls initiated from Alcatel fax end points towards Cisco UCM
fax end points fail. Please refer to the Limitations section for additional information.

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 2 of 64
Limitations
 “Redirect by Application” checkbox must be enabled under the SIP Profile used by the SIP Trunk connecting Cisco UCM-SME to the
Alcatel PBX (and a SIP Route Pattern must also be configured), in order for External Call Forwarding to work properly on Alcatel end
points.
 Alcatel’s implementation of SIP REFER w/Replaces does not work properly: the Refer-To header provided by the Alcatel PBX during
local early-attended call transfers contains wrong Replaces dialog. Because of this issue, Cisco UCM-SME must be configured so as not
to accept inbound Replaces headers.
 COLP, CONP, COLR and CONR features:
- Alcatel Omni PCX 4400 with software release 8.0 restricts connected Name/Number delivery by sending Privacy: user on the
200 OK response message after call completion. Cisco UCM ignores any Privacy headers sent on SIP response messages, as per
RFC3323 interpretation.
 Alerting Name:
- Alcatel Omni PCX 4400 with software release 8.0 does not support Alerting Name feature support across SIP Trunk. Cisco
UCM does support Alerting Name feature using “Remote-Party-Id” field. Since both systems do not interoperate with one
another, both systems kept the dialed number on the phone.
 Attended Call Transfer:
- Both systems support Attended Call Transfer feature where the transferor places the transferee on hold and calls the target. After
conversing with the target, the transferor completes the transfer and drops out of both calls. The transferee is automatically taken
off of hold and connected to the target. However, they are not able to update the phone displays properly after the transfer is
completed. This is due to the differences between the two systems method of passing the name and number information across
SIP Trunk.
 Early Attended Call Transfer:
- Both systems support Early Attended Call Transfer feature but there are some interoperability issues with the Alcatel Omni PCX
4400 software with their SIP software stack. With Early Attended Transfer, the transferor places the original call on hold and
calls the target. Upon hearing ring-back tone, the transferor transfers the call to the target and drops out of both calls. The
transferee hears ring back while the target’s phone is alerting. When the target answers, a connection is established between
transferee and target.
- One example of call transfer failed to complete is for Early Attended Local Call Transfer (where Alcatel phones are the transferor
and the target phone). The call scenario is when Cisco UCM phone calls an Alcatel phone, and then the Alcatel phone performs
early attended transfer to another Alcatel phone. During this call scenario, it appears as though the Alcatel Omni PCX is not
sending Cisco UCM the correct “Replaces” header within the SIP Refer message. Because of this limitation, “Accept Replaces
Header” in the SIP Trunk Security Profile assigned to the SIP trunk connecting Cisco UCM-SME to the Alcatel PBX must be
disabled.
 Local Call Forwarding (CFU, CFB, and CFNA):
- Both systems support Local Call Forwarding (CFU, CFB, and CFNA) features. Calls are forwarded properly and establish audio
path. However, they are not able to update the phone display properly after the call is forwarded because the two systems have
different methods of passing the name and number information.
 Network Call Forwarding (CFU, CFB, and CFNA):
- There are interoperability issues between the two systems depending on the call flow.
- For CFU and CFB call scenario where Alcatel station is the forwarding station, it required CISCO UCM to have the “Redirect by
Application” checkbox enabled under the SIP Profile used by the SIP Trunk to the Alcatel PBX. For example, for the call flow
where a Cisco UCM phone calls an Alcatel phone, and that phone is CFU or CFB back to another Cisco UCM phone, without the
checkbox enabled, the call would fail. Trace analysis shows Cisco UCM sends out a regular SIP Invite message to Alcatel.
Alcatel respond back with SIP 302 Moved Temporarily with Contact header sip:xxxx@yyyy, where xxxx = ext. number of
forwarding target, and yyyy = IP address of the Alcatel PBX. Cisco UCM then send a new SIP Invite message to Alcatel based
on the Contact header information. Alcatel responds with SIP 301 Moved Permanently with a different Contact header
sip:xxxx@zzzz, where zzzz = IP address of Cisco UCM-SME. By enabling “Redirect by Application”, Cisco UCM-SME will

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 3 of 64
perform digit analysis and will initiate a call to the forwarding target extension residing on Cisco UCM, using the Route Pattern
configuration to properly route the call out to Cisco UCM.
 Call Conference:
- Both systems support call conferencing using their local media resources. However, if Alcatel station is the conferencing party,
local call conferences will work fine but network call conferences encounter one-way audio issues. For example, a network
conference call where an Alcatel station conferences in a Cisco UCM station over the SIP trunk, one-way audio occurred
between the conferenced-in party and the Alcatel station that initiated the conference. Trace analysis shows that the Alcatel PBX
never sends a SIP INVITE message to signal the conferenced-in station to redirect media to the PBX’s conference bridge
resource after the call conference is established.
 No support for centralized voice messaging across the SIP Trunk. Cisco UCM uses SIP Diversion header to pass the redirect
information across the SIP Trunk. However, Alcatel Omni PCX 4400 does not support any redirect information. Also noticed during
testing is that the Alcatel PBX, upon receiving inbound SIP NOTIFY messages (sent as message waiting activation/deactivation updates
for Alcatel stations), would respond with 200 OK response messages, but would not update the status of message waiting indicators on
its stations.
 Cisco SIP phones hear double ringback (both local ringback and remote ringback playing simultaneously) when calling Alcatel phones.
This is caused by the Alcatel PBX connecting media immediately after sending 180 Ringing message, causing the Cisco SIP phone to
play local ringback while listening to the remote ringback provided by the Alcatel. This issue affects Cisco SIP phones using G.711
codec. Cisco SIP phones using G.729 codec are unaffected: although the Alcatel PBX still connects media to the Cisco SIP phone
immediately, the media stream being sent only contains silence. This issue is currently under investigation. Cisco SCCP phones are
unaffected by this issue.
 Fax transmissions from Cisco UCM to Alcatel fax end points can be successfully established using T.38 fax relay. Fax transmissions
from Alcatel-controlled to Cisco-controlled fax end points fail. Trace analysis shows Cisco UCM sending mid-call INVITE to negotiate
T.38 fax containing SDP with connection information = 0.0.0.0. This media attribute seems to be causing the Alcatel PBX not to
properly connect the media after a second INVITE is sent by Cisco UCM with valid connection information. Fax Pass-Through is not
supported by the Alcatel PBX.
System Components
Hardware Requirements
 Cisco MCS 7800 Unified Communications Manager Appliance
 2 Cisco Unified IP phone 7960 configured as SCCP phones
 2 Cisco Unified IP phone 7970 configured as SIP phones
 Alcatel Omni PCX 4400 PBX with INT-IP2 card
 Alcatel digital and IP phones
Software Requirements
 Cisco Unified Communications Manager Release 8.5(1) - Session Manager Edition
 Cisco Unified Communications Manager Release 8.5(1) – Cisco UCM
 Alcatel software R8.0 (g1.503)
Features Supported
 CLIP-Calling Line (Number) Identification Presentation (Refer to Limitations section)
 CLIR-Calling Line (Number) Identification Restriction (Refer to Limitations section)
 CNIP-Calling Name Identification Presentation (Refer to Limitations section)
 CNIR-Calling Name Identification Restriction (Refer to Limitations section)
 Alerting Name (Refer to Limitations section)

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 4 of 64
 Attended Call Transfer (Refer to Limitations section)
 Early Attended Call Transfer (Refer to Limitations section)
 CFU-Call Forwarding Unconditional (Refer to Limitations section)
 CFB-Call Forwarding Busy (Refer to Limitations section)
 CFNA-Call Forwarding No Answer (Refer to Limitations section)
 COLP-Connected Line (Number) Identification Presentation (Refer to Limitations section)
 COLR- Connected Line (Number) Identification Restriction (Refer to Limitations section)
 CONP-Connected Name Identification Presentation (Refer to Limitations section)
 CONR-Connected Name Identification Restriction (Refer to Limitations section)
 Hold and Resume
 Conference Call (Refer to Limitations section)
 DTMF-relay using RFC2833
Features Not Supported
 Centralized Voicemail
 Call Completion (Callback; Automatic Callback)
 SIP Blind Call Transfer
 Inbound Fax to Cisco UCM (Refer to Limitations section)

Configuration
This section contains configuration menus and commands and describes configuration sequences and tasks.
Configurating the Alcatel Omni PCX 4400
1. Alcatel Omni PCX 4400 Software Version and Hardware Configuration List
2. Configure System  Other System Parameters  Compression Type
3. Configure IP  IP Domain  Extra Domain Without Compression
4. Configure SIP Network: Translator  Network Routing Table
5. Configure SIP Trunk group
6. Configure T2 Trunk Group Type
7. Configure Virtual Access for SIP
8. Configure Alcatel SIP Gateway
9. Configure Alcatel SIP Proxy setting
10. Configure SIP External Gateway
11. Configure IP Parameters
12. Configure GF diversion on joining
13. Configure call routing (Translator) to Cisco UCM phone extensions
14. Configure Alcatel standard users

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 5 of 64
Alcatel Omni PCX 4400 Software Version and Hardware Configuration List:

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 6 of 64
Configure System  Other System Parameters  Compression Type
- Ensure the Compression Type used by the system is set to G.729

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 7 of 64
Configure IP  IP Domain  Extra Domain Coding Algorithm Without Compression
- Ensure the Extra Domain Coding Algorithm is set to “Without Compression”

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 8 of 64
Configure SIP Network: Translator  Network Routing Table:
- Ensure the sub-network number used by SIP sets and SIP trunk group have the “Protocol Type = ABC_F”

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 9 of 64
Configure SIP Trunk group:
Trunk Group ID: Enter the trunk group number
Trunk Group Type: T2
Remote Network: Enter the sub-network number associated with the trunk group.
Node number: Enter the node number
Q931 signal variant: Select ABC-F for the main SIP trunk group
T2 Specification: SIP
Overlap dialing: No

© 2006 Cisco Systems, Inc. All right reserved.
Important notices, privacy statements, and trademarks of Cisco Systems, Inc. can be found on cisco.com
Page 10 of 64