[asterisk-bugs] [JIRA] (ASTERISK-19502) Wrong port specified on SIP INVITE response when using custom TCP port

Joshua Colp (JIRA) noreply at issues.asterisk.org
Tue Dec 19 06:09:07 CST 2017


     [ https://issues.asterisk.org/jira/browse/ASTERISK-19502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp updated ASTERISK-19502:
-----------------------------------

    Severity: Minor  (was: Major)

> Wrong port specified on SIP INVITE response when using custom TCP port
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-19502
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19502
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/TCP-TLS
>    Affects Versions: 10.1.2, 13.18.4
>         Environment: Ubuntu Server 11.10
>            Reporter: Seth Miller
>            Severity: Minor
>
> After specifying a custom SIP port in sip.conf:
> udpbindaddr=0.0.0.0:8925 
> tcpbindaddr=0.0.0.0:8925
> operation using UDP transport is normal, but when using TCP transport Asterisk specifies the wrong port in the INVITE message, as follows:
> Using UDP (correct response):
> Received:
> 192.168.0.62:4033 <- 125.137.61.10:8925
> [pbx.testserver.com/125.137.61.10:8925; 125.137.61.10:8925]
> 830
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP
> 192.168.0.62:4033;branch=z9hG4bKrEBGe2DJePrhhWsR;received=97.23.74.126;rport=4033
> From: "Tom" <sip:460 at pbx.testserver.com:8925>;tag=F03BD320754F86C854C1EAF1DFC3AED2
> To: <sip:256 at pbx.testserver.com:8925>;tag=as0818278a
> Call-ID: 9590211AA57086D6A948F00DC2B9623F57E9A3DC
> CSeq: 2 INVITE
> Server: Asterisk PBX 10.1.2
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY,
> INFO, PUBLISH
> Supported: replaces, timer
> Contact: <sip:256 at 125.137.61.10:8925>
> Content-Type: application/sdp
> Content-Length: 282
> Using TCP (incorrect response):
> Received:
> 192.168.0.62:65009 <- pbx.testserver.com/125.137.61.10:8925
> [pbx.testserver.com/125.137.61.10:8925; 125.137.61.10:8925]
> 836
> SIP/2.0 200 OK
> Via: SIP/2.0/TCP
> 192.168.0.62:65009;branch=z9hG4bKFuTKuZb8AsoRhbyA;received=97.23.74.126;rport=65009
> From: "Tom" <sip:460 at pbx.testserver.com>;tag=2C9624E0B9A7E5283CA5E362CC7BC594
> To: <sip:256 at pbx.testserver.com>;tag=as5fbd3f8f
> Call-ID: D37F16A22EF49A91B5D828313631B6818310CE89
> CSeq: 2 INVITE
> Server: Asterisk PBX 10.1.2
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY,
> INFO, PUBLISH
> Supported: replaces, timer
> Contact: <sip:256 at 125.137.61.10:5060;transport=TCP>   
> Content-Type: application/sdp
> Content-Length: 280
> Note that in the line 'Contact: <sip:256 at 125.137.61.10:5060;transport=TCP>' the wrong port is specified (5060 instead of 8925).



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list