Not Null Property Refrences Error when adding IP phone

[dabble]

I'm trying to add a new IP phone via UCM from a template.
CS1000E at Rls 6 but I receive the error message below:

I have no idea what this means!

not-null property references a null or transient value: com.nortel.ems.mgmt.phone.model.AssignedDirectoryNumber.dn

 

[Tman45]

That's why I hate using TM - try building it using command line

My guess would be that the DN you entered in might already be an assigned DN or one that is out of your range?

 

[dabble]

I think somehow it has something to do with message center DN. When I try to add a new phone via element manager based on a template, I have key 16 defined as MWK 4000, I get SCH0658 which is invalid DN type of MC DN. So I remove key 16 and just leave it as NUL, then try to save it and that is when I get the not-null property error message.

I can add a set OK via command line without the MWK key.

How can I define the Message center DN in the switch?

 

[dabble]

Just found out that we need package 175 for network message services which some how the engineering group missed when designing this new system. That seems to be the cause of these errors.

 

[Dphone]

not-null property references a null or transient value: com.nortel.ems.mgmt.phone.model.AssignedDirectoryNumber.dn

I'm getting this error also. I have package 175. CS1000M 7.0

Anyone know what it means?

 

[Dphone]

My problem was that I had Key 16 assigned as MWK with no voice number. I don't have voice mail on this phone so I just unassigned key 16 and everything was fine.

 

[Tman45]

Yeah that makes sense. Quit trying to assign voicemail without the number (DN) to launch voicemail I have never built one blank because configuring a Message Waiting Key I thought required the mailbox DN.

So dabble is your extension to enter voicemail 4000? For example our Nortel Voicemail extension is 6000 and my MWK is setup as KEY 16 MWK 6000 so if yours is 4000 make sure you have MWA setup in your CLS as well.

 

[dabble]

I have to wait until I get Packagd 175 installed before I can configure key 16 as an MWK key.

Still trying to get through all the red tape and paper work from my vendor in order to get this new keycode.