I see what you’re doing now. That’s pretty clever, I have often needed to have the ability to define custom parameters for each extension, but it never occurred to me that I might repurpose the accountcode field for this. Totally stealing this idea.
edit 3 years later - with the addition of the JSON_DECODE function in Asterisk, you can store multiple key → values pairs in this field in JSON format, then parse out what you need when you need it.