[asterisk-bugs] [JIRA] (ASTERISK-19446) Improvement to MWI (with Teksavvy Tektalk service (Metaswitch Networks equipment)

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-19446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell closed ASTERISK-19446.
------------------------------------

    Resolution: Suspended

Suspending ticket for inactivity.  Feel free to reopen by posting an updated patch and following Code Review instructions \[1\].

\[1\] https://wiki.asterisk.org/wiki/display/AST/Code+Review

> Improvement to MWI (with Teksavvy Tektalk service (Metaswitch Networks equipment)
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19446
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19446
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Channels/chan_sip/Subscriptions
>    Affects Versions: 1.8.10.0
>            Reporter: Daryl Boyd
>         Attachments: mwi_patch
>
>
> (Disclaimer: This is my first patch for asterisk, and I learnt SIP this week to figure this out...)
> When subscribing to MWI the subscription would last for less than 15min after which an unknown dialog error would eventually occur. 
> After some debug, it traced it to the switch sending a NOTIFY with a "Subscription-State: terminated;reason=timeout" line in it. Asterisk did not handle this line, it would think its dialog is still good and try and reuse it. I modified asterisk to handle these requests, by closing the dialog and re-registering.
> I also then got issues with asterisk complaining about bad sequence numbers with NOTIFY packets. Looking in the standards it seems that asterisk is assuming that CSeq numbers for NOTIFY packets must be sequential. My reading shows otherwise, and this switch does not present them in a sequential order. I patched the code to ignore order just for NOTIFY messages. 
> I have a patch that when applied has been running MWI successfully with TekTalk for 2 weeks with no issues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)