[Home]

Summary:ASTERISK-05352: AgentCallbackLogin parsing issues
Reporter:wunderkin (wunderkin)Labels:
Date Opened:2005-10-22 22:10:00Date Closed:2011-06-07 14:10:27
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:* AgentcallbackLogin is trying to parse the Local channel as options

* An * at the beginning of the extension does not work, it only works once it asks me to enter the extension manually

* Local /n does not work on AgentcallbackLogin, although it is accepted as a static member in queues.conf

Output:

   -- Accepting call from '2' to '202' on channel 0/1, span 3
   -- Executing AgentCallbackLogin("Zap/49-1", "11000|Local/*12222222222@autodial-outagent-test/n") in new stack
   -- Warning: option L is unknown.
   -- Warning: option o is unknown.
   -- Warning: option c is unknown.
   -- Warning: option a is unknown.
   -- Warning: option l is unknown.
   -- Playing 'agent-pass' (language 'en')
Oct 22 20:05:57 WARNING[12370]: chan_agent.c:1856 __login_exec: Extension '12222222222' is not valid for automatic login of agent '11000'
   -- Playing 'agent-newlocation' (language 'en')
Oct 22 20:06:06 WARNING[12370]: chan_agent.c:1860 __login_exec: Extension '*1222222222@autodial-outagent-test/n' is not valid for automatic login of agent '11000'
   -- Playing 'invalid' (language 'en')
   -- Playing 'agent-newlocation' (language 'en')
   -- Channel 0/1, span 3 got hangup request
Oct 22 20:06:17 WARNING[12370]: file.c:579 ast_readaudio_callback: Failed to write frame
   -- Playing 'vm-goodbye' (language 'en')
 == Spawn extension (default, 202, 1) exited non-zero on 'Zap/49-1'
   -- Hungup 'Zap/49-1'
Comments:By: Russell Bryant (russell) 2005-10-24 21:11:36

That is the incorrect syntax.  You need to remove "Local/".
By: wunderkin (wunderkin) 2005-10-24 21:31:11

The Local/ thing was my fault yes sorry, but everything else still stands.  

Yeah I know I put in the wrong exten the 2nd time too.  That's a long exten.  It
still doesn't work though if I do put the right one in as you see.

Oh, maybe /n isn't needed? or not supposted to be used?  (I was trying that to help fix my other bug reported)

Ok so that leaves me down to 1 problem still then with * at the beginning.


By: Russell Bryant (russell) 2005-10-24 22:12:28

I have created a new bug, ASTERISK-5361, which addresses your problem with an extension beginning with '*'.  Please test the patch and report your results to that bug.  Thanks!