syntax test

master
Jay 2 years ago
parent a7101b0b01
commit b756f7df3e

@ -18,7 +18,7 @@ Anyway…after three days of stumbling around search results, reading older revi
I did not keep track of what modules I had to activate in my barebones install; I know I activated voicemail and while applications a while back; I dont remember if db was in the minimal config. I dont think queue requires any of those, so its probably a good bet these are all youll need to put in modules.conf:
```
```bash
load = app_queue.so
load = app_agent_pool.so
@ -33,16 +33,13 @@ I seem to remember in reading the documentation, you needed to make sure that ap
I wanted the call agent function simply so I could use \* and # on the deskphone in a way that felt “more radio” than punching them on a softphone. I mostly just didnt want to have to switch apps to switch calls. This is what gave me the most trouble, mostly due to the lack of chan\_local and knowing that I had to specify the agent as local…and…wow. The way agents are created is also VASTLY different than the old software. You no longer have a single \[agents\] context that specifies agents; each agent ID gets its own context.
```
```bash
[501]
ackcall=yes
acceptdtmf=#
autologoff=0
musiconhold=silence
```
@ -54,7 +51,7 @@ This is my absolute minimal configuration for Agent 501. The options themselves
I was so close on this one. In fact the only thing I had wrong was how I was adding agents as members. Most docs and examples made it look as easy as:
```
```bash
member = Agent/501
@ -63,7 +60,7 @@ member = Agent/501
But no, thats wrong; and it was only after reading about the change to app\_agent\_pool and a forum post that I figured out how to actually specify an agent as a member:
```
```bash
member => Local/501@agents,,Jay,Agent:501

Loading…
Cancel
Save