Telephone Service

telephony-service
load 7960-7940 P00305000301
load 7902 CP7902010200SCCP031023A
max-ephones 124
max-dn 288
ip source-address 192.168.1.1 port 2000
timeouts interdigit 4
timeouts ringing 30
system message What Ever Corporate
url services http://phone-xml.berbee.com/menu.xml
create cnf-files version-stamp 7960 May 27 2004 14:09:20
dialplan-pattern 1 24.. extension-length 4
voicemail 22999
mwi sip-server 192.168.1.2 unsolicited
max-conferences 8
dn-webedit
time-webedit
transfer-system full-consult
after-hours block pattern 1 1900 7-24
after-hours block pattern 2 011 7-24
night-service code *1234
night-service day Sun 09:01 08:59
night-service day Mon 17:00 09:00
night-service day Tue 17:00 09:00
night-service day Wed 17:00 09:00
night-service day Thu 17:00 09:00
night-service day Fri 17:00 09:00
night-service day Sat 09:01 09:00
directory last-name-first

The two items bolded and enlarged is all that is needed to have CME access voice mail on Asterisk and have Asterisk light the Message Waiting Indicator light on the IP Phone.

The command "voicemail 22999" dials 22999 when the message button on the IP Phones is pushed. Dial peer 400 is selected which routes the call to Asterisk VoiceMailmain.

To make the message indicator light work, on the IP Phones, you need to use the unsolicited option with the command "mwi sip-server ..... unsolicited". If you where to use the default setting the lamp will never light. This is because Asterisk does not confirm to section 3.3.4 of RFC 3265.

What Asterisk does to implement the RFC wrong is when the CME sends a Subscribe message to the Asterisk which then replies with a Notify but with a different call ID. Thus causing the CME to send a 481 "Call Leg/Transaction Does Not Exist" to Asterisk which fails to light the indicator lamp on the IP Phone.

To see the trap click here

See sip.conf for how to set up Asterisk.