[asterisk-bugs] [Asterisk 0017090]: MWI SIP NOTIFY may contain wrong "Via: ..." header, making the phone discard the whole message
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Jul 24 21:58:40 CDT 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=17090
======================================================================
Reported By: rlr2maverick
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17090
Category: Channels/chan_sip/General
Reproducibility: sometimes
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.6.1.18
JIRA: SWP-1168
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-03-24 09:23 CDT
Last Modified: 2010-07-24 21:58 CDT
======================================================================
Summary: MWI SIP NOTIFY may contain wrong "Via: ..." header,
making the phone discard the whole message
Description:
Under some circumstances MWI are not honored by our CP 7945 phones because
of an annoying bug which affects SIP NOTIFY: the udp port is low value in
'Via:' header. By now a quick-dirty approach is to change 0 in 5060 when
the port is 0 ... and it does work with our phones flashing for new
messages waiting !!!
A missing functionality is a periodic check&MWI for new messages, our
version is emitting MWI in case of chan_sip.so reload only.
I'm investigating ...
======================================================================
----------------------------------------------------------------------
(0124967) pabelanger (manager) - 2010-07-24 21:58
https://issues.asterisk.org/view.php?id=17090#c124967
----------------------------------------------------------------------
Please retest with 1.6.2, if still an issue attach a debug log (see
below).
---
We require a complete debug log to help triage the issue.
This document will provide instructions on how to collect debugging logs
from an Asterisk machine for the purpose of helping bug marshals
troubleshoot an issue:
http://svn.digium.com/svn/asterisk/trunk/doc/HOWTO_collect_debug_information.txt
Issue History
Date Modified Username Field Change
======================================================================
2010-07-24 21:58 pabelanger Note Added: 0124967
2010-07-24 21:58 pabelanger Status acknowledged =>
feedback
======================================================================
More information about the asterisk-bugs
mailing list