[asterisk-users] Using SIP stack within Asterisk to reboot phones - Possible?

Danny Nicholas danny at debsinc.com
Mon Dec 27 19:39:33 UTC 2010


From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Bruce B
Sent: Monday, December 27, 2010 1:31 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Using SIP stack within Asterisk to reboot
phones - Possible?

 

Thanks Kai-Uwe and everyone else. I have seen all those examples and I am
exploring the sip_notify.conf file now which makes things more clear to me.

 

However, when sending a SIP notify to a phone that is not registered to
Asterisk via it's IP address should I expect to receive a success of fail
packet back or that is not how SIP Notify works?

 

sip notify aastra-check-cfg 192.168.0.5

Sending NOTIFY of type 'aastra-check-cfg' to '192.168.0.5'

 

That is all I see and the phone is not restarted. There might be a few
things different about Aastra phones to get them accept SIP Notifies and I
would like to hear your experience about it and what features and notifies
are available to me as it pretains particulary to Aastra phones.

 

P.S. Are these SIP notifies anything different than simple HTTP get or XML
push and receive or do they require a sip stack or a program like Asterisk
and it's much more complicated than I think? I want to get a simple page
where some phone controls can be done without relying on a heavy program
like Asterisk but again if it get's too complicated I won't mind using
Asterisk for this purpose. Just want to know my options.

 

Thanks again,

 

On Mon, Dec 27, 2010 at 1:59 PM, Kai-Uwe Jensen <kujensen at gmail.com> wrote:

Lots of good info and pointers so far. But do keep in mind that not all
phones will automatically reboot just because you sent it a "check-sync" or
"resync" event with the "sip notify" command.

I vaguely remember that for e.g. the Polycoms some other condition had to be
true: either the phone's config file on the ftp/tftp server had to have a
newer time-stamp than the one that was downloaded during the phone's last
boot, or a config option had to be set to a non-default value to make the
phone reboot unconditionally upon receiving the SIP notify, regardless of
the config file's modification date.

This is just my opinion:

#1 - if you are using sip notify to send a command to an unregistered
"peer", you won't get a result back unless you are in a very verbose/debug
mode.

#2 - they are probably xml push/receives and there are "lighter clients"
than Asterisk out there to accomplish what you want.  Google for
"lightweight SIP server"

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20101227/294fc847/attachment-0001.htm>


More information about the asterisk-users mailing list