|
Hi,
I need some expert advise on how to properly tear
down transactions in the case of an H323 to SIP proxy. H323,
being TCP based has very short tolerance for inactivity as compared to
SIP. Given the example of an H323 originated call proxied to SIP, the H323
session would have already torn down the connection if SIP connection wasn't
able to receive a 1xx response from remote long before all the timers for the
INVITE transaction has expired. Given this scenario, we would have
destroyed the proxy session and left ghost transactions in the FSM continuosly
firing retransmit timers. If, at the last set of timers, we
got a response, what would be the proper behavior? It's definitely not a
487 since you cannot respond to response with another response. It should
therefore be an ACK, followed with a BYE? Is it even worth the effort to
code for this NOOP behavior just to comply not to mention that if the SIP end of
the call is a PSTN Gateway, the phone would have rang followed by a fast busy
which would be really annoying? What would be the consequenses if the
transactions are torn down prematurely without having the timers expire
completely in this case?
Joegen
|
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
