How to detect or manage expansion modules ?

[jolouis]

Agree that the most convenient way to implement this would be to have it show up as part of the header for auto-provisioning, though I'm not sure if the expanders are initialized at that point in order to make that actually possible.

Since expansion setup is usually tied to specific extensions it usually makes sense to build the logic into your provisioning generation scripts rather than the config itself. i.e. if the mac address matches the extension for reception, then generate the additional config for the reception expanders.

One of the things worth noting is that there is no adverse side effects for configuring expansion modules that don't exist; the phone simply doesn't do anything with the settings. So for example we have a customer who has an expander on every desk phone in their office, but not common area and meeting room phones. The provisioning file generates the expansion_module.x configs for every single request, and the phones that don't have expanders simply ignore it.

As for the type of expander, that's also kind of a mute point since realistically all the Yealink modules are basically the same from a config perspective; not really sure why you would care about an exp-20 vs an exp-40 (and you could easily solve that by checking the model number of the phone itself in the request header).