Displaying 2 results from an estimated 2 matches for "4d61cf9e505d40e905032a18329d61ec".
2006 Mar 15
0
OT: Using Sipsak to reboot a Snom phone < -a nswered my own question
...<CR><LF>
4. Contents of the file:
NOTIFY sip:<peer>@<registrar>;user=phone SIP/2.0
Via: SIP/2.0/UDP <registrar>:5060
From: <sip:unknown@<registrar>>
To: <sip:<peer>@<registrar>>
Contact: <sip:<peer>@<registrar>>
Call-ID: 4d61cf9e505d40e905032a18329d61ec@192-168-1-46 <--this can be
whatever you like. Note the @registrar
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Event: snom-reboot <-- For Snom 2XX models, the event is just "reboot" - for
the 3XX models, this is "snom-reboot"
Content-Length: 0
5. With some fancy bash script...
2006 Mar 15
0
OT: Using Sipsak to reboot a Snom phone
...68.1.46:34767 at 15/3/2006 11:35:29:070 (363 bytes):
NOTIFY sip:8247@192.168.1.46;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.1.46:34767;rport
Via: SIP/2.0/UDP 192.168.1.46:5060
From: <sip:unknown@192.168.1.46>
To: <sip:8247@192.168.1.46>
Contact: <sip:8247@192.168.1.46>
Call-ID: 4d61cf9e505d40e905032a18329d61ec@192-168-1-46
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Event: reboot
Content-Length: 0
----------------------------------------------------------------------------
----
Sent to udp:192.168.1.46:34767 at 15/3/2006 11:35:29:070 (259 bytes):
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 192.168.1.46:34767;rport...