Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Image AddedThe integration between PrivateServer Appliance and the Cisco Unified Call Manager Business Edition version 8.6.2 (from now on shortly CUCMBE) is made possible by setting up a SIP Trunk. Both the appliances can speak SIP, both work out the UDP transport protocols and the G711/ulaw codec and that's mostly all we need to start.

1. Configuring the CUCMBE

As the CUCMBE is prone to a wide range of configurations and network VoIP setup, we will explain to you the basic configuration and let the CUCMBE managers work out how to integrate it in their own environment. It's out of the scope of the present documentation to teach you how to manage a CUCMBE.

1.1 Prerequisite

Of course you need the CUCMBE appliance, which may come both in VMWare virtualization fashion or in real steel installed one. In either cases we assume that:

  • basic services are activated (see the fig. X). Beware the "Cisco IP Voice Media Streaming App" which must be activated in order to create an MTP (Media Termination Point)

  • The phones (both SCCP or SIP ones) are correctly configured and functioning
  • Your network design let the UDP packets to stream from the PrivateServer to the CUCMBE and vice versa

1.2 Basic CUCMBE configuration

If the prerequisites are matched then we first need to configure a new SIP Trunk. Go to the Cisco Unified CM Administration and from its GUI use the 

Image RemovedWe'll see how to configure both CUCMBE and PrivateServer to make this link possible and running.




The Cisco phones connected to the CUCMBE can be both SCCP or SIP ones: it makes no difference to PrivateServer.