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

Sun Jan 20 04:33:21 CST 2013

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

Walter Doekes commented on ASTERISK-20902:
------------------------------------------

Does anyone else notice that the AGI "end" has no timely equivalent:

{noformat}
[Jan 14 08:59:45] DEBUG[5183] chan_sip.c:  Header  0 [ 58]: INVITE sip:0000003 at xx.xx.46.25:5070;transport=udp SIP/2.0
[Jan 14 08:59:45] DEBUG[5183] chan_sip.c:  Header  6 [ 36]: Call-ID: 69ee90ac-1b46636 at 10.0.0.214
...
[Jan 14 08:59:46] DEBUG[7537] chan_sip.c:  Header  0 [ 44]: INVITE sip:0000003 at xx.xx.46.25:5060 SIP/2.0
[Jan 14 08:59:46] DEBUG[7537] chan_sip.c:  Header  6 [ 59]: Call-ID: 768af463211d72c301aa3c0270a1bd70 at xx.xx.46.25:5070
...
[Jan 14 08:59:49] DEBUG[5183] chan_sip.c:  Header  0 [ 14]: SIP/2.0 200 OK
...
[Jan 14 08:59:49] VERBOSE[7537] res_agi.c:        > agi://127.0.0.1/answered?screen=0&puniqueid=1358153985.13474&pcallid=&snumber=: AGI starting at Mon Jan 14 08:59:49 2013 (1358153989)
...
[Jan 14 08:59:49] VERBOSE[7537] res_agi.c:     -- <SIP/xx.xx.46.25:5060-0000170d>AGI Script agi://127.0.0.1/answered?screen=0&puniqueid=1358153985.13474&pcallid=&snumber= completed, returning 0
[Jan 14 08:59:49] VERBOSE[7537] res_agi.c: <SIP/xx.xx.46.25:5060-0000170d>AGI Tx >> HANGUP
...
[Jan 14 08:59:49] DEBUG[7514] chan_sip.c: Trying to put 'SIP/2.0 200' onto UDP socket destined for xx.xx.46.25:5060
{noformat}

In non-working, it's at:

{noformat}
[Jan 14 09:03:47] DEBUG[5183] chan_sip.c:  Header  0 [ 58]: INVITE sip:0000003 at xx.xx.46.25:5070;transport=udp SIP/2.0
[Jan 14 09:03:47] DEBUG[5183] chan_sip.c:  Header  6 [ 37]: Call-ID: 472ee090-fe2c15f1 at 10.0.0.214
...
[Jan 14 09:03:47] DEBUG[9558] chan_sip.c:  Header  0 [ 44]: INVITE sip:0000003 at xx.xx.46.25:5060 SIP/2.0
[Jan 14 09:03:47] DEBUG[9558] chan_sip.c:  Header  6 [ 59]: Call-ID: 73d4569b2b7b918136a3bb4e55316db9 at xx.xx.46.25:5070
...
[Jan 14 09:03:49] DEBUG[5183] chan_sip.c:  Header  0 [ 14]: SIP/2.0 200 OK
...
[Jan 14 09:03:49] VERBOSE[9558] res_agi.c:        > agi://127.0.0.1/answered?screen=0&puniqueid=1358154227.13485&pcallid=&snumber=: AGI starting at Mon Jan 14 09:03:49 2013 (1358154229)
...
[Jan 14 09:03:54] DEBUG[9558] res_agi.c: SIP/xx.xx.46.25:5060-00001714 hungup
[Jan 14 09:03:54] VERBOSE[9558] res_agi.c: <SIP/xx.xx.46.25:5060-00001714>AGI Tx >> HANGUP
...
[Jan 14 09:03:56] DEBUG[5183] chan_sip.c:  Header  0 [ 58]: CANCEL sip:0000003 at xx.xx.46.25:5070;transport=udp SIP/2.0
[Jan 14 09:03:56] DEBUG[5183] chan_sip.c:  Header  3 [ 37]: Call-ID: 472ee090-fe2c15f1 at 10.0.0.214
{noformat}

> 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