Asterisk
  1. Asterisk
  2. ASTERISK-3168

[patch] Add a CLI command to send SIP notify to peers (ex:reboot phone)

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Severity: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Target Release Version/s: None
    • Component/s: Core/General
    • Labels:
      None
    • Mantis ID:
      3231
    • Regression:
      No

      Description

      This patch add the posibility to send notify defined in a new sip_notify.conf.
      So can do this :
      sip notify Type PEERNAME

                • ADDITIONAL INFORMATION ******

      This patch was about rebooting SIP phone, but I changed it due to comments about making it more general. The example notify for reboot have being tested on Polycom phone. Please update if it not working, or how to make it working (with other phone type also)

      Disclamed

        Activity

        Hide
        Brian West added a comment -

        contact is wrong.. you have to direct it at a contact on the phone... check the cisco docs.. this could be a small issue to use the FULL contact in that field.

        bkw

        Show
        Brian West added a comment - contact is wrong.. you have to direct it at a contact on the phone... check the cisco docs.. this could be a small issue to use the FULL contact in that field. bkw
        Hide
        Kevin P. Fleming (Inactive) added a comment -

        Hmm, that's strange. It shouldn't be requiring SDP for a NOTIFY message. Then again, according to RFC3265 NOTIFY is not supposed to be sent except as part of a subscription created with SUBSCRIBE anyway, so using it this way is somewhat outside the specs anyway. In spite of that, phone implementors are using it for this function

        Show
        Kevin P. Fleming (Inactive) added a comment - Hmm, that's strange. It shouldn't be requiring SDP for a NOTIFY message. Then again, according to RFC3265 NOTIFY is not supposed to be sent except as part of a subscription created with SUBSCRIBE anyway, so using it this way is somewhat outside the specs anyway. In spite of that, phone implementors are using it for this function
        Hide
        Kevin P. Fleming (Inactive) added a comment -

        Yeah, these packets are not being constructed properly. I've already opened a new bug with a rebuilt version of this, let me try to figure out how to get them built correctly...

        Show
        Kevin P. Fleming (Inactive) added a comment - Yeah, these packets are not being constructed properly. I've already opened a new bug with a rebuilt version of this, let me try to figure out how to get them built correctly...
        Hide
        nick added a comment -

        Let's carry the fun on in 3243 to avoid duplicating efforts...

        Show
        nick added a comment - Let's carry the fun on in 3243 to avoid duplicating efforts...
        Hide
        Digium Subversion added a comment -

        Repository: asterisk
        Revision: 4656

        U trunk/channels/chan_sip.c
        A trunk/configs/sip_notify.conf.sample

        ------------------------------------------------------------------------
        r4656 | markster | 2008-01-15 15:19:43 -0600 (Tue, 15 Jan 2008) | 2 lines

        Allow generic sip notify (bug ASTERISK-3168)

        ------------------------------------------------------------------------

        http://svn.digium.com/view/asterisk?view=rev&revision=4656

        Show
        Digium Subversion added a comment - Repository: asterisk Revision: 4656 U trunk/channels/chan_sip.c A trunk/configs/sip_notify.conf.sample ------------------------------------------------------------------------ r4656 | markster | 2008-01-15 15:19:43 -0600 (Tue, 15 Jan 2008) | 2 lines Allow generic sip notify (bug ASTERISK-3168 ) ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=4656

          People

          • Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development