Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

This applies to Sangoma D-series, P310, and P315 model phones.

Remote Restart

Digium Sangoma phones will, typically, automatically restart themselves whenever they receive a configuration parameter that necessitates a full restart.

Otherwise, Digium Sangoma phones, beginning with firmware 1.1.0, may be remotely notified to restart by using a check-sync SIP NOTIFY Event sent from the Asterisk CLI. This feature is enabled by default and is controlled by the:

...

Older versions of Asterisk may not have a properly configured pjsipsip_notify.conf file to allow sending the restart notices from the Asterisk CLI. To enable this functionality, add the following lines to pjsip_notify.conf if they are not already present:

...

Following an Asterisk reload or restart, Digium Sangoma phones may then be remotely sent restart notices by executing the following Asterisk CLI command:

No Format
pjsip send notify digium-check-cfg <my endpoint identifier, e.g. 1000>

Remote Reconfigure

Digium Sangoma phones, when connected to DPMA, can be remotely reconfigured using the Asterisk CLI command:

No Format
digium_phones reconfigure phone <my endpoint identifier, e.g. 1000>

Or using by using the the DigiumPhoneReconfigure AMI Action.

If phones are not connected to DPMA, they can be reconfigured, as opposed to restarted, beginning with firmware 2.3.0, by issuing a new notify command.

Most Some versions of Asterisk will may not have a properly configured sippjsip_notify.conf file to allow sending the reconfigure notices from the Asterisk CLI. To enable this functionality, add the following lines to pjsip_notify.conf if they are not already present:

...

Like the other check-sync Event, this command depends on the phone's enable_check_sync setting being enabled.

...

Following an Asterisk reload or restart, Digium Sangoma phones may then be remotely sent reconfigure notices by executing the following Asterisk CLI command:

...

No Format
pjsip send notify digium-check-reconfig <my endpoint identifier, e.g. 1000>

 

Performing Remote Restart or Reconfigure outside of Asterisk

 

The SIPp test tool can be used with the following scenario file:

 

Expand
titleSIPp Reconfigure checksync.xml
No Format
<?xml version="1.0" ?>
<scenario name="Reconfigure">
 <send>
  <![CDATA[
    NOTIFY sip:[service]@[remote_ip]:[remote_port];ob SIP/2.0
    Via: SIP/2.0/UDP [local_ip]:[local_port];branch=[branch];rport
    Max-Forwards: 70
    From: "asterisk" <sip:asterisk@[local_ip]>;tag=[call_number]
    To: <sip:[service]@[remote_ip]:[remote_port];ob>
    Contact: <sip:asterisk@[local_ip]:[local_port]>
    Call-ID: [call_id]@[local_ip]:[local_port]
    CSeq: 102 NOTIFY
    User-Agent: Asterisk PBX SVN-branch-11-r377355
    Date: Mon, 10 Dec 2012 16:23:50 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
    Supported: replaces, timer
    Subscription-State: terminated
    Event: check-sync
    Content-Length: 0
  ]]>
</send>
</scenario>

 

to programmatically restart Digium Sangoma phones like:

 

./sipp 10.24.19.95 -sf checksync.xml -m 1

 

where 10.24.19.95 represents the IP address of the Digium phone to be restarted.

 

This is also possible using other tools, such as sipsak with the following file:

 

Expand
titlesipsak reboot.phone restart example file
No Format
NOTIFY sip:10.1.2.3 SIP/2.0
To: sip:10.1.2.3
From: sip:asterisk@10.1.2.3
CSeq: 10 NOTIFY
Call-ID: 1234@10.1.2.3
Event: check-sync

 

as executed like:

./sipsak -f reboot.phone -s sip:101@10.1.2.3

...