(1) Short problem description:


No way to turn off message light.

(2) Longer problem description (what happens):

If you acquire a used phone with the message light enabled, and connect it to a SIP system with no VoiceMail there is no built-in way to acknowledge/disable the message light.

(3) Possible solution (what did you expect):

Some command in the administrative or telnet interface to do this.

(4) How to reproduce (if possible / applicable):

Hook a phone to a system with VoiceMail and leave a message on the phone line. Then move the phone to a different system without voicemail, perhaps even reconfiguring it. The VoiceMail indicator is always present.

(5) Workaround used currently (if applicable):

Perl script Martin Levy wrote

Here is a perl script. It can be used as follows...
./sip_message 1 ; turns on the message led
./sip_message 0 ; turns off the led
Please change the X.X.X.X to be the IP of your phone and Y.Y.Y.Y to be the IP of the box running the perl code. Also change the sip phone number. (Hey... what do you want for a five minute hack).
And yes... if you know someone's SIP phone IP address you can have a lot of fun with this code. :-) In fact if I had known Richard's IP address I could have turned off the LED for him. :-)
Martin
------------------------
#!/usr/bin/perl

use Socket;

#
# message_sip_phone ip_address_of_phone, ip_address_of_server, phone_number
#
#
sub message_sip_phone {
  my $phone_ip = shift;
  my $local_ip = shift;
  my $sip_phone_number = shift;
  my $sip_message_state = shift;
  my $sip_from, $tm, $call_id, $MESG, $port;
  my $yes_or_no;

  $sip_from = "0";
  $tm = time();
  $call_id = $tm ."msgto$sip_phone_number";
  $port = 5060;
  $yes_or_no = $sip_message_state ? "yes" : "no ";

  my $MESG="NOTIFY sip:$sip_phone_number\@$phone_ip:$port SIP/2.0
Via: SIP/2.0/UDP $local_ip
From: <sip:$sip_from\@$local_ip>
To: <sip:$sip_phone_number\@$phone_ip>
Date: Thu, 10 Apr 2003 21:26:53 -0000
Call-ID: $call_id\@$local_ip
CSeq: 5 NOTIFY
Contact: <sip:$sip_from\@$local_ip>
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Content-Length: 87
Messages-Waiting: $yes_or_no
Message-Account: sip:$sip_phone_number\@$phone_ip
Voice-Message: 0/0 (0/0)
";

  $proto = getprotobyname('udp');
  socket(SOCKET, PF_INET, SOCK_DGRAM, $proto) || warn "socket $!\n";

  ## $iaddr = inet_aton("$phone_ip");

  $paddr = sockaddr_in($port, $iaddr);
  bind(SOCKET, $paddr) || warn "bind $!\n";
  $phone_iaddr = inet_aton($phone_ip);
  $phone_paddr = sockaddr_in($port, $phone_iaddr);

  send(SOCKET, $MESG, 0, $phone_paddr) || warn "send $host $!\n";
}
sub main {
  message_sip_phone('X.X.X.X', 'Y.Y.Y.Y', '42*655', $ARGV[0] ? 1 : 0);
}

main();

exit(0);

(7) Would you classify this as:

(D) Missing feature: Ok to deploy with workaround (see 5)

(8) Version:

P0S3-04-3-00.bin

(9) Contact information:

Richard V. Ford <rvf@SPAM.packeteer.com>

(11) Report:

Message-Id: <5.1.0.14.0.20030623161429.03a9f4e0@10.100.99.30>
Date: Mon, 23 Jun 2003 16:24:56 -0700