For UAC it is a non-INVITE client transaction and after receiving a 481 response on a matching transaction it should do the below:
1) cancel the E & F timers. Which would stop the retransmission. 2) Move to completed state and create another timer K to handle duplicate 481 responses... You may want to check the 481 response transaction identifiers ( cseq, branch and call-id ) to see if they are correctly populated. Regards, Indresh -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext Daniel Corbe Sent: Thursday, April 05, 2007 12:28 PM To: [email protected] Subject: [Sip-implementors] Question about BYE/481 Hi, I'm seeing the following behavior out of one of my endpoints, Its trying to hang up a call which doesn't exist so the natural thing to do seems to be to send a 481, like so: ---> BYE <-- 481 --> BYE <-- 481 --> BYE <-- 481 --> BYE <-- 481 --> BYE <-- 481 --> BYE <-- 481 --> BYE <-- 481 Always 7 retransmits which would lead be to believe that T2 is expiring on the UAC sending me the BYE packets. I don't think that the UAC is tearing down the call like its supposed to because I am seeing some anomalous behavior out of it. If I'm responding to a BYE with a 481, I wouldn't expect the UAC to retransmit the BYE and I'm of the opinion that the UAC is wrong in this case. I'm just wondering if that's correct or not. -Daniel _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
