We have multiple offices and each has its own PBX. We are using DUNDI for extensions. I’d really like it if someone could call the main office and search the company wide dial-by-name directory - getting routed to remote offices via DUNDI.
Kind of a vague description, but is there anyway to do this? It doesn’t appear that DUNDI has the commands to do this, but would it be possible using LDAP? Astirectory linked off the ldap *wiki page sounded promising, but I can’t find much info on that project so I’m guessing it’s dead?
Directory() uses the voicemail.conf file for the user information. I have scripts on the remote servers that parse their config file and send the relevant portions, including if the user recorded their name from within VM (not the greeting, just the name) to the central server. Then a script on the central server puts all the pieces together and creates a special VM context for Directory(). As the number of changes is not dramatic on any single day, I only run the scripts once a day.
Cool, that sounds simple enough. Since none of the extensions exist on the main pbx if the other pbx is down things might fail. How do you handle that? I guess it would be possible to do some sort of host-up check and based on those results determine if that context should be included in the dial-by-name dir.
We add the user extensions to the ldap server so I’d like to find a way to use that info instead of voicemail.conf. Still will need a host-up check, so I guess the only real benefit is no script to run from cron.
I do not do anything special for error handling of Directory().
If the directory look up fails (extension 0, *, i) , the caller gets sent to the attendant. (I don’t know if I ever got an ‘i’ exten)
If the DUNDI look up files, the caller gets sent to the attendant.
If the call fails after a successful DUNDI look up, a generic error message is played and the caller is sent to the attendant.
I have seen reference to voicemail in realtime using LDAP, but I have never used it. With that, it looks like you could move to a central VM server and accomplish the same thing. But do you want a central VM server using LDAP?
You could write a script that will pull the ldap entries out and create a voicemail.conf file based on the LDAP contents.