No subject

Asterisk features transfer, but it might be worth confirming this.

You may find that the difference is the result of how the phone handles
the transfer.  SIP wasn't designed with the forwarder pays billing policy
in mind, but rather with the ability to optimise the call route.  If
Asterisk were to actually pass the REFER back up stream, the party A to
party C call would appear as a completely seperate call, that might not
even go through Asterisk.  It is only because Asterisk doesn't do this that
it is possible to attempt to bill this case.

One possibility that I can see here is that the phone sends the
REFER/Replaces to A in one case and to C in the other case.  Both are
allowed by the RFCs, as far as I know.  I wonder if it is sending it to C
when the call is established and to A, otherwise.  The protocol traces
would help to show whether that is the case.  It may even be dropping the
unanswered call and sending a simple REFER.

When you say user fields, I take it that you mean CLI and "extension"
number.

Note that there is a new CDR mechanism, channel event logging, being
introduced from about version 6.2, which is intended to make billing
complex cases possible. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-06 11:53 davidw         Note Added: 0111912                          
======================================================================