I think the problem here is that if you accept the call and then you play the announcement
the call will be billed.
Regards Diego B
Dale Worley wrote:
From: David Benoit
I've looked in RFC 3666 and the best that it has is section
3.4, but that
releases with cause busy. That's unacceptable for the user
experience as
it would cause the user to hear a service announcement
followed by a busy
signal.
It seems to me that the problem is philosophical -- You want to deliver information to the caller, then terminate the call, but you don't want to terminate it with any particular error indication. But that sequence of operations is just a normal call. You should be accepting the call with 200 OK, sending the information, then terminating with BYE.
Or maybe I should say, you appear to have a requirement that the call be rejected, but you seem to be unwilling to use any of the 4xx or 6xx responses to indicate why it is rejected.
Dale
_______________________________________________ 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
