CM6.3 to AAM integration issue (Restricted per CPN)

[IVRGirly]

We have a customer that was on CM6.2 and had multiple stations that had Restricted CPN as they didn't want their numbers shown when they made outbound calls. After the CM6.3 upgrade, these folks no longer could hit their message button to route to Voicemail. The only work around that can be found is to change the Restricted CPN back to no so the VM integration would begin working again. Obviously, this is not ideal, as when the customer makes an outbound call, their DID shows.

Any suggestions on how to restrict the outbound calling ID AND keep the CM to AAM integration still happy?

 

[kyle555]

It's probably a numbering format problem. I haven't looked into it, but I know for a fact I have restricted users on voicemail with no problem.

If the trunking to voicemail is of a public numbering format, I can see that being restricted, but it shouldn't be if the numbering format is private.

I'm not saying this PSN solves your problem, but it's a fantastic description of how CM decides what numbering format to use:

https://downloads.avaya.com/css/P8/documents/101034284