On 4 April 2013 09:05, Ishfaq Malik i...@pack-net.co.uk wrote:
On Tue, 2013-03-26 at 07:26 -0500, Matthew Jordan wrote:
On 03/26/2013 05:22 AM, Ishfaq Malik wrote:
Hi
In asterisk 1.8.7.0, an inbound call that was transferred to another
peer would have 2 cdr entries.
In
On Wed, 2013-04-24 at 12:48 +0100, Steve Davies wrote:
On 4 April 2013 09:05, Ishfaq Malik i...@pack-net.co.uk wrote:
On Tue, 2013-03-26 at 07:26 -0500, Matthew Jordan wrote:
On 03/26/2013 05:22 AM, Ishfaq Malik wrote:
Hi
In asterisk
On Tue, 2013-03-26 at 07:26 -0500, Matthew Jordan wrote:
On 03/26/2013 05:22 AM, Ishfaq Malik wrote:
Hi
In asterisk 1.8.7.0, an inbound call that was transferred to another
peer would have 2 cdr entries.
In asterisk 1.8.18.0 this same activity has a single cdr entry.
This is a
On Tue, 2013-03-26 at 07:26 -0500, Matthew Jordan wrote:
On 03/26/2013 05:22 AM, Ishfaq Malik wrote:
Hi
In asterisk 1.8.7.0, an inbound call that was transferred to another
peer would have 2 cdr entries.
In asterisk 1.8.18.0 this same activity has a single cdr entry.
This is a
Hi
In asterisk 1.8.7.0, an inbound call that was transferred to another
peer would have 2 cdr entries.
In asterisk 1.8.18.0 this same activity has a single cdr entry.
This is a rather large and fundamental change to be enacting halfway
through a single family branch, was there any reason why
On 03/26/2013 05:22 AM, Ishfaq Malik wrote:
Hi
In asterisk 1.8.7.0, an inbound call that was transferred to another
peer would have 2 cdr entries.
In asterisk 1.8.18.0 this same activity has a single cdr entry.
This is a rather large and fundamental change to be enacting halfway
