Hi Brett, Our implementation makes the 180 seconds as default setting and it can be configured at run-time, so it should not be an issue.
Thanks, Yong -----Original Message----- From: Brett Tate [mailto:[EMAIL PROTECTED] Sent: Monday, January 08, 2007 12:14 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [email protected] Subject: RE: [Sip-implementors] SIP question about "INVITE clienttransaction"in RFC3261 > Our implementation currently chooses to include a "Expires" header in > outbound INVITE message with a value of 180 seconds (minimum of Timer > C value) and generate a CANCEL request if no final response is > received once it is expired, any comments? Sounds ok if you really want to limit the time before answer to 180 seconds. Be aware that some customer service and reservation systems send 18x responses while queued waiting to be answered by person. It might take longer than 180 seconds for the call to be answered by person. Thus your users might complain about poor interoperability (dropped calls) concerning calls to such numbers. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
