Here's a bit of a strange questions, but one who's answer eludes me. I have a service that takes SIP calls and interacts with them. Sometimes the service has to interact with calls that have not yet been answered (they are in the equivalent of ALERTING on the ISDN side of things). So, I get the INVITE, I send back a 183 to playback some service announcement and now I want to hang-up on the call as "NORMAL" in the ISDN world. However, since the call has not been answered, I can only send a 3xx-6xx status message to end the call. There are no messages that seem to allow me to do that. In the ISDN world I would simply release with normal as the cause code.
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. Any of the interoperability documents for PSTN gateways (over which I will likely have no control) only release with normal as a result of a CANCEL or BYE. I can't send a CANCEL because I'm the recipient of the call, and I can't send a BYE because I haven't answered the call; nor do I want to. Am I missing something? David -- [EMAIL PROTECTED] | phone: 902-832-2649 fax: 902-832-1015 "Complex problems have simple, neat and wrong solutions" - H. L. Menken _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
