asterisk users - Jun 2004 - CDR for transfered calls

Hi there,
                I have the following scenario:
I want user A to make a call to user B. If, any of these users transfer the 
call to user C, then asterisk should generate a CDR for the first leg of the 
call. And after the transfered call is finished, asterisk should generate a 
second CDR.
I believe I was able to do it once, a long time ago...
But, I tried this feature again today, and asterisk was generating only one 
CDR (for the transfered call).
Is this possible?
I use aterisk 0.7.2 with Grandstream phones.

thanks in advance,
                           Pablo Salinas

pesb wrote:
> Hi there,
>                 I have the following scenario:
> I want user A to make a call to user B. If, any of these users
> transfer the 
> call to user C, then asterisk should generate a CDR for the first leg
> of the 
> call. And after the transfered call is finished, asterisk should
> generate a 
> second CDR.
> I believe I was able to do it once, a long time ago...
> But, I tried this feature again today, and asterisk was generating
> only one 
> CDR (for the transfered call).
> Is this possible?
> I use aterisk 0.7.2 with Grandstream phones.
> 
> thanks in advance,
>                            Pablo Salinas
> 
Try 
notransfer=no in iax.conf

Hi, 
> -----Original Message-----
> Try 
> notransfer=no in iax.conf
Hmm, I assume you mean transfer=no, but that also keeps the voice flow
through the machine. Would IAX2 support having signalling going through all
machines and voice data through the shortest path, more or less like how SIP
works, while keeping the nice NAT/firewall functionality :-)

I would not be surprised if this is impossible by design, but who knows...

Florian

> Would IAX2 support having signalling going through
> all machines and voice data through the shortest path
No, Signalling+Voice is tightly coupled.

Holger Schurig wrote:
>> Would IAX2 support having signalling going through
>> all machines and voice data through the shortest path
> 
> No, Signalling+Voice is tightly coupled.
To my knowledge, IAX2 will take shortest route possible. I.e.

A call from UA A to UA C through server B will switch from original path
(A>B>C) to (A>C) and this is default behaviour unless
"notransfer=yes"
exist in iax.conf.

Anyone know for sure?

Ta
Senad

Hi, 
> -----Original Message-----
> > No, Signalling+Voice is tightly coupled.
> 
> To my knowledge, IAX2 will take shortest route possible. I.e.
> 
> A call from UA A to UA C through server B will switch from 
> original path
> (A>B>C) to (A>C) and this is default behaviour unless
"notransfer=yes"
> exist in iax.conf.
Yes. The issue here is that billing information is never correct in such a
scenario, since the call duration on the registered asterisk machine (the
one that is kicked from the path) is no longer correct. To fix this a
notransfer=yes is mandatory, but that defies the practicality of having a
voip conversation take the shortest path.

Florian

Florian Overkamp wrote:
> Hi,
> 
>> -----Original Message-----
>>> No, Signalling+Voice is tightly coupled.
>> 
>> To my knowledge, IAX2 will take shortest route possible. I.e.
>> 
>> A call from UA A to UA C through server B will switch from
>> original path
>> (A>B>C) to (A>C) and this is default behaviour unless
>> "notransfer=yes" exist in iax.conf.
> 
> Yes. The issue here is that billing information is never correct in
> such a scenario, since the call duration on the registered asterisk
> machine (the one that is kicked from the path) is no longer correct.
> To fix this a notransfer=yes is mandatory, but that defies the
> practicality of having a voip conversation take the shortest path. 
Sure... So, this issue is "sort of a bug" and it really needs to be
implemented then!