[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:43 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0106818) klaus3000 (reporter) - 2009-06-22 12:43
 https://issues.asterisk.org/view.php?id=14659#c106818 
---------------------------------------------------------------------- 
Good point!

Yes, I had problems. SNOM uses this URI when the user presses the
Voicemail button.

Regarding the RFC: I think it depends on the setup. For example,
sip:user at domain and sip:user at domain:1234;transport=tcp are both valid SIP
accounts. If domain is resolved (by using NAPTR/SRV records) to port 1234
and TCP, probably there are routed identically, but from an external points
of view they address to different SIP accounts.

So, if an Asterisk setup uses NAPTR/SRV there is no need to include the
port/transport. But if NAPTR/SRV are not used, it is necessary to specify
port and transport manually.

> ... It seems to just identify the account the MWI is for...

I think this is correct - but the account can have port/transport.

If there are NAPTRs/SRVs, the SIP AoR would be "sip:user at domain". If there
are no NAPTRs/SRVs, the SIP AoR would be
"sip:user at domain:port;transport=...".

Now there is the problem: How should Asterisk now if there are NAPTRs/SRVs
which point to the non-standard port? Maybe a sip.conf option is needed to
tell Asterisk that the port/transport is part of the SIP AoR (the
Message-Account). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-22 12:43 klaus3000      Note Added: 0106818                          
======================================================================