[asterisk-bugs] [Asterisk 0014659]: [patch] MWI NOTIFY contains a wrong URI if Asterisk listens to non-standard port (5060)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14659 
====================================================================== 
Reported By:                klaus3000
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   14659
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Target Version:             1.4.28
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-13 06:00 CDT
Last Modified:              2009-06-22 12:08 CDT
====================================================================== 
Summary:                    [patch] MWI NOTIFY contains a wrong URI if Asterisk
listens to non-standard port (5060)
Description: 
Hi! The MWI Message-Account URI does not contain the port - which is wrong
if a non-standard port is used. Attached patch fixes this.
====================================================================== 

---------------------------------------------------------------------- 
 (0106816) dvossel (administrator) - 2009-06-22 12:08
 https://issues.asterisk.org/view.php?id=14659#c106816 
---------------------------------------------------------------------- 
I've spent some time investigating this and it doesn't appear that the URI
in the Message-Account field is meant to be a reachable URI used for
dialing.  It seems to just identify the account the MWI is for.  I could be
wrong, but I see no evidence of this being required in RFC 3842.  

Was this causing any problems for you?  I'm just curious how this came to
your attention. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-22 12:08 dvossel        Note Added: 0106816                          
======================================================================