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
Here is a basic stuff to implement the mgcp config
!
ccm-manager fallback-mgcp
ccm-manager redundant-host 172.17.123.201
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 172.17.123.200
!
mgcp
mgcp call-agent 172.17.123.200 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 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).
CME is more or less the same as we have seen in the SRST implementation. But there is some other enhancements, so let’s see or recap the available mode:
- Cisco Unity Express
- Cisco Unity
- Analog voicemail systems . (See this post for this point as it is still valid)