I do not think such a thing is needed.
I will also note that there is no such header on an IETF standards track.
SIP already defines ways to correlate requests into transactions, calls, and
call-legs. I see no reason for the definition of additional fields to convey
exactly the same information.
-Jonathan R.
---
Jonathan D. Rosenberg 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PHONE: (973) 952-5000
http://www.dynamicsoft.com
> -----Original Message-----
> From: Krishna Sai [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 24, 2001 1:07 PM
> To: Jonathan Rosenberg; Takumi Ohba; [EMAIL PROTECTED]
> Subject: Re: [RE: [Sip-implementors] billing information]
>
>
> I think the DCS architecture defines a billing ID, other than
> the sip Call ID
> for correlating billing records.
>
> -- Krishna Sai
>
> > > -----Original Message-----
> > > From: Takumi Ohba [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, April 12, 2001 6:44 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: [Sip-implementors] billing information
> > >
> > >
> > > Hi,
> > >
> > > How can SIP carry billing information, such as
> > > origination/destination area
> > > information, origination/transit/destination network provider
> > > identification, or charging rate?
> >
> > In networks, you bill for services. Thus, you need to be
> able to obtain
> > information from your systems (gateways and proxies) on the services
> > provided. For VoIP gateway services, the aspects of the
> service provided
> > include dialed number, calling party number, minutes for
> the call, packets
> > sent, etc. All of this information is known to the
> gateways. Some of it,
> > such as the caller and callee identity, are carried in the
> SIP messages.
> > Call duration is determined by the gateway. Information
> such as "charging
> > rate" is not part of the service provided. This information
> is known to the
> > provider, and would be used to generate the final bill,
> based on the call
> > detail information.
> >
> > As a result, there are no extra headers or fields defined
> to carry billing
> > information for SIP. Headers have been defined to carry
> authorization
> tokens
> > for calls. See:
> >
> >
http://search.ietf.org/internet-drafts/draft-johnston-sip-osp-token-01.txt
>
> but that is not billing information.
>
> -Jonathan R.
> ---
> Jonathan D. Rosenberg 72 Eagle Rock Ave.
> Chief Scientist First Floor
> dynamicsoft East Hanover, NJ 07936
> [EMAIL PROTECTED] FAX: (973) 952-5050
> http://www.jdrosen.net PHONE: (973) 952-5000
> http://www.dynamicsoft.com
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
