[asterisk-bugs] [JIRA] (ASTERISK-22071) 11.4 (as opposed to 11.2.1) sends OK to BYE to ip address different from the one in first Via
Michael L. Young (JIRA)
noreply at issues.asterisk.org
Mon Jul 15 09:30:03 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-22071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207966#comment-207966 ]
Michael L. Young edited comment on ASTERISK-22071 at 7/15/13 9:29 AM:
----------------------------------------------------------------------
Alex,
Can you double check your sip.conf settings in regards to nat in the [general] context? Perhaps you can attach a sanitized version of the sip.conf settings (not sure if the one you attached in the first attachment was the entire file or not). Right now, not sure what can be triggering the following observation.
{quote}
Record off feature: automon
Force rport: Auto (No)
DTMF: rfc2833
{quote}
If you have nat=no in the [general] context, Force rport should be set to plain "No", not Auto (No). Auto is the default setting when nothing is specified in the [general] section.
To double check this, I set nat=no on a machine running the latest code and it appears to be functioning properly.
Please check that setting and report back. Based on the debug trace of the call in the file [^issue_22071_gen], nat is being turned on because Force rport is set to Auto or at least Asterisk thinks that is the setting you want for some reason.
_edit_: Just thought of something. Can you check "sip show settings" before make a call to the outbound proxy, after freshly reloading sip.conf or starting Asterisk for the first time? Then check "sip show settings" after making the call? I want to make sure that something is not changing the default setting when making an outbound call through the proxy.
Thanks
was (Author: elguero):
Alex,
Can you double check your sip.conf settings in regards to nat in the [general] context? Perhaps you can attach a sanitized version of the sip.conf settings (not sure if the one you attached in the first attachment was the entire file or not). Right now, not sure what can be triggering the following observation.
{quote}
Record off feature: automon
Force rport: Auto (No)
DTMF: rfc2833
{quote}
If you have nat=no in the [general] context, Force rport should be set to plain "No", not Auto (No). Auto is the default setting when nothing is specified in the [general] section.
To double check this, I set nat=no on a machine running the latest code and it appears to be functioning properly.
Please check that setting and report back. Based on the debug trace of the call in the file [^issue_22071_gen], nat is being turned on because Force rport is set to Auto or at least Asterisk thinks that is the setting you want for some reason.
Thanks
> 11.4 (as opposed to 11.2.1) sends OK to BYE to ip address different from the one in first Via
> ---------------------------------------------------------------------------------------------
>
> Key: ASTERISK-22071
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22071
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/General
> Affects Versions: 11.4.0
> Environment: CentOS 6.4
> Reporter: Alex Zarubin
> Assignee: Alex Zarubin
> Attachments: AsteriskJira22071.txt, issue_22071_gen, issue_22071_sipsettings
>
>
> The same exact sip call works in 11.2.1 and fails in 11.4. Outbound call is established normally via proxy. BYE comes from proxy with <proxy ip/port> in first Via header. 11.4 adds received=<carrier ip/port> and sends OK there. BYE is repeated several times.
> Will try to attach sip.conf and trace once this jira issue is created. Thank you.
--
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
More information about the asterisk-bugs
mailing list