On 4 April 2013 09:05, Ishfaq Malik <[email protected]> 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 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 this happened? > > > It means we can't upgrade without doing significant extra development > > > and testing. > > > > > > > This was most likely an unintended consequence of some other change > > (most likely dealing with masquerades). Is 1.8.18.0 the exact version > > when the behaviour changed? > > > > Just so I'm clear on the scenario, what are the channel technologies > > involved? Is the transfer initiated via a protocol message or via a DTMF > > feature? > > > > Thanks, > > > > Matt > > > > Hi Matt > > Did you ever spot/recreate the change I was referring to? > > > "me too" - I can confirm a behaviour change and will go try and pin down at what point it happened.
This may take me a while :( Steve
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
