VoIP Mailing List Archives

[ish at pack-net.co.uk]

Hi

I'm using asterisk 1.8.23.1 but I've seen this same issue in previous versions of 1.8. I have created some work arounds but the behaviour is incorrect.


This is the scenario:
Call comes in and goes to appropriate dialplan
In the dialplan the call is forwarded to another number using a Local channel (and using /n ) e.g.
Dial(Local/<my-number>@outbound-context/n,60)
The number is dialled and the call is all fine.


In the CDR we have 2 entries, one for the inbound leg and one for the outbound leg as is expected by the use of the /n


However, the outbound leg CDR entry has a billsec of 0. The CDR for the inbound leg has the correct duration of the call in the billsec column (I'm writing CDRs to MySQL)


This is causing issues in my billing module for obvious reasons. I'm having to find the inbound call by matching the channel in one leg with the dstchannel in the other leg and that is quite messy.


Would others agree that this behaviour is incorrect? Has anyone else seen this or be able to replicate it? Am I just missing something obvious?


Thanks in Advance


Ish


--

[ish at pack-net.co.uk]

A big correction to the above! 

This 0 billsec entry happens when someone forwards a call from their phone using an auto forward (which then uses a Local channel on the asterisk server). The phone in question is a Snom.


If I use a Local channel in the dial plan, the entry has a the correct billsec.








On 2 May 2014 11:23, Ishfaq Malik <ish@pack-net.co.uk (ish@pack-net.co.uk)> wrote: