[asterisk-bugs] [JIRA] Commented: (ASTERISK-17340) [patch] Out-of-dialog MWI from a SIP Trunk in asterisk 1.8.2.2 always responds with 489 Bad event

[Clinton Goudie-Nice (JIRA)]

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

Clinton Goudie-Nice commented on ASTERISK-17340:
------------------------------------------------

If you're visiting this issue, you should go to the updated issue here: https://issues.asterisk.org/jira/browse/ASTERISK-17362

> [patch] Out-of-dialog MWI from a SIP Trunk in asterisk 1.8.2.2 always responds with 489 Bad event
> -------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-17340
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17340
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_sip/Interoperability
>            Reporter: Clinton Goudie-Nice
>         Attachments: patch-chan_sip-1.8.2.2-unsolicited_notify_routing-2.diff.txt, patch-chan_sip-1.8.2.2-unsolicited_notify_routing.diff.txt, patch-chan_sip-1.8.2.3-unsolicited_notify_yes_sir.diff.txt, sipsample.txt
>
>
> Issue 13028 is said to have fixed this issue, however in 1.8 when I send an out-of-dialog notify, I only receive 489 Bad event
> Here is an example of the sip notify and response from wireshark: (.23 is the Asterisk server. .47 is the host sending the sip notify)
> ---- From host sending sip notify ----
> NOTIFY sip:5820 at 10.16.0.23 SIP/2.0
> From: "Anonymous"<sip:Anonymous at 10.16.0.47:5065>;tag=beeafd8-0-13c9-50022-ffdc7-52327663-ffdc7
> To: <sip:5820 at 10.16.0.23:5060>
> Call-ID: beeafd8-0-13c9-50022-ffdc7-4db95f02-ffdc7
> CSeq: 1 NOTIFY
> Via: SIP/2.0/UDP 10.16.0.47:5065;branch=z9hG4bK-ffdc7-3e7753f9-3403d179
> Max-Forwards: 70
> Supported: replaces
> Contact: <sip:Anonymous at 10.16.0.47>
> Event: message-summary
> Content-Type: application/simple-message-summary
> Content-Length: 47
> Messages-Waiting:yes
> Voice Message: 1/0 (0/0).
> ---- Response from Asterisk server ----
> SIP/2.0 489 Bad event
> Via: SIP/2.0/UDP 10.16.0.47:5065;branch=z9hG4bK-ffdc7-3e7753f9-3403d179;received=10.16.0.47
> From: "Anonymous"<sip:Anonymous at 10.16.0.47:5065>;tag=beeafd8-0-13c9-50022-ffdc7-52327663-ffdc7
> To: <sip:5820 at 10.16.0.23:5060>;tag=as56d33dc9
> Call-ID: beeafd8-0-13c9-50022-ffdc7-4db95f02-ffdc7
> CSeq: 1 NOTIFY
> Server: FPBX-2.8.1(1.8.2.2)
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
> Supported: replaces, timer
> Content-Length: 0
> --------
> I have a SIP phone (grandstream) on extension 5820, and if I leave a voice mail message with asterisk for that phone, it does activate the MWI light. 
> In doing some additional debugging, I see the code path headed through (around line 20539) if(!p->mwi). it then searches for a peer on around 20541 and doesn't find one.
> Additionally, the line char *c = ast_strdupa(get_body(req, "Voice-Message", ':'));  doesn't appear to place any text into c as a result of these two packets.
> My sip trunk's inbound is context=from-internal and it's able to dial the extension 5820 fine. My phone's mailbox is 5820 at default 
> We are sending these out of dialog notifies from a SIP auto-attendant/voicemail/ivr system. I can change how these packets look (to an extent), however it's worth noting these packets currently work with cisco call manager.
> ****** ADDITIONAL INFORMATION ******
> https://issues.asterisk.org/view.php?id=13028

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira