Quote:
Originally Posted by pmx  First off thanks for an amazing zimlet! I have used it every day since installed and must say its rock solid as far as I can tell.
Today I embarked on getting my colleagues to also use it - but I encountered a problem;
We use a pbx from a company named Diptel ( link) - It is based on asterisk 1.4. It is the one I have configured for my account now, so it is working; but it takes complete control of the asterisk dialplan and it places every user in a unique context they need to use in order to get the right MSN number when calling pstn.
For now I have created a common user that has our main switchboard number as MSN, and use that context, but that means our customers will see the main switchboard number calling, not the agents personal extension - it could create some confusion if not answered and the customer dials back later on hitting the switchboard that does not know who called who 
Would it be possible to allow the context to be configureable on a per-user basis? And, for scalability in the future - maybe the server/user/pass fields also since I can foresee scenarios where I might place some of my users on a separate pbx, e.g. a branch office or something...
Well.. just my 2c.. thanks again for this great piece of code |
Hi pmx
A user configurable context is rather easy to implement. I am just a bit skeptical because of security reasons. I could let the global option and if present it would always override the user preference. So its up to the admin to decide. But it think its not worth to implement user configurable AMI user/pass. I would prefer same AMI user/pass for all asterisk instances than user editable one's(that are even readable when using a JSdebugger in the Browser).
You don't have multiple zimbra hosts, dou you? There would be the possibilty to user host based options instead of global one's. But of course these refer to the zimbra host. So if there is a 1:1 relation of zimbra hosts to asterisk instances it might be a solution.