[Rtcomm] [Rtcomm] [Bug 4014] bad SIP behavior in certain network topology
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Tue Feb 17 18:03:42 EET 2009
- Previous message: [Rtcomm] [Bug 4014] bad SIP behavior in certain network topology
- 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 mikhail.zabaluev at nokia.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords|moreinfo | ------- Comment #9 from mikhail.zabaluev at nokia.com 2009-02-17 18:03 GMT+3 ------- (In reply to comment #8) > Created an attachment (id=1125) --> (https://bugs.maemo.org/attachment.cgi?id=1125&action=view) [details] > tcpdump trace > > Try#2 with proxy as IP address and calling sip:17771234567 at callcentric.com 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. -- 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 4014] bad SIP behavior in certain network topology
- Next message: [Rtcomm] [Bug 4014] bad SIP behavior in certain network topology
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]