Extension Mobility (em) not working with Call Control Discovery (CCD) on CME
PhoneA <=> CME1 <=> CME2 <=> PhoneB
Phone A original number: 10011
Phone B original number: 10021
EM on B number: 10099
Problem: I have extension mobility working (minus a bug where EM hangs when you try to log in as described here and here). I also have call control discovery working (I can call from phone B to A and from A to B without a predefined dial-peer). However when I log on to my extension mobility account on CME2 who has number 10099 I'm unable to call from A to EM on B, but I can call out from EM on B to A. It seems as though ccd isn't able to realize that my user is available and doesn't pass that information on. Is there someway to make EM work with CCD?
Relevant Config on B:
voice logout-profile 1
user tom password tom
number 10021 type normal
voice user-profile 1
user t password adgj
number 10099 type normal
router eigrp saf-fwdr
service-family ipv4 autonomous-system 10
dial-peer voice 100 voip
session target saf
voice service saf
profile trunk-route 1
session protocol sip interface GigabitEthernet0/0 transport tcp port 5060
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.