I have a question:
Can an upgrade to a Call Manager Publisher cause MGCP to get updated and stop working for the subscribers?
I had the following configuration. 50 and 51 are subscribers and 40 is the publisher. I upgraded the publisher and after it rebooted, the phones stopped working. I changed 50 to 40 and then I failed all of the phones over to the publisher by taking the two subscribers offline. The phones started working again. I then changed the calll manager groups so that all phones would register to 40, brought 50 and 51 back online and I am in the process of upgrading them. I was hoping somebody could verify if the 40 publisher updated the MGCP and it made the gateways stop working for the subscribers? Or any other ideas of the cause of the issue would be great.
!
ccm-manager redundant-host 10.10.10.50 10.10.10.51
ccm-manager mgcp
no ccm-manager fax protocol cisco
ccm-manager music-on-hold
ccm-manager config server 10.10.10.40
ccm-manager config
!
mgcp
mgcp call-agent 10.10.10.50 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp package-capability fxr-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 inhibit
mgcp rtp payload-type g726r16 static
mgcp bind control source-interface GigabitEthernet0/0
mgcp bind media source-interface GigabitEthernet0/0
!
mgcp profile default
Thanks,
Alex
