Limitation of specific Expansion Module to use only on single specific phone (to avoid wild module changes between users)

[tobias.brauer]

Hi there,

is it possible to bind and limit one specific expansion module, Type 7914/7915/7916 to an single specific IP Phone, based on MAC or serial number etc.?

We recently had a large rollout of 7962 Phones and expansion modules.

The problem was that users began to randomly exchange their modules so that we don't know where specific devices remained.

The only limitation parameter I know so far is just enabling/disabling expansion module.

Do you know any method to limit an user phone to use only that exp. module what has been provided to it?

CUCM 7.1.5

Many thanks in advance!

-Tobias

[paolo bevilacqua]

I don't think  it's easily possible, because CM does not use the S/N of expansion module in any manner.

You would have to create a custom application that interrogate the phone via HTTP, and alerts detects when a S/N change connected module.

[Jaime Valencia]

No way to do such thing, since you only configure the expansion module in the phone config using the model.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

[slashdots · Accepted solution]

As Paolo and Jaime stated this would be a very complex, if not impossible task to do.

However its possible to make a List of the Phones with one or more connected:

This way you can at least find out were to search for modules..

run sql select d.name Devicename, phone.name Phonemodel, t.name Modulename1, t2.name Modulename2 from device as d
inner join deviceaddonmodulemap as dm on d.pkid=dm.fkdevice
inner join deviceaddonmodulemap as dm2 on d.pkid=dm2.fkdevice
inner join typemodel as t on dm.tkmodel=t.enum and dm.moduleindex=1
left join typemodel as t2 on dm2.tkmodel=t2.enum and dm2.moduleindex=2
inner join typemodel as phone on d.tkmodel=phone.enum 
 
 Example Output:
 
devicename              phonemodel    modulename1                                                     modulename2
=============== ========== ==================================== ===========
SEP000000000000   Cisco 7961     7914 14-Button Line Expansion Module                 NULL
SEP000000000001   Cisco 7962     7915 12-Button Line Expansion Module                 NULL
 

This query was tested on CUCM 8.6.2 (LAB environment)

[tobias.brauer]

Hi Slashdots,

this idea is great!

So we can at least see and compare if an user is still using the expansion module which was selected for him.

The other answers are also helpful, maybe we let develop a new software solution for that to lookup the S/N and compare.

Thank you and have a nice day!

-Tobias