<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello list,<br>
<br>
I don't know if anybody faced this issue, but I finally found a
workaround. I am using an external program with an AMI connection to
originate outbound calls to Local/ channels, and on the dialplan
context I dial outside with the corresponding trunk according to the
prefix of the dialed number. The problem here was CDR, more precisely
the uniqueid. Reading these mail lists I learned that when a Local
channel finds a Dial instruction on the dialplan, and when the new
requested channel is answered then a masquerading begins, so the new
dialed channel becomes the active and the Local/ one becomes inactive
as a <zombie>. This was putting problems for me because when I
record calls, I use the following sentence:<br>
<br>
exten => s,n,MixMonitor(${UNIQUEID}.gsm,b)<br>
<br>
Instead of the workarounded right one for me:<br>
<br>
exten => s,n,MixMonitor(${CDR(uniqueid)}.gsm,b)<br>
<br>
Does anyone know why the ${UNIQUEID} variable is not updated on the
masquerading process while ${CDR(uniqueid)} is? Is this a bug or is a
correct behavior?<br>
<br>
I faced another issue too, when the answered call gets queued, the
queue log results in this:<br>
<br>
1237931601|1237931598.374076|prueba_outbound|NONE|ENTERQUEUE||3555555<br>
1237931601|1237931598.374076|prueba_outbound|Agent/1000|CONNECT|0|1237931601.374079<br>
1237931601|1237931598.374076|prueba_outbound|Agent/1000|TRANSFER|s|marcador-prueba_outbound|0|0<br>
<br>
This queue log behavior renders the information unusable, because the
queued call could not be tracked anymore. The dialplan was this:<br>
<br>
[marcador-prueba_outbound]<br>
exten => s,1,Answer()<br>
exten => s,n,MixMonitor(${CDR(uniqueid)}.gsm,b)<br>
exten => s,n,Queue(prueba_outbound,ht)<br>
exten => s,n,Hangup()<br>
<br>
So I introduced a little Wait() to help asterisk finish the
masquerading process before queueing the call, to the bogus transfer
event does not occur inside the queue application:<br>
<br>
[outbound-context]<br>
exten => s,1,Answer()<br>
<b>exten => s,n,Wait(0.5) ;(WORKAROUND FOR QUEUE_LOG BUG)</b><br>
exten => s,n,MixMonitor(${CDR(uniqueid)}.gsm,b)<br>
exten => s,n,Queue(prueba_outbound,ht)<br>
exten => s,n,Hangup()<br>
<br>
This produces the correct events in the queue log:<br>
<br>
1237932417|1237932415.374509|prueba_outbound|NONE|ENTERQUEUE||53555555<br>
1237932417|1237932415.374509|prueba_outbound|Agent/1000|CONNECT|0|1237932417.374512<br>
1237932424|1237932415.374509|prueba_outbound|Agent/1000|COMPLETEAGENT|0|7|1<br>
<br>
This kind of problems seems very weird to me. Should I post bug notes
about this issues?<br>
<br>
Any comments welcome.<br>
<br>
Thanks in advance,<br>
<pre class="moz-signature" cols="72">--
Ing. Miguel Molina
Grupo de Tecnología
Millenium Phone Center
PBX: (+57 1)6500800 ext. 1201
Fax: (+57 1)6500816
Móvil: (+57)3138873587
</pre>
</body>
</html>