| Summary: | ASTERISK-05598: AgentCallbackLogin Ver 1.2 rc2 | ||
| Reporter: | Justin Alonzo (syquoatwork) | Labels: | |
| Date Opened: | 2005-11-14 11:17:44.000-0600 | Date Closed: | 2011-06-07 14:10:34 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_agent |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | 2 Problems 1. When an agent logs in or out instead of the prompt at the end that says agent logged in or agent logged out all they get is a busy signal. 2. The application will only use extensions in the default context but we did not have one, so we had to add one with include statements to the real contexts. This did not happen in 1.09 | ||
| Comments: | By: Kevin P. Fleming (kpfleming) 2005-11-15 15:23:20.000-0600 The AgentCallbackLogin can direct the agent calls to any context you wish; 'show application AgentCallbackLogin' will show you the syntax for doing this. As far as your other problem, without a detailed console trace showing what is happening, we can't even begin to help you. Please try to reproduce the problem and generate a call trace and then reopen this bug with the details (although you'd probably be better off finding a bug marshal on IRC to help you determine whether the problem is actually in your dialplan before coming back here). | ||