buttercool
IS-IT--Management
Hey folks,
I've got a bit of an odd question with respect to MWK on 3904s.
Background: I have previously been using a 25.30 11c integrated to Cisco Unity via DMS100 PRI trunks. On the 25.30 system I was able to program key 16 as MWK 5000 (which is a DSC pointing to my Cisco Unity Pilot DN across the PRI). This set up worked perfectly in that I could press the built-in (bottom row of keys) messages button on a 3904 and it would ring the Unity server and would auto log in to the mailbox corresponding to the extn.
Recently, I rebuilt my config on a newer SSC that is running 4.50w. Everything is working as expected and the configuration is near-identical to the previous one on the 25.30 SSC (same PRI in D100 mode, same DSCs, same Unity server etc etc). However, when building the 3904 and specifying the MWK key pointing to DSC 5000 I received an "SCH0658 - Invalid DN type for MC DN.". Further research led me to this post ( and I ended up using the 'workaround' of having a dummy ACD number NCFW to 5000 with MWC set to yes. The end result is that the built-in messages button *does* dial the Unity server (ACDN 7000 NCFWs to DSC 5000); however, due to the forwarding behavior the Unity server views the calling DN as 7000 and answers with a generic IVR instead of the user's mailbox.
Are there any other options for routing the call whilst still utilizing the built-in Messages button as an MWK and having the Unity server recognize the initial calling number? I looked around to see if ACDNs had any CLS settings like SFA etc, but that doesn't seem to be available. Perhaps since this was a pre-owned SSC that I out'd everything from and re built my config there's something in the CDB that I missed when I was making the two match?
Also, totally understand that I could set up an ADL or HOT D to the DSC (as dialing 5000 manually works just fine), but it would be nice to use the existing messages key to prevent confusion.
I've got a bit of an odd question with respect to MWK on 3904s.
Background: I have previously been using a 25.30 11c integrated to Cisco Unity via DMS100 PRI trunks. On the 25.30 system I was able to program key 16 as MWK 5000 (which is a DSC pointing to my Cisco Unity Pilot DN across the PRI). This set up worked perfectly in that I could press the built-in (bottom row of keys) messages button on a 3904 and it would ring the Unity server and would auto log in to the mailbox corresponding to the extn.
Recently, I rebuilt my config on a newer SSC that is running 4.50w. Everything is working as expected and the configuration is near-identical to the previous one on the 25.30 SSC (same PRI in D100 mode, same DSCs, same Unity server etc etc). However, when building the 3904 and specifying the MWK key pointing to DSC 5000 I received an "SCH0658 - Invalid DN type for MC DN.". Further research led me to this post ( and I ended up using the 'workaround' of having a dummy ACD number NCFW to 5000 with MWC set to yes. The end result is that the built-in messages button *does* dial the Unity server (ACDN 7000 NCFWs to DSC 5000); however, due to the forwarding behavior the Unity server views the calling DN as 7000 and answers with a generic IVR instead of the user's mailbox.
Are there any other options for routing the call whilst still utilizing the built-in Messages button as an MWK and having the Unity server recognize the initial calling number? I looked around to see if ACDNs had any CLS settings like SFA etc, but that doesn't seem to be available. Perhaps since this was a pre-owned SSC that I out'd everything from and re built my config there's something in the CDB that I missed when I was making the two match?
Also, totally understand that I could set up an ADL or HOT D to the DSC (as dialing 5000 manually works just fine), but it would be nice to use the existing messages key to prevent confusion.