[Rtcomm] [Rtcomm] [Bug 4014] bad SIP behavior in certain network topology
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Wed May 20 16:08:08 EEST 2009
- Previous message: [Rtcomm] [Bug 2817] XMPP contacts not updating presence after network switch
- Next message: [Rtcomm] [Bug 4014] bad SIP behavior in certain network topology
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=4014 ------- Comment #12 from aklapper at openismus.com 2009-05-20 16:08 GMT+3 ------- (In reply to comment #9) > Thanks. You're right, it doesn't change anything. The client does not get any > responses to its requests after the successful REGISTER, and the incoming > NOTIFY responded with 405 Method Not Allowed (which shouldn't be the problem > because it isn't in other networks). I wonder if it should cause connection > errors to be reported by the stack, so that the user is aware of problems. > > We should consider STUNning the binding, maybe as an option. So what options do we have here? Is this an enhancement request to provide better error messages? Is this a WONTFIX? Is this a real bug that is also still valid in Fremantle? -- Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email Replies to this email are NOT read, instead please add comments at https://bugs.maemo.org/show_bug.cgi?id=4014 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
- Previous message: [Rtcomm] [Bug 2817] XMPP contacts not updating presence after network switch
- Next message: [Rtcomm] [Bug 4014] bad SIP behavior in certain network topology
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]