<p class="MsoNormal">This is a very interesting topic and very relevant for
advanced configuration of Asterisk. Yes we all know it is the wrong list! <span style="font-family: Wingdings;"><span style="">:-)</span></span></p>
<p class="MsoNormal">In all earlier versions of Asterisk including Beta 1.2 we
got the following:</p>
<p class="MsoNormal">agi_channel: IAX2/70104@83.229.221.208:4569-3</p>
<p class="MsoNormal">in the brand new Asterisk 1.2 we got the following:</p>
<p class="MsoNormal">agi_channel: IAX2/83.229.221.208:4569-2</p>
<p class="MsoNormal">We used to identify the device or username using channel. But
on IAX from 1.2 that is not working at all. I posted this on the user list and Kevin
P. Fleming replied.<br>
<br>
It was changed without specific notice, because you could
not rely on<br>
the IAX2 user name always being present in the channel name
anyway. The<br>
other channel drivers also do not put the user name into the
channel<br>
name, so now it's consistent.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-weight: bold;">The Solution:</span></p>
<p class="MsoNormal"><span style="font-weight: bold;">We use accountcode</span></p>
<p class="MsoNormal">For each device/username we add the username as accountcode.</p>
<p class="MsoNormal">In extension.conf we can now retrieve the value using ${ACCOUNTCODE}</p>
<p class="MsoNormal">This is very simple and very reliable and has removed the
need to parse the channel variable. This is even more important now when Kevin P. Fleming
has confirmed that we can't rely on the channel information.</p>
<p class="MsoNormal"> --<br>
Are Casilla<br>
</p>
<a href="http://astartelecom.com">http://astartelecom.com</a> - Independent VOIP Telecoms Broker. Asterisk Consultants<br><a href="http://astbill.com">http://astbill.com</a> - Open Source Billing, Routing and Management software for Asterisk and VOIP
<br>AstBill DEMO: <a href="http://demo.astbill.com">http://demo.astbill.com</a><br>