Calling ID , Type and Plan

Hi ,

Just as a reminder when you sit in the lab, try to not forget to put the correct Calling number , type and plan and this for all situation so it is true as well for SRST.

So a good vision of the call routing is important

The Minimum MGCP configuration

Here is a basic stuff to implement the mgcp config

ccm-manager fallback-mgcp
ccm-manager redundant-host
ccm-manager mgcp

ccm-manager music-on-hold
ccm-manager config server
mgcp call-agent service-type mgcp version 0.1
mgcp bind control source-interface GigabitEthernet0/0.102
mgcp bind media source-interface GigabitEthernet0/0.102

mgcp profile default

CUE : Quick Definition

CUE is as the CME a small business voice mail solution that you can easily deploy on a router. Most of the time, CUE will reside on the same chassis than the CME but for some implementations, you can split both. The only backdraw is that you must have a LAN connectivity between your elements.

CUE is interesting because it doens’t provide only voice mail but can also provide a small Auto-Attendant (AA). The integration between CUE and CME is done via the SIP protocol, while the integration with a Call Manager will be done via JTAPI ( CTI-QBE). It can be the case for implementation where you need to provide Unity backup on SRST location).

CUE will be supported by Network Module (NM-CUE) or as an Advanced Integration Module (AIM-CUE).

Page 1 of 41234