[asterisk-bugs] [Asterisk 0008173]: [patch] No Uniqueid generated on Async Originate AMI request

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=8173 
====================================================================== 
Reported By:                datacompboy
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   8173
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:            1.2.12.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             10-18-2006 11:22 CDT
Last Modified:              04-17-2008 06:27 CDT
====================================================================== 
Summary:                    [patch] No Uniqueid generated on Async Originate AMI
request
Description: 
Async Originate AMI request should allocate Uniqueid, and report it in
Response, so it will be possible to run from parrallel AMI managers async
Originations and correctly separate messages and events for that
originations.
====================================================================== 

---------------------------------------------------------------------- 
 datacompboy - 04-17-08 06:27  
---------------------------------------------------------------------- 
Message log with comments below.

   * Send async origination request
<<0.298.0>> Send packet: [["Action",": ","Originate","\r\n"],
                          ["Channel",": ","Local/1 at ps_out","\r\n"],
                          ["Async",": ","yes","\r\n"],
                          ["Timeout",": ","120000","\r\n"],
                          ["Variable",":
",["number","=","0079139257974"],
                           "\r\n"],
                          ["\r\n"]]
  * got reply with uniqueid
<<0.298.0>> Got packet: [<<"Uniqueid: asterisk-4616-1208430784.48\r\n">>,
                         <<"Message: Originate successfully
queued\r\n">>,
                         <<"Response: Success\r\n">>]
  * dialout start, created new channel. it have its own uniqueid! but
should have same as origination ID, to have possibility of matching
<<0.298.0>> Got packet: [<<"Uniqueid: asterisk-4616-1208430785.49\r\n">>,
                         <<"CallerIDName: <unknown>\r\n">>,
                         <<"CallerIDNum: <unknown>\r\n">>,
                         <<"State: Down\r\n">>,
                         <<"Channel: Local/1 at ps_out-47e2,1\r\n">>,
                         <<"Privilege: call,all\r\n">>,
                         <<"Event: Newchannel\r\n">>]
  * created second part of local channel, it also have its own uniqueid:
<<0.298.0>> Got packet: [<<"Uniqueid: asterisk-4616-1208430785.50\r\n">>,
                         <<"CallerIDName: <unknown>\r\n">>,
                         <<"CallerIDNum: <unknown>\r\n">>,
                         <<"State: Ring\r\n">>,
                         <<"Channel: Local/1 at ps_out-47e2,2\r\n">>,
                         <<"Privilege: call,all\r\n">>,
                         <<"Event: Newchannel\r\n">>] 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-17-08 06:27  datacompboy    Note Added: 0085608                          
======================================================================