Skip to content
Snippets Groups Projects
  • Mike Bradeen's avatar
    58636a6e
    res_pjsip: Upgraded bundled pjsip to 2.13 · 58636a6e
    Mike Bradeen authored
    Removed multiple patches.
    
    Code chages in res_pjsip_pubsub due to changes in evsub.
    
    Pjsip now calls on_evsub_state() before on_rx_refresh(),
    so the sub tree deletion that used to take place in
    on_evsub_state() now must take place in on_rx_refresh().
    
    Additionally, pjsip now requires that you send the NOTIFY
    from within on_rx_refresh(), otherwise it will assert
    when going to send the 200 OK. The idea is that it will
    look for this NOTIFY and cache it until after sending the
    response in order to deal with the self-imposed message
    mis-order. Asterisk previously dealt with this by pushing
    the NOTIFY in on_rx_refresh(), but pjsip now forces us
    to use it's method.
    
    Changes were required to configure in order to detect
    which way pjsip handles this as the two are not
    compatible for the reasons mentioned above.
    
    A corresponding change in testsuite is required in order
    to deal with the small interal timing changes caused by
    moving the NOTIFY send.
    
    ASTERISK-30325
    
    Change-Id: I50b00cac89d950d3511d7b250a1c641965d9fe7f
    58636a6e
    History
    res_pjsip: Upgraded bundled pjsip to 2.13
    Mike Bradeen authored
    Removed multiple patches.
    
    Code chages in res_pjsip_pubsub due to changes in evsub.
    
    Pjsip now calls on_evsub_state() before on_rx_refresh(),
    so the sub tree deletion that used to take place in
    on_evsub_state() now must take place in on_rx_refresh().
    
    Additionally, pjsip now requires that you send the NOTIFY
    from within on_rx_refresh(), otherwise it will assert
    when going to send the 200 OK. The idea is that it will
    look for this NOTIFY and cache it until after sending the
    response in order to deal with the self-imposed message
    mis-order. Asterisk previously dealt with this by pushing
    the NOTIFY in on_rx_refresh(), but pjsip now forces us
    to use it's method.
    
    Changes were required to configure in order to detect
    which way pjsip handles this as the two are not
    compatible for the reasons mentioned above.
    
    A corresponding change in testsuite is required in order
    to deal with the small interal timing changes caused by
    moving the NOTIFY send.
    
    ASTERISK-30325
    
    Change-Id: I50b00cac89d950d3511d7b250a1c641965d9fe7f