[asterisk-bugs] [JIRA] (ASTERISK-20902) Asterisk does not send 200 OK to caller after receiving 200 OK from callee

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-20902:
-----------------------------------------

{quote}
If we give one of your engineers access to the production server while the scenario is being repeated would that be helpful?
{quote}

Not really, that would likely consume significant time for an Engineer who already has more defined core supported issues allocated to them. We have a multitude of issues already in progress. Any community developer is of course free to help you out.

I'd follow Walter and Michael's suggestions for now.
                
> Asterisk does not send 200 OK to caller after receiving 200 OK from callee
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-20902
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20902
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/PBX
>    Affects Versions: 1.8.11.1
>         Environment: Ubuntu 10.10
>            Reporter: David Cunningham
>            Assignee: Rusty Newton
>         Attachments: 0000004-0000003-notworking.txt, 0000004-0000003-working.txt, notworking_2013-01-14.txt, sip.conf, working_2013-01-14.txt
>
>
> Three phones on one network: 0000001, 0000003, and 0000004.
> When phone 0000001 is NOT plugged in, and 0000004 calls 0000003, when 0000003 answers Asterisk does NOT send a 200 OK to 0000004.
> When phone 0000001 IS plugged in, under the same call scenario and with no other changes, when 0000003 answers Asterisk DOES send a 200 OK to 0000004.
> Bizarre I know. Traces of both working and not working scenarios attached. Happens on both 1.8.11.1 and 1.8.7.1. Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira