[asterisk-bugs] [JIRA] (ASTERISK-19979) Request URI port inclusion inconsistency during outbound registration

[Olle Johansson (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206094#comment-206094 ] 

Olle Johansson commented on ASTERISK-19979:
-------------------------------------------

Klaus - DId you ever dig deeper into this? Is this bug still around?
                
> Request URI port inclusion inconsistency during outbound registration
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-19979
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19979
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 10.5.0
>            Reporter: klaus3000
>            Severity: Minor
>
> When having an outbound registration, Asterisk has different URIs in the request line and uri parameter (see following trace of outgoing registration): The first REGISTER has the port in the RURI, but not in From and To headers. The second REGISTER does not have the port in RURI anymore, but has the port in the uri parameter in the Authorization header. IMO the URI should be identically everywhere (RURI, From/To, uri-parameter in Authorization header) - with or without port.
> register => u+437206200730102 at app.example.com:5160/incoming
> Reliably Transmitting (NAT) to 11.22.33.184:5160:
> REGISTER sip:app.example.com:5160 SIP/2.0
> Via: SIP/2.0/UDP 83.136.32.165:4343;branch=z9hG4bK409150c7;rport
> Max-Forwards: 70
> From: <sip:u+437206200730102 at app.example.com>;tag=as4655d4cf
> To: <sip:u+437206200730102 at app.example.com>
> Call-ID: 0769691b7cd9040a2df2d4f8613719d9 at 83.136.32.165
> CSeq: 102 REGISTER
> User-Agent: Asterisk PBX 10.5.0
> Expires: 300
> Contact: <sip:incoming at 83.136.32.165:4343>
> Content-Length: 0
> <--- SIP read from UDP:11.22.33.184:5160 --->
> SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 83.136.32.165:4343;branch=z9hG4bK409150c7;received=83.136.32.165;rport=4343
> From: <sip:u+437206200730102 at app.example.com>;tag=as4655d4cf
> To: <sip:u+437206200730102 at app.example.com>;tag=as79170bf9
> Call-ID: 0769691b7cd9040a2df2d4f8613719d9 at 83.136.32.165
> CSeq: 102 REGISTER
> User-Agent: InnoSIP-app
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
> Supported: replaces
> WWW-Authenticate: Digest algorithm=MD5, realm="app.example.com", nonce="29fd3ad6"
> Content-Length: 0
> <------------->
> --- (11 headers 0 lines) ---
> Responding to challenge, registration to domain/host name app.example.com
>        > doing dnsmgr_lookup for 'app.example.com'
>        > ast_get_srv: SRV lookup for '_sip._udp.app.example.com' mapped to host app.example.com, port 5160
> REGISTER 11 headers, 0 lines
> Reliably Transmitting (NAT) to 11.22.33.184:5160:
> REGISTER sip:app.example.com SIP/2.0
> Via: SIP/2.0/UDP 83.136.32.165:4343;branch=z9hG4bK361361b2;rport
> Max-Forwards: 70
> From: <sip:u+437206200730102 at app.example.com>;tag=as6f9408ad
> To: <sip:u+437206200730102 at app.example.com>
> Call-ID: 0769691b7cd9040a2df2d4f8613719d9 at 83.136.32.165
> CSeq: 103 REGISTER
> User-Agent: Asterisk PBX 10.5.0
> Authorization: Digest username="u+437206200730102", realm="app.example.com", algorithm=MD5, uri="sip:app.example.com:5160", nonce="29fd3ad6", response="eba65da0c50796ad257787dff90a1797"
> Expires: 300
> Contact: <sip:incoming at 83.136.32.165:4343>
> Content-Length: 0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira