Summary:ASTERISK-15870: MWI SIP NOTIFY may contain wrong "Via: ..." header, making the phone discard the whole message
Reporter:Roberto La Rosa (rlr2maverick)Labels:
Date Opened:2010-03-24 09:23:38Date Closed:2011-06-07 14:00:36
Versions:Frequency of
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 ...


       /* z9hG4bK is a magic cookie.  See RFC 3261 section */
       snprintf(p->via, sizeof(p->via), "SIP/2.0/%s %s:%d;branch=z9hG4bK%08x%s",
/* ********** */
/* under some circumstances seems the port is not initialized:
* ...
* Via: SIP/2.0/UDP x.x.x.x:0;branch=z9hG4bK5251cc93;rport
* ----------------------> ^^^
* ...
*               ntohs(p->ourip.sin_port), (int) p->branch, rport);
/* ********** */
                ntohs(p->ourip.sin_port) ? ntohs(p->ourip.sin_port) : 5060, (int) p->branch, rport);

/*! \brief NAT fix - decide which IP address to use for Asterisk server?
"channels/chan_sip.c" [readonly] line 3211 of 24880 --12%-- col 1-8
Comments:By: Elazar Broad (ebroad) 2010-03-24 14:28:16

Do you have pollmailboxes set in voicemail.conf?

By: Paul Belanger (pabelanger) 2010-07-24 21:58:40

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:


By: Paul Belanger (pabelanger) 2010-08-04 11:54:19

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines