| Summary: | ASTERISK-00035: agentcallbacklogin does not use the optional context to find a ext | ||
| Reporter: | tclark (tclark) | Labels: | |
| Date Opened: | 2003-08-02 15:52:15 | Date Closed: | 2004-03-27 14:56:01.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | if you use the AgentCallbackLogin with the optional context arg the extention entered at the promt is not found exten => *3,1,AgentCallbackLogin(101|dispatchlogin) but if you place the ext in the [default] context the ext is found | ||
| Comments: | By: Mark Spencer (markster) 2003-08-03 13:14:15 Should be added in CVS. Please confirm so I can close this ticket. By: Mark Spencer (markster) 2003-08-03 13:15:04 Note that it should be |@context, as matching documentation. By: tclark (tclark) 2003-08-04 09:57:42 tested 08/04/03, this appears to be working with r1.19 of chan_agent.c BUT if you enter an invalid ext in the @context a prompt should say "Invalid extension. please try again" & return an error and not say "agent logged in" a Notice is properly generated on the CLI NOTICE[213012]: File chan_local.c, Line 310 (local_alloc): No such extension/context dispatchlogin@1 creating local channel By: Mark Spencer (markster) 2003-08-16 10:24:41 Fixed in CVS, including feature request | ||