COX CISCO UC320, Configuration Manual

Page: 5 / 13

3.1 Hardware Components

Cisco UC320

Cisco IP Phones

Analog Fax Machine
3.2 EdgeMarc 4550 e-SBC Software Requirements

Cisco UC320 with software Release 2.1.1

EdgeMarc 4550 9.12.8 release
4 Features
4.1 SIP Registration Method
Cox Network requires SIP REGISTER support to allow the IP-PBX to originate calls from the IP-PBX and
to send calls to the PBX from the PSTN. The Cisco UC320 supports SIP Register with authentication.
Cox implementation team provides the Pilot number and the authentication key, which should be
provisioned in the Cisco UC320.
4.2 Features Supported

Basic Calls using G.711ulaw

Calling Party Number Presentation and Restriction

Call Transfer

Call Forwarding

RFC2833 transcoding

Fax and Modem inband G.711
4.3 Features Not Supported

Codec negotiation of G.729, G.726, and others

T.38 Fax relay
5 Caveats and Limitations

Cisco UC320 does not support custom Calling Line ID (CLID) – a.k.a. “Calling Line ID spoofing”.
The UC320 only sends Trunk Group Pilot User telephone number for outbound calls and
outbound features would be associated to pilot user instead of individual DID.

Cisco UC320 does not support casual dialing.

Cisco UC320 did not work when ‘Caller ID Block’ enabled for extension-to-extension dialing, but it
did work when making external calls.

Must load Cisco UC320 three of the Platform Modification Files in order for the system to work
properly:

CallWaitingToneEnable_USA_CA.pmf

ChangeNTPserver.pmf

COX.pmf
The Platform Modification Files (.pmf) for Cox Communications are available online at the
Cisco
UC320 Customized Clearinghouse at http://www.ciscosbs2.com/movies/ucc/latest/ .
Property of Cox Communications, Inc. Version 1.0
Page 5 of 13