[Serusers] call log and accounting for forwarded and referredcalls

[Martin Koenig]

Hello,

welcome to the world of SIP, where the end devices are supposed to be the
intelligent network, not the network itself.

To really make this and other features ISDN-like features work in the
network, one needs a b2bua somewhere.

A---SER---B2BUA---SER---B
C---^
     ^accounting SER

A calls from PSTN, B2BUA receives the call, sends INVITE to B
B sends 302 to B2BUA.
B2BUA sends INVITE in the name of B to C.

Regards,
Martin



> -----Original Message-----
> From: serusers-bounces at lists.iptel.org 
> [mailto:serusers-bounces at lists.iptel.org] On Behalf Of Atle Samuelsen
> Sent: Wednesday, December 22, 2004 9:40 AM
> To: Richard
> Cc: serusers at lists.iptel.org
> Subject: Re: [Serusers] call log and accounting for forwarded 
> and referredcalls
> 
> 
> At the moment SER does'nt do recursion on 302. If ser had 
> done this, The
> world would be a bether place for all us.
> Anyhow. in a A-B-C-D scenario.. A should pay to B, B to C and C to D.
> 
> 
> 
> -Atle
> 
> * Richard <richard at o-matrix.org> [041222 09:04]:
> > 
> > 
> > > -----Original Message-----
> > > From: Juha Heinanen [mailto:jh at tutpro.com]
> > > Sent: Tuesday, December 21, 2004 9:25 PM
> > > To: Richard
> > > Cc: serusers at lists.iptel.org
> > > Subject: [Serusers] call log and accounting for forwarded 
> and referred
> > > calls
> > > 
> > > Richard writes:
> > > 
> > >  > When a SIP call is blind-transferred with REFER and 
> forwarded with "302
> > >  > moved temporarily", UA would start a brand new call. 
> The problem is how
> > > to
> > >  > log and account for their calls. For example, A calls 
> B, B sends 302
> > > and
> > >  > uses C's number as contact. The new call is made from 
> A to C. The call
> > > log
> > >  > would show it is from A to C. The call log should at 
> least have an
> > >  > indication of B forwarding the call. Also B is 
> supposed to pay the
> > bill.
> > > It
> > >  > is not A although the call log shows it is A to C. A 
> has no knowledge
> > > that a
> > >  > toll call is made when calling B.
> > > 
> > > richard,
> > > 
> > > i disagree that in case of 302, b should pay the bill.  
> 302 means "b has
> > > moved to c and it is up to you if you want to try this new uri".
> > > 
> > > if you want b to pay the bill, then b should configure 
> ser to FORWARD
> > > the call to c, not to REDIRECT a to c.
> > > 
> > 
> > The issue is that A has no choice to be forwarded or not. 
> When a 302 is
> > received by A, there is no option for A to continue or 
> reject the call. In
> > this example, B (an IP phone) sets his phone forwarding to 
> C which is a long
> > distance number. A is from PSTN. When A makes a call to B, 
> B sends 302 to
> > the PSTN gateway. The gateway forwards the call to ser 
> which routes it back
> > to C via the PSTN gatway. So in ser's call log, I see a 
> call from A to C.
> > Apparently I can't charge A or C. Only B is in my domain. 
> But B is not even
> > in the second call log. In my understanding, if B sets the 
> forward setting
> > on his phone to a toll number, he should be the one paying the bill.
> > 
> > This also applies even if A is in my domain.
> > 
> > Cheers,
> > Richard
> > 
> > 
> > _______________________________________________
> > Serusers mailing list
> > serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
> > 
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>