Unable to access NuPoint

[Odycon]

Greetings to the Massed Might of the Forum.
Kind of new to this so here goes.  We have a VMware bundle of MCD, MAS, MBG etc all running smoothly apart from when I try to access a nupoint mailbox (dial 6000) I get "NO DISTB"
The phone has a mailbox provided via MAS, the 6000 group is a voicemail group with 3 ports in and all the appropriate COS seem to be OK.
Scratching my head a bit now so I will throw myself at the mercy of the forum to see what I've done wrong.
Many thanks in appreciation.

[lundah]

The port answering the call probably has permanent DND enabled in COS. Double check the COS settings for your ports, only those ports set aside for MWI should have permanent DND enabled.

[Odycon]

Thanks for the reply.  I went down that road when I saw the NO DISTB indication. The DND Permanent is turned off on all ports except the MWI as you would expect (or hope) as the system had initial setup with MiCW.

[Odycon]

As additional info.  When you ring one of the ports it shows as out of service.

[lundah]

Just that one port, or all of them? Is NuPoint actually up and running?

[markyb73]

When you ring the hunt group and get DND then all the ports will be out of service.
So something must be wrong on either the MCD config, NuPoint config, or both i would think.

What have you setup so far?

[johnkeri]

Step one: make sure the hunt group is ok.
Hunt group 6000, verify members are present. Check rerouting: no reroute.
Step two: verify ports are up
Command line: state extension <hunt group members>
Check for all the ports.
Note:
Dependent on software level ports must be programmed as trusted service.
If you have the Record a call feature the set type must be changed.
Step three:
Line group configuration in the voicemail. make sure ports are included and dial plan is correct.
If the number of digits are different say 4 on the phone system but three in the dial plan, you will never get to a mailbox.
And there are many many more steps..

[Odycon]

Mmmm. Think I've found the problem. checked with the IT guys that look after the VM platform and they updated the MAS by SW update instead of deploying an updated OVA & restoring database. As such there is an error showing on the MCD network element of MAS which seems to be messing up NuPoint. Will have to do some work on it & get it back to normal and hopefully that will resolve the NuPoint problem.
Thanks for your input guys.