[Sipping] Re: Questions on draft-jennings-sipping-pay-00

Good points - inline ...

On 7/15/04 3:01 AM, "Elwell, John" <john.elwell@siemens.com> wrote:

> Cullen, 
> 
> 1. I see nothing to indicate what happens if the called user is busy, switched
> off, etc. at the time the request with receipt arrives. This might be a
> particular problem for the case where the UAS is a PSTN gateway, since it
> probably won't check on the availability of the destination user before
> sending the 402, so if the party is not available or busy it will probably
> still be not available or busy when the request with receipt arrives.
>

yes - this is a somewhat fundamental limitation of the whole system. It
somewhat assumes that if you pay, you will at least go to voicemail. Even if
the proxy found out if the UA was online, there is no  way to know if the
user will answer, or if they do answer, will they instantly hangup.

> Trying later would help in some circumstances, but the draft suggests a window
> of only 30s between payment and accepting the request. Also the caller may not
> be interested later.
> 
> 2. It talks about a proxy in the same domain as the UAS performing UAS
> behaviour, but what about a proxy in the same domain as the UAC performing UAC
> behaviour? For example, a proxy in an enterprise may wish to  make payments on
> behalf of its users.
> 

Yes - I would like to make this work. I think is the next rev, perhaps, I
will move the transfer of the receipt to a header to make this possible.
Originally I was concerned about the consent aspects of this but as I looked
at how the OSP Token worked and a few other things, I suspect we can make
this work fine such that the outbound proxy for the UAC can make the payment
on the UAC's behalf.

> John Elwell (john.elwell@siemens.com)
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP