i am trying to use entries in sip_notify.conf to set message waiting lights on phones regardless of whether they have voicemail or not… this is so that say a front desk at a hotel can turn on the Message light without having to leave a voicemail for that user…
so i set up entries in my sip_notify.conf as follows
[set-light]
Event=>message-summary
Content-Type=>application/simple-message-summary
Content-Length=>88
Messages-Waiting=>yes
Message-Account=>sip:7002@192.168.1.5
Voice-Message=>1/0 (0/0)
[kill-light]
Event=>message-summary
Content-Type=>application/simple-message-summary
Content-Length=>87
Messages-Waiting=>no
Message-Account=>sip:7002@192.168.1.5
Voice-Message=>0/0 (0/0)to test I can simply go to my asterisk console and type sip notify kill-light 7201 and it should send the proper notify out to the device…
instead what happens is the notify message goes out in the incorrect format…
here is the Correct format when the asterisk notify mechanism automatically sends a notify event such as when a voice message is deleted from a user;s mailbox… this of course as you can see the device parses and likes…
Reliably Transmitting (no NAT) to 192.168.1.50:5060:
NOTIFY sip:7201@192.168.1.50:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5:5060;branch=z9hG4bK767e224c;rport
From: "asterisk" <sip:asterisk@192.168.1.5>;tag=as1243ad0c
To: <sip:7201@192.168.1.50:5060;transport=UDP>
Contact: <sip:asterisk@192.168.1.5>
Call-ID: 4b8caceb28c08b4937802f1f046f7040@192.168.1.5
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 87
Messages-Waiting: no
Message-Account: sip:7002@192.168.1.5
Voice-Message: 0/0 (0/0)
---
<--- SIP read from 192.168.1.50:5060 --->
SIP/2.0 200 OK
From: "asterisk"<sip:asterisk@192.168.1.5>;tag=as1243ad0c
To: <sip:7201@192.168.1.50:5060>;tag=2b52938-0-13c4-15631-287e0b19-15631
Call-ID: 4b8caceb28c08b4937802f1f046f7040@192.168.1.5
CSeq: 102 NOTIFY
Via: SIP/2.0/UDP 192.168.1.5:5060;rport=5060;branch=z9hG4bK767e224c
Supported: 100rel,replaces
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/A1.04.00.E
Content-Length: 0
<------------->
--- (10 headers 0 lines) ---
Really destroying SIP dialog '4b8caceb28c08b4937802f1f046f7040@192.168.1.5' Method: NOTIFY
hosted1*CLI>Now here is the notify message generated when I use the asterisk console to send the message created in my sip_notify.conf file
Sending NOTIFY of type 'kill-light' to '7201'
Transmitting (no NAT) to 192.168.1.50:5060:
NOTIFY sip:7201@192.168.1.50:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5:5060;branch=z9hG4bK401f27ab;rport
From: "asterisk" <sip:asterisk@192.168.1.5>;tag=as678429e7
To: <sip:7201@192.168.1.50:5060;transport=UDP>
Contact: <sip:asterisk@192.168.1.5>
Call-ID: 36e50c6b66b5a9d421f1bdbb27c1e291@192.168.1.5
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Max-Forwards: 70
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 87
Messages-Waiting: no
Message-Account: sip:7002@192.168.1.5
Voice-Message: 0/0 (0/0)
---
Scheduling destruction of SIP dialog '10f26ae941745d44449ab1ed128f94cf@192.168.1.5' in 32000 ms (Method: NOTIFY)
hosted1*CLI>
<--- SIP read from 192.168.1.50:5060 --->
SIP/2.0 503 Service Unavailable
From: "asterisk"<sip:asterisk@192.168.1.5>;tag=as678429e7
To: <sip:7201@192.168.1.50:5060>;tag=2b52b00-0-13c4-156b4-303a26f6-156b4
Call-ID: 36e50c6b66b5a9d421f1bdbb27c1e291@192.168.1.5
CSeq: 102 NOTIFY
Via: SIP/2.0/UDP 192.168.1.5:5060;rport=5060;branch=z9hG4bK401f27ab
Supported: 100rel,replaces
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/A1.04.00.E
Content-Length: 0
<------------->
--- (10 headers 0 lines) ---
hosted1*CLI>looks real similar except there is no blank line underneath the Content-length field… so my guess is that my device is choking on this as it appears the device doesnt recognize the syntax… at least thats some of the debug coming back from my Adtran 924… as it puts in its debug output that it thinks the content-length is zero so in my opinion it is not liking the missing blank line…
is this an asterisk bug that I should submit? or is there a way to get that blank line in my sip_notify.conf file so it can be sent to the device as part of the notify packet…??..??
I am running Asterisk version 1.4.27
-Christopher