I have an MCDN keycode on one unit that I took out on site on Friday where the other existing BCM50 has MCDN on it. I couldn't get private digits to work there either. I came home. Hooked up the unit here and thought maybe if I played around, I'd get private at least to work one direction. Nothing, just public rec'd works? Doesn't seem to matter if it's non, cdp, udp? Is there something I'm missing? I've put the calls out on a private route and it is reflected in that the incoming OLI and name display seem to reflect the private information, however I can only get the calls to ring the target line if the extension # is in the public rec'd digits field. If I only put it in the private rec'd digits, the call rings in on the prime set, and still shows the private incoming OLI and name? I'm testing with a 3.7 BCM 200 and I've put the recent core and SU3 patches on just in case. Public only on incoming even though there's an MCDN keycode in it? Do I need other fields filled in like access codes, location codes, virtual private network id, zone id? I've turn on MCDN over IP in UIP so that I could check but all it get is Trunk 60 23:18:09 < CC < CRef Origin CRef 7E28 SETUP EDGE 3 BILL 321 226 when I'm dialing from 321 to 226 on the other system. I get the same Trunk 60 23:18:33 < CC < CRef Origin CRef 7E28 ALERTING when I call from 226 to 321, when answered it shows Trunk 60 23:18:39 < CC < CRef Origin CRef 7E28 CONNECT 321. MCDN shows nothing in the NON-MCDN unit. Go over all settings in case I'm missing something, it can't be this difficult? Thanks.
