Hi all, I have two things to discuss about XX-517: Problem clearing down inbound ITSP call through sipXbridge
1. Polycoms send 603 Decline after a configurable period of time, when an INVITE is not answered or cancelled. Scott, you state that the phone "should _NOT_ send a 603 response _ever_." The problem I think is that the phone does not know that no other end point will answer the request? (http://tools.ietf.org/html/rfc3261#section-21.6.2) I can raise an issue with Polycom. We recommend sending 480 Temporarily Unavailable instead? 2. Chaitra noted three different observed behaviours: http://track.sipfoundry.org/browse/XX-517?focusedCommentId=38999&page=co m.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_ 38999 Behaviour #2 is the Polycom's mysterious 400 Bad Request response to the CANCEL. I've alerted Polycom to the new logs Chaitra has provided. Behaviour #1 seems to be the desired sipXbridge behaviour, where it is able to detect and decline the unwanted second INVITE from the ITSP. Behaviour #3 seems to be a issue with sipXbridge, where it was not able to detect that the third INVITE from the ITSP is also unwanted. Can I suggest that a separate JIRA issue be raised for Behaviour #3? Thanks. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
