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

SNR – Side Effect

Hi ,

Take care to the fact that any change under Remote Destination Configuration will disable the Mobility. So in order to test it , don’t forget to enable it again if you need to test it .

Proctor Labs Solution

As said in my previous post, I’m still lacking the lab section so I decided this 05th April to rent a rack by ProctorLabs ( The solution that they offer is incredible but is also not so cheap. It is worth to try it as you can manipulate the core with all their routers and cards.

The only problems for the first time was to connect correctly to the rack as the config that they sent you is good but not complete at all so you definitively need  to review it before you can process your lab. When you don’t know how to process with their connectivities , it is really amazing the time that you can lose .

But next time if I need , I have a template that I can apply to have a quicker setup .


Still trying to make a lab

Hi ,

Since the last update , I’m still working on deploy a home lab with GNS 3 and Vmware image. Still no luck as last week one of my servers crashed. The result was that one DD3 memory is dead …. I can’t tell you how it is funny to discover that once it happened , nothing stay anymore stable. No more possibility to register my remote sites and phones are very slow on the network. I can imagine that GNS3 is taking soo much memories that it sucks my network.

Now still looking to have a real hardware, I’m nearly on the process to have one but still missing some E1/T1 cards to perform it .

Will try to chase for extra-hardware ….

See the results soon 😉

GNS3 – Cloud Interface Trunk

After adding some network adaptor (DUB-E100) on my server to make the trunk available for my 3 sites , DOT1Q was not able to work on the config …. Damned I figured out at this point that I could pass my vlan over this link .

After more troubleshooting and thinking, I came to the point to enable ISL instead of DOT1Q , and after this my trunk was really up and useful as it passed now the vlan information ….. woohoo .

Can continue right now on implementation ….


CTI Route Points and Ports – Partition and CSS Approach

Pay attention that normally the order of the partitionins is always L1,L2,L3, D1,D2,D3 , where Lx are the partitions assosiated to the Line model and Dx are the partitions associated to the Device model.

So this order will give you the order/ priority in case of tie-break !

In the case of CTI Route Point or CTI ports , the order is changed by the following D1,D2,D3,L1,L2,L3 …. Please recall this if you are involved in a troubleshooting with these elements !

Page 4 of 1512345678910...Last »