Vishal wrote:
> Dr Jonathan,
>  As is clear , there is no formal mechanism for "packet based"
> billing.SIP 
> applications assume "call duration " based billing.

Of course that is not true. SIP makes no assumptions about billing. You 
can bill for anything you can account for. Its possible to even account 
for individual packets, so you could conceivably bill for that, but I 
wouldn't advise it. You can't always account for everything in a proxy, 
but in a complete system, as long as something knows about the thing you 
want to account for, you can account for it.


At this point of time
> ,I 
> have following questions in mind: 
> 
> 1. Should it be made mandatory to handle message body in BYE method ? 

The only mandatory body type in bis is SDP.

> 
> 2. Should there be mechanism to choose billing type at the time of user 
> registeration? UA may register one  billing type while SIP registrar
> may send another billing type in 2xx response to register method .
> This will require another header field (say, "billing-type:") 

I don't see why this would ever be negotiated like this.

> 
> 3. Should there be different billing type allowed for audio and video in
> the 
> same call? Is this mechanism required? 

SIP should never say what one can and cannot bill for.


> 
> 4. Can SIP proxy enforce media routing through it? Ofcourse , in this
> case 
> billing record generation will not be required at UA . 

It is possible to design sip networks where media is forced through an 
intermediary, through the use of firewalls. Such configurations depend 
on the SIP provider also owning the IP network. See:

http://www.ietf.org/internet-drafts/draft-ietf-sip-call-auth-06.txt

for an example.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
[EMAIL PROTECTED]                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to