[asterisk-bugs] [JIRA] Issue Comment Edited: (ASTERISK-17362) Unsolicited SIP notifies cannot be routed to MWI lights on individual phones

[alexr1 (JIRA)]

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

alexr1 edited comment on ASTERISK-17362 at 7/18/12 5:15 AM:
------------------------------------------------------------

Slightly off-topic but related to the above, I've noticed that Asterisk will send a Notify to a phone with "mailbox" parameter set even if it has no subscription (which is great), but Asterisk seems to send a Notify on Register and Invite TWICE if it sends a 401 Unauthorised (All of our peers need to re-authenticate for every call). So each time they make a call it is:

Phone -> Register
Phone <- NOTIFY (MWI)
Phone <- Unauthorised

Phone -> Register (With auth)
Phone <- NOTIFY (MWI)
Phone <- OK (Register OK)

Probably undesirable behaviour, so I thought I'd throw that in for anyone who's clued up enough to do anything with it...

      was (Author: alexr1):
    Slightly off-topic but related to the above, I've noticed that Asterisk will send a Notify to a phone with "mailbox" parameter set even if it has no subscription, but Asterisk seems to send a Notify on Register and Invite - even if when it sends a 401 Unauthorised (All of our peers need to re-authenticate for every call). So each time they make a call it is:

Phone -> Register
Phone <- NOTIFY (MWI)
Phone <- Unauthorised

Phone -> Register (With auth)
Phone <- NOTIFY (MWI)
Phone <- OK (Register OK)

Probably undesirable behaviour, so I thought I'd throw that in for anyone who's clued up enough to do anything with it...
  
> Unsolicited SIP notifies cannot be routed to MWI lights on individual phones
> ----------------------------------------------------------------------------
>
>                 Key: ASTERISK-17362
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17362
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Channels/chan_sip/NewFeature
>            Reporter: Clinton Goudie-Nice
>         Attachments: patch-1.8.7.1-chan_sip-unsolicited-notify-handling.jira-bug-17362.diff.txt, patch-chan_sip-unsolicited_notify_routing.diff.txt, patch-chan_sip-unsolicited_notify_routing.diff.txt, sipsample.txt
>
>
> Currently, the implementation for unsolicited_mailbox routes all inbound unsolicited sip notifies to a single mailbox at the hard coded context SIP_Remote.
> This makes it impossible for 3rd party SIP integrations to light MWI lights on phones attached to Asterisk. This is critical for 3rd party applications such as voicemail and IVR systems (IE: Exchange UM and Callware Callegra) to fully integrate with Asterisk as they can with other PBX systems such as Cisco Unified Communications Manager. 
> For these types of integrations, Asterisk needs the ability to receive unsolicited SIP notifies and route them as MWI lights to the appropriate physical device, within a context defined per trunk. This needs to occur without breaking anyone relying on the current Asterisk functionality of routing all unsolicited sip notifies to a single box.
> The submitted patch handles this as follows:
> If unsolicited_mailbox is unset, unsolicited notifies are not delivered anywhere.
> If unsolicited_mailbox=somebox all unsolicited notifies will be delivered to somebox at SIP_Remote to preserve existing functionality.
> If unsolicited_mailbox=somebox at somecontext all unsolicited notifies will be delivered to somebox at somecontext
> If unsolicited_mailbox=@somecontext the box from the sip notify will be used to deliver the sip notify to the specified box at somecontext.
> The box is specified either through the Message-Account portion of the body, and if unspecified there, the To header, as specified in RFC3842. 
> Additionally, this patch adds debug logging so that an end user can troubleshoot unsolicited sip notify issues by turning on debug logging.
> ****** ADDITIONAL INFORMATION ******
> This issue supersedes issue 18736. Thanks also go to cmaj for his submission of the UM patch and additional guidance as we created this patch.

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