I have a custom sip reboot message I am transmitting to a Snom 200 to reboot it. The Snom gets it, it says "200 OK" but it doesn't reboot. I have turned off the challenge-reboot option in the Snom. When I modify the "Event:" directive from "reboot" to "snom-reboot" the phone yields "Bad Event" and when it is just "reboot" the phone responds with 200 OK, so I know it is parsing the event properly. Here is a sip trace:
Received from udp:192.168.1.46:34767 at 15/3/2006 11:35:29:070 (363 bytes): NOTIFY sip:[EMAIL PROTECTED];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:[EMAIL PROTECTED]> To: <sip:[EMAIL PROTECTED]> Contact: <sip:[EMAIL PROTECTED]> Call-ID: [EMAIL PROTECTED] 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=34767 Via: SIP/2.0/UDP 192.168.1.46:5060 From: <sip:[EMAIL PROTECTED]> To: <sip:[EMAIL PROTECTED]> Call-ID: [EMAIL PROTECTED] CSeq: 102 NOTIFY Content-Length: 0 Anyone have an idea? Christian? _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
