BCM 400 caller id set grayed out

[eyezen]

bcm 400, trying to assign a line to a DN, where one would set appearance type, appearances and caller ID set, the caller ID set box is grayed out and wont let me change it.

I've tried untying the line from the DN, restarting element manager, and even rebooting the bcm, but no dice on this particular dn/line pair

I've tied target lines to other DN's before and after without issue

Any suggestions?

 

[gberger]

Make sure the line is set to "appear&ring" on the set.

 

[eyezen]

Thanks for the reply, however doesn't seem to make a difference.

 

[telcodog]

If it's a CO trunk you're trying to assign, the only way that happens is if it is set to appear only. Ring only and Appear & Ring allow you to check the caller id box but the appearances show as N/A.

If it's a target Line, Ring & Appear allow you to select the number of appearances and check the caller id box and so does Ring only. Appear only allows you to select the number of appearances but does not allow you to check the caller id box.

This is assuming you are trying to assign these types of lines to digital/IP sets, although pretty much the same thing happens with analog sets except that you can only make them Ring only of course.

 

[eyezen]

It's a PRI DID target line, I've tried toggling thru just to see if it would kick it loose. No dice.

For kicks I've assigned other target lines to this DN and it works like its supposed to and I've assigned this target line to another DN and it doesn't work.

 

[cook1082]

Is that target assigned to olat of other phones if it is there is a limit on how many can get CLID .try unassigning from another then assign it to that phone and see.

 

[eyezen]

Thanks for the reply.

No, it is not assigned to any other DNs.

 

[cook1082]

Then rebuild the target on another line number since other lines work.

 

[eyezen]

Ok, I can do that and is a viable workaround. But it doesn't get to the crux and explain why the one is not working.

Thanks everyone.

 

[JTDubai]

Do not watse your time if you are trying to do it on analog trunks and using GATM8.I am not sure whether this is enabled in the recent software release.



JT

 

[eyezen]

It's not, as stated above its a DID coming in on a PRI.

 

[cook1082]

I have seen some times that a target line is corrupted amd wont work and rebuilding it on another target it will work. Ex. not going into VM.